The INCOSE Handbook has been written to be consistent with ISO/IEC/IEEE 15288 in order to ensure it can be applied to (choose 3):
System-of-systems
Medical systems
Products
Services
Buisness
Avionics
ISO/IEC/IEEE 15288 provides (choose 2):
Practices necessary to execute processes
activities necessary to execute processes
generic top-level process descriptions
generic top-level process requirements
The number of process groups identified by ISO/IEC/IEEE 15288 is:
3
4
5
6
The INCOSE Handbook is ready to be applied to your company or project
The 4 process groups from ISO/IEC/IEEE 15288 that support systems engineering include (choose 2):
Organizational project-enabling Processes
Work Breakdown Processes
Technical Processes
Project Initiation
The 2 Agreement Processes are:
Contract Management
Acquisition
Supply Chain Management
Supply
Negotiate
Life Cycle Modeling Processes
Agreement Processes
Model Based Engineering
Technical Management Processes
The 8 Technical Management Processes include (choose 4):
Project Planning
Project Assessment and Control
Requirements Analaysis
Configuration Management
Implementation
Stakeholder Requriements Definition
Information Management
The 5 Organizational Project-Enabling Processes identified by ISO/IEC/IEEE 15288 include (choose 3):
Technical Process
Infrastructure Management Process
Agreement Process
Human Resources Management Process
Quality Management Process
The 5 Organizational Project-Enabling Processes identified by ISO/IEC/IEEE 15288 include (choose 2):
Portfolio Management Processes
Life Cycle Model Management Processes
When joining a project, one of the first jobs of a systems engineering is to:
Create Integrated Product Development Teams (IPDT's)
Initiate a function based analysis to establish a foundation for defining a system architecture
Begin writing the Concept of Operations document in order to demonstrates the organization grasps the customers wants and needs
Establish nomenclature and terminology to support clear, unambiguous communication
Input-process-output diagrams typically include controls and enablers
How many items are called out in the Controls box
Select the Controls from the list below:
Applicable laws and regulations
Organizational policies, procedures and standards
Organizational Infrastructure
Standards
Agreements
Project Infrastructure
Project Direction
Knowledge Management
Project Control Requests
The definition of "Process" used in the Activities box is:
a series of actions or steps taken in order to achieve a particular end
sequence of interdependent and linked procedures which, at every stage, consume one or more resources
an integrated set of activities that transforms inputs into desired outputs
a series of action, changes, or functions bringing about a result
The input-process-output diagrams represent:
the single best way to perform systems engineering processes
the fact that systems engineering must produce the documents listed in the outputs
one potential way the systems engineering processes can be performed
Project direction, as found in the Controls box of the input-process-output (IPO) diagram, is defined as:
a vector defining the success criteria for a project
the organizations direction to a project to continue, redirect or terminate
a measurement against assessment criteria that determines if a project is moving forward or stalled
permission to continue forward at the conclusion of a phase-gate or state-gate review
The difference between "project direction: and "project control requests" is best described by:
Project control requests are internally generated by the project due to deviations form the project plan
Project direction is internally generated by the project in response to deviations from the project plan
Project control requests are suggestions white project direction is an authoritative order
