Scenarios, Stories, Use Cases: Through the Systems Development Life–Cycle

Communicating user needs – the requirements of a system – is a skill difficult to learn, pin down and put into practice. There is no single right way. Much of the recent history of large engineering projects has been a tale of waste and error, where system needs were not defined early, or carefully, enough. Carefully organised and themed, Scenarios, Stories, Use Cases presents the scenario – a powerful antidote to the complexity of systems and analysis – as an effective technique for discovering, communicating and organising requirements at any stage in the system life–cycle.
This book presents a range of scenario techniques from light, sketchy and agile to careful and systematic, and celebrates diversity in requirements discovery and modelling. Including real world case studies from Nokia, Eurocontrol and DaimlerChrysler, the authors demonstrate a variety of practical approaches to show how to apply scenarios to projects throughout the life–cycle. Domain coverage spans custom software, integrations of COTS software packages, and embedded hardware/software systems. The scenario techniques described differ in many respects, but share a motivation to improve industrial practice, a clearly defined approach which has been applied on projects, and a grounding in theory.
Stories are quite insistent on one point: a tale is not over until it is finished in every detail. Scenarios, Stories, Use Cases communicates a practical approach to ensure that every detail of a project’s requirements is considered, making systems more reliable, safe, and secure. The rich wealth of stories will engage requirements engineers, developers, usability and human factors specialists, and systems and business analysts and students on requirements engineering courses.

Spis treści:
Preface.
Biographies and Photographs.
Part I: Overview.
Chapter 1. Introduction: Scenarios in System Development.
Chapter 2. Scenario–Based Approaches.
Part II: Scenarios through the System Life–Cycle: Techniques.
Chapter 3. Scenarios in Requirements Discovery.
Chapter 4. Scenarios for Innovation: Developing Scenario–Based User Needs Analysis (SUNA).
Chapter 5. Running a Use Case/Scenario Workshop.
Chapter 6. Alternative World Scenarios to Assess Requirement Stability.
Chapter 7. Negative Scenarios and Misuse Cases.
Chapter 8. Authoring Use Cases.
Chapter 9. Systematic Scenario Walkthroughs with Art–Scene.  
Chapter 10. The Role of Scenarios in Contextual Design: From User Observations to Work Redesign To Use Cases.
Chapter 11. A Scenario–Based Design Method Human–Centred Interaction Design.
Chapter 12. Use Case–Based Software Development.
Chapter 13. User Stories in Agile Software Development.
Chapter 14. Use Cases, Test Cases.
Chapter 15. Project Stories: Combining Life–Cycle Process Models (Andrew Farncombe).
Part III: Scenarios in Action: Case Studies.
Chapter 16. Story Use and Reuse in Automotive Systems Engineering.
Chapter 17. Use and Misuse Cases in Railway Systems.
Chapter 18. Scenarios in Air Traffic Control (ATC).
Chapter 19. Scenarios and Quality Requirements in Telecommunications.
Chapter 20. Scenarios in Rail Rolling Stock with Reveal.
Chapter 21. Evaluating Scenarios by Simulation.
Part IV: The Way Ahead.
Chapter 22. Putting Scenarios into Practice.
Chapter 23. Teaching Computer Scientists to Make Use.
Chapter 24. What Scenarios (Still) Aren′t Good For.
Chapter 25. The Future of Scenarios.
Appendix 1: Scenario–Based System Development Templates.
Appendix 2: Exercises.
Appendix 3: Answers to Exercises.
Glossary.
Index.

Nota biograficzna:
Ian F Alexander is an independent consultant researches with DaimlerChrysler (in Ulm, Germany) he also writes, teaches, and consults on requirements, especially scenarios.. He is on the committee of the BCS Requirements Engineering Specialist Group and runs the Requirements chapter of the IEE Professional Network for Systems Engineers. He has written extensively on Requirements
Neil Maiden is a Reader and Head of the Centre for Human–Computer Interface Design, in City University′s School of Informatics, London UK. He is co–founder and treasurer of the British Computer Society Requirements Engineering Specialist Group.

Okładka tylna:
Communicating user needs – the requirements of a system – is a skill difficult to learn, pin down and put into practice. There is no single right way. Much of the recent history of large engineering projects has been a tale of waste and error, where system needs were not defined early, or carefully, enough. Carefully organised and themed, Scenarios, Stories, Use Cases presents the scenario – a powerful antidote to the complexity of systems and analysis – as an effective technique for discovering, communicating and organising requirements at any stage in the system life–cycle.
This book presents a range of scenario techniques from light, sketchy and agile to careful and systematic, and celebrates diversity in requirements discovery and modelling. Including real world case studies from Nokia, Eurocontrol and DaimlerChrysler, the authors demonstrate a variety of practical approaches to show how to apply scenarios to projects throughout the life–cycle. Domain coverage spans custom software, integrations of COTS software packages, and embedded hardware/software systems. The scenario techniques described differ in many respects, but share a motivation to improve industrial practice, a clearly defined approach which has been applied on projects, and a grounding in theory.
Stories are quite insistent on one point: a tale is not over until it is finished in every detail. Scenarios, Stories, Use Cases communicates a practical approach to ensure that every detail of a project’s requirements is considered, making systems more reliable, safe, and secure. The rich wealth of stories will engage requirements engineers, developers, usability and human factors specialists, and systems and business analysts and students on requirements engineering courses.