Effective requirements; or why user stories and use cases are not enough

With the growth of UML during the late 1990's and early 2000's Use Cases became the most prominent approach for gathering and documenting requirements. Their simplicity enabled easy adoption for many projects. With the advent of Agile development, Use Cases have been largely replaced with the User Stories. Agile evangelists claim User Stories drive the product backlog and that it can be thought of as a replacement for the requirements document.


In this video, Niall Cooling reviews the shortcomings of Use Cases and User Stories in the context of Requirements. He then addresses the need for understanding the hierarchical nature of requirements and intent specification. Finally, he clarifies where Use Cases and Users Stories fit into the gathering and documenting process.

#embedded,#agile,#user stories,#use cases,#requirements,#feabhas,#niall cooling,