Requirements Management Program Functions

Download Report

Transcript Requirements Management Program Functions

Requirements Management
Program Functions
R-9
Michael deLamare
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
Important Considerations for
Establishing a Program
•
Learn from Industry
•
•
Recognize that RM is an enterprise process
•
•
not just bookkeeping
Must be intertwined with system development
processes
•
•
ISO 29148, ISO 15288, etc.
Key Systems Engineering concepts are needed
Clear roles, responsibilities accountabilities &
authorities
• Process over tools
3
Arriving at Recommendations
Best
Practices
Voice
of the
Customer
Project Gaps
and Issues
Process
Failure
Modes
4
Project
Process
Design
Recommendations
Level 3
Functional Baseline
(Requirements)
Level 2
Level 1
Level 0
Technical Requirements
Technical Requirements
Regulatory and Agency
Baseline (Stakeholder Level) Baseline (Contract Level)
Key Concept: Document Hierarchy
5
Laws
Regulations
Client
Directives
Contract
(Client/BSII)
Contract
Change
Letters
Contractually
Imposed
Documents
Regulatory
Permits*
External
Interface
Documents
License/
Authorization
Basis
Documents*
Permits issued to the client
Functional
Specification/
Basis of
Design
Integrated Facility
DisciplineSpecific
Design
Criteria
Client Mission
Definition
Key Concept: “V” Model
Plant/Facility
Requirements
System/
Structure
Requirements
Component
Requirements
© 2012 Bechtel | 6
Plant/Facility
Validation
System/
Structure
Verification
Component
Verification
Key Concept: Technical Requirement Areas
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
Packaging, Handling, Storage and
Mechanical Design
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
These technical requirements areas need to
Reliability, Availability, Maintainability be recognized when developing requirements
Seismic
7
High Ranked Program Needs
•
•
•
•
•
•
•
•
•
8
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
Requirements Management Process
RM Functions
• Identify and Document
Inputs
• Analyze and Allocate
Outputs
• Control Change
• Contract
• Client Specifications
• Verify Compliance
• Oversight
• Validated
• Operational Concepts
• Laws/Regs
• Permits
• Etc.
© 2012 Bechtel | 9
• Managed
Rqmts Baseline
These are a proposed set of
RM Functions
• Traceable
• Verified Rqmts
• Metrics
Requirements Management Functions
•
10
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
These Functions establish and
maintain a Project
Requirements Baseline
Questions?
11