Applying Requirements and Business Analysis

• Autore: Bruel Jean-Michel
• Pubblicazione: Cham : , : Springer, , 2025; ©2025
• Edizione: 1st ed.
• Descrizione fisica: 1 online resource (174 pages)
• Disciplina: 658.4032
• Nota di contenuto: Intro -- Foreword -- Preface -- Disclaimer and Conventions -- Acknowledgments -- Contents -- About the Authors -- 1: Introduction -- 1.1 Why Read This Book -- 1.2 A Guided Tour -- 1.2.1 Principles and Good Practices Rules -- 1.2.2 Requirements Kinds -- 1.2.3 The Four PEGS -- 1.2.4 Requirements Are Software -- 1.2.5 Requirements Quality and Management -- 1.2.6 Taking Advantage of a Formal OO Approach -- 1.2.7 Life Cycle -- 1.3 Organization of This Companion Book -- 2: Presentation of the PEGS Approach -- 2.1 Basic Principles -- 2.1.1 The Critical Role of Requirements Engineering -- 2.1.2 Universe of Discourse -- 2.1.3 Kind of Requirements -- Requirements Applying to All Dimensions -- Requirements Affecting Goals -- Requirements About the Project -- Requirements About the System -- Requirements About the Environment -- Document Description -- Where Are Your Types of Requirements? -- 2.1.4 How to Find the Category of Existing Requirements -- 2.1.5 People Involved -- 2.2 Standard Plan for Requirements -- 2.2.1 The Four PEGS -- 2.2.2 Metadata -- 2.2.3 Goals -- G.1 Context and Overall Objectives -- G.2 Current Situation -- G.3 Expected Benefits -- G.4 Functionality Overview -- G.5 High-Level Usage Scenarios -- G.6 Limitations and Exclusions -- G.7 Stakeholders and Requirements Sources -- 2.2.4 Environment -- E.1 Glossary -- E.2 Components -- E.3 Constraints -- E.4 Assumptions -- E.5 Effects -- E.6 Invariants -- 2.2.5 System -- S.1 Components -- S.2 Functionality -- S.3 Interfaces -- S.4 Detailed Usage Scenarios -- S.5 Prioritization -- S.6 Verification and Acceptance Criteria -- 2.2.6 Project -- P.1 Roles and Personnel -- P.2 Imposed Technical Choices -- P.3 Schedule and Milestones -- P.4 Tasks and Deliverables -- P.5 Required Technology Elements -- P.6 Risk and Mitigation Analysis -- P.7 Requirements Process and Report. ; 2.2.7 Links Between the Four PEGS -- 2.3 The Life Cycle Model -- 2.3.1 The Definition Step -- 2.3.2 The Implementation Step -- 2.4 Frontier Between Requirements and Analysis -- 2.4.1 Design Versus Requirements -- 2.4.2 About Versioning and Variability -- 2.4.3 What About Requirement Attributes? -- 3: Object-Oriented Requirements -- 3.1 Main Concepts -- 3.1.1 Class as the Core Concept of OO Requirements -- 3.1.2 Relations Between Classes -- 3.1.3 Contracts -- 3.2 Producing OO Requirements -- 3.2.1 How to Produce Object-Oriented Requirements -- 3.2.2 Eliciting and Documenting Requirements -- 3.2.3 Modeling Components of the System and Its Environment -- 3.2.4 Producing Functional Specification -- 3.2.5 Behavioral Specification -- 3.3 Requirements Traceability -- 4: Quality and Verification Criteria for Requirements -- 4.1 Books Mutual References -- 4.2 The "To Be Determined" Rule -- 4.3 The Minimum Requirements Outcome Principle -- 4.4 GitHub Implementation Example -- 4.5 Additional Guidelines for Quality -- 5: Case Studies -- 5.1 A Library Management System (LMS) -- 5.1.1 Context -- 5.1.2 Goals -- G.1 Context and Overall Objectives -- G.2 Current Situation -- G.3 Expected Benefits -- G.4 Functionality Overview -- G.5 High-Level Usage Scenarios -- G.6 Limitations and Exclusions -- G.7 Stakeholders and Requirements Sources -- G.7.1 Stakeholders -- G.7.2 Resources -- 5.1.3 Environment -- E.1 Glossary -- E.1.2 Book -- E.1.3 Borrowing -- E.1.4 Borrowing Period -- E.1.5 Catalog -- E.1.6 Checkout -- E.1.7 Daily Sheet with Expired Holds -- E.1.8 Daily Sheet with Overdue Checkouts -- E.1.9 Holding -- E.1.10 Hold Duration -- E.1.11 ISBN -- E.1.12 Librarian -- E.1.13 Library -- E.1.14 LMS -- E.1.15 Meta Book -- E.1.16 Overdue Checkout -- E.1.17 Patron -- E.1.18 Return -- E.2 Components -- E.2.1 Login Management -- E.3 Constraints. ; E.4 Assumptions -- E.5 Effects -- E.6 Invariants -- 5.1.4 System -- S.1 Components -- S.1.1 Books Management -- S.1.2 Patrons Management -- S.1.3 Holds Management -- S.1.4 Checkouts Management -- S.2 Functionality -- S.2.1 Functional Requirements for the LMS -- S.2.2 Non-functional Requirements for the LMS -- S.3 Interfaces -- S.4 Detailed Usage Scenarios -- S.5 Prioritization -- S.6 Verification and Acceptance Criteria -- S.6.1 Verification Criteria for the LMS -- S.6.2 Acceptance Criteria for the LMS -- 5.1.5 Project -- P.1 Roles and Personnel -- P.2 Imposed Technical Choices -- P.3 Schedule and Milestones -- P.4 Tasks and Deliverables -- P.5 Required Technology Elements -- P.6 Risks and Mitigation Analysis -- P.7 Requirements Process and Report -- 5.2 A Book on Requirements -- 5.2.1 Context -- 5.2.2 Changelog -- 5.2.3 Goals Book -- Front Matter -- Numbering Requirements -- Goals Book Requirements -- G.1 Context and Overall Objective -- G.2 Current Situation -- G.3 Expected Benefits -- G.4 Functionality Overview -- G.5 High-Level Usage Scenarios -- G.6 Limitations and Exclusions -- G.7 Stakeholders and Requirements Sources -- 5.2.4 Environment Book -- E.1 Glossary -- E.1.1 Terms -- E.1.2 Icons -- E.3 Constraints -- E.4 Assumptions -- 5.2.5 Project Book -- P.1 Roles and Personnel -- P.2 Imposed Technical Choices -- P.3 Schedule and Milestones -- P.4 Tasks and Deliverables -- P.7 Requirements Process and Report -- 5.2.6 System Book -- S.1 Components -- Back Matter -- 5.2.7 Traceability Matrix -- 5.3 The Roborace -- 5.3.1 Context -- 5.3.2 Goals Book -- G.1 Context and Overall Objective -- G.2 Current Situation -- G.3 Expected Benefits -- G.4 Functionality Overview -- G.5 High-Level Usage Scenarios -- G.6 Limitations and Exclusions -- G.7 Stakeholders and Requirements Sources -- 5.3.3 Environment -- E.1 Glossary -- E.2 Components. ; E.3 Constraints -- E.3.1 Constraints on the Project -- E.3.2 Constraints on the System -- E.4 Assumptions -- E.5 Effects -- E.6 Invariants -- 5.3.4 System -- S.1 Components -- S.2 Functionality -- S.2.1 Planning Module -- S.2.6 Non-functional Requirements -- S.3 Interfaces -- S.4 Detailed Usage Scenarios -- S.5 Prioritization -- S.6 Verification and Acceptance Criteria -- 5.3.5 Project -- P.1 Roles -- P.2 Imposed Technical Choices -- P.3 Schedule, Milestones, and Deliverables -- P.4 Tasks and Deliverables -- P.5 Required Technology Elements -- P.6 Risk and Mitigation Analysis -- P.7 Requirements Process and Report -- 5.4 Industrial and Other Use Cases -- 6: Lessons Learned -- 6.1 Producing OO Requirements -- 6.2 Concrete Use of a PEGS Book as an Initial Set of Requirements -- 6.3 Requirements Engineering Course in Toulouse (2024) -- 6.3.1 Active Learning -- 6.3.2 Projects -- 6.3.3 Outcomes -- 6.4 Producing PEGS Requirements: A Study at the Constructor University -- 6.5 McMaster University (2024) -- 6.5.1 First Window of Opportunity -- 6.5.2 Second Window of Opportunity -- 6.5.3 Final Delivery -- 6.5.4 Measurements -- 6.6 PEGS Requirements for the MVP (2023) -- 6.7 RE Conference Tutorials (2023 and 2024) -- Appendix A: Glossary -- Appendix B: Frequently Asked Questions -- B.1. Kinds of Requirements and Specific Concepts -- B.1.1. Business Analysis vs. Mission Analysis -- B.1.2. Multiple Categories -- B.1.3. Goals vs. Needs -- B.1.4. Actors -- B.1.5. Constraints Versus Imposed Technical Choices -- B.1.6. Constraints Versus Assumptions -- B.1.7. Constraints Versus Obligations -- B.1.8. Glossary Entries -- B.1.9. Effect Versus Functional Requirement -- B.1.10. Effect Versus Expected Benefits -- B.1.11. Rationale -- B.1.12. Interviews and Reviews -- B.1.13. Software Architecture -- B.1.14. Security -- B.2. Agile Approach. ; B.3. Goal-Oriented Requirements Engineering -- B.3.1. Goal Modeling and Decomposition -- B.3.2. Responsibility Modeling -- Appendix C: Categories of Stakeholder -- C.1. Target Groups -- C.2. Production Groups -- Appendix D: Principles and Good Practice Rules -- Appendix E: Book Templates -- Appendix F: Exercises: Elements of Solutions -- F.1. Requirements: Basic Concepts and Definitions -- F.2. Requirements: General Principles -- F.3. Standard Plan for Requirements -- F.4. Complementary Exercises -- F.4.1. Object-Oriented Requirements -- F.4.2. The Standard Plan -- F.4.3. Requirements Category -- Appendix G: Handbook Errors in the First Edition (2022) -- References and Links.
• Sommario/riassunto: This book provides a practical view of how to use requirements effectively.It contains several complete examples and practical material, and this way ideally complements Bertrand Meyer's "Handbook of Requirements and Business Analysis".
• Titolo autorizzato: Applying Requirements and Business Analysis
• ISBN: 9783031921605; 9783031921599
• Formato: Materiale a stampa
• Livello bibliografico: Monografia
• Lingua di pubblicazione: Inglese
• Record Nr.: 9911039320303321
• Lo trovi qui: Univ. Federico II
• Serie: Business and Management Series