-
Key: KDM12-52
-
Legacy Issue Number: 13300
-
Status: closed
-
Source: KDM Analytics ( Dr. Nikolai Mansourov)
-
Summary:
Related to 8.2, paragraph 1, bullet 10
"Structure package defines the architectural components of existing application, subsystems, layers, packages, etc."
DIS should articulate how the Structure package supports common architectural concepts of architecture, architecture description, architecture viewpoint, architecture view, and architecture model per ISO 42010
-
Reported: KDM 1.1 — Fri, 16 Jan 2009 05:00 GMT
-
Disposition: Resolved — KDM 1.2
-
Disposition Summary:
Change sentence Page 12, Structure package defines the architectural components of existing
application, subsystems, layers, packages, etc.
into
Structure package defines meta-model elements that represent architectural components of
existing software systems, such as subsystems, layers, packages, etc. and define traceability of
these elements to other KDM facts.
Editorial changes to the other bullets of the list:
Change bullet:
The Source package defines the inventory of the physical artifacts of the existing software system and
references to the source code.
Into
The Source package defines meta-model elements that represent the inventory of the physical artifacts of
the existing software system and define the key traceability mechanism of KDM how KDM facts
reference back to their original representation in the artefacts of the software system (for example, source
code).
Change bullet:
The Code package defines the low-level building blocks of application source files, such as procedures,
datatypes, classes, etc. (as determined by a programming language).
Into
The Code package defines meta-model elements that represent the low-level building blocks of software
such as procedures, datatypes, classes, variables, etc. (as determined by a programming language).
Change bullet:
Action package defines end points of relations, and the majority of KDM relations.
Into
Action package defines meta-model elements that represent s statements of software as the end points of
relations, as well as the majority of low-level KDM relations.
Change bullet: Platform package defines artifacts, related to the run time platform of the enterprise application.
Into
Platform package defines meta-model element that represent the run time resources used by the software
systems, as well as relationships determined by the run-time platform.
Change bullet:
UI package defines the user-interface aspects of the application.
Into
UI package defines meta-model element that represent the user-interface aspects of the application.
Change bullet:
Event package defines a common concept related to event-driven programming.
Into
Event package defines meta-model element that represent event-driven aspects of the software systems,
such as events, states, state transitions, as well as relations determined by the event-driven semantics of the
application’s run-time framework.
Change bullet:
Data package defines the persistent data aspects of an application.
Into
Data package defines meta-model elements that represent persistent data aspects of the software system.
Change bullet:
Conceptual package defines the domain-specific elements of an application.
Into
Conceptual package defines meta-model elements that represent the domain-specific elements of existing
software system.
Change bullet:
Build package defines the artifacts related to engineering of an application.
Into
Build package defines meta-model elements that represent the artefacts related to the build process of
the software system (including but not limited to the engineering transformations of the
“source code” to “executables”). -
Updated: Fri, 6 Mar 2015 20:57 GMT