Scenarios, Stories, Use Cases

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.

"... this book is a breath of fresh air, providing practical guidance on incorporating techniques and approaches to the development cycle."—Usability Consultant

• Preface xiiiBiographies and Photographs xviiPart I Overview Chapter 1 Introduction: Scenarios in System DevelopmentContext 3Through the Life Cycle 17Types of System 18Scenarios for Systems—Not Necessarily Software 19The Way Ahead 21Keywords 21References 21Recommended Reading 22Chapter 2 Scenario-based ApproachesOverview: The Crews Scenario Framework 25The Framework 26The Scenario Approaches Described in this Book 28Conclusion 32Keywords 32References 32Part II Scenarios Through the System Life-cycle: Techniques Chapter 3 Scenarios in Requirements DiscoveryApplicability 39Position in the Life Cycle 40Key Features 40Strengths 40Weaknesses 41What Is a Requirements Scenario? 41From Scenarios to Atomic Requirements 51Keeping Track of the Investigation 54Who Produces the Scenarios? 54Techniques for Building Scenarios 55When to Use Scenarios 58Keywords 59References 59Chapter 4 Scenarios for Innovation: Developing Scenario-based User Needs Analysis (Suna)Applicability 61Position in the Life Cycle 62Key Features 62Strengths and Weaknesses 63Technique 64Worked Example 73Comparisons 77Keywords 79References 79Recommended Readings 79Chapter 5 Running a Use Case/scenario WorkshopApplicability 81Position in the Life Cycle 82Key Features 82Strengths 83Weaknesses 84Technique 85Worked Example 93Comparisons 99Keywords 100References 100Recommended Reading 101Chapter 6 Alternative World Scenarios to Assess Requirement StabilityApplicability 103Position in the Life Cycle 104Key Features 104Strengths 104Weaknesses 104Technique 105Worked Example 110Comparisons 115Keywords 116References 116Recommended Reading 117Chapter 7 Cases Negative Scenarios and MisuseApplicability 119Roles in the Life Cycle 119Key Features 120Strengths 120Weaknesses 120Technique 120Worked Example 128Comparisons 131Keywords 138References 138Recommended Reading 139Chapter 8 Authoring Use CasesApplicability 141Position in the Life Cycle 141Key Features 142Strengths 143Weaknesses 143Technique 143Comparisons 158Keywords 159References 159Recommended Reading 160Chapter 9 Systematic Scenario Walkthroughs with Art-scenePosition in the Life Cycle 161Applicability 161Key Features 162Strengths 162Weaknesses 162The Art-Scene Process and Environment 162Art-Scene’s Research Provenance 163The Art-Scene Approach 164The Structure and Representation of an Art-Scene Scenario 164The Art-Scene Software Environment 166Facilitating Scenario Walkthroughs 171The Scenario Workshop Environment 173Worked Example 173Comparisons 176Keywords 177References 177Recommended Reading 178Chapter 10 The role of scenarios In Contextual Design: From User Observations to Work Redesign To Use CasesApplicability 180Position in the Life Cycle 180Key Features 181Strengths 181Weaknesses 185Technique 185Techniques and Worked Example 186Lessons Learnt 205Comparisons 206Keywords 207References 207Recommended Readings 208Chapter 11 A Scenario-based Design Method for Human-centred Interaction DesignOverview 211Applicability 211Position in the Life Cycle 212Key Features 212Strengths 213Weaknesses 213The Method 213Other Artifacts in the Method 218Processes of the Method 220Summary 223Worked Example 224User Story 225Comparisons 232Acknowledgements 233Keywords 234References 234Recommended Reading 234Chapter 12 Use Case-based Software DevelopmentApplicability 237Position in the Life Cycle 238Key Features 238Strengths 238Weaknesses 238Technique and Worked Example 239Summary and Comparisons 262Keywords 263References 263Recommended Reading 264Chapter 13 User Stories in Agile Software DevelopmentApplicability 265Applicability II—Why User Stories? 266Position in Life Cycle 267Key Features 267Strengths 268Weaknesses 268Technique 269Worked Example 275Comparisons 278Keywords 279References 279Recommended Reading 279Chapter 14 Use Cases, Test CasesApplicability 281Position in the Life Cycle 281Key Features 282Strengths 282Weaknesses 282Background: The V-Model 283Technique 284Worked Example 290Comparisons 296Keywords 297References 297Recommended Reading 298Chapter 15 Project Stories: Combining Life-cycle Process ModelsApplicability 299Position in the Life Cycle 299Key Features 300Strengths 300Weaknesses 300Technique 300Conclusion 323Keywords 324References 324Recommended Reading 324Part III Scenarios in Action: Case Studies Chapter 16 Story Use and Reuse in Automotive Systems EngineeringType of Project 329Applicability 329Position in the Life Cycle 330Roles Played by Scenarios 330Strengths 330Weaknesses 330Introduction 330Automotive Software Development 331Stories in Automotive Software Development 334Lessons Learnt 342Keywords 345References 346Chapter 17 Systems Use and Misuse Cases in RailwayA: Use Cases for Train Control Requirements Discovery 347Type of Project 347Applicability 348Position in the Life Cycle 348Roles Played by Scenarios 348Strengths 348Weaknesses 348Case Study 349Methods and Tools 350Approach 350Lessons Learnt 352Keywords 353B: Misuse Cases for a Seats Trade-Off 354Type of Project 354Applicability 354Position in the Life Cycle 354Roles Played by Scenarios 354Strengths 355Weaknesses 355Case Study 355Lessons Learnt 360Summary 361Keywords 362References 362Chapter 18 Scenarios in Air Traffic Control (ATC)Applicability 363Roles in the Life Cycle 364Key Features 364Strengths 364Weaknesses 365Background 366Results 372Keywords 376References 376Chapter 19 Scenarios and Quality Requirements in TelecommunicationsType of Project 379Applicability 379Position in the Life Cycle 380Roles Played by Scenarios 380Strengths 380Weaknesses 380Case Study 381Lessons Learnt 389Acknowledgements 391Keywords 391References 391Chapter 20 Scenarios in Rail Rolling Stock with RevealApplicability 393Position in the Life Cycle 394Key Features 394Strengths 394Weaknesses 395Case Study 396Lessons Learnt 408Keywords 409References 409Chapter 21 Evaluating Scenarios by SimulationType of Project 411Applicability 412Position in the Life Cycle 412Roles Played by Scenarios 412Strengths 412Weaknesses 412Case Study 413Lessons Learnt 425Keywords 426References 426Part IV The Way AheadChapter 22 Putting Scenarios Into PracticeWhich Kind of Scenario, When? 431Which Scenario Technique, When? Conclusions from Part 2 432Who, and Why? 435Scenarios Everywhere? 436How Does Project Scale Affect Scenario Usage? 437Into Practice: Conclusions from the Part 3 Case Studies 439Do Scenarios Replace Requirements? 440Getting Started 443Keywords 444References 444Chapter 23 Teaching Computer Scientists To Make UseChallenges in Teaching Students to Make Use 445Comparisons—Scenarios for Making Use 446Using Cases to Teach Scenario-Based Usability Engineering 449Strengths and Weaknesses 458Discussion and Future Directions 459Acknowledgements 461Keywords 461References 462Recommended Readings 463Chapter 24 What Scenarios (Still) Aren’t Good forContinuous Behaviour 465Very Large Systems 466Fragmentary Models 466Episodic, Allusory 467Domain-Specific? 467Which Representation? 467Open-Ended 468Tacit Knowledge 468Non-Functional Requirements (NFRs) 468Summary 468References 469Chapter 25 The Future of ScenariosIntroduction: Horses for Courses 471Towards a Framework 471Representation 471Process 472Domain Knowledge 473COTS 473Dissemination 473Summary 474References 474Appendix 1 Scenario-based System Development Templates 475Appendix 2 Exercises 499Appendix 3 Answers to Exercises 501Glossary 507Index 513