DoD Enterprise Architecture DoD EA Conference 2012 Chris White 3 May, 2012 accelerating growth reducing risk increasing profitability
Enterprise Architecture Enterprise Architecture is Discipline i of translating ti business vision ii and strategy t into enterprise change The Value of EA is The ability for business and ITl leaders to make more effective investment t decisions The Output of EA is Creation and communication of key requirements, principles, and models that describe the enterprise s future state and enable its evolution The Scope of the Enterprise Architecture includes The people, processes, information, and technology of the enterprise Their relationships to one another and to the external environment
Enterprise Architecture We don t need to design the network, we need to justify the network Do we have an integrated end to end process? Why are we so focused on what we re building before we do the functional allocation? How do we prioritize Data Center Consolidation?
The DoD Architecture Framework
The DoDAF 2.0 Metamodel (DM2)
UML and SySML a standardized general purpose modeling languagein the field of object oriented software engineering includes a set of graphic notation techniques to create visual models of object oriented softwareintensive systems a general purpose modeling language for systems engineering applications supports the specification, analysis, design, verification and validation of a broad range of systems and systems of systems
UPDM Unified Profile for DoDAF/MODAF A profile in the Unified Modeling Language (UML) provides a generic extension mechanism for customizing UML models for particular domains and platforms (e.g J2EE and.net) UPDM dfi defines a set of UML and optional SysML stereotypes, t model dl elements and associations to satisfy the requirements of the UPDM RFC. www.updmgroup.com UML is NOT a required mandate for developing DoDAF architecture UPDM is NOT a required mandate for developing DoDAF architecture UPDMISthe required UMLprofile IFyou are using UML/SysML for a UPDM IS the required UML profile IF you are using UML/SysML for a DoDAF architecture
DoDAF Landscape Enterprise Architecture Reference Architectures Service Level Architectures Branch Level Architecture Program Architecture DM2 CDM DM2 LDM DM2 PES Service Level Architectures Branch Level Architecture Program Architecture Solution Architecture UPDM XMI Solution Architecture
DoDAF Models mapped to Zachman FW Where Who What How When Why Scope Contexts DV 1 CV 2 CV 4 CV 3 PV 2 AV 1 CV 1 Strategists As Theorists OV 1 Business Concepts OV 4 OV 2 DV 2 OV 5b CV 6 CV 7 OV 5a OV 6a Executive Leaders As Owners OV 3 OV 6b/c System Logic SV 3 DV 3 SV 1, SvcV 1 SV 2, SvcV 2 SV 5 SvcV 5 SvcV 8 SvcV 9 SV 8 SvcV 10a SV 10a Architects as Designers SvcV 3b SvcV 4 SV 9 SvcV 3a SV 4 StdV 2 SvcV 6 SV 6 SvcV 10b/c SV 10b/c DM2 Conceptual Entities Location Performers Resources, 9 Capabilities, Time, DoDAF: Vision, Information Activities Projects Desired Operational View Effects
Enterprise Architecture CIOs are under increased pressure from business leaders to show the business relevance (i.e Mission Relevance) and value of IT. CIOs use the enterprise architecture (EA) )process as a key to transforming IT and addressing this challenge
Gartner EA Magic Quadrant Focused frameworks and Models Bringing information to more people in the organization Good modeling and simulation provide diverse methods Collaboration among diverse stakeholders
The Casewise Offering/Suite of Capabilities Support for DoDAF 2.0 and the DM2 Tools, Training, Consulting
The Casewise Offering/Suite of Capabilities Architecture Analysis and Business Intelligence
The Casewise Offering/Suite of Capabilities Business Process/Workflow Automation
The Casewise Offering/Suite of Capabilities Technology Innovation Application Portfolio Management/Collaborative Web/Mobile