Systems Engineering
- A way to translate customer needs into requirements and to spread the requirements in all relevant functions
- When spreading the requirements it is crucial that they are complete, i.e. all functions and specifications from different parts are considered and included, to fulfil the end function of the product
Comparing Traditional engineering with systems engineering
Traditional Engineering
- Serial development
- Reactive, iterative
downstream emphasis
Design-Build-Fix
Systems Engineering
- Iterative focus up front
- Serial verification
Design-Analyse-Build-Verify
We are recommending systems engineering since we regard it as being quicker and less risky
When using Systems Engineering you focus on tests and evaluations early in the project using calculations and tests of subsystems
Simple/Not complex product
A not so complex solution =>
Systems Engineering needs to be performed on an overview level
Complex product
The more complex a solution is the more Systems Engineering needs to be performed on a detailed level
Using systems engineering is especially important when the design is physical combined with digital which is more and more the case.
The two different worlds need to seamlessly work together
Problems to address
- Prerequisites not completed and well-defined
- Requirements not balanced between stakeholders
- Requirements not measurable and prioritised
- Concept selection not balanced with requirements
- Late changes creating loops and delays
Benefits
- Stakeholder needs are met
- Well-defined/balanced Quality, Delivery, Cost and Feature (QDCF) targets
- Systematic design of complex systems with multifaceted interactions
- Proactive system design focus avoiding loops and delays
