Physical Design Criteria for an Enterprise Architecture Repository

, , ,

Keywords: , , ,

Rory Darling

Abstract

The repository is the primary physical product produced by an Enterprise Architecture (EA) program. A well designed EA repository extends specialized methodologies while avoiding the burdensome overhead of duplication. The most practical design strategy is adapting a flexible model pattern based on the Unified Modeling Language (UML). The essential elements of that pattern are architectural models that bind working models and extend them with architectural information, a profile of EA stereotypes that resolves conflicting terms, a mapping of the EA profile to viewpoints and decision support processes, and guidance on incorporating the syntax of a specific enterprise into model elements to make them understandable. This article examines physical EA repository design factors that affect its quality and practical usefulness, arguing that customization of a UML-based pattern guided by EA principles is the most practical and beneficial approach. It establishes the role of an EA repository as the mechanism for aggregating operational models into decision support models that expose architectural viewpoints. It defines relevant modeling terms and contrasts different model distribution patterns, concluding with a series of recommendations on extending working models into the enterprise decision support realm with minimal redundancy and without loss of meaning.

Keywords

UML, repository, Enterprise Architecture, model, methodology, physical design, repository design

ABOUT THE AUTHOR

Rory Darling is a consulting Enterprise Architect offering practical organizational and system development expertise. UML models are a distinguishing feature of his work. His experience includes custom application design; enterprise, business process, and data modeling; and Enterprise Architecture program implementation. Rory earned a BS in mathematics from Yale University and an MS in information management from the Syracuse University School of Information Studies.

REFERENCES

S. Bernard: Class notes for “Enterprise Architecture Basic Concepts” professional training course, slide 35: EA Program & Approach – Core Elements (2009).

C. Casanave: Enterprise Service-Oriented Architecture Using the OMG SoaML Standard (2009); found at: www.omg.org/news/whitepapers/EnterpriseSoaML.pdf.

Institute of Educational Cybernetics: Archi Overview (2012); found at: http://archi.cetis.ac.uk/.

Office of Government Commerce (UK): ITIL® Service Strategy, The Stationery Office (2007).

The Open Group: The TOGAF® 9 Standard, Section 34.3.1: Core Content Metamodel (2009).

The Open Group: Archimate® 2.0 Specification (2012). No Magic, Inc.: UPDM Plugin Introduction (2012); found at: www.nomagic.com/products/magicdraw-addons/updmplugin. html.

S.A. White: Introduction to BPMN, White Paper; found at: www.omg.org/bpmn/Documents/Introduction_to_BPMN.pdf.

Leave a Comment