7.3.1

De 12207.

7.3.1
Title : Domain Engineering Process
Process group : 7.3
Lower-level process of : none
Replaced by process : none
Specialization of : none
Conforming instance of : none

Purpose : The purpose of the Domain Engineering Process is to develop and maintain domain models, domain architectures and assets for the domain.

Activities : 7.3.1.3.1, 7.3.1.3.2, 7.3.1.3.3, 7.3.1.3.4 et 7.3.1.3.5

List of outcomes : As a result of successful implementation of the Domain Engineering Process:
a) the representation forms for the domain models and the domain architectures are selected;
b) the boundaries of the domain and its relationships to other domains are established;
c) a domain model that captures the essential common and different features, capabilities, concepts, and functions in the domain are developed;
d) a domain architecture describing the family of systems within the domain, including their commonalities and variabilities, is developed;
e) assets belonging to the domain are specified;
f) assets belonging to the domain are acquired or developed and maintained throughout their life cycles; and
g) the domain models and architectures are maintained throughout their life cycles.
NOTE 1 Domain engineering is a reuse-based approach to defining the scope (i.e., domain definition), specifying the structure (i.e., domain architecture), and building the assets (e.g., requirements, designs, software code, documentation) for a class of systems, subsystems, or applications.warning.pngLa chaîne de représentation NOTE 1 Domain engineering is a reuse-based […] s of systems, subsystems, or applications. est trop grande pour ce site.
NOTE 2 The Domain Engineering Process may overlap with development and maintenance processes that use assets produced by the Domain Engineering Process.

Faits relatifs à 7.3.1 — Recherche de pages similaires avec +.Voir comme RDF
Id7.3.1  +
IsConformingInstanceOfnone  +
IsLowerLevelProcessOfNone  +
IsPartOf7.3  +
IsReplacedByNone  +
IsSpecializationOfnone  +
OutcomeAs a result of successful implementation of the Domain Engineering Process:  +, a) the representation forms for the domain models and the domain architectures are selected;  +, b) the boundaries of the domain and its relationships to other domains are established;  +, c) a domain model that captures the essential common and different features, capabilities, concepts, and functions in the domain are developed;  +, d) a domain architecture describing the family of systems within the domain, including their commonalities and variabilities, is developed;  +, e) assets belonging to the domain are specified;  +, f) assets belonging to the domain are acquired or developed and maintained throughout their life cycles; and  +, g) the domain models and architectures are maintained throughout their life cycles.  + et NOTE 2 The Domain Engineering Process may overlap with development and maintenance processes that use assets produced by the Domain Engineering Process.  +
TitleDomain Engineering Process  +
Outils personnels