Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

INCOSE CSEP Exam Prep > Chapter 4 Technical Processes > Flashcards

Chapter 4 Technical Processes Flashcards

Technical processes are used to define the requirements for a system, to transform the requirements into an effective product, to permit consistent reproduction of the product where necessary, to use the product to provide the required services, to sustain the provision of those services and to dispose of the product when it is retired from service.

1
Q

What is the purpose of the business or mission analysis process?

A

To define the business or mission problem or opportunity, characterize the solution space, and determine potential solution classes that could address problem or take advantage of an opportunity - ISO/IEC/IEEE 15288

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

What are inputs to the Business or Mission Analysis process?

A
  • Organization strategic plan
  • ConOps
  • Source documentation
  • Life cycle constraints
  • Project constraints
  • Stakeholder requirements traceability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are outputs to 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/data
Business requirements traceability
Business or mission analysis record
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are activities to the Business or Mission Analysis process?

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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is a ConOps?

A

Developed by/for leadership; Organizations way of doing things; typically embodies long range strategic plans and annual operations plans; basis for the organization to direct overall characteristics of future business and systems

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

What is an OpsCon?

A

Summarizes business needs from an operational perspective for solution classes addressing prop or opportunity; what the system will do (not how) and why; user-oriented describing system characteristics from user’s viewpoint; used to communicate overall quantitative and qualitative system characteristics to acquirer, user, supplier, and other org elements.

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

What is the purpose of Stakeholder needs & requirements definition process?

A

Define stakeholder requirements for a system that can provide the capabilities needed

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

What are inputs to the Stakeholder needs & requirements process?

A 
Source documents
Project constraints
Major stakeholder 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are activities to the Stakeholder needs & requirements process?

A

Prepare for stakeholder needs and requirements
Define stakeholder needs
Develop the operational concepts and other life cycle concepts
Transform stakeholder needs into stakeholder requirements
Analyze stakeholder requirements
- Manage the stakeholder needs and requirements definition

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

What are outputs to the Stakeholder needs & requirements 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the purpose of the System requirements definition process?

A

Transform the stakeholder, user-oriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user

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

How is iteration and recursiveness related to requirements definition?

A

Requirements definition is both iterative and recursive; iterative: process is repeated on the same level of the system; recursive: when the same set of processes are applied to successive levels of a system elements within the system structure

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

What are inputs to 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are activities to the System requirements definition process?

A

Prepare for system requirements definition
This task includes identification of expected interactions of the system with systems external to the system (control) boundary as defined in negotiated interface control documents (ICD)
Define system requirements
A documentation tree, that evolves with the interaction of system requirements definition, architecture, and design definition processes, can be developed.
identify the technical risks that need to be accounted for in the system requirements
Analyze system requirements
Define verification criteria, critical performance measures that allow assessment of technical achievement.
Measures of Performance (MOP)
Technical Performance Measures (TPM)
: “implementation” measures of success that should be traceable to MOES and MOSs
Manage system requirements
Provide baseline information for configuration management

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

What are outputs to 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the objective of requirements analysis?

A

Objective of requirements analysis is to provide understanding of the interaction between the various functions and to obtain a balanced set of requirements based on user objectives

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

Characteristics of individual requirements (8)

A 
Necessary
	Implementation independent
	Unabiguous
	Complete
	Singular
	Achievable
	Verifiable
	Conforming
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Characteristics of sets of requirements as a whole (4)

A

Complete
Consistent
Feasible/affordable
Bounded

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

Characteristics of individual requirements statements (17)

A 
Trace to parent
Trace to source
Trace to interface definition
Trace to peer requirements
Trace to verification method
Trace to verification requirements
Trace to verification results
Requirements validation status
Priority
Criticality
Risk
Key driving requirement (KDR)
Owner
Rationale
Applicability
Type
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is the purpose of the Architecture definition process?

A

Purpose: generate system architecture alternatives, to select one or more alternatives 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
21
Q

What are inputs to 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What are outputs to the Architecture definition process?

A 
Architecture definition strategy
System architecture description
System architecture rationale
Documentation tree
Preliminary TPM needs
Preliminary TPM data
Architecture traceability
Architecture definition record
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What are activities to 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What the purpose of the Design definition process?

A

Purpose: provide sufficient detailed data and information about the system and 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
25
What are inputs to the Design definition process?
``` 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 ```
26
What are outputs to the Design definition process?
``` Design Definition Strategy System design description System design rationale Interface definition TPM needs TPM data Design traceability System element descriptions Design definition record ```
27
What are activities for the Design definition process?
Prepare for design definition Establish design characteristics and design enablers related to each system element Assess alternatives for obtaining a system element Manage the design
28
What is the purpose of the system analysis process?
provide a rigorous basis of data and information for technical understanding to aid decision-making across the life cycle.
29
What are inputs to the system analysis process?
Life cycle concepts Analysis situations Life cycle constraints
30
What are outputs to the system analysis process?
System analysis strategy System analysis report System analysis record
31
What are activities for the system analysis process?
Prepare for system analysis Perform system analysis Manage system analysis
32
What is the purpose of the Implementation process?
Purpose: realize a specified system element
33
What are inputs to the Implementation Process?
``` Life cycle concepts System architecture description System architecture rationale System design descrription System design rational Interface definition Design traceability System element descriptions ```
34
What are outputs to the Implementation Process?
``` Implementation strategy Implementation enabling system requiremetns Implementation constraints System elements Hardware/physical Software Operational resources (procedures & training) Services System element documentation Operator/maintaner training materials Implementation traceability Implementation report Implementation record ```
35
What are activities for the Implementation Process?
Prepare for implementation Perform implementation Manage results of implementation
36
What is the process of the Integration process?
Purpose: synthesize a set of system elements into realized system that satisfies system requirements, architecture, and design
37
What are inputs to the Integration process?
``` Life cycle concepts Interface definitions System element descriptions System elements System element documentation Implementation traceability Accepted system or system element ```
38
What are outputs to the Integration process?
``` Integration strategy Integration enabling system requirements Integration constraints Integration procedure Integrated system or system elements Interface definition update identification Integration report Integration record ```
39
What are activities for the Integration process?
Prepare for integration Perform integration Manage results of integration
40
What are some integration strategies and approaches?
Global integration or "big bang integration" Pro: simple and does not require simulating the system elements not being available at that time Con: Difficult to detect and localize faults; interface faults are detected late Integration "with the stream" Delivered system elements are assembled as they become available. Pro: Allows starting the integration quickly Con: complex to implement bc you need to simulate system elements not yet available; Impossible to control the end-to-end "functional chains"; global tests are postponed very late in the schedule Incremental integration One or a very few system elements are added to an already integrated increment of system elements (in a predefined order) Pro: Allows fast localization of faults; new fault is usually localized in lately integrated system elements or dependent on a faulty service Con: Requires simulators for absent system elements and many test cases; each system element addition requires the verification of the new configuration and regression testing Subset Integration, "functional chain integration" System elements are assembled by subsets (aggregate), then subsets are assembled together Pro: saves time due to parallel integration of subsets; delivery of partial products is possible; requires less means (enablers) and fewer test cases than integration by increments Top-down integration System elements or aggregates are integrated in their activation or utilization order Pro: availability of a skeleton of the system and early detection of architectural faults; definition of test cases is close to reality, test data reuse is possible Con: Many stubs/caps need to be created; difficult to define test cases of the leaf system elements Bottom-up integration System elements or aggregates are integrated in opposite order of their activation or utilization Pro: Definition of test cases is easy; early detection of faults is possible; number of simulators needed are reduced; aggregate can be a subsystem Con: test cases are redefined for each step; drivers are difficult to realize; system elements of lower levels are over tested; slow detection of architectural faults Criterion-driven integration Reorganization of coupling matrices
41
What is the purpose of the Verification process?
provide objective evidence that a system or system element fulfills its specified requirements and characteristics
42
What are inputs to the Verification process?
``` Life cycle concepts System requirements Verification requirements Updated RVTM Interface definition Integrated system or system elements Integration report ```
43
What are outputs to the Verification process?
``` Verification strategy Verification enabling system requirements Verification constraints Verification procedure Final RVTM Verified system Verification report Verification record ```
44
What are activities for the Verification process?
Prepare for verification Perform verification Manage the results of verification
45
What are some verification techniques?
``` Inspection Analysis Demonstration Test Analogy or similarity Simulation Sampling ```
46
What's the process of the transition process?
establish a capability for a system to provide services specified by stakeholder requirements in the operational environment
47
What's are inputs to the transition process?
``` Life cycle concepts Operator/Maintaner training materials Final RTVM Verified system Verification report ```
48
What's are outputs to the transition process?
``` Transition strategy Transition enabling system requirements Transition constraints Installation procedure Installed system Trained operators and maintainers Transtion report Transition record ```
49
What's are activities for the transition process?
Prepare for the transition Perform the transition Manage results of the transition
50
What's the purpose of the Validation process?
What's the purpose of the Validation process?
51
What are inputs to the Validation process?
``` Life cycle concepts Stakeholder requirements Final RVTM Installed system Transition report Validation Criteria ```
52
What are outputs to the Validation process?
``` Validation strategy Validation enabling system requirements Validation constraints Validation procedure Validated requirements Validated system Validated system Validated report Validated record ```
53
What are activities for the Validation process?
Prepare for validation Perform validation Manage results of validation
54
What's the purpose of the Operation process?
Purpose: use the system to deliver its services
55
What are inputs to the Operation process?
``` Life cycle concepts Operator/Maintainer training materials Trained operator and maintainers Validated system Maintenance report ```
56
What are outputs to the Operation process?
``` Operation strategy Operation enabling system requirements Operation constraints Operation report Operation record ```
57
What are activities for the Operation process?
Prepare for operation Perform operation Manage results of operation Support the customer
58
What is the purpose of the maintenance process?
Purpose: sustain the capability of the system to provide a service
59
What are inputs to the maintenance process?
``` Life cycle concepts Operator/Maintaner training materials Trained operator and maintaners Validated system Validation report Operation report ```
60
What are outputs to the maintenance process?
``` Maintenance strategy Maintenance enabling system requirements Maintenance constraints Maintenance procedure Maintenance report Maintenance record ```
61
What are activities for the maintenance process?
Prepare for maintenance Perform maintenance Perform logistics support Manage results of maintenance and logistics
62
What are the different types of maintenance?
Corrective Preventative System modifications
63
What is the purpose of the disposal process?
Purpose: 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.
64
What are inputs to the disposal process?
Life cycle concepts Validated system Operation report Maintenance report
65
What are outputs to the disposal process?
``` Disposal strategy Disposal enabling system requirements Disposal constraints Disposal procedure Disposed system Disposal report Disposal record ```
66
What are activities for the disposal process?
Prepare for disposal Perform disposal Finalize the disposal

INCOSE CSEP Exam Prep (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions