Enterprise Architecture and Systems Engineering: Relationships, Frameworks, and Modeling Approaches

The author, a member of the Open Group and the INCOSE California chapter, recounts a heated debate in a joint meeting where the INCOSE local chair argued that EA is fully encompassed by SE and that distinguishing between them is irrelevant.

The SE community did not fully accept this view; the INCOSE Architecture Working Group (AWG) aims to extend architectural practice within SE, and DoDAF meetings have been held by the Department of Defense.

A DoDAF‑SE integration paper highlighted that EA involves far more than engineering, encompassing social, cultural, business, and management factors, and only about 10% of a 500‑person audience identified as engineers.

EA draws from multiple practices, including SE, and TOGAF 9.2 emphasizes Business Architecture as the primary driver for other domains. Numerous frameworks exist, prompting an OMG‑led effort to create a Unified Architecture Framework (UAF) that unifies DoDAF, MoDAF, NAF, and others under the UPDM (Unified Profile for DoDAF and MoDAF) initiative.

UPDM uses SysML and UML as its primary modeling languages, reflecting OMG’s strong focus on model‑based systems engineering (MBSE). Shared vocabularies and processes such as project management, requirements management, architecture, testing, configuration, and risk management are emphasized.

MBSE is defined as a formal modeling approach that supports the entire lifecycle of system development, producing system models, specifications, and other deliverables from a unified model repository.

The benefits of SE and EA models include capturing, analyzing, sharing, and managing information; improving stakeholder communication; enhancing the ability to manage complexity; and supporting knowledge reuse, change management, and design accuracy.

OMG describes SysML as a general‑purpose graphical language for specifying, analyzing, designing, and verifying complex systems, and asserts that SysML combined with DoDAF equals UPDM.

UPDM has been adopted by several tool vendors (Atego, IBM, No Magic, Sparx) enabling architects to develop architectures at higher abstraction levels consistently.

The purpose of UPDM is to provide a concise language that captures stakeholder concerns, reduces ambiguity, and supports the optimization of architecture designs.

UPDM is not a new framework; according to ISO/IEC/IEEE 42010 it is a graphical enterprise modeling language rather than a method or process.

The future direction is UAF, which aims to address the proliferation of frameworks, support industrial, federal, and military needs, and allow both SysML and non‑SysML tools to implement the unified specifications.

A grid‑based approach is illustrated (image) to manage competing frameworks and simplify complex mapping tables.

Another image shows a mapping between DoDAF models and the TOGAF content meta‑model, emphasizing the relationship between the two.

While SE and EA share many modeling features and stakeholder sets, they differ in perspective: EA focuses on business and how IT (data, application, technology architecture) supports it, providing a roadmap for transformation, whereas SE implements the system designs derived from that roadmap.

For further discussion and community resources, the article lists various contact channels such as the Knowledge Planet, WeChat accounts, QQ groups, video channels, and other social media platforms.