SYSTEMS ENGINEERING Flashcards
Successful organizations, large and small, need to think both
operationally and strategically
Operational thinking relates to ___________________ operations
“business as usual”
Strategic thinking relates more to (lti, o, d)
longer term imperatives,
opportunities, and direction.
Gaps in organizational capability may be a problem because
Gaps prevent achieving strategic objectives
Gaps prevent exploiting opportunities
Gaps open potential threats
Examples of organizations and their capability gaps
(ICGM)
- Individuals with personal capability gaps
- Commercial businesses with business-related gaps
- Government organization with a gap in government services
- Military organization with a gap relating to military capability shortfalls
Conceptual Design Steps
(D-Dst-Dsy-Csl-Csd)
C1. Define business needs and requirements/BNR
C2. Define stakeholder needs and requirements/SNR
C3. Define system requirements.
C4. Conduct system-level synthesis.
C5. Conduct System Design Review (SDR)
C1. Define business needs and requirements (IESEF)
Identify stakeholders
Elicit needs
Scope system
Extract requirements
Finalize requirements
T or F: Stakeholders involved in the early stages of conceptual design are generally limited to those who have a right to affect the system
True
Stakeholders may include: MEMLUC
Management
Engineering/technical
Maintenance
Logistics
Users
Clients
Types of Constraints (BPED)
○ Business constraints
○ Project constraints
○ External constraints
○ Design Constraints
In eliciting business needs, (Dmgo-Ds-Dvc-Dlc)
Define mission, goals, objectives (MGO)
Develop scenario on system usage
Develop validation criteria
Define lifecycle concepts
It is important for business stakeholders to explain expectations on how the system will be (OADSD)
Operated
Acquired
Deployed
Supported
Disposed
When finalizing on business requirements
Update and record the Business Needs and Requirements (BNR)
○ Preliminary Lifecycle Concept Document (PLCD)
○ Business Requirements Specifications (BRS)
C2. Define stakeholder needs and requirements. (DDF)
▪ Define stakeholder needs
▪ Define stakeholder requirements
▪ Finalize stakeholder needs and requirements
C3. Define system requirements. (Erf-Praa-Dsy-Csr)
▪ Establish a requirements framework
▪ Perform requirements analysis and allocation
▪ Draft the System Requirements Specification (SyRS)
▪ Conduct System Requirements Review (SRR)
What question is asked to Determine functional/non-functional requirements
What does the system need to be able to
do?
What question is asked to Define performance requirements?
○ What other characteristics are required
○ What other systems are involved
What question is asked to Define verification requirements?
○ Have we built the system right?
○ Have we built the right system?
C4. Conduct system-level synthesis. (DPCP)
▪ Draft System Requirements Specification
▪ Potential solutions are proposed against the SyRS
▪ Compliance level, options, and other information considered
▪ Preferred solution selected
C5. Conduct System Design Review/SDR (RRTP)
▪ Review the proposed solution.
▪ Review the refined SyRS,
▪ the traceability back to the Stakeholder requirements Specification (StRS), and
▪ the planning that has been put in place to execute and manage the technical program
Preliminary Design
Define the system elements
Perform requirement analysis and allocate requirements to the elements
What are the sub-system options in preliminary design?
▫ Off-the-shelf (OTS)
▫ Modified off-the-shelf (MOTS)
▫ Developmental
Advantages of OTS
Known function
Known performance
Availability
Known costs
Disadvantages of OTS (TO)
Technical documentation
Obsolescence
