Issues for Mailing list of the Federal Transition Framework (FTF) 1.1 Revision Task Force

To comment on any of these issues, send email to ftf-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 13123: The metamodel does not provide a means of relating the type, CrossAgencyInitiative

Issue 13123: The metamodel does not provide a means of relating the type, CrossAgencyInitiative (ftf-rtf)

Click here for this issue's archive.
Source: Escape Velocity (Mr. Bob Daniel, bob.daniel(at)escapevelocity.com)
Nature: Revision
Severity: Critical
Summary:
The metamodel does not provide a means of relating the type, CrossAgencyInitiative, which is found in the "Initiatives Layer" to any type found in the layers below it. As a consequence, the detailed elements comprising the full elaboration of a Cross Agency Initiative are not connected to it. In reviewing the original source documentation from OMB, no association was present. A Cross Agency Initiative represents a configuration of elements instantiated from the metamodel. The means of characterizing this configuration would need to consider that the element instances in the configuration may NOT be unique to it, e.g., an instance of Business Requirement. The implication is that an instance of the CrossAgencyInitiative type would be associated with instantiated elements based on multiple types in the lower levels. Examples of types that would likely be associated include: BusinessRequirement, CommonBusinessProcess, SharedService, SharedComponent, etc. The alternative would be that some claim of uniqueness can be made such that the instantiated type elements are unique to a specific Cross Agency Initiative, which seems highly unlikely.

Resolution:
Revised Text:
Actions taken:
November 25, 2008: received issue