The UML definition Dragon1 Open EA Method delivers a visual and textual modeling approach for enterprise architecture. This method unifies UML semantics with Dragon1 platform artifacts to support clear decision making and traceable design outcomes.
Targeted at architects and enterprise designers, the method aligns strategic goals with solution structures using lightweight diagrams and explicit metadata. The following sections detail the method overview, specialization profiles, modeling workflows, and operational guidance.
| Aspect | Definition | Key Artifacts | Primary Owner |
|---|---|---|---|
| UML Core | Standardized modeling language for structure, behavior, and interactions | Class, Activity, Sequence diagrams | Enterprise Architect |
| Dragon1 Viewpoints | Configurable visual layers linking stakeholders to architecture elements | Viewpoints, Viewmodels, Cards | Platform Admin |
| Open EA Method | Open, vendor-neutral approach to enterprise architecture practice | Method guidance, KPIs, maturity indicators | EA Governance Board |
| Traceability | UML elements linked to Dragon1 strategy cards and business capabilitiesTrace matrices, Impact maps | Architecture Owner |
Modeling With UML in Dragon1 Open EA
Structural and Behavioral Diagrams
Use UML class and component diagrams to map application landscapes within Dragon1. Complement them with activity and sequence diagrams to capture dynamic behavior and service flows.
Viewpoints Integration
Dragon1 viewpoints organize UML diagrams into stakeholder-specific layers. Each viewpoint references model fragments, ensuring relevance for executives, developers, and operators.
Specialization Profile for Enterprise Context
Profile Metamodel Overview
The Dragon1 Open EA Method defines a UML profile with stereotypes like {Capability}, {ValueStream}, and {KPI}. These extensions align modeling elements directly with enterprise strategy.
Tooling and Metadata Binding
Tools supporting the profile enforce trace links from UML packages to Dragon1 entities. Metadata such as owners, status, and priority are stored in tagged values for automated reporting.
Workflow and Governance
Model Development Lifecycle
Adopt an iterative workflow: discover assets, refine UML diagrams in Dragon1, validate with stakeholders, and publish view cards. Governance checks ensure model quality and policy compliance.
Quality and Version Controls
Use Dragon1 change tracking to manage diagram versions. Apply modeling guidelines that cover naming, stereotypes usage, and diagram completeness thresholds.
Operational Recommendations
- Define a UML profile tailored to your domain using Dragon1 extension points.
- Map high-level capabilities to UML packages and components for clear traceability.
- Standardize viewpoint templates for recurring stakeholder questions.
- Automate validation checks to enforce modeling standards and reduce manual reviews.
- Use versioned view cards to communicate decisions and monitor architecture evolution.
FAQ
Reader questions
How does the UML definition Dragon1 Open EA Method differ from pure UML modeling?
The method extends UML with Dragon1 stereotypes and viewpoint layers, directly linking models to enterprise capabilities, strategy cards, and KPIs for governance and traceability.
Can existing UML tools integrate with Dragon1 Open EA Method workflows?
Yes, model exchange via XMI and REST APIs connects mainstream UML tools to Dragon1, enabling synchronized updates between behavioral diagrams and enterprise view models.
What skills are needed to apply this method effectively in an enterprise setting?
Roles require familiarity with UML fundamentals, Dragon1 platform concepts, and EA governance practices; structured training and hands-on workshops accelerate adoption.
How is compliance validated when using UML diagrams within Dragon1 Open EA Method?
Built-in validation rules and policy templates check stereotype usage, trace completeness, and KPI alignment, with audit logs capturing review outcomes for compliance reporting.