BACM11-71 |
Process has no representation of sequential execution constraints |
BACM 1.0b2
|
|
|
open |
|
BACM11-70 |
OWL translation does not handle ordered associations |
BACM 1.0b2
|
|
|
open |
|
BACM11-66 |
Replace metaclass Resource with metaclass AbstractBusinessObject |
BACM 1.0b2
|
|
|
open |
|
BACM11-64 |
Target of "stateOf" is insufficiently broad |
BACM 1.0b2
|
|
|
open |
|
BACM11-63 |
Consider adding CapabilitySpecialization to the metamodel |
BACM 1.0b2
|
|
|
open |
|
BACM11-53 |
Binding object |
BACM 1.0b2
|
|
|
open |
|
BACM11-52 |
Relate Outcome to Performer |
BACM 1.0b2
|
|
|
open |
|
BACM11-45 |
Customer Causation tagging of Outcomes |
BACM 1.0b2
|
|
|
open |
|
BACM11-35 |
Sequencing of ValueStreamStages |
BACM 1.0b2
|
|
|
open |
|
BACM11-25 |
Resolve ordering semantics for Outcome connections |
BACM 1.0b2
|
|
|
open |
|
BACM11-23 |
Determine of the triggers association between Outcome and ValueStreamStage is needed. |
BACM 1.0b2
|
|
|
open |
|
BACM11-15 |
Customer triggers ValueStream |
BACM 1.0b2
|
|
|
open |
|
BACM11-3 |
Entry- and Exit-Criteria missing |
BACM 1.0b1
|
|
|
open |
|
BACM11-14 |
Expand target of InformationItem isAbout |
BACM 1.0b2
|
|
|
open |
|
BACM11-40 |
Change naming convention of OWL object properties and datatype properties |
BACM 1.0b2
|
|
|
open |
|
BACM11-42 |
OWL TTL does not include UUIDs |
BACM 1.0b2
|
|
|
open |
|
BACM11-38 |
Missing path specifications for some sortcut associations |
BACM 1.0b2
|
|
|
open |
|
BACM11-30 |
The owns-0 association uses dash; all other associations use underscore to separate suffix. |
BACM 1.0b2
|
|
|
open |
|
BACM11-20 |
Add "rdfs:label" predicate object to OWL ontology for all generated elements |
BACM 1.0b2
|
|
|
open |
|
BACM11-29 |
Duplicated owned constraint elements in MOF XMI |
BACM 1.0b2
|
|
|
open |
|
BACM11-10 |
Reconsider the packaging and namespace conventions |
BACM 1.0b2
|
|
|
open |
|
BACM11-18 |
BACM Turtle File should use https rather than http |
BACM 1.0b2
|
|
|
open |
|
BACM11-19 |
Remove "subClassOf owl:Thing" from OWL TTL file |
BACM 1.0b2
|
|
|
open |
|
BACM11-6 |
Undocumented association "recordedAs" |
BACM 1.0b2
|
|
|
open |
|
BACM11-57 |
No relationship between ProductOffering and Customer |
BACM 1.0b2
|
|
|
open |
|
BACM11-55 |
Revise notes for "stateOf" to match glossary format |
BACM 1.0b2
|
|
|
open |
|
BACM11-32 |
Operating Value Streams |
BACM 1.0b2
|
|
|
open |
|
BACM11-5 |
The BACM metamodel does not have a domain of individuals |
BACM 1.0a1
|
|
|
open |
|
BACM11-31 |
Important shortcut supports relation between capability and ValueItem |
BACM 1.0b2
|
|
|
open |
|
BACM11-28 |
Resolve specification of ownership and quantification in OWL specification |
BACM 1.0b2
|
|
|
open |
|
BACM11-7 |
Policy concept is missing from specification |
BACM 1.0b2
|
|
|
open |
|
BACM11-8 |
OWL TTL does not represent composition properly |
BACM 1.0b2
|
|
|
open |
|
BACM11-9 |
OWL translates "generalizes_0" association incorrectly |
BACM 1.0b2
|
|
|
open |
|
BACM11-1 |
Dispose of the content from Annex B |
BACM 1.0a1
|
|
|
open |
|
BACM11-4 |
Dispose of content from Section 9 |
BACM 1.0a1
|
|
|
open |
|
BACM11-2 |
Abstract Process missing from Diagram 7.3.7.3 and following text |
BACM 1.0a1
|
|
|
open |
|
BACM11-11 |
rename "provides" association to "offers" |
BACM 1.0b2
|
|
|
open |
|
BACM11-12 |
Define JSON interchange specification |
BACM 1.0b2
|
|
|
open |
|
BACM11-17 |
Is Offering an InformationItem? |
BACM 1.0b2
|
|
|
open |
|
BACM11-13 |
Reconsider ValueStream(Stage) produces as shortcut |
BACM 1.0b2
|
|
|
open |
|
BACM11-16 |
Reconsider ValueCharacteristic |
BACM 1.0b2
|
|
|
open |
|
BACM-9 |
Dispose of the content from Annex B |
BACM 1.0a1
|
BACM 1.0b2
|
Deferred |
closed |
|
BACM-38 |
Entry- and Exit-Criteria missing |
BACM 1.0b1
|
BACM 1.0b2
|
Deferred |
closed |
|
BACM-66 |
Dispose of content from Section 9 |
BACM 1.0a1
|
BACM 1.0b2
|
Deferred |
closed |
|
BACM-13 |
Abstract Process missing from Diagram 7.3.7.3 and following text |
BACM 1.0a1
|
BACM 1.0b2
|
Deferred |
closed |
|
BACM-68 |
The BACM metamodel does not have a domain of individuals |
BACM 1.0a1
|
BACM 1.0b2
|
Deferred |
closed |
|
BACM-116 |
Concept of participating stakeholder missing from metamodel |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-114 |
Issue BACM-73 and resolution BACM-80 incorrectly stated |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-122 |
Generalization relations missing from 7.3.7.1 |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-120 |
Classes missing from 7.3.7.4 ValueModel diagram |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-83 |
Review uses of "owns" and "aggregates" for consistency |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-84 |
Beta specification ambiguous with respect to SMOF |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-97 |
Update Conformance section of the document |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-76 |
"owns" and "generalizes" associations missing from ProductOffering |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-55 |
Determine compliance requirement for MEF |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-26 |
Compliance statements for shortcuts and touchpoints hard to evaluate |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-15 |
Incomplete Symbols and Abbreviations - section 5 |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-85 |
Revise the definition of shortcut to eliminate virtual associations |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-98 |
Eliminate duplicate association names in EA model |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-100 |
Eliminate same named association with common src transformation rule |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-112 |
Replace IRI uml:Class in BACM_Model with IRI uml:DataType |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-118 |
Diagram 7.3.6.5 Service Offering - overlapping associations |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-79 |
Regenerate the specification document from the EA model |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-74 |
Inconsistent ownedEnd quantification in special associations (owns, ...) |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-89 |
Entry- and Exit-Criteria missing |
BACM 1.0b1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-75 |
The BACM specification does not document XML for interoperability |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-71 |
Can other property names in this specification be “modified”? |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-91 |
Incorrect shortcut specification of Capability supports ValueStreamStage |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-14 |
Import SMM and specialize some SMM classes for integration |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-72 |
Remove category and categorization from the specification |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-81 |
ValueProposition aggregates ValueProposition - owns vs aggregates |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-21 |
Provide an OWL 2 ontology as a machine readable file |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-25 |
Material in Section 0.6 that should be in the specification |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-20 |
Failure to meet RFP requirement 6.5.2.4 regarding specification alignment |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-28 |
Section 3 reference to SIMF |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-34 |
The term "user" is imprecise |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-27 |
Mix of version specific and non-specific references |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-77 |
Corrections to EA model to fix definitions and glossary |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-1 |
Make changes to the spec to enable the production of MOF compliant XMI |
BACM 1.0b1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-2 |
Replace diagram 7.3.1.1.3 and following text |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-45 |
Rewrite section 7.2.2 for clarification |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-17 |
Remove or replace mentions of category and categorization |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-6 |
Remove Section 9 and republish as a separate, informative adjunct document |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-30 |
Use of term "parent" confusing |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-23 |
Touchpoint notion does not require query capability |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-29 |
Metamodel level terminology obsolete |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-73 |
ResourceRole AssignTo association in Organization diagram 7.3.4.1 reversed |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-36 |
Meaning of "generalization" of instances |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-37 |
Semantic treatment of n-ary associations as tuples |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-18 |
Beta document does not address all the RFP perspectives |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-19 |
No glossary in the package descriptions |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-22 |
Section 1 - Scope should describe the submission, not the RFP |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-24 |
The term "class association" is an improper use |
BACM 1.0a1
|
BACM 1.0b2
|
Closed; No Change |
closed |
|
BACM-31 |
BACM semantic specification unclear |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-5 |
Remove Annex B from the specification document |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-32 |
Use of "leg" terminology to describe relationships |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-41 |
Rewrite the second paragraph of section 7.2.1 to clarify the relationship between the specification document and the normative XMI |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-43 |
The 3rd paragraph of 7.2 is unclear |
BACM 1.0a1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-35 |
Unclear specification of instantiation of variable arity relationships |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-11 |
Deliver MOF compliant XMI for specification |
BACM 1.0b1
|
BACM 1.0b2
|
Resolved |
closed |
|
BACM-33 |
Usage of "leg target" terminology unclear |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|
BACM-16 |
Incomplete description of association reification |
BACM 1.0a1
|
BACM 1.0b2
|
Duplicate or Merged |
closed |
|