Systems Engineering V4
9 important questions on Systems Engineering V4
What kind of stakeholders are there? (SAVAGE)
- „Supportive“
- „Marginal“
- „Nonsupportive“
- „Mixed Blessing“
What is the process between a Stakeholder and System requirement?
Stakeholder Requirements -> (translation) System Requirements= a process
- Interviews with (potential) users
- Accompany during work
- Analyze similar or existing systems
- Review reports with suggestions and problems
- Requirements of user service/support
- Improvement by users
- Unplanned use
- Workshops
- Modeling (scenarios, environment, structure …)
- Prototypes
- Use-cases
What is a RVTM?
- List of requirements, their verification attributes and traces
- Includes proposed changes
Outputs:
• Stakeholder needs and
requirements definition strategy
• Life cycle concepts
• System function identification
• Stakeholder requirements
• Validation criteria
• MOE needs
• MOE data
• Stakeholder requirements traceability
• Initial RVTM
• Stakeholder needs and
requirements definition record
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
What is a Systems Requirement Document (SRD)?
-> represent the customer/user requirement
Describes the requirements of the stakeholder not the system!
What are the activities in the Stakeholder needs and requirements definition process? (Part one of translation)
Process activities:
• Prepare for stakeholder needs and requirements definition
• Define stakeholder needs
• Develop the operational concept and other life cycle concepts
• Transform stakeholder needs into stakeholder requirements
• Analyze stakeholder requirements
• Manage the stakeholder needsand requirements definition
Describe the communication during the requirements elicitation.
Describe the 'Measure of performance' (Outputs).
- Characterization of physical or functional attributes relating to the system operation
- Measured or estimated under specific testing and/or operational environment conditions.
Possible outputs:
• System requirements definition strategy
• System function definition
• System requirements
• System functional interface identification
• Verification criteria
• MOP needs
• MOP data
• System requirements traceability
• Updated RVTM
• System requirements definition record
What makes a requirement a good requirement?
- Necessary
- Implementation Independent
- Clear and Concise
- Complete
- Consistent
- Achievable
- Traceable
- Verifiable
Quantify whenever possible!
How to implement 'In-Process Validation'?
- Possible at any “time now” of the development process
- “Do we develop in the right direction?”
- “Does the system status fulfill expectations?”
- Comparison with the customer
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding