Lecture-03 Flashcards
Sys Life Cycle, Materialization, Sys Eng Methods
System Life Cycle
Concept Dev > Engineering Dev > Post Development
Concept Dev: 3 Steps
1. Needs Analysis
2. Concept Exploration
3. Concept Definition
- Needs Analysis: System Studies, Tech Assessment and Operational Studies.
- Concept Exploration: Requirement Studies, Concept Synthesis, Feasibility experiments
- Concept Definition: Analysis of Alternatives, Functional & Physical Architecture
Needs Analysis + Concept Exploration = Feasibility Studies
So, System life cycle starts with Feasibility Studies
2nd Stage of Life cycle is Engineering Development. It has 3 parts.
- Advanced Development
- Engineering Design
- Evaluation and Integration
2nd Stage of Life cycle is Engineering Development. It has 3 parts.
1. Advanced Development
2. Engineering Design
3. Evaluation and Integration
- Advanced Development: Risk Management, Subsystem Def, Component Specs.
- Eng Design: Component Eng, Compo tests, Specialty Tests
- Eval & Integration: System integration and Testing, Operational Evaluation.
2nd Stage of Life cycle is Engineering Development. Its first step Advanced Development finishes with Component Specifications.
In Its second Step (Engineering Design), the specifications are turned into Prototypes (Component testing and engineering)
The Last and 3rd Stage of Life Cycle is Post Development.
In Post Development, Operational and Maintenance Documentation and Installation is covered.
Evolution of Systems Materialization through System Life Cycle: Slide 14 (Very Important)
For Example, Requirement Analysis and Feasibility are done in Subsystem Level in Concept Exploration Substage.
Concept is validated in Advanced Development Substage in System Level and Specification is defined in Component Level.
System Engineering Method has 4 Basic Steps.
I. Requirements analysis : identifies why requirements are needed.
II. Functional definition: translates requirements into functions.
III. Physical definition: synthesizes alternative physical implementations
IV. Design validation: models the system environment
First Step of System Engineering Method: Requirements Analysis
(i) Operational Requirements Analysis:
*Understand the operational requirements
*Identify and resolve problems with the operational requirements.
–Conflicts
–Incomplete requirements
–Obviously expensive/impossible
(ii) Provide feedback to the users:
*Request clarifications
*Recommend changes
First Step of System Engineering Method: Requirements Analysis
(i) Operational Requirements Analysis: Mission and purpose of the system.
Requirements elicitation: is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders.
* Users and operators (via market survey and interviews)
* Subject matter experts
* Previous studies and system development efforts
Requirements analysis:-
*Check if the requirements are “valid”, “feasible”, “vague” or “inconsistent”
*Avoid any “redundant” requirements.
Requirements Elicitation Techniques:
1. Interviews
2. Surveys/Questionnaires
3. Document Analysis
4. Observation
5. Brainstorming
- Prototyping
- Use Cases
- Scenarios
- Workshops
- Storyboarding
2nd Step of System Engineering Method: Functional Definition (there are four steps in sys eng method)
Functional Definition
–Determine System requirements: Go to 1st subsystem level if needed.
–Determine required performance
–Define top level scope of system.
2nd Step of System Engineering Method: Functional Definition (there are four steps in sys eng method)
Translate requirements (why) into functions (actions and tasks) that the
system must accomplish (what)
* Partition (allocate) requirements into functional building blocks
* Define interactions among functional elements to lay a basis for their organization into a modular configuration.
The distinctions among objectives, requirements and functions are tedious.
Objective : tends to be at higher level
Requirement : tends to be more technical with various types
Function : context of functional build blocks