Effective requirements; or why user stories and use cases are not enough
Thursday 12 September 10am & 3pm BST
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. Subsequently, a significant proportion of these projects failed to make use cases work effectively for them, leading to disillusionment with use cases as a requirements technique. 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. However, Use Cases, User Stories or Product Backlogs are insufficient to fully define requirements for an embedded system.
In this webinar, Niall Cooling will review what is meant by a requirement, addressing stakeholder, derived and regulatory requirements. We will discuss why it is impossible to define all of a system's possible requirements at a project outset. Finally it will clarify where Use Cases and Users Stories fit into the gathering and documenting process.
There will also be time for questions. If you'd like to submit a question in advance for Niall to include in the webinar, please let us know.
You can submit your question when you register or by emailing us firstname.lastname@example.org
We hope you can join us.