Issue 15925: KDM Build package issue (kdm-rtf) Source: Benchmark Consulting (Mr. Alain Picard, apicard(at)benchmarkconsulting.com) Nature: Uncategorized Issue Severity: 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? Resolution: Revised Text: Actions taken: January 10, 2011: received issue Discussion: End of Annotations:===== te: Mon, 10 Jan 2011 20:45:57 -0500 Subject: KDM Build package issue From: Alain Picard To: kdm-rtf@omg.org 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? Cheers, Alain -- Alain Picard Chief Strategy Officer Benchmark Consulting 813-787-3424 apicard@benchmarkconsulting.com www.benchmarkconsulting.com