Community
Participate
Working Groups
Build Identifier: The brief description explicitly states that a build may be a subset of the system, while the main description incorrectly implies that it is only the entire system. It also incorrectly states that this is a composite artifact when it is not. Reproducible: Always
Todd, I see that both the brief and main descriptions state that this artifact may represent the whole system of part of the system (so the descriptions are consistent). As for the second comment on this being a composite artifact, even though it does not structurally have any sub-artifacts, the representation options field states "This work product is almost always a composite product made up of numerous parts required to make the executable system". Do you have a concern with this definition? Should it be reworded to "This work product is almost always a product made up of numerous parts required to make the executable system"? (removed the word "composite"). Please clarify.
The subset issues seems to have been addressed in the current main description. The text in the main description that states "This executable version will typically have a number of supporting files that are also considered part of this artifact." was the portion that caused concern about this looking like a composite artifact since there are other supporting artifacts that may be confused with this the way it's stated.
I reworded the Representation Options section as proposed in comment #1. For comment #2, because we are not explicitly saying there is a composition relationship (as defined by the tool metamodel), instead the build may contain supporting files in addition to the executable files, then I think there should be no confusion. Considering this resolved unless there is more to it.
Closed for 1.5.1.2 release on Jun 10.
