12 Systems Engineering Lifecycle Design Steps
1. Formulate the Problem Statement
1.1 Identify Key Design Decisions
1.2 Choose Use Cases to Support
1.3 List of Customers / Entities (Internal and External)
1.4 Define System Boundary
2. Elaborate Use Cases into Steps
3. Identify Customer Needs (CNs) based on Use Cases
4. Translate Customer Needs and Use Case Steps to Functional Requirements (FRs) and FR Measures (FRms)
5. Generate Physical Solution Alternatives (PS-ALT)
6. Choose PS to achieve FR and decompose to next level when design is acceptable
7. Model System Behavior
8. Develop Risk Mitigation Approach
8.1 Conduct Design FMEA
8.2 Develop Process FMEA
9. Develop Test Verification Plan
10. Apply DFMA principles to determine the manufacturability of your design
11. Define Normal Operating Condition with Standard Work
12. Look for Gaps or White Space in the Design and feedback results
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 1
Exercise – Step 1
1. Formulate Problem Statement 1.4 Draw the System Boundary
1.1 Identify Key Design Decisions
1.2 Choose Use Cases to Support
1.3 List Internal and External Customers
Internal:
System Boundary
External:
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 2
Exercise – Step 2
2. Elaborate Use Cases into Steps
Step
2
And
Step
Step 1 Loop And Loop
4
Step
3
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 3
Exercise – Step 3
3. Identify Customer Needs (CNs) based on Use Cases
-
-
-
-
Customer Needs Use Case
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 4
Exercise – Step 4
4. Translate Needs and Use Case Steps to FRs and FRms
Needs / Use Case Step Functional Requirement and FRm (how well)
- -
- -
- -
- -
- -
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 5
Step 4: Translate Customer Needs and Use Case Steps to FRs and FRms
Customer Needs
Use Case
Use Case Step
Functional Requirement
FRm
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 6
Step 5
5. Generate Physical Solution Alternatives (PS-ALT)
(remember, the designer chooses a PS!)
Functional Requirement PS-ALT
-FR1 -PS1.1
-PS1.2
-FR2 -
-
-FR3 -
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 7
Step 5: Exercise with Color-Coded Post-It Notes
An FR states what
we MUST achieve
Customer FRm
FR
Needs
Understood How Well?
from Use Cases
PS-
PS-
PS-ALT
A PS is a
hypothesis
to achieve an FR
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 8
Step 5: Generate physical solution Alternatives (PS-ALT)
“Decision – Requirements Derivation” Hierarchy Diagram – “Decision” Class
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 9
Step 6
6. Choose PS to achieve FR and
decompose to the next level when
design is acceptable (i.e.,
uncoupled or path-dependent)
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 10
Step 7: Model System Behavior
This diagram is one example of
System Behavior Modelling
Model FRs to define requirements
associated with:
• Flow logic (dependencies)
• Inputs/outputs
Check each FR description to ensure
that it accounts for transformation of
inputs into outputs.
Look for input/output “loose ends”
Item Flow Logic: Matter, energy or information as
inputs to or outputs from a FR
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 11
Step 8.1: Conduct Design FMEA
FMEA Basic Report
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 12
Step 8.2: Develop Process FMEA + Derived Requirements from Mitigation
Process FMEA
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 13
Step 9: Develop Test Verification Plan
Verification Plan Hierarchy Diagram - "FRm" Class
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 14
Steps 10 - 12
PS10 – DFM and DFA and the implications on your design
- Input for Design for Manufacturing/Assembly
PS11 - How will you train someone to use your product?
- Standardization
- Guidelines
PS12 - Look for Gaps or White Space in the Design and feedback results
- are there any points not yet covered in the design?
Systems Engineering Project, Dr.-Ing. Erwin Rauch, Prof. Dr. David Cochran 15
