Ch4 Technical Processes Flashcards

1
Q

Why are technical processes important?

A

Because they enable system engineers to coordinate the interactions between engineering specialists, other engineering disciplines, system stakeholders and operators, and manufacturing. They also address conformance with the expectations and legislated requirements of society.
Without the technical processes, the risk of project failure would be unacceptably high.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What’s the definition of needs?

A

For a system, needs are often capabilities or things that are lacking but wanted or desired by one or more stakeholders.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What’s the definition of requirements?

A

Requirements are formal structured statements that can be verified and validated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How many technical processes are there and which ones are they?

A

14:
Business or mission analysis,
Stakeholder needs and requirements definition,
System requirements definition,
Architecture definition,
Design definition,
System analysis,
Implementation,
Integration,
Verification,
Transition,
Validation,
Operation,
Maintenance,
Disposal.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the purpose of the Business or mission analysis?

A

Define the problem domain;
identify major stakeholders;
identify environmental conditions and constraints that bound the solution domain;
develop preliminary life cycle concepts for acquisition, operations, deployment, support, and retirement;
develop business requirements and validation criteria.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the “concept of operations”, or ConOps?

A

The ConOps addresses the leadership’s intended way of operating the organization. It describes the organization’s assumptions or intent in regard to an overall operation or series of operations of the business with using the system to be developed, existing systems, and possible future systems. The ConOps document serves as a basis for the organization to direct the overall characteristics of the future business and systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the “operational concept”, or OpsCon?

A

The OpsCon describes what the system will do and why. It is user-oriented and describes the system characteristics of the to-be-delivered system from the user’s viewpoint. It is used to communicate overall quantitative and qualitative system characteristics to the acquirer, user, supplier and other organizational elements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the main differences between the ConOps and OpsCon?

A

Both are prepared by the organization that has the business need for the SOI. However, the ConOps is prepared by/for the leadership at the enterprise level and is written from a business/strategy perspective, while the OpsCon is prepared at the business level and is written from an operational perspective. Furthermore, the OpsCon may be iteratively refined as a result of feedback during the system requirements and architecture definition processes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is a stakeholder?

A

Any entity (individual or organization) with a legitimate interest in the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the purpose of the Stakeholder Needs and Requirements Definition process?

A

Identify the stakeholders;
Elicit the stakeholder needs;
Analyze these needs and operational scenarios;
Transform stakeholder needs into requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Why are stakeholder requirements important?

A

Because they are the primary reference against which the operational capability is validated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Which practical artifacts are dependent on a proper Stakeholder Needs and Requirement Definition process?

A

OpsCon;
StRS;
SOW (statement of work);
RFP (request for proposal);
acquisition concept;
deployment concept;
support concept;
retirement concept.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the purpose of the System Requirements Definition process?

A

To generate a set of technical requirements from the supplier’s perspective; such set shall be complete but minimum, since each requirement carries a cost. The requirements shall specify the system characteristics, attributes, functions, and performance that will meet the stakeholder requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Which are the important characteristics and attributes of good requirements?

A

Necessary;
Implementation independent;
Unambiguous;
Complete;
Singular;
Achievable;
Verifiable;
Conforming.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the purpose of the Architecture Definition process?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the difference between architecture and design activities?

A

System architecture is more abstract, conceptualization oriented, global. focused to achieve the mission and OpsCon of the system, and focused on high-level structure in systems and system elements.
System design is more technology oriented through physical, structural, environmental, and operational properties forcing decisions for implementation by focusing on compatibility with technologies and other design elements and feasibility of construction and integration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What is emergence?

A

The principle that whole entities exhibit properties, which are meaningful only when attributed to the whole, not to its parts. Emergent properties can be desirable and undesirable. The latter shall be avoided, with help of analysis of interaction between entities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What are coupling matrices (or N2 matrices?).

A

A basic method to define the aggregates and the order of integration. Used during architecture definition, with the goal of keeping the interfaces as simple as possible.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is the purpose of the Design Definition process?

A

To provide sufficient detailed data and information about the system ad its elements to enable the implementation consistent with architectural entities as defined in models and views of the system architecture.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is holistic design?

A

An approach to design that considers the system being designed as an interconnected whole, which is also part of something larger. Holistic design is about more than merely trying to meet the system requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is the purpose of the System Analysis process?

A

To provide a rigorous basis of data and information for technical understanding to aid decision-making across the life cycle.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is the purpose of the Implementation process?

A

To realize a specified system element.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What is the purpose of the Integration process?

A

To synthesize a set of system elements into a realized system (product or service) that satisfies system requirements, architecture , and design.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Describe the global integration technique.

A

A.k.a. “big bang” integration, all system elements are assembled in one step.
+ simple;
+ does not require simulation;
- difficult to detect and locate faults;
- interface faults detected late.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Describe the integration “with the stream” technique.

A

The system elements are assembled as they become available.
+ quick start of integration;
- complex to implement due to simulation needs;
- impossible to control functional chains end-to-end;
- global tests postponed very late.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Describe the incremental integration technique.

A

A few system elements are added to an already integrated increment of system elements in a predefined order.
+ allows fast localization of faults;
- requires simulators for absent system elements;
- requires many test cases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Describe the subset integration technique.

A

System elements are assembled by subsets, and then subsets are assembled together.
+ saves time due to parallel integration of subsets;
+ enables delivery of partial product;
+ requires less means and fewer test cases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Describe the top-down integration technique.

A

System elements or aggregates are integrated in their activation or utilization order.
+ availability of a skeleton of the system possible;
+ early detection of architectural faults;
+ definition of test cases close to reality;
+ possible reuse of data set;
- necessity to create many stubs/caps;
- difficult to define test cases of leaf system elements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Describe the bottom-up integration technique.

A

System elements or aggregates are integrated in the opposite order of their activation or utilization.
+ easy definition of test cases;
+ early detection of faults (in leaf elements);
+ reduced number of simulators used;
- test cases to be redefined for each step;
- drivers are difficult to define and realize;
- lower-level elements are overtested;
- no quick detection of architectural faults.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Describe the criterion-driven integration technique.

A

The most critical system elements (w.r.t. a chosen criterion) are firstly integrated.
+ allows early testing;
+ allows for early verification of architecture and design choices;
- difficult to define test cases;
- difficult to define data sets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

What is the purpose of the Verification process?

A

To provide objective evidence that a system or system element fulfils its specified requirements and characteristics.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

What is the difference between verification and validation?

A

Verification is intended to ensure that the “product is built right”, while validation is intended to ensure that the “right product is built”.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

List the basic verification techniques.

A

1) Inspection;
2) Analysis;
3) Demonstration;
4) Test;
5) Analogy or similarity;
6) Simulation;
7) Sampling.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

What is the purpose of the Transition process?

A

To establish a capability for a system to provide services specified by stakeholder requirements in the operational environment. Ultimately, it enables the transfer of custody of the system and responsibility for system support from one organizational entity to another.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

What is the purpose of the Validation process?

A

To provide objective evidence that the system, when in use, fulfils its business or mission objectives and stakeholder requirements, achieving its intended use in its intended operational environment.

36
Q

What is “acceptance”?

A

An activity conducted prior to transition such that the acquirer can decide that the system is ready to change ownership from supplier to acquirer.

37
Q

What is “certification”?

A

A written assurance that the product or article has been developed, and can perform its assigned functions, in accordance with legal or industrial standards. Certification is typically performed by outside authorities.

38
Q

What is “readiness for use”?

A

An assessment performed by the project team, to establish whether the system is ready for use.

39
Q

What is “qualification”?

A

A process that has to demonstrate that the characteristics or properties of the realized system, including margins, meet the applicable system requirements and/or stakeholder requirements. It is concluded by an acceptance review and/or operational readiness review.

40
Q

What is the purpose of the Operation process?

A

To use the system to deliver its services.

41
Q

What is the purpose of the Maintenance process?

A

To sustain the capability of the system to provide a service.

42
Q

What is the purpose of the Disposal process?

A

To end the existence of a system element or system for a specified intended use, appropriately handle replaced or retired elements, and to properly attend to identified critical disposal needs.

43
Q

What are the inputs of the Business or mission analysis process?

A
  • Organization strategic plan
  • ConOps
  • Source documents
  • Life cycle constraints
  • Project constraints
  • Stakeholder requirements traceability
44
Q

What are the activities of the Business or mission analysis?

A
  • Prepare for business or mission analysis
  • Define the problem or opportunity space
  • Characterize the solution space
  • Evaluate alternative solution classes
  • Manage the business or mission analysis
45
Q

What are the outputs of the Business or mission analysis process?

A
  • Business or mission analysis strategy
  • Major stakeholder identification
  • Preliminary life cycle concepts
  • Problem or opportunity statement
  • Business requirements
  • Alternative solution classes
  • Preliminary validation criteria
  • Preliminary MOE needs
  • Preliminary MOE data
  • Business requirements traceability
  • Business or mission analysis record
46
Q

What are the inputs of the Stakeholder needs and requirements definition process?

A
  • Source documents
  • Project constraints
  • Major stakeholders identification
  • Preliminary life cycle concepts
  • Problem or opportunity statement
  • Business requirements
  • Alternative solution classes
  • Preliminary validation criteria
  • Validated requirements
  • Preliminary MOE needs
  • Preliminary MOE data
  • Business requirements traceability
  • Life cycle constraints
  • Stakeholder needs
  • System requirements traceability
47
Q

What are the activities of the Stakeholder needs and requirements definition process?

A
  • 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 needs and requirements definition
48
Q

What are the outputs of the Stakeholder needs and requirements definition process?

A
  • 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
49
Q

What are the inputs of the System requirements definition process?

A
  • Life cycle concepts
  • System function identification
  • Stakeholder requirements
  • Stakeholder requirements traceability
  • Initial RVTM
  • Architecture traceability
  • Final RVTM
  • Life cycle constraints
50
Q

What are the activities of the System requirements definition process?

A
  • Prepare for system requirements definition
  • Define system requirements
  • Analyze system requirements
  • Manage system requirements
51
Q

What are the outputs of the System requirements definition process?

A
  • 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
52
Q

What are the inputs of the Architecture definition process?

A
  • Life cycle concepts
  • System function definition
  • System requirements
  • System functional interface identification
  • System requirements traceability
  • Updated RVTM
  • Design traceability
  • Interface definition update identification
  • Life cycle constraints
53
Q

What are the activities of the Architecture definition process?

A
  • Prepare for architecture definition
  • Develop architecture viewpoints
  • Develop models and views of candidate architectures
  • Relate the architecture to design
  • Assess architecture candidates
  • Manage the selected architecture
54
Q

What are the outputs of the Architecture definition process?

A
  • Architecture definition strategy
  • System architecture description
  • System architecture rationale
  • Documentation tree
  • Preliminary interface definition
  • Preliminary TPM needs
  • Preliminary TPM data
  • Architecture traceability
  • Architecture definition record
55
Q

What is the definition of Measures of effectiveness (MOEs)?

A

Measures that define the information needs of the decision makers with respect to system effectiveness to meet operational expectations.

56
Q

What is the definition of Measures of performance (MOPs)?

A

Measures that define the key performance characteristics the system should have when fielded and operated in its intended operating environment.

57
Q

What is the definition of Technical Performance measures (TPMs)?

A

Measures that define attributes of a system element to determine how well a system or system element is satisfying or expected to satisfy a technical requirement or goal.

58
Q

What are the inputs of the Design definition process?

A
  • Life cycle concepts
  • System function definition
  • System requirements
  • System functional interface identification
  • System architecture description
  • System architecture rationale
  • Preliminary interface definition
  • Preliminary TPM needs
  • Preliminary TPM data
  • Architecture traceability
  • Interface definition update identification
  • Implementation traceability
  • Life cycle constraints
59
Q

What are the activities of the Design definition process?

A
  • Prepare for design definition
  • Establish design characteristics and design enablers related to each system element
  • Assess alternatives for obtaining system elements
  • Manage the design
60
Q

What are the outputs of the Design definition process?

A
  • Design definition strategy
  • System design description
  • System design rationale
  • Interface definition
  • TPM needs
  • TPM data
  • Design traceability
  • System element descriptions
  • Design definition record
61
Q

What are the inputs of the System analysis process?

A
  • Life cycle concepts
  • Analysis situations
  • Life cycle constraints
62
Q

What are the activities of the System analysis process?

A
  • Prepare for system analysis
  • Perform system analysis
  • Manage system analysis
63
Q

What are the outputs of the System analysis process?

A
  • System analysis strategy
  • System analysis report
  • System analysis record
64
Q

What are the inputs of the Implementation process?

A
  • Life cycle concepts
  • System architecture description
  • System architecture rationale
  • System design description
  • System design rationale
  • Interface definition
  • Design traceability
  • System elements descriptions
65
Q

What are the activities of the Implementation process?

A
  • Prepare for implementation
  • Perform implementation
  • Manage results of implementation
66
Q

What are the outputs of the Implementation process?

A
  • Implementation strategy
  • Implementation enabling system requirements
  • Implementation constraints
  • System elements
  • System element documentation
  • Operator/maintainer training materials
  • Implementation traceability
  • Implementation report
  • Implementation record
67
Q

What are the inputs of the Integration process?

A
  • Life cycle concepts
  • Interface definitions
  • System element descriptions
  • System elements
  • System element documentation
  • Implementation traceability
  • Accepted system or system element
68
Q

What are the activities of the Integration process?

A
  • Prepare for integration
  • Perform integration-successively integrate system element configurations until the complete system is synthesized
  • Manage result of integration
69
Q

What are the outputs of the Integration process?

A
  • Integration strategy
  • Integration enabling system requirements
  • Integration constraints
  • Integration procedure
  • Integrated system or system elements
  • Interface definition update identification
  • Integration report
  • Integration record
70
Q

What are the inputs of the Verification process?

A
  • Life cycle concepts
  • System requirements
  • Verification criteria
  • Updated RVTM
  • Interface definition
  • Integrated system or system elements
  • Integration report
71
Q

What are the activities of the Verification process?

A
  • Prepare for verification
  • Perform verification
  • Manage results of verification
72
Q

What are the inputs of the Transition process?

A
  • Life cycle concepts
  • Operator/maintainer training material
  • Final RVTM
  • Verified system
  • Verification report
73
Q

What are the activities of the Transition process?

A
  • Prepare for the transition
  • Perform the transition
  • Manage results of transition
74
Q

What are the outputs of the Transition process?

A
  • Transition strategy
  • Transition enabling system requirements
  • Transition constraints
  • Installation procedure
  • Installed system
  • Trained operators and maintainers
  • Transition report
  • Transition record
75
Q

What are the inputs of the Validation process?

A
  • Life cycle concepts
  • Stakeholder requirements
  • Final RVTM
  • Installed system
  • Transition report
  • Validation criteria
76
Q

What are the activities of the Validation process?

A
  • Prepare for validation
  • Perform validation
  • Manage results of validation
77
Q

What are the outputs of the Validation process?

A
  • Validation strategy
  • Validation enabling system requirements
  • Validation constraints
  • Validation procedure
  • Validated requirements
  • Validated system
  • Validation report
  • Validation record
78
Q

What are the inputs of the Operation process?

A
  • Life cycle concepts
  • Operator/maintainer training materials
  • Trained operators and maintainers
  • Validated system
  • Validation report
  • Maintenance report
79
Q

What are the activities of the Operation process?

A
  • Prepare for operation
  • Perform operation
  • Manage results of operation
  • Support the customer
80
Q

What are the outputs of the Operation process?

A
  • Operation strategy
  • Operation enabling system requirements
  • Operation constraints
  • Operation report
  • Operation record
81
Q

What are the inputs of the Maintenance process?

A
  • Life cycle concepts
  • Operator/maintainer training materials
  • Trained operator and maintainers
  • Validated system
  • Validation report
  • Operation report
82
Q

What are the activities of the Maintenance process?

A
  • Prepare for maintenance
  • Perform maintenance
  • Perform logistics support
  • Manage results of maintenance and logistics
83
Q

What are the outputs of the Maintenance process?

A
  • Maintenance strategy
  • Maintenance enabling system requirements
  • Maintenance constraints
  • Maintenance procedure
  • Maintenance report
  • Maintenance record
84
Q

What are the inputs of the Disposal process?

A
  • Life cycle concepts
  • Validated system
  • Operation report
  • Maintenance report
85
Q

What are the activities of the Disposal process?

A
  • Prepare for disposal
  • Perform disposal
  • Finalize the disposal
86
Q

What are the outputs of the Disposal process?

A
  • Disposal strategy
  • Disposal enabling system requirements
  • Disposal constraints
  • Disposal procedure
  • Disposed system
  • Disposal report
  • Disposal record