130 likes | 184 Views
This briefing covers the streamlined methodology of CADM 1.04, providing a high-level overview, current status, and walk-through of DoDAF products. It discusses the concept of irreducible complexity in information models, emphasizing the balance between explicit model complexity (EM) and business rules (BR). Key aspects include explicit versioning, legacy data transferability, and reduction in entities and relations. The methodology introduces new supertypes and guidance for implementation, ensuring compliance with DoDAF 1.0 requirements. The conclusion emphasizes the simplification of models and outlines recommendations for future steps.
E N D
CADM 1.04Way Ahead for the Core Architecture Data Model Francisco Loaiza IDEAS 23-27 OCT 06
Briefing Contents • Preliminary Considerations • CADM 1.04 – Streamlining Methodology Employed • High-Level Overview • Current Status • Walk-Through (DoDAF Products) • Conclusions & Recommendations
Irreducible Complexity 1 2 EM BR BR EM • There is a certain amount of Irreducible Complexity in every Information ModelEM + BR = Constant • Reduction in the Explicit Model (EM) complexity ends up increasing the number of Business Rules (BR) • Conversely, simplification of the BR complexity normally requires a more complex EM 1 2
CADM 1.02/1.03 • An explicit model • Large number of entities • Large number of attributes • Large number of relations • BR’s mostly for data fill • Scope • All 26 DoDAF 1.0 products • Additional DoD Requirements (e.g., FEAF) • Additional Service Requirements(e.g., Army, Navy)
CADM 1.04 • Streamlines CADM 1.02/1.03 Specifications • Supports Repository Implementation (DARS, etc.) • Explicit Versioning • Scope Identical to CADM 1.02/1.03 • Any data set built in accordance with CADM 1.02/1.03 can be recast as a CADM 1.04 data set • Provides full legacy data transferability • Reduced Number of: • Entities • Relations • Increased Number of BR’s to express same CADM 1.02/1.03 semantics
Methodology(1) • Addition of New Supertypes • Object • ObjectVersion • ObjectVersionAssociation • ObjectByReference • ObjectItem • ObjectType • ArchitectureElement • Only Essential CADM 1.02/1.03 are modeled explicitly • All retained CADM 1.02/1.03 entities are now part of one of the following “taxonomies” • ObjectType • ObjectItem • ArchitectureElement • BR’s provide guidance for implementation
CADM 1.04 Status • UML Version Completed • Sparx Enterprise Architect • Rational Rose • XMI • ERwin Version Completed • Uses Object Oriented Naming Convention • Main Report Draft Completed • Business Rule Document Draft Completed
Conclusions & Recommendations • CADM 1.04 • Eliminates explicit complexity • Supports all DoDAF 1.0 Requirements • Supports additional requirements identified during 1998-2004 period (DoD, Services, Agencies) • Next Steps • Assess Applicability of Approach and Structures • Focus debate on the “Taxonomies” and other Functionality not Captured • Continue adoption of 1.0x versions of CADM as DoD standards