From the course: Software Architecture Foundations
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Narrowing: Vertical vs. horizontal splitting
From the course: Software Architecture Foundations
Narrowing: Vertical vs. horizontal splitting
- After creating your user stories, there's typically two steps necessary to refine the stories, since they're often too large. In an agile world, you need to be able to fully implement a story and deploy it to your end users in a couple days, at most. That's the only way you can get the feedback that you need when you need it. Stories out of the gate are rarely small enough. The process of making a story smaller is sometimes called slicing. But that term can be misleading. It might lead you to an anti-pattern called horizontal slicing. When you slice horizontally, the first slice describes the UI only. The second adds business logic, the third adds data persistence. The problem with that thinking is that a story isn't really done until an end user can actually use the implementation to do something useful. Filling out some form that has no business logic under it is not useful. You haven't really made the story smaller by slicing horizontally. What you really want to do is vertical…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.