Domain asset

From CNM Wiki
Jump to: navigation, search

Domain asset is the output of a subprocess of domain engineering that is reused for producing two or more products in a product line. A domain asset may be a variability model, an architectural design, a software component, a domain model, a requirements statement or specification, a plan, a test case, a process description, or any other element useful for producing products and services. Syn: domain artifact (ISO 26550 2nd Cd) Note: In systems engineering, domain assets may be subsystems or components to be reused in further system designs. Domain assets are considered through their original requirements and technical characteristics. Domain assets include, but are not limited to, use cases, logical principles, environmental behavioral data, and risks or opportunities learned from the previous projects domain assets are not physical products available off‐the‐shelf and ready for commissioning. Physical products (e.g., mechanical parts, electronic components, harnesses, optic lenses) are stored and managed according to the best practices of their respective disciplines Note: In software engineering, domain assets can include source or object code to be reused during the implementation Note: Domain assets have their own life cycles. ISO/IEC/IEEE 15288 may be used to manage a life cycle.

Definitions

According to the INCOSE Systems Engineering Handbook (4th edition),

Domain asset. Is the output of a subprocess of domain engineering that is reused for producing two or more products in a product line. A domain asset may be a variability model, an architectural design, a software component, a domain model, a requirements statement or specification, a plan, a test case, a process description, or any other element useful for producing products and services. Syn: domain artifact (ISO 26550 2nd Cd) Note: In systems engineering, domain assets may be subsystems or components to be reused in further system designs. Domain assets are considered through their original requirements and technical characteristics. Domain assets include, but are not limited to, use cases, logical principles, environmental behavioral data, and risks or opportunities learned from the previous projects domain assets are not physical products available off‐the‐shelf and ready for commissioning. Physical products (e.g., mechanical parts, electronic components, harnesses, optic lenses) are stored and managed according to the best practices of their respective disciplines Note: In software engineering, domain assets can include source or object code to be reused during the implementation Note: Domain assets have their own life cycles. ISO/IEC/IEEE 15288 may be used to manage a life cycle.