KDM12 — Missing definition of software asset (rh-4)

Related to section 4

Unable to determine intended scope of this standard without a definition of "software asset". Does it intend to cover information items as defined in ISO 15289?

Define "software asset". Clarify which information items and work products specified in ISO 15289 are included within the scope of this DIS.

In the following editing instructions, the occurrences of terms in the original sentences are highlighted, and
the changes are underlined.
Change sentence Page 1. This specification defines a meta-model for representing existing software assets,
their associations, and operational environments, referred to as the Knowledge Discovery Meta-model
(KDM).
Into:
This specification defines a meta-model for representing existing software, its elements, associations, and
operational environments, referred to as the Knowledge Discovery Meta-model (KDM).
Change sentence Page 1. One common characteristic of various tools that address SwA and ADM
challenge is that they analyze existing software assets (for example, source code modules, database
descriptions, build scripts, etc.) to obtain explicit knowledge.
Into
One common characteristic of various tools that address SwA and ADM challenge is that they analyze
existing software artifacts (for example, source code modules, database descriptions, build scripts, etc.) to
obtain explicit knowledge..
Change sentence page 1: Each tool produces a portion of the knowledge about existing software assets.
Such tool-specific knowledge may be implicit (“hard-coded” in the tool), restricted to a particular source
language, and/or particular transformation, and/or operational environment.
Into:
Any tool that operates on existing software produces some portion of the knowledge about the
given software system. However, such tool-specific knowledge may not be exported in any
explicit format. For example, such knowledge may be used internally by the tool: a compiler
generates precise knowledge about a compilation unit only to discard it as soon as the object file is generated. Tool-specific knowledge may be limited in scope, restricted to a particular source
language and/or particular transformation, and/or particular operational environment.
Change sentence Page 1. The meta-model for Knowledge Discovery provides a common repository
structure that facilitates the exchange of data contained within individual tool models that represent existing
software assets. The meta-model represents the physical and logical assets at various levels of abstraction.
Into
The meta-model for Knowledge Discovery provides a common ontology and an interchange format that
facilitates the exchange of data contained within individual tool models that represent existing software.
The meta-model represents the physical and logical elements of software as well as their relations at
various levels of abstraction.
Change Page 9. section 7. This specification defines a meta-model for representing information related to
existing software assets, their associations, and operational environments (referred to as the Knowledge
Discovery Meta-model (KDM)).
Into
This specification defines a meta-model for representing information related to existing software, its
elements, associations, and operational environments (referred to as the Knowledge Discovery Meta-model
(KDM)).
Change sentence Page 9. section 7. More specifically, (KDM) provides a common repository structure that
facilitates the exchange of data currently contained within individual tool models that represent existing
software assets. The meta-model represents the physical and logical software assets at various levels of
abstraction as entities and relations.
Into
More specifically, (KDM) defines a common ontology and an interchange format that facilitates the
exchange of data currently contained within individual tool models that represent existing software. The
meta-model represents the physical and logical elements of software as well as their relations at various
levels of abstraction.
EDITORIAL NOTE: For traceability purposes the following minor edits are marked as Block 2 in
the specification text with changebars
Section 10.1 change “application” into “system”
KDM instance is not a model that represents constraints, like the ones used during the design phase, rather,
this is an intermediate representation that captures precise knowledge about the system.
Section 10.1 change “artifacts” to “elements”
The remaining KDM packages provide meta-model elements that represent various elements of
existing systems.
Section 11.1
The Source package also represents traceability links between instances of KDM meta-elements
and the regions of source code, which is represented by these meta-model elements.