This textbook lays the foundations for System-of-Systems Requirements Engineering and Requirements Management practices, principles, technique, and processes. It provides a comprehensive treatment of requirements engineering, an integral part of Multidisciplinary Systems Engineering. The book takes the student/reader though the entire process of documenting, analyzing, tracing, prioritizing, and managing requirements, and then goes on the describe controlling and communicating requirement change throughout the system development lifecycle. The authors discuss the role of requirements management in support of other requirements engineering processes; describe the principal requirements engineering activities and their relationships; introduces techniques for requirements elicitation and analysis and describes requirements validation and the role of requirements reviews; and discusses the role of requirements management in support of other requirements engineering processes. A full suite of classroom material is provided including exercises, assignments, and PowerPoint slides.
Author(s): James A. Crowder, Curtis W. Hoff
Series: Textbooks in Telecommunication Engineering
Publisher: Springer
Year: 2022
Language: English
Pages: 244
City: Cham
Preface
Contents
1: Introduction to Multidisciplinary Requirement Engineering (MDRE)
1.1 Requirements Engineering: The Backbone of Multidisciplinary Systems Engineering
1.2 Chapter Organization
1.2.1 Section I: The Basics of Requirements Engineering
1.2.1.1 Chapter 2 The Need for Requirements Engineering
1.2.1.2 Chapter 3 MDRE Systems Supportability Analysis
1.2.1.3 Chapter 4 MDRE: Designing for Manufacturability
1.2.1.4 Chapter 5 MDRE: The Requirements Engineering Process
1.2.1.5 Chapter 6 Systems Engineering and Requirements
1.2.1.6 Chapter 7 Developer Derived/Decomposed Requirements
1.2.1.7 Chapter 8 New Development Vs. Existing System, Extension, or Upgrade
1.2.1.8 Chapter 9 System Tiers
1.2.2 Section II: The Mechanics of Requirements Engineering
1.2.2.1 Chapter 10 Multidisciplinary Systems Engineering and Requirements Management
1.2.2.2 Chapter 11 Categories of Requirements
1.2.2.3 Chapter 12 Requirements Composition
1.2.2.4 Chapter 13 Requirements Traceability
1.2.3 Section III: Requirements Management: Change Is Inevitable
1.2.3.1 Chapter 14 Requirements Change Management
1.2.3.2 Chapter 15 Requirements Agility
1.2.3.3 Chapter 16 Requirements Antipatterns
1.2.3.4 Chapter 17 New Trends in Requirements Management: Model-Based Systems Engineering (MBSE)
1.2.3.5 Chapter 18 Conclusions and Discussion: Putting it all Together
1.2.3.6 Assignments
1.2.4 Design Problem
1.2.4.1 Design Problem Description: Alternative Energy Power Grid
1.2.4.2 DC Power Grid Requirements Discussion
1.2.4.3 High-Level Technical Description of the DC Power Grid System
1.2.4.4 High-Level Technical Requirements for the DC Grid System
1.2.4.5 Assignments
References
2: The Need for Requirements Engineering
2.1 Requirements Engineering: A Multidisciplinary Process
2.2 Multidisciplinary Requirements Engineering
2.3 The MDRE Process
2.3.1 The MDRE Feasibility Study
2.3.2 The Requirements Analysis Process
2.4 MDRE Technical Requirements
2.5 Formal Vs. Informal Requirements
2.5.1 Case Study: The Denver International Airport Baggage Handling System
2.6 The MDRE Process: Enhancement of an Existing Legacy System
2.6.1 Design Problem
2.6.2 Design Problem Description: Alternative Energy Power Grid
2.6.3 DC Power Grid Requirements Discussion
2.6.4 High-Level Technical Description of the DC Power Grid System
2.6.5 High-Level Technical Requirements for the DC Grid System
2.6.6 Assignments
References
3: MDRE System Supportability Analysis
3.1 Introduction to Supportability Analysis
3.2 MDRE: DREX+ Mission Analysis
3.2.1 Use of Radar Systems for Military and Civil Surveillance Operations
3.2.2 Case Study #1: Naval Long-Range Radar Systems
3.2.3 Case Study #2: Border Patrol Surveillance
3.2.4 MDRE: Data Mining and Discovery
3.2.5 MDRE Supportability, Maintainability, and Manufacturability Considerations
3.2.6 DREX+ Mission/Operational Applicability
3.3 DREX+ Requirements Analysis
3.3.1 Requirements Decomposition
3.3.1.1 Completeness
3.3.1.2 Correctness
3.3.1.3 Consistency
3.3.1.4 Traceability
3.3.1.5 Disambiguation
3.3.1.6 Testability
3.3.1.7 Atomicity
3.3.2 MDRE Example: Radar System Requirements
3.3.2.1 Radar Frequency Bands
3.3.2.2 Radar Beam Width
3.3.2.3 Radar Range
3.3.2.4 Case Study 1: Navy Long-Range Radar Specification
3.3.2.5 Case Study 2: Border Patrol Surveillance Specification
3.3.2.6 DREX+ Requirements Analysis Discussion
3.4 DREX+ Maintainability Analysis
3.4.1 The MDRE Maintainability Engineering Process
3.4.1.1 Enhancing System Maintainability
3.4.1.2 Enhancing Maintainability through Standardization of Components
3.4.1.3 Enhancing Maintainability through Standardization of Interfaces
3.4.1.4 Enhancing Maintainability through Standardization of Maintenance Manuals/Procedures
3.4.1.5 Enhancing Maintainability through Ease of Accessibility
3.4.1.6 Enhancing Maintainability through Ease of Maintenance Activities
3.4.1.7 Enhancing Maintainability through Designing for Safety
3.4.1.8 Enhancing Maintainability through Designing for Modularity
3.4.2 The MDRE Maintainability of the DREX+ System
3.4.2.1 Maintenance Cost as a Part of Overall Life Cycle Cost (LCC)
3.4.2.2 Enhancing the DREX+ Maintainability through Standardization of Components
3.4.2.3 Enhancing the DREX+ Maintainability through Standardization of Maintenance Manuals/Procedures
3.4.2.4 Enhancing the DREX+ Maintainability through Ease of Accessibility
3.4.2.5 Enhancing the DREX+ Maintainability through Ease of Maintenance Activities
3.4.2.6 Enhancing the DREX+ Maintainability through Designing for Safety
3.4.2.7 Enhancing the DREX+ Maintainability through Designing for Modularity
3.5 DREX+ Supportability Analysis
3.5.1 Designing for Supportability
3.5.2 Designing for Supportability through Testability
3.5.3 MDRE Operational Supportability Engineering
3.5.3.1 MDRE Continued Operational Supportability Engineering
3.6 DREX+ Supportability Conclusions and Discussion
3.6.1 Sample Supportability Requirements
3.6.1.1 Design Problem
3.6.1.2 Design Problem Description: Alternative Energy Power Grid
3.6.1.3 DC Power Grid Requirements Discussion
3.6.1.4 High-Level Technical Description of the DC Power Grid System
3.6.1.5 High-Level Technical Requirements for the DC Grid System
3.6.1.6 Assignments
References
4: MDRE Designing for Manufacturability
4.1 MDRE Supply Chain Management Analysis
4.1.1 MDRE Supply Chain Considerations
4.1.2 MDRE Supply Chain Management Considerations
4.1.3 MDRE Disruption Is the New Normal
4.1.4 MDRE Supply Chain Management System Implementation
4.1.4.1 MDRE Supply Chain Management System Development Process
4.1.5 MDRE Supply Chain Management Critical Steps
4.1.5.1 MDRE Supply Chain Management Metrics Development
4.1.5.2 MDRE SCM Inventory Velocity
4.1.5.3 MDRE SCM Time Compression
4.1.5.4 MDRE SCM Perfect Order: The Customer
4.1.5.5 MDRE SCM Perfect Order: The Supplier
4.1.5.6 MDRE SCM Metrics Discussion Example: DREX+
4.1.6 MDRE Supply Chain Management Applications
4.1.6.1 MDRE SCM Traceability
4.1.6.2 MDRE SCM Parts Compatibility
4.1.6.3 MDRE SCM PCB Manufacturing and Assembly
4.1.6.4 MDRE SCM Front-End Production Processes
4.1.6.5 MDRE SCM Sustainability
4.1.7 MDRE PCB Assembly Analysis
4.1.7.1 MDRE Design for Assembly (DFA) Analysis
4.1.8 MDRE Design for Assembly (DFA) Implementation
4.1.8.1 MDRE Design for Assembly (DFA) Background
4.1.8.2 MDRE Design for Assembly (DFA) Applied to the DREX+
4.1.8.3 MDRE Design for PCB Inspection and Verification
4.1.8.4 MDRE DFA Quality Inspection/Verification Process
4.1.8.5 MDRE DFA Quality on-Site Inspection/Verification Traceability
4.2 MDRE Manufacturability Analysis
4.2.1 Design for Manufacturability (DFM)
4.2.1.1 MDRE DFM and System Design Process
4.2.2 Design for Manufacturability (DFM) Example: DREX+
4.2.2.1 MDRE DFM Best Practices
4.2.2.2 MDRE DFM Frame of Reference
4.2.2.3 MDRE DFM Logical Analysis
4.2.3 Design for Manufacturability (DFM) Root Causes of Redesign
4.2.3.1 Insufficient Performance Margin(s)
4.2.3.2 Projected Life Cycle Cost Too High
4.2.3.3 Improper Handling of Mission Needs
4.2.3.4 Poor Communication and/or Inadequate Handling of Requirements
4.2.3.5 Improper Functional Decomposition of the System
4.2.3.6 Improper Consideration of Inputs and Outputs
4.2.3.7 Improper Emphasis on Static Functional Decomposition
4.2.3.8 Improper Handling of System Management
4.3 Design for Manufacturability (DFM) Discussion
4.3.1 Design Problem
4.3.2 Design Problem Description: Alternative Energy Power Grid
4.3.3 DC Power Grid Requirements Discussion
4.3.4 High-Level Technical Description of the DC Power Grid System
4.3.5 High-Level Technical Requirements for the DC Grid System
4.3.6 Assignments
References
5: MDRE: The Requirements Engineering Process
5.1 The MDRE Requirements Process Flow
5.1.1 Elicitation
5.1.2 Requirements Analysis and Validation
5.1.3 Requirements Classification
5.1.4 Requirements Documentation
5.1.4.1 Requirements Vs. Features
5.1.4.2 Ongoing Requirements Documentation
5.1.5 Requirements Prioritization
5.1.6 Requirements Management
5.1.6.1 Design Problem
5.1.6.2 Design Problem Description: Alternative Energy Power Grid
5.1.6.3 DC Power Grid Requirements Discussion
5.1.6.4 High-Level Technical Description of the DC Power Grid System
5.1.6.5 High-Level Technical Requirements for the DC Grid System
5.1.6.6 Assignments
References
6: MDRE: Systems Engineering and Requirements
6.1 Formal Vs. Informal Requirements
6.1.1 Informal Requirements
6.1.2 Formal Requirements
6.1.2.1 Requirements Elicitation Process
6.1.2.2 Communication between the MDRE Team and the Customer
6.1.2.3 Requirements Traceability
6.1.2.4 Documentation Organization and Management
6.1.2.5 Requirement Language Formality
6.1.3 Use of Informal Requirements: Agile Development
6.2 Primary/Contractual Requirements
6.3 Statement of Work (SOW) and Statement of Objectives (SoO)
6.3.1 The Statement of Work (SOW)
6.3.1.1 Writing a Statement of Work
6.3.2 The Statement of Objectives (SOO)
6.4 Interface Control Documents
6.5 Compliance Documents and Policy Compliance
6.6 Concept of Operations (CONOPS)
6.7 Case Study: Requirements Management Disaster
6.7.1 A Classic Pitfall
6.7.2 Background Material
6.7.3 Program Execution
6.7.4 The Path to Preliminary Design Review Disaster
6.7.5 The Path to Preliminary Design Review Disaster #2
6.7.6 Case Study Assessment
6.7.6.1 Design Problem
6.7.6.2 Design Problem Description: Alternative Energy Power Grid
6.7.6.3 DC Power Grid Requirements Discussion
6.7.6.4 High-Level Technical Description of the DC Power Grid System
6.7.6.5 High-Level Technical Requirements for the DC Grid System
6.7.6.6 Assignments
References
7: MDRE: Developer Derived/Decomposed Requirements
7.1 Implied Requirements
7.1.1 Case Study “the Front Cover”
7.2 Requirement Derivation/Decomposition Process
7.2.1 Top-Level Requirements Assessment
7.2.2 Requirement Decomposition and Derivation
7.3 Requirement Development Guidelines
7.3.1 Design Problem
7.3.2 Design Problem Description: Alternative Energy Power Grid
7.3.3 DC Power Grid Requirements Discussion
7.3.4 High-Level Technical Description of the DC Power Grid System
7.3.5 High-Level Technical Requirements for the DC Grid System
7.3.6 Assignments
References
8: MDRE: New System Vs. Existing System, Extension or Upgrade
8.1 MDRE for Legacy System Upgrades, Extensions, and Technology Refresh
8.1.1 Requirements Validation for Legacy System Upgrades, Extensions, and Technology Refresh
8.1.2 Case Study: Requirement Validation Failure—The Tacoma Bridge Project
8.2 Design Problem
8.2.1 Design Problem Description: Alternative Energy Power Grid
8.2.2 DC Power Grid Requirements Discussion
8.2.3 High-Level Technical Description of the DC Power Grid System
8.2.4 High-Level Technical Requirements for the DC Grid System
8.2.5 Assignments
References
9: System Tiers
9.1 Explanation of System Tiers
9.1.1 Presentation Tier
9.1.2 Mission/Business Application Services Tier
9.1.3 Mission/Business Processes Tier
9.1.4 Persistent Services Tier
9.1.5 Data Access Tier
9.1.6 Data Storage Tier
9.1.7 Orchestration/Management Tier
9.1.8 Communications Tier
9.2 MDRE Requirements Planning for Tiers
9.3 MDRE Program Structure and Tiers
9.3.1 Design Problem
9.3.2 Design Problem Description: Alternative Energy Power Grid
9.3.3 DC Power Grid Requirements Discussion
9.3.4 High-Level Technical Description of the DC Power Grid System
9.3.5 High-Level Technical Requirements for the DC Grid System
9.3.6 Assignments
References
10: Multidisciplinary Requirements Engineering
10.1 Requirements Development
10.1.1 Existing Specifications
10.1.2 Operational Assessment: User Scenarios, Use Cases, and Storyboards
10.1.2.1 User Scenarios
10.1.2.2 Use Cases
10.1.2.3 Storyboards
10.1.3 Requirements Specification
10.1.4 System Architecture
10.1.5 System Models
10.2 Requirements Management
10.2.1 MDRE Requirements Management Approach
10.2.2 MDRE Requirements Documentation and Configuration Management
10.2.3 MDRE Requirements Prioritization
10.2.4 MDRE Requirements Traceability
10.2.5 MDRE Requirements Management Tools
10.2.5.1 Design Problem
10.2.5.2 Design Problem Description: Alternative Energy Power Grid
10.2.5.3 DC Power Grid Requirements Discussion
10.2.5.4 High-Level Technical Description of the DC Power Grid System
10.2.5.5 High-Level Technical Requirements for the DC Grid System
10.2.5.6 Assignments
References
11: Categories of Requirements
11.1 Functional Requirements
11.1.1 User Interface Requirements
11.1.2 Technical Requirements
11.2 Nonfunctional Requirements
11.2.1 Quality Requirements
11.2.2 Performance Requirements
11.2.2.1 Performance Requirement Analysis Models
11.2.3 Constraints/Assumptions
11.3 Inter-Relationships Between Requirements
11.3.1 Design Problem
11.3.2 Design Problem Description: Alternative Energy Power Grid
11.3.3 DC Power Grid Requirements Discussion
11.3.4 High-Level Technical Description of the DC Power Grid System
11.3.5 High-Level Technical Requirements for the DC Grid System
11.3.6 Assignments
References
12: Requirements Composition
12.1 Requirements: The WHAT of Systems Design
12.2 Writing SMART Requirements
12.2.1 SMART Requirements Are Specific
12.2.2 SMART Requirements Are Measurable
12.2.3 SMART Requirements Are Attainable
12.2.3.1 Case Study: Maintenance Nightmare
12.2.4 SMART Requirements Are Realistic
12.2.5 SMART Requirements Are Testable
12.3 Requirements: The Good and the Bad
12.3.1 User Interface Requirements
12.3.2 Technical Requirements
12.3.3 Quality Requirements
12.3.4 Performance Requirements
12.3.5 Constraint/Assumption Requirements
12.4 Additional Considerations for Writing Requirements
12.4.1 Correct Requirement Language
12.4.2 Clear Requirement Language
12.4.3 Concise Requirement Language
12.4.4 Complete Requirement Language
12.5 Final Thoughts on Writing Good Requirements
12.5.1 Design Problem
12.5.2 Design Problem Description: Alternative Energy Power Grid
12.5.3 DC Power Grid Requirements Discussion
12.5.4 High-Level Technical Description of the DC Power Grid System
12.5.5 High-Level Technical Requirements for the DC Grid System
12.5.6 Assignments
References
13: Requirements Traceability
13.1 The Need for Requirement Traceability
13.2 The Requirements Traceability Hierarchy
13.3 Requirements Traceability Best Practices
13.3.1 Unique Requirement Identifiers
13.3.2 Traceability Ownership
13.3.3 Traceability Update Consistency
13.4 The Requirements Traceability Matrix (RTM)
13.5 The Requirement Traceability Tools
13.5.1 Design Problem
13.5.2 Design Problem Description: Alternative Energy Power Grid
13.5.3 DC Power Grid Requirements Discussion
13.5.4 High-Level Technical Description of the DC Power Grid System
13.5.5 High-Level Technical Requirements for the DC Grid System
13.5.6 Assignments
References
14: Requirements Change Management
14.1 Change Management Vs. Configuration Management
14.2 RCM and Agile Development
14.3 Requirements and Change History
14.4 The Perils of Deleted Requirements
14.5 Case Study: Satellite Launch Systems RCM Gone Wrong: Early 1990’s Satellite Launch
14.6 Final Thoughts on Change Management
14.6.1 Design Problem
14.6.2 Design Problem Description: Alternative Energy Power Grid
14.6.3 DC Power Grid Requirements Discussion
14.6.4 High-Level Technical Description of the DC Power Grid System
14.6.5 High-Level Technical Requirements for the DC Grid System
14.6.6 Assignments
References
15: Requirements Agility
15.1 The Agile Development Cycle
15.2 Case Study: The Disruptive MDRE Engineer
15.3 Establishing Agile Requirements Management Goals
15.4 Case Study: Scaling MDRE Processes within Large Agile Development Projects
15.5 Requirements Agility in an Agile World
15.5.1 Design Problem
15.5.2 Design Problem Description: Alternative Energy Power Grid
15.5.3 DC Power Grid Requirements Discussion
15.5.4 High-Level Technical Description of the DC Power Grid System
15.5.5 High-Level Technical Requirements for the DC Grid System
15.5.6 Assignments
References
16: Requirements Anti-Patterns
16.1 High-Level Requirements Management Anti-Patterns
16.1.1 Design Problem
16.1.1.1 Design Problem Description: Alternative Energy Power Grid
16.1.1.2 DC Power Grid Requirements Discussion
16.1.1.3 High-Level Technical Description of the DC Power Grid System
16.1.1.4 High-Level Technical Requirements for the DC Grid System
16.1.2 Assignments
References
17: Model-Based Systems Engineering
17.1 The Basics of Model-Based Systems Engineering
17.2 MBSE Modeling Languages
17.3 System Architecture Modeling Frameworks
17.3.1 The Zachman Modeling Framework
17.3.2 The Department of Defense Architecture Framework (DoDAF)
17.3.3 The Open Group Architectural Framework (TOGAF)
17.3.4 The Ministry of Defense Architecture Framework (MODAF)
17.3.5 The International Defense Enterprise Architecture Specification (IDEAS)
17.3.6 The Unified Modeling Language (UML)
17.3.7 The System Modeling Language (SysML)
17.4 MDRE in a Model-Based Systems Engineering Environment
17.4.1 Design Problem
17.4.2 Design Problem Description: Alternative Energy Power Grid
17.4.3 DC Power Grid Requirements Discussion
17.4.4 High-Level Technical Description of the DC Power Grid System
17.4.5 High-Level Technical Requirements for the DC Grid System
17.4.6 Assignments
References
18: Conclusions and Discussion: Putting it all Together
18.1 When MDRE Goes Right
18.2 When MDRE Goes Wrong
18.3 Final Thoughts on MDRE and Agile Development
18.4 MDRE and the End of the “Paper Paradigm”
18.5 Organizational Changes for MDRE
18.5.1 The MDRE Organization
18.5.1.1 Design Problem
18.5.1.2 Design Problem Description: Alternative Energy Power Grid
18.5.1.3 DC Power Grid Requirements Discussion
18.5.1.4 High-Level Technical Description of the DC Power Grid System
18.5.1.5 High-Level Technical Requirements for the DC Grid System
18.5.1.6 Assignments
References
Index
