Holarch

Frameworks

DoDAF

DoD Architecture Framework 2.02 products built from the LML model. Each product is tracked on a root entity and opens the matching Holarch view.

Where to find it

  • In the navigation rail: Frameworks → DoDAF.
  • Tabs: Products, Architecture Description (dodaf?tab=arch) and Check Architecture (dodaf?tab=check).

Main actions

  • Top bar: Export ▾ (Architecture Package (Word), DoDAF Products (JSON), DM2 PES Subset (XML, not schema-validated)) and + Create DoDAF Product, whose ▾ adds Create from Existing… and Update Schema with DoDAF Labels.
  • The DoDAF 2.02 product catalog on the Products tab lists all 57 products; click one to create it. A product page has All Products and Open … for its view in the top bar.
  • Architecture Description: name the architecture and state its purpose, tick the products in scope and write the decision each one supports. Status: Not started, In progress or Populated.
  • Check Architecture: cross-view consistency checks; each finding links to the entity and the product to fix. Run Again repeats them.

Viewpoints

ViewpointWhat it describesHolarch representation
AV (All)Scope, purpose, findings and vocabularyAV-1: a document with a standard outline and pictures. AV-2: the Integrated Dictionary.
CV (Capability)Vision, taxonomy, phasing and dependenciesCV-1: whiteboard, imported picture or Asset diagram. CV-2: Hierarchy. CV-3: Timeline. CV-4…CV-7: matrices.
DIV (Data and Information)Concepts, logical and physical dataClass diagrams.
OV (Operational)Concept, performers, exchanges, activities, rules, states, event tracesOV-1: whiteboard, imported picture or Asset diagram. OV-2: Physical I/O. OV-3: resource-flow table. OV-4, OV-5a: Hierarchy. OV-5b: IDEF0 or Action. OV-6a: rules table. OV-6b: State Machine. OV-6c: Sequence.
PV (Project)Projects, organizations and timelinesPV-1/PV-3: matrices. PV-2: Timeline.
SV / SvcV (Systems / Services)Systems or services, interfaces, functions, measures, evolution, rules, statesSV-1: Asset. SV-2: Physical I/O. SV-3: I². SV-4: Hierarchy, IDEF0 or Action. SV-5, SV-7 and SvcV matrices. SV-6: resource-flow table. SV-8/9: Timeline. SV-10a: rules table. SV-10b: State Machine. SV-10c: Sequence.
StdV (Standards)Current and forecast standardsA query of Artifacts labeled Standard.

Matrix products use labels such as Capability, Activity, Function, Organization, Project, Service and System. Add them in the Entity View or the Database (Label ▾). Click a matrix cell to add or remove the relationship.

OV-1 and CV-1 pictures

  • Whiteboard: the product page draws the board or frame live. Elements linked to model entities become hotspots and are listed as the view's linked elements; they count as product entities for AV-2, checks and exports. Open Whiteboard edits the board; Change Board… picks another.
  • Imported image: the picture is stored on the root Artifact. SVG files are cleaned on import (scripts, event handlers, embedded content and external references are removed). Drag to pan, scroll or − / + / ⤢ to zoom. Replace Graphic… keeps the earlier picture under Versions; Download Original saves the stored file. Draw Hotspot links a rectangle of the picture to an entity.
  • The picture is also an Imported Graphic diagram for documents and presentations.

Rules, AV-1 and AV-2

  • OV-6a, SV-10a, SvcV-10a are rules tables: Statements labeled Operational, System or Service Rule, with a type (Structural Assertion, Action Assertion, Derivation) and what each applies to (traced to). Download CSV or XLSX, or open the rules as a document.
  • AV-1 starts with an outline (Architecture Identification, Scope, Purpose and Viewpoint, Context, Time Frame, Tools and File Formats, Findings) and + Attach Graphic….
  • AV-2 Integrated Dictionary lists every entity used by a product with its class, definition and the products that use it; download CSV or XLSX.

Tips

  • The Architecture Package (Word) has a contents field (Word asks to update it on opening), the description, then each in-scope product with its picture or diagram, tables, narrative and captions.
  • The DM2 PES Subset uses DoDAF Meta Model concept names in Holarch's own namespace and is not validated against the DM2 schema.

Related

Make an OV-1 for DoDAF · UAF · Whiteboards