Technical Processes Flashcards
Is “Initial RVTM” an output of 4.1 ?
No, only a Preliminary validation criteria.
Page 146
Which process does “project constraints” come from in the IPO diagram of 4.1?
5.1 Project Planning Process
Page 146
“We have to establish a comprehensive set of alternative solution classes in the activity of ‘defining the problem or opportunity space’ during the business or mission analysis process (4.1) .” True or false.
False. We have to do it in the activity of “characterizing the solution space”.
Page 148
What are the definitions of needs and requirements for a system?
For a system, needs are often capabilities or things that are lacking but wanted or desired by one or more stakeholders, and requirements are formal structured statements that can be verified and validated.
Page 140
What are the 14 technical processes?
- Business or mission analysis process
- Stakeholder needs and requirements definition process
- System requirements definition process
- Architecture definition process
- Design definition process
- System analysis process
- Implementation process
- Integration process
- Verification process
- Transition process
- Validation process
- Operation process
- Maintenance process
- Disposal process
Page 142-144
What concepts are included within the preliminary life cycle concepts?
Acquisition concept, deployment concept, operational concept (OpsCon), support concept, and retirement concept.
Page 142
What are the 3 purposes stated in ISO/IEC/IEEE 15288 for 4.1 ?
- To define the business or mission problem or opportunity
- To characterize the solution space
- To determine potential solution class(es) that could address a problem or take advantage of an opportunity.
Page 146
Do we have to nominate major stakeholders to be involved in the retirement of the solution during 4.1?
Yes, business owners nominate the major stakeholders who are to be involved in the acquisition, operation, support, and retirement of the solution.
Page 148
What’s the main distinction between ConOps (concept of operations) and OpsCon (operational concept) ?
ANSI/AIAA G-043A-2012 notes that an important distinction exists in that each has a separate purpose and is used to meet different ends. The ConOps is developed by/for the leadership at the enterprise level of the organization using the SOI, addressing the leadership’s intended way of operating the organization. The OpsCon is prepared at the business level, a user-oriented document that describes system characteristics of the to-be-delivered system from the user’s viewpoint.
Page 150-152
Is it true that the purpose of 4.2 is to define the stakeholder requirements for a system in whatever environment?
No, it shall be a defined environment.
Page 154
What are the 4 “preliminary” inputs of 4.2?
Preliminary life cycle concepts, preliminary validation criteria, preliminary MOE needs and preliminary MOE data.
Page 158
What are included in stakeholder validation criteria?
It includes measures of effectiveness (MOEs) and measures of suitability (MOSs).
Page 160
What is the reason for eliciting and analyzing requirements?
To understand the needs of the stakeholders well enough to support the architecture definition and design definition processes.
Page 162
Do engineers need to consider stakeholders of enabling systems when identifying stakeholders?
Yes, same as stakeholders of interoperating systems, these will also impose constraints that need to identified and considered.
Page 162
Where can the outputs of the stakeholder needs and requirements definition process be captured?
These outputs can be captured in life cycle concept documents (particularly the OpsCon) and the StRS.
Page 164
Please think of some techniques for requirements elicitation.
Interviews, focus groups, the Delphi method, and soft systems methodology etc.
Page 166
If you have to cope with the uncertainty, what are the essential tools you can use?
Scenarios and what-if thinking.
Page 166
What is the primary goal of a concept document?
To capture, early in the system life cycle, an implementation-free understanding of stakeholder needs by defining what is needed, without addressing how to satisfy the need.
Page 168
Do we need to define a complete OpsCon or to allocate functions to hardware or software elements at the stage of developing life cycle concepts?
No, this comes later during architectural design.
Page 170
Is it true that the purpose of the 4.3 is to transform the stakeholder, user-oriented view of desired capabilities into a technical view of a solution that meets the operational needs of the customer?
No, is to meets the operational needs of the user.
Page 172
Is “stakeholder requirements traceability” necessary in 4.3?
Yes, the output of the process must be compared for traceability to and consistency with the stakeholder requirements, without introducing implementation biases, before being used to drive the architecture definition process.
Page 174
What are included in system verification criteria?
It includes measures of performance (MOPs) and technical performance measures (TPMs).
Page 178
What can be employed during requirements definition and analysis?
This complex process employs performance analysis, trade studies, constraint evaluation, and cost-benefit analysis.
Page 180
Is requirements definition and analysis a “top-down” or a “bottom-up” process?
Both. Once the top-level set of system requirements has been established, it is necessary to allocate and flow them down to successively lower levels. As the allocation and flow-down process is repeated, it is essential that traceability be maintained to ensure that all system level requirements are satisfied in the resulting design.
Page 180
What are the necessary constraints that need to be reflected during requirements definition and analysis?
Standards, utilization environments, essential design considerations and design constraints.
Page 180-182
What are the characteristics should be considered for every requirement?
It should be necessary, implementation independent, unambiguous, complete, singular, achievable, verifiable and conforming.
Page 182-186
What are the characteristics should be considered for a set of requirements as a whole?
The set of requirements should be complete, consistent, feasible/affordable and bounded.
Page 186
Individual requirement statements may have a number of attributes attached to them, what are they?
Trace to parent, trace to source, trace to interface definition, trace to peer requirements, trace to verification method, trace to verification requirement(s), trace to verification results, requirements verification status, requirements validation status, priority, criticality, risk, key driving requirement (KDR), owner, rationale, applicability and type.
Page 188-192
What is the primary focus through System Requirement Review (SRR)?
Defining, deriving, and refining functional and performance requirements apply to the total system over its life cycle.
Page 192
What is the purpose of the Architecture Definition process?
To generate system architecture alternatives, to select one or more alternative(s) that frame stakeholder concerns and meet system requirements, and to express this in a set of consistent views.
Page 196