Introduction / 1: |
Introduction to Requirements / 1.1: |
Introduction to Systems Engineering / 1.2: |
Defining Requirements Engineering / 1.3: |
Definition of a Requirement / 1.3.1: |
Definition of a Stakeholder / 1.3.2: |
Definition of Requirements Engineering / 1.3.3: |
Requirements and Quality / 1.4: |
Requirements and the Lifecycle / 1.5: |
Requirements Tracing / 1.6: |
Requirements and Modelling / 1.7: |
Requirements and Testing / 1.8: |
Requirements in the Problem and Solution Domains / 1.9: |
How to Read this Book / 1.10: |
A Generic Process for Requirements Engineering / 2: |
Developing Systems / 2.1: |
Generic Process Context / 2.3: |
Input Requirements and Derived Requirements / 2.3.1: |
Acceptance Criteria and Qualification Strategy / 2.3.2: |
Generic Process Introduction / 2.4: |
Ideal Development / 2.4.1: |
Development in the Context of Change / 2.4.2: |
Generic Process Information Model / 2.5: |
Information Classes / 2.5.1: |
Agreement State / 2.5.2: |
Qualification State / 2.5.3: |
Satisfaction State / 2.5.4: |
Information Model Constraints / 2.5.5: |
Generic Process Details / 2.6: |
Agreement Process / 2.6.1: |
Analyse and Model / 2.6.2: |
Derive Requirements and Qualification Strategy Fig. 2.1.3 Portrays the Process for Deriving Requirements and Qualification Strategy / 2.6.3: |
Summary / 2.7: |
System Modelling for Requirements Engineering / 3: |
Representations for Requirements Engineering / 3.1: |
Data Flow Diagrams / 3.2.1: |
Entity-Relationship Diagrams / 3.2.2: |
Statecharts / 3.2.3: |
Object-Oriented Approaches / 3.2.4: |
Methods / 3.3: |
Viewpoint Methods / 3.3.1: |
Object-Oriented Methods / 3.3.2: |
The UML Notation / 3.3.3: |
Formal Methods / 3.3.4: |
Writing and Reviewing Requirements / 3.4: |
Requirements for Requirements / 4.1: |
Structuring Requirements Documents / 4.3: |
Key Requirements / 4.4: |
Using Attributes / 4.5: |
Ensuring Consistency Across Requirements / 4.6: |
Value of a Requirement / 4.7: |
The Language of Requirements / 4.8: |
Requirement Boilerplates / 4.9: |
Granularity of Requirements / 4.10: |
Criteria for Writing Requirements Statements / 4.11: |
Requirements Engineering in the Problem Domain / 4.12: |
What is the Problem Domain? / 5.1: |
Instantiating the Generic Process / 5.2: |
Agree Requirements with Customer / 5.3: |
Analyse & Model / 5.4: |
Identify Stakeholders / 5.4.1: |
Create Use Scenarios / 5.4.2: |
Scoping the System / 5.4.3: |
Derive Requirements / 5.5: |
Define Structure / 5.5.1: |
Capture Requirements / 5.5.2: |
Define Acceptance Criteria / 5.5.3: |
Define Qualification Strategy / 5.5.4: |
Requirements Engineering in the Solution Domain / 5.6: |
What is the Solution Domain / 6.1: |
Engineering Requirements from Stakeholder Requirements to System Requirements / 6.2: |
Producing the System Model / 6.2.1: |
Creating System Models to Derive System Requirements / 6.2.2: |
Banking Example / 6.2.3: |
Car Example / 6.2.4: |
Deriving Requirements from a System Model / 6.2.5: |
Agreeing the System Requirements with the Design Team / 6.2.6: |
Engineering Requirements from System Requirements to Subsystems / 6.3: |
Creating a System Architecture Model / 6.3.1: |
Deriving Requirements from an Architectural Design Model / 6.3.2: |
Other Transformations Using a Design Architecture / 6.4: |
Advanced Traceability / 6.5: |
Elementary Traceability / 7.1: |
Satisfaction Arguments / 7.3: |
Requirements Allocation / 7.4: |
Reviewing Traceability / 7.5: |
The Language of Satisfaction Arguments / 7.6: |
Rich Traceability Analysis / 7.7: |
Rich Traceability for Qualification / 7.8: |
Implementing Rich Traceability / 7.9: |
Single-Layer Rich Traceability / 7.9.1: |
Multi-Layer Rich Traceability / 7.9.2: |
Design Documents / 7.10: |
Metrics for Traceability / 7.11: |
Breadth / 7.11.1: |
Depth / 7.11.2: |
Growth / 7.11.3: |
Balance / 7.11.4: |
Latent Change / 7.11.5: |
Management Aspects of Requirements Engineering / 7.12: |
Introduction to Management / 8.1: |
Requirements Management Problems / 8.2: |
Summary of Requirement Management Problems / 8.2.1: |
Managing Requirements in an Acquisition Organisation / 8.3: |
Planning / 8.3.1: |
Monitoring / 8.3.2: |
Changes / 8.3.3: |
Supplier Organisations / 8.4: |
Bid Management / 8.4.1: |
Development / 8.4.2: |
Product Organisations / 8.5: |
DOORS: A Tool to Manage Requirements / 8.5.1: |
The Case for Requirements Management / 9.1: |
DOORS Architecture / 9.3: |
Projects, Modules and Objects / 9.4: |
DOORS Database Window / 9.4.1: |
Formal Modules / 9.4.2: |
Objects / 9.4.3: |
Graphical Objects / 9.4.4: |
Tables / 9.4.5: |
History and Version Control / 9.5: |
History / 9.5.1: |
Baselining / 9.5.2: |
Attributes and Views / 9.6: |
Attributes / 9.6.1: |
Views / 9.6.2: |
Traceability / 9.7: |
Links / 9.7.1: |
Traceability Reports / 9.7.2: |
Import and Export / 9.8: |
UML Modelling with DOORS/Analyst / 9.9: |
Bibliography / 9.10: |
Index |
Introduction / 1: |
Introduction to Requirements / 1.1: |
Introduction to Systems Engineering / 1.2: |