Do DAF 2 0 An Emerging Success Story

  • Slides: 10
Download presentation
Do. DAF 2. 0 – An Emerging Success Story Making the Leap from Do.

Do. DAF 2. 0 – An Emerging Success Story Making the Leap from Do. DAF 1. x Kendall Young AP&T, Chief Architect, Enterprise Architecture Northrop Grumman Aerospace Systems Approved for Public Release: Northrop Grumman Aerospace Systems Case 11 -1644, 1/3/2012

Success with Do. DAF 2. 0 Topics • What Constitutes Success with Do. DAF

Success with Do. DAF 2. 0 Topics • What Constitutes Success with Do. DAF 2. 0 ? • Planning for Success • Results so Far • DM 2 – the Key to Success • Migration Lessons 2 Approved for Public Release: Northrop Grumman Aerospace Systems Case 11 -1644, 1/3/2012

Do. DAF 2. 0 – What Constitutes Success ? • Executing EA in Do.

Do. DAF 2. 0 – What Constitutes Success ? • Executing EA in Do. DAF 2. 0 & DM 2 • Utilizing Do. DAF 2. 0 – Reporting – Analyses • Impacting Business Results – Supporting Business Process Execution – Program Execution – Pursuits & Initiatives • Enhancing Community & Communications – Shared Awareness – Stakeholder Engagement – Architectural Vision Common Thread – Thinking and Speaking in DM 2 3 Approved for Public Release: Northrop Grumman Aerospace Systems Case 11 -1644, 1/3/2012

Do. DAF 2. 0 – Planning for Success • Migrating to Do. DAF 2.

Do. DAF 2. 0 – Planning for Success • Migrating to Do. DAF 2. 0 & DM 2 – As-Is: Do. DAF 1. x & CADM – To-Be: Do. DAF 2. 0 & DM 2 – Transition Plan: the “How To” on Migrating for • Green Fields – Do. DAF 2. 0 Architectures from scratch • Conversions from Existing Do. DAF 1. x Architectures Transition Plan Do. DAF 1. 5 As-Is Do. DAF 2. 0 To-Be A Classic Enterprise Architecture Approach 4 Approved for Public Release: Northrop Grumman Aerospace Systems Case 11 -1644, 1/3/2012

Do. DAF 2. 0 – Results To Date • Executing EA: Several Architectures Generated

Do. DAF 2. 0 – Results To Date • Executing EA: Several Architectures Generated / In Work – 2 Green Fields, 3 Conversions, 1 Hybrid • Tooling Online, Shared Databases – 9 Tools Assessed; 5 Tools Deployed; 3 Tools in Evaluation • Do. DAF 2. 0 Processes – Evolved from Do. DAF 1. x Processes • Portal Deployment Online • Standards Available – Sample Data & Artifacts • Skill Development – Do. DAF 2. 0 Training Materials Developed – Conducted first two Do. DAF 2. 0 Training events – 7 Architects Fluent in Do. DAF 2. 0 / DM 2 Thinking in Do. DAF 2. 0 / DM 2 – The Most Vital Thing 5 Approved for Public Release: Northrop Grumman Aerospace Systems Case 11 -1644, 1/3/2012

Navigating from CADM to DM 2 • Assumptions • Constraints – Do. DAF 1.

Navigating from CADM to DM 2 • Assumptions • Constraints – Do. DAF 1. 5 Objects and Associations have a place within DM 2 – DM 2 is the “point of departure” for Do. DAF 2. 0 Compliance – For conformance, Tools must: • fully implement DM 2 structure – Framework and Data Concept Changes – Tools • Do. DAF Maturity • Conversion Capability • Cross-Tool Interoperability OR • provide a credible data mapping taxonomy – Changes in Data Concepts will have minor impacts to existing graphical products – Tools will provide data export and import functionality 6 Do. DAF 1. 5 Approvedfor for. Public. Release: Northrop. Grumman. Aerospace. Systems. Case 11 -0417, 11 -1644, 3/28/2011 1/3/2012 Do. DAF 2. 0

CADM to DM 2 Migration: High Level Concept Do. DAF 1. 5 Tool &

CADM to DM 2 Migration: High Level Concept Do. DAF 1. 5 Tool & Data Schema Do. DAF 2. 0 Key Data Exports Logical Data Mapping Key Data Imports Views and Products Viewpoints and Models Objects and Data Associations Tool & Data Schema Data and Association, Graphical Products, Project Structure 7 Approvedfor for. Public. Release: Northrop. Grumman. Aerospace. Systems. Case 11 -0417, 11 -1644, 3/28/2011 1/3/2012

OV-2 Operational Resource Flow Description • Do. DAF 2. 0 OV-2 Description: A description

OV-2 Operational Resource Flow Description • Do. DAF 2. 0 OV-2 Description: A description of the Resource Flows exchanged between operational activities. Necessary Do. DAF 1. 5 Product Data Concepts Necessary Do. DAF 2. 0 Model Data Concepts Operational Node Performer Org, Location, Person Role • Do. DAF 1. 5 OV-2 Description: Operational nodes, connectivity, and information exchange need lines between nodes Op. Activity Need Line No 1 st Class Concept Information Resource Do. DAF 2. 0 Necessary Associations Performer Part Of Org, Loc, Ind. Type Performs activity. Resource. Overlap Activity Performs activity. Whole. Producing Part. Of. Activity Producing. Part Of. Activity Resource Part Of Type Of Performs activity. Whole. Consuming Part. Of. Activity Consuming. Part Of. Activity Part Of Activity Performs Resource Model Depiction Type: Structural Diagram 8 Performer Approvedfor for. Public. Release: Northrop. Grumman. Aerospace. Systems. Case 11 -0417, 11 -1644, 3/28/2011 1/3/2012 Org, Loc, Ind. Type

Do. DAF 2. 0 – Migration Lessons • Execute Migration with an EA Approach

Do. DAF 2. 0 – Migration Lessons • Execute Migration with an EA Approach (As-Is, To-Be, Transition) • Full Spectrum (Framework) Migration – More Than…. tools, DM 2 • Map the Data Concepts (diagram by diagram) • Choose a Tool that Implements DM 2 – get the Metadata Right! – Diagrams & Language Standards are secondary • Conversions are VITAL! More important than Green Fields for learning – Trains the mind on the Data Mapping – Provides a means of Validation (comparison with the Source 1. x architecture) – Enables Reuse – Tooling Support is Key: • DM 2 compliance, Data Mapping, Diagram Support Migration to Do. DAF 2. 0 Hinges on DM 2 9 Approved for Public Release: Northrop Grumman Aerospace Systems Case 11 -1644, 1/3/2012