1. OMG Mailing List
  2. Business Architecture Core Metamodel 1.1 Revision Task Force

Open Issues

  • Issues not resolved
  • Name: bacm-rtf
  • Issues Count: 17

Issues Descriptions

Is Offering an InformationItem?

  • Key: BACM11-17
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    Adding this specialization would open a lot of other connections to Capabilities (e.g. that produce Offerings)

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 23:01 GMT
  • Updated: Tue, 28 Nov 2023 23:01 GMT

Reconsider ValueCharacteristic

  • Key: BACM11-16
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    The abstract syntax of this allows for value fit between value item and customer segment to be rolled up into an overall value fit between the value proposition and the customer, but it permits a lot of nonsense constructions as well. Consider splitting ValueCharacteristic into two parts: one between ValueProposition and Customer, and the other between ValueItem and CustomerSegment and have the latter owned by the former.

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:57 GMT
  • Updated: Tue, 28 Nov 2023 22:57 GMT

Customer triggers ValueStream

  • Key: BACM11-15
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    Consider whether/how to implement this concept which is defined in the BIZBOK and the Guild Metamodel whitepaper.

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:52 GMT
  • Updated: Tue, 28 Nov 2023 22:52 GMT

Expand target of InformationItem isAbout

  • Key: BACM11-14
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    The target of isAbout is currently restricted to BusinessObject but should be broadened to any concept in the AbstractOperatingModel or AbstractValueModel (except abstract constructs such as ValueStreams and Capabilities as those are documented in the business architecture model)

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:49 GMT
  • Updated: Tue, 28 Nov 2023 22:49 GMT

Reconsider ValueStream(Stage) produces as shortcut

  • Key: BACM11-13
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    Consider Capability supports ValueStreamStage as the shortcut, justified by Capability producing Outcome valued by ValueItem produced by ValueStreamStage. This avoids a shortcut whose definition falls outside of the Customer package and would put it in the Capability/ValueStream crossmap package (per BACM11-9).

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:43 GMT
  • Updated: Tue, 28 Nov 2023 22:43 GMT

Define JSON interchange specification

  • Key: BACM11-12
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    JSON is an increasingly popular serialization format. JSON-LD provides some key additional capabilities.

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:35 GMT
  • Updated: Tue, 28 Nov 2023 22:35 GMT

rename "provides" association to "offers"

  • Key: BACM11-11
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    Current name can be confused with "provider" association that links Outcome with LegalEntity. This association links LegalEntity with Offering. Affects all product diagrams.

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:31 GMT
  • Updated: Tue, 28 Nov 2023 22:31 GMT

Reconsider the packaging and namespace conventions

  • Key: BACM11-10
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    The justification for namespaces is to permit parts of the model to be used independently. The current packaging is close, but crossmaps between value stream and capability are defined in Capability and crossmaps between ValueItem and Outcome are defined in Customer. Customer mixes together Journeys and Value Streams. Consider repackaging to eliminate crossmaps from the core packages and add new packages with just the crossmaps. This would also benefit use of the OWL as a group of ontologies instead of one large one.

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:21 GMT
  • Updated: Tue, 28 Nov 2023 22:21 GMT

OWL translates "generalizes_0" association incorrectly

  • Key: BACM11-9
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    BACM has this as an association prototype with semantics of inheritance between instances (that are also classes) to conform to MOF. RDFS already has the subClassOf and subPropertyOf predicates and generalizes_0 should be translated into one of these predicates.

  • Reported: BACM 1.0b2 — Thu, 16 Nov 2023 17:56 GMT
  • Updated: Thu, 16 Nov 2023 17:56 GMT

OWL TTL does not represent composition properly

  • Key: BACM11-8
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    The MOF XMI owns_0 association is translated to an owl:ObjectProperty that is used with appropriate cardinalities in object property restriction axioms. But there is nothing that indicates that the association and its object property restrictions should have the cascading delete semantics. In the MOF2RDF specification, this is indicated by marking the object property as a subproperty of a "well-known" object property named "hasPart". The OWL version of BACM should follow this pattern.

  • Reported: BACM 1.0b2 — Thu, 16 Nov 2023 17:51 GMT
  • Updated: Thu, 16 Nov 2023 17:51 GMT

Policy concept is missing from specification

  • Key: BACM11-7
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    Policy is a common business concept. It is specified in the BIZBOK. Policy is also defined in the BMM.

  • Reported: BACM 1.0b2 — Wed, 15 Nov 2023 18:32 GMT
  • Updated: Wed, 15 Nov 2023 18:32 GMT

Undocumented association "recordedAs"

  • Key: BACM11-6
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    This association between Outcome and AbstractBusinessObject is undocumented. The association documentation is in generated material and several sections will be regenerated.

  • Reported: BACM 1.0b2 — Wed, 15 Nov 2023 17:55 GMT
  • Updated: Wed, 15 Nov 2023 17:55 GMT

Abstract Process missing from Diagram 7.3.7.3 and following text

  • Key: BACM11-2
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    This diagram represents the capabilities that would be required to carry out a means or initiative. Often, these capabilities are not a part of the organization and must be added, e.g. by contract. The issue is that abstract process should be included because it represents a perspective that abstractly represents the operations of the business that is distinct from the capability perspective but at the same level of abstraction.

  • Reported: BACM 1.0a1 — Wed, 19 Oct 2022 16:30 GMT
  • Updated: Mon, 9 Oct 2023 15:16 GMT

Entry- and Exit-Criteria missing

  • Key: BACM11-3
  • Status: open  
  • Source: Business Architecture Guild ( Hermann Schlamann)
  • Summary:

    Metamodel of Business Architecture Guild defines two relationships between Value Stream Stages and Value Item labeled as Entry Criteria and Exit Criteria. These relationships are missing in the BACM.

  • Reported: BACM 1.0b1 — Sun, 30 Oct 2022 09:13 GMT
  • Updated: Mon, 9 Oct 2023 15:16 GMT

Dispose of the content from Annex B

  • Key: BACM11-1
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    This issue depends on acceptance of the proposal BACM_5 to remove Annex B from the specification document. It seeks proposals to dispose of this content.

  • Reported: BACM 1.0a1 — Wed, 22 Jun 2022 17:00 GMT
  • Updated: Mon, 9 Oct 2023 15:16 GMT

The BACM metamodel does not have a domain of individuals

  • Key: BACM11-5
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    This issue arises from the resolution of BACM-45 and BACM-43. Taken together these proposals create an interpretation of the BACM model elements that does not syntactically distinguish elements representing sets from elements representing individuals. Rather, it represents individuals by an OCL constraint that allows only a single model element to have a given metaclass. This solution works for the only case in the current BACM spec, but does not resolve the underlying issue of the inability to represent individuals and make assertions about them.

  • Reported: BACM 1.0a1 — Thu, 8 Dec 2022 21:14 GMT
  • Updated: Mon, 9 Oct 2023 15:16 GMT

Dispose of content from Section 9

  • Key: BACM11-4
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    A prior vote of the FTF approved the removal of this content from the specification. The FTF must now decide what to do with this content.

  • Reported: BACM 1.0a1 — Tue, 6 Dec 2022 17:21 GMT
  • Updated: Mon, 9 Oct 2023 15:16 GMT