- Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users
- Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic
- Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems
Arvustused
"... this book is a breath of fresh air, providing practical guidance on incorporating techniques and approaches to the development cycle." Usability Consultant
|
|
|
|
Biographies and Photographs. |
|
|
|
|
|
|
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. |
|
|
|
|
|
|
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 3: Answers to Exercises. |
|
|
|
|
|
|
|
|
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.
Lisainfo e-raamatute kohta