KDM 1.4 RTF Avatar
  1. OMG Issue

KDM14 — KDM Build package issue

  • Key: KDM14-70
  • Legacy Issue Number: 15925
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    There is an inconsistency between the documentation in the KDM build package and the example in the section.

    The example shows a BuildStep consuming it's input source elements which are classified as BuildComponent.

    In the description for BuildComponent we have: "The BuildComponent class represents binary files that correspond to deployable components, for example executable files."

    Obviously the input source elements being consumed in the example are .c and .h files, which are not binary.

    So is BuildComponent the right class to use for input source elements or is the description of the class incorrect?

  • Reported: KDM 1.3 — Mon, 10 Jan 2011 05:00 GMT
  • Disposition: Resolved — KDM 1.4
  • Disposition Summary:

    Add definitions of BuildComponent, BuildProduct, Library

    Rename Library to BuildLibrary for consistency.
    The description of BuildProduct and BuildLibrary are missing. Definition of a BuildComponent is actually related to (missing) BuildProduct. A BuildProduct defines the product of a build process.
    A Library is a collection of InventoryItems (usually BinaryFiles, or SourceFiles) which is used as an intermediate product of a build process.
    BuildComponent can be described as any collection of InventoryItems. A BinaryComponent defines SourceFlles as inputs to BuildSteps or any other anonymous collections of resources as they are used as inputs of outputs of a build process.
    The intention is to identify sources and targets of BuildStep as sets of InventoryItem (in fact, the definition is more general and will accept any KDMEntity).

    With this interpretation the example on page 306 is correct.

  • Updated: Tue, 12 Jul 2016 14:44 GMT