Discovering Requirements: How to Specify Products and Services

"This book is not only of practical value. It's also a lot of fun to read." Michael Jackson, The Open University. Do you need to know how to create good requirements? Discovering Requirements offers a set of simple, robust, and effective cognitive tools for building requirements. Using worked examples throughout the text, it shows you how to develop an understanding of any problem, leading to questions such as: What are you trying to achieve? Who is involved, and how? What do those people want? Do they agree? How do you envisage this working? What could go wrong? Why are you making these decisions? What are you assuming? The established author team of Ian Alexander and Ljerka Beus-Dukic answer these and related questions, using a set of complementary techniques, including stakeholder analysis, goal modelling, context modelling, storytelling and scenario modelling, identifying risks and threats, describing rationales, defining terms in a project dictionary, and prioritizing. This easy to read guide is full of carefully-checked tips and tricks. Illustrated with worked examples, checklists, summaries, keywords and exercises, this book will encourage you to move closer to the real problems you're trying to solve. Guest boxes from other experts give you additional hints for your projects. Invaluable for anyone specifying requirements including IT practitioners, engineers, developers, business analysts, test engineers, configuration managers, quality engineers and project managers. A practical sourcebook for lecturers as well as students studying software engineering who want to learn about requirements work in industry. Once you've read this book you will be ready to create good requirements!

[1]  Eberhardt Rechtin,et al.  The art of systems architecting (2nd ed.) , 2000 .

[2]  Ian F. Alexander,et al.  A Taxonomy of Stakeholders: Human Roles in System Development , 2005, Int. J. Technol. Hum. Interact..

[3]  Lindsay I. Smith,et al.  A tutorial on Principal Components Analysis , 2002 .

[4]  Sivasailam Thiagarajan,et al.  Design Your Own Games and Activities: Thiagi's Templates for Performance Improvement , 2003 .

[5]  Marina Jirotka,et al.  Supporting requirements with video-based analysis , 2006, IEEE Software.

[6]  I. Alexander,et al.  Scenarios, stories, and use cases: the modern basis for system development , 2004 .

[7]  Allan MacLean,et al.  Design space analysis and use representations , 1995 .

[8]  Henry Dreyfuss,et al.  Designing for people , 1955 .

[9]  Daniel E. O'Leary Wikis: 'From Each According to His Knowledge' , 2008, Computer.

[10]  Charles Ashbacher Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior. , 2008 .

[11]  Ralph R. Young Effective Requirements Practices , 2001 .

[12]  Mike Cohn,et al.  User Stories Applied: For Agile Software Development , 2004 .

[13]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[14]  Victor Valqui Vidal,et al.  Fundamental Concepts , 2006 .

[15]  Soren Lauesen User Interface Design: A Software Engineering Perspective , 2004 .

[16]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[17]  Kristin A. Farry,et al.  Customer Centered Products: Creating Successful Products Through Smart Requirements Management (Продукты для клиента: создание успешных продуктов с помощью грамотного управления требованиями) , 2000 .

[18]  K. autorů The Cluetrain Manifesto - The End of Business as Usual , 2001 .

[19]  Michael Schrage,et al.  Serious Play: How the World's Best Companies Simulate to Innovate , 1999 .

[20]  Jonah Z. Lavi,et al.  Systems modeling & requirements specification using ECSAM: an analysis method for embedded & computer-based systems , 2005, Innovations in Systems and Software Engineering.

[21]  Ian Alexander Designing Collaborative Systems. A Practical Guide to Ethnography , 2003, Eur. J. Inf. Syst..

[22]  R. Schank,et al.  Tell Me a Story: Narrative and Intelligence , 1991 .

[23]  S. Lauesen Software Requirements Styles and Techniques , 2001 .

[24]  Mike Kuniavsky,et al.  Observing the User Experience: A Practitioner's Guide to User Research (Morgan Kaufmann Series in Interactive Technologies) (The Morgan Kaufmann Series in Interactive Technologies) , 2003 .

[25]  J. Heron Co-Operative Inquiry: Research into the Human Condition , 1996 .

[26]  Jorge Teixeira,et al.  Understanding the customer experience for service design , 2010 .

[27]  David Lorge Parnas,et al.  A Rational Design Process: How and Why to Fake It , 1985, TAPSOFT, Vol.2.

[28]  Tim Kelly,et al.  The Goal Structuring Notation – A Safety Argument Notation , 2004 .

[29]  Robert Eastaway,et al.  Why Do Buses Come in Threes: The Hidden Mathematics of Everyday Life , 1998 .

[30]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[31]  Leszek A. Maciaszek,et al.  Requirements analysis and system design: developing information systems with UML , 2001 .

[32]  Bill Wiley Essential System Requirements: A Practical Guide to Event-Driven Methods , 1999 .