INCOSE Chapter 1: Appendix E Input Output Descriptions
Accepted system or system element - correct answers System element or system is transferred from supplier to acquirer and the product or service is available to the project
Acquired system - correct answers The system or system element (product or service) is delivered to the
acquirer from a supplier consistent with the delivery conditions of the acquisition agreement
Acquisition agreement - correct answers An understanding of the relationship and commitments between the project organization and the supplier. The agreement can vary from formal contracts to less formal interorganizational work orders. Formal agreements typically include terms and conditions
Acquisition need - correct answers The identification of a need that cannot be met within the organization encountering the need or a need that can be met in a more economical way by a supplier
Acquisition payment - correct answers Payments or other compensations for the acquired system. Includes remitting and acknowledgement
Acquisition record - correct answers Permanent, readable form of data, information, or knowledge related to acquisition
Acquisition reply - correct answers The responses of one or more candidate suppliers in response to a request for supply
Acquisition report - correct answers An account prepared for interested parties in order to communicate
the status, results, and outcomes of the acquisition activities
Acquisition strategy - correct answers Approaches, schedules, resources, and specific considerations required to acquire system elements. May also include inputs to determine acquisition constraints Agreements - correct answers Agreements from all applicable life cycle processes, including acquisition agreements and supply agreements
Alternative solution classes - correct answers Identifies and describes the classes of solutions that may address the problem or opportunity
Analysis situations - correct answers The context information for the analysis including life cycle stage, evaluation drivers, cost drivers, size drivers, team characteristics, project priorities, or other characterization information and parameters that are needed to understand analysis and represent the element being analyzed. Relevant information from the process that invokes the analysis. Any existing models related to the element being analyzed. Any data related to the element being analyzed, including historical, current, and projected data. Can originate from any life cycle process
Applicable laws and regulations - correct answers International, national, or local laws or regulations
Architecture definition record - correct answers Permanent, readable form of data, information, or knowledge related to architecture definition
Architecture definition strategy - correct answers Approaches, schedules, resources, and specific considerations required to define the selected system architecture that satisfies the requirements
Architecture traceability - correct answers Bidirectional traceability of the architecture characteristics
Business or mission analysis record - correct answers Permanent, readable form of data, information, or knowledge related to business or mission analysis
Business or mission analysis strategy - correct answers Approaches, schedules, resources, and specific considerations required to conduct business or mission analysis and ensure business needs are elaborated and formalized into business requirements
Business requirements - correct answers Definition of the business framework within which stakeholders will define their requirements. Business requirements govern the project, including agreement constraints, quality standards, and cost and schedule constraints. Business requirements may be captured in a Business Requirements Specification (BRS), which is approved by the business leadershipNote: Business requirements may not always be formally captured in the system life cycle
Business requirements traceability - correct answers Bidirectional traceability of the business requirements
Candidate configuration items (CIs) - correct answers Items for configuration control. Can originate from any life cycle process
Candidate information items - correct answers Items for information control. Can originate from any life cycle process
Candidate risks and opportunities - correct answers Risks and opportunities that arise from any stakeholder. In many cases, risk situations are identified during the project assessment and control process. Can originate from any life cycle process
Concept of operations (ConOps) - correct answers The ConOps is a verbal and/or graphic statement prepared for the organization's leadership that describes the assumptions or intent regarding the overall
operation or series of operations of the enterprise, to include any new capability (ANSI/AIAA, 2012; ISO/IEC/IEEE 29148, 2011)
Configuration baselines - correct answers Items placed under formal change control. The required configuration baseline documentation is developed and approved in a timely manner to support required systems engineering (SE) technical reviews, the system's acquisition and support strategies, and production
Configuration management record - correct answers Permanent, readable form of data, information, or knowledge related to configuration management
Configuration management report - correct answers An account prepared for interested parties in order to communicate the status, results, and outcomes of the configuration management activities. Documents the impact to any process, organization, decision (including any required change notification), products, and services affected by a given change request
