1. Michael deLamare Requirements Management Program Functions R-9

2. Need for Requirements Management Reliance on the intelligent informed individual (People over Process) Staff Turnover and long projects Many requirements from multiple stakeholders that staff are expected to know Contract, Laws, regulations, interfacing facilities, etc. Easily exceed 10,000 Requirements are not implemented in design They do not systematically flow down to design or to suppliers. Requirements changes are not well understood prior to approval Leads to unanticipated schedule delays and unexpected cost growth. Requirements are incomplete, unclear and subject to widely varying interpretations. Unable to justify requirements readily Difficulty verifying requirements were met. 2

3. Important Considerations for Establishing a Program Learn from Industry ISO 29148, ISO 15288, etc. Recognize that RM is an enterprise process not just bookkeeping Must be intertwined with system development processes Key Systems Engineering concepts are needed Clear roles, responsibilities accountabilities & authorities Process over tools 3

4. Arriving at Recommendations 4 Recommendations Voice of the Customer Project Gaps and Issues Process Failure Modes Best Practices Project Process Design

5. Key Concept: Document Hierarchy 5

6. Key Concept: “V” Model Plant/Facility Requirements System/ Structure Requirements Component Requirements Plant/Facility Validation System/ Structure Verification Component Verification © 2012 Bechtel | 6

7. Key Concept: Technical Requirement Areas 7 Technical Areas Architectural Design Environmental Permitting Civil Design Nuclear Safety, Criticality, ALARA Controls & Instrumentation Design Constructability Electrical Design Operations, Maintenance, Human Factors HVAC Personnel Safety Mechanical Design Packaging, Handling, Storage and Transportation Mechanical Handling Design Security Plant Design System Support Process (Chem) Interface (External) Structural Design Interface (Internal) Environmental Conditions Mission Fire Protection Plant Capability Materials engineering System Functions and Requirements Plant Software Design Reliability, Availability, Maintainability Seismic These technical requirements areas need to be recognized when developing requirements

8. High Ranked Program Needs Baseline Requirements Responsible requirement owners Interpretive authority Requirements validation Two-way traceability down to the appropriate level Enable change impact analysis Protect assumptions/requirements Support Procurement Support Verification 8

9. Requirements Management Process Managed Rqmts Baseline Validated Traceable Verified Rqmts Metrics RM Functions Identify and Document Analyze and Allocate Control Change Verify Compliance Oversight OutputsInputs Contract Client Specifications Operational Concepts Laws/Regs Permits Etc. © 2012 Bechtel | 9 These are a proposed set of RM Functions

10. Requirements Management Functions Identification and Documentation – Identify/Elicit Requirements – Document Requirements Analysis and Allocation – Analyze Requirements – Validate Requirements – Allocate Requirements – Trace Requirements – Document Analysis and Allocation Change Control – Control Change Verification – Verify Compliance Process Oversight – Organize Requirements – Balance and Integrate Requirements – Manage Process 10 These Functions establish and maintain a Project Requirements Baseline

11. Questions? 11