Successfully reported this slideshow.

2003-1118 REAP Overv..


Published on

  • Be the first to comment

2003-1118 REAP Overv..

  1. 1. Integrating TOGAF, Zachman and DoDAF Into A Common Process Rolf Siegers Senior Principal Software Systems Engineer November 2003
  2. 2. Topics <ul><li>Definitions </li></ul><ul><li>Why Architecture? </li></ul><ul><li>Building Blocks of an Architecture Process </li></ul><ul><li>Unifying the Standards </li></ul><ul><li>Summary </li></ul>
  3. 3. Definitions <ul><li>Architecture </li></ul><ul><ul><li>“ The fundamental organization of a system embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution.” (IEEE 1471-2000) </li></ul></ul><ul><li>Architecture Framework </li></ul><ul><ul><li>A resource that guides the development or description of an architecture </li></ul></ul><ul><li>Business Architecture </li></ul><ul><ul><li>A perspective of the overall architecture reflecting enterprise mission, strategies, goals, business drivers, business processes, information flows, and the supporting organizational structure </li></ul></ul><ul><li>Technical Architecture </li></ul><ul><ul><li>Perspectives of the overall architecture reflecting the enterprise’s data, applications and technical components </li></ul></ul><ul><li>Enterprise Architecture </li></ul><ul><ul><li>A blueprint (set of models) that depicts how various business and technical elements work together as a whole </li></ul></ul><ul><li>Enterprise </li></ul><ul><ul><li>“ e” : the highest level of a system or system of systems </li></ul></ul><ul><ul><li>“ E” : a Department or Agency of the government </li></ul></ul>
  4. 4. Why Architecture?
  5. 5. Why Architecture? <ul><li>Government </li></ul><ul><li>Customer Expectations </li></ul><ul><li>Industry </li></ul><ul><li>Competition </li></ul><ul><li>Academia </li></ul><ul><li>Our Future </li></ul>
  6. 6. Why Architecture? – Government: Background <ul><li>The US Government has clearly established their direction and expectation for how complex systems of the future will be developed and integrated… through architecture. </li></ul><ul><li>Spans all Departments and Agencies </li></ul><ul><li>Not the tech or process trend du jour – this is traceable back over a decade </li></ul><ul><ul><li>Department of Defense Architecture Framework 2003 </li></ul></ul><ul><ul><li>Federal Enterprise Architecture Service Component & 2003 Technical Reference Models </li></ul></ul><ul><ul><li>Federal Enterprise Architecture Business Reference Model 2002 </li></ul></ul><ul><ul><li>Federal/DoD Enterprise Architecture Certification Institute 2002 </li></ul></ul><ul><ul><li>Federal Enterprise Architecture Program Management Office 2001 </li></ul></ul><ul><ul><li>Treasury Enterprise Architecture Framework 2000 </li></ul></ul><ul><ul><li>Federal Enterprise Architecture Framework 1999 </li></ul></ul><ul><ul><li>C4ISR Architecture Framework 1996, 1997 </li></ul></ul><ul><ul><li>Establishment of CIO Council by Executive Order 13011 1996 </li></ul></ul><ul><ul><li>Congressional acts (GPRA 1993; FASA 1994; ITMRA 1996) </li></ul></ul><ul><ul><li>Defense Science studies of early 1990s </li></ul></ul>
  7. 7. Why Architecture? – Government: Sound Bites <ul><li>OMB: Business cases must relate to enterprise architectures for 2005 ; Government Computer News; 5/22/03 </li></ul><ul><ul><li>“ Agencies should include with their business case submissions a copy of their architecture framework and an explanation of how it relates to the federal blueprint…more than 2,000 agency officials have attended seminars the office conducts on how to prepare business cases. ” </li></ul></ul><ul><li>Get down to business with an architecture ; Government Computer News; 4/7/03 </li></ul><ul><ul><li>“ The message from the Office of Management and Budget to agency managers is loud and clear: No enterprise architecture, no funding.” </li></ul></ul><ul><li>DoD lays out enterprise architecture plans ; Government Computer News; 4/4/03 </li></ul><ul><ul><li>“… the grid will be a globally connected, single information system with an enterprise architecture called the Net-Centric Enterprise Service …[SAIC] last month received a $50 million, five-year contract from the Office of the Joint Chiefs of Staff to plan and develop the grid.” </li></ul></ul><ul><li>Architecture due diligence ; Federal Computer Week; 3/31/03 </li></ul><ul><ul><li>“ Agency spending on enterprise architectures is expected to increase to more than $1 billion this year according to OMB…” </li></ul></ul><ul><li>Feds work on melding architectures ; Federal Computer Week; 2/10/03 </li></ul><ul><ul><li>“ The Defense framework is probably the farthest removed from the FEA, but developers of the framework have checked, and if components are collecting the data needed to meet DOD architecture requirements, the data should also qualify for the FEA reference models , [Mitre] said.” </li></ul></ul><ul><ul><li>[Note: Article titles above are hyperlinks] </li></ul></ul>
  8. 8. Why Architecture? – Government: Sound Bites <ul><ul><li>OMB looks to extend architecture to DOD, intelligence ; Government Computer News; 9/13/02 </li></ul></ul><ul><ul><ul><li>“ The Office of Management and Budget is beginning to figure out how to integrate the federal enterprise architecture with the Defense Department and intelligence agencies systems.” </li></ul></ul></ul><ul><ul><li>If you only read one article on the importance of this topic, please read Information Week, Nov 11 2002 </li></ul></ul><ul><ul><li>One Nation, Under I.T. </li></ul></ul><ul><ul><li>http://www. informationweek .com/shared/ printableArticle . jhtml ? articleID =6504197 </li></ul></ul>
  9. 9. <ul><li>Architecting Method </li></ul>Piecing The Puzzle Together: What’s Needed In An “Architecting Process”? <ul><li>Architecture Validation </li></ul><ul><li>Product Formats </li></ul><ul><li>Collaboration </li></ul><ul><li>Architectural Products </li></ul>METHOD PRODUCTS FORMATS VALIDATION COLLABORATION
  10. 10. <ul><li>Architecting Method </li></ul><ul><li>Architectural Products </li></ul><ul><li>Product Formats </li></ul><ul><li>Architecture Validation </li></ul><ul><li>Collaboration </li></ul>Building Blocks The Open Group Architecture Framework (TOGAF) Version 8.0 Enterprise Edition Architecture Development Method (ADM)
  11. 11. <ul><li>Architecting Method </li></ul><ul><li>Architectural Products </li></ul><ul><li>Product Formats </li></ul><ul><li>Architecture Validation </li></ul><ul><li>Collaboration </li></ul>Building Blocks (cont’d) The Department of Defense Architecture Framework (DoDAF) Final Draft Version 1.0
  12. 12. <ul><li>Architecting Method </li></ul><ul><li>Architectural Products </li></ul><ul><ul><li>Supplementing the DoDAF </li></ul></ul><ul><li>Product Formats </li></ul><ul><li>Architecture Validation </li></ul><ul><li>Collaboration </li></ul>Building Blocks (cont’d) The Zachman Framework For Enterprise Architecture
  13. 13. <ul><li>Architecting Method </li></ul><ul><li>Architectural Products </li></ul><ul><li>Product Formats </li></ul><ul><li>Architecture Validation </li></ul><ul><li>Collaboration </li></ul>Building Blocks (cont’d) <ul><li>DoDAF Templates </li></ul><ul><li>Unified Modeling Language (UML) </li></ul><ul><li>Integrated Computer-Aided Manufacturing (ICAM) DEFinition (IDEF) </li></ul>DoDAF, Final Draft Version 1.0
  14. 14. <ul><li>Architecting Method </li></ul><ul><li>Architectural Products </li></ul><ul><li>Product Formats </li></ul><ul><li>Architecture Validation </li></ul><ul><li>Collaboration </li></ul>Building Blocks (cont’d) <ul><li>Software Engineering Institute’s Architecture Tradeoff Analysis Method SM </li></ul><ul><li>Quality Attribute Assessment Techniques (e.g., Colored Petri Nets) </li></ul>Software Engineering Institute University of Aarhus CS Department
  15. 15. Building Blocks (cont’d) <ul><li>Architecting Method </li></ul><ul><li>Architectural Products </li></ul><ul><li>Product Formats </li></ul><ul><li>Architecture Validation </li></ul><ul><li>Collaboration </li></ul>
  16. 16. REAP: A Unification of Standards <ul><li>Raytheon Enterprise Architecture Process (REAP) </li></ul><ul><ul><li>I Enterprise Understanding </li></ul></ul><ul><ul><li>II Architecture Planning </li></ul></ul><ul><ul><li>III Business Architecting </li></ul></ul><ul><ul><li>IV Technical Architecting </li></ul></ul><ul><ul><li>V Architecture Validation </li></ul></ul>Software Engineering Institute Five Activities of Architecture Process Inter-Activity Iteration Intra-Activity Iteration Activity V Architecture Validation Activity IV Technical Architecting Activity I Enterprise Understanding Activity II Architecture Planning Activity III Business Architecting
  17. 17. Activity I: Enterprise Understanding <ul><li>Goals </li></ul><ul><ul><li>Set context for architecture and architecting activities </li></ul></ul><ul><ul><li>Common understanding with customer on the [E/e]nterprise, the architecting initiative, and the problem space </li></ul></ul><ul><li>TOGAF Relationship </li></ul><ul><ul><li>ADM: Phase A </li></ul></ul><ul><li>Outputs </li></ul><ul><ul><li>DoDAF AV-1, Overview & Summary Information </li></ul></ul><ul><ul><li>DoDAF AV-2, Integrated Data Dictionary </li></ul></ul><ul><ul><li>DoDAF OV-1, High Level Operational Concept Graphic </li></ul></ul><ul><ul><li>DoDAF TV-1, Technical Standards Profile </li></ul></ul><ul><li>Subprocesses </li></ul><ul><ul><li>Customer-focused architecting </li></ul></ul><ul><ul><li>Requirements analysis </li></ul></ul><ul><ul><li>Operational/Business analysis </li></ul></ul><ul><ul><li>Quality attribute analysis </li></ul></ul><ul><li>Inputs </li></ul><ul><ul><li>Customer vision, needs, & requirements documents </li></ul></ul><ul><ul><li>Domain expertise </li></ul></ul><ul><ul><li>Industry & government standards </li></ul></ul>Activity I Enterprise Understanding
  18. 18. Activity II: Architecture Planning <ul><li>Goal </li></ul><ul><ul><li>Establish a plan for the upcoming architecting activities, the goals of the architecture and the architectural outputs </li></ul></ul><ul><li>TOGAF Relationship </li></ul><ul><ul><li>ADM: Preliminary Phase, Phase A </li></ul></ul><ul><li>Outputs </li></ul><ul><ul><li>Architecture principles </li></ul></ul><ul><ul><li>Architecture schedule </li></ul></ul><ul><ul><li>Enhanced DoDAF AV-1, Overview & Summary Information </li></ul></ul><ul><ul><li>Architecture engineering environment </li></ul></ul><ul><li>Subprocesses </li></ul><ul><ul><li>Identify stakeholders </li></ul></ul><ul><ul><li>Define architecture principles </li></ul></ul><ul><ul><li>Identify architectural products, formats and the supporting Zachman cells </li></ul></ul><ul><ul><li>Define product relationships / dependencies </li></ul></ul><ul><ul><li>Define schedule </li></ul></ul><ul><ul><li>Select tool(s) </li></ul></ul><ul><ul><li>Plan concordance, configuration & consolidation of architectural products </li></ul></ul><ul><ul><li>Form/train Architecture Team </li></ul></ul><ul><li>Inputs </li></ul><ul><ul><li>Customer vision, needs, & requirements documents </li></ul></ul><ul><ul><li>DoDAF AV-1, AV-2, OV-1, TV-1 </li></ul></ul><ul><ul><li>Quality attribute-based requirements </li></ul></ul>Activity II Architecture Planning
  19. 19. Activity III: Business Architecting <ul><li>Goal </li></ul><ul><ul><li>Model the customer’s view </li></ul></ul><ul><li>TOGAF Relationship </li></ul><ul><ul><li>ADM: Phase B </li></ul></ul><ul><li>Outputs </li></ul><ul><ul><li>Business/Mission Scenarios within DoDAF OV-5, Operational Activity Model </li></ul></ul><ul><ul><li>Catalogued information from Zachman Framework Row 2 Cells </li></ul></ul><ul><li>Subprocesses </li></ul><ul><ul><li>Collect Zachman Framework “primitives” for Row 2 </li></ul></ul><ul><ul><ul><li>Produce mapping matrices as needed </li></ul></ul></ul><ul><ul><li>Model Business/Mission Scenarios </li></ul></ul><ul><li>Inputs </li></ul><ul><ul><li>Customer vision, needs, & requirements documents </li></ul></ul><ul><ul><li>Domain expertise </li></ul></ul><ul><ul><li>Architecture principles </li></ul></ul><ul><ul><li>DoDAF AV-1, AV-2, OV-1 </li></ul></ul><ul><ul><li>Architecture engineering environment </li></ul></ul>Activity III Business Architecting
  20. 20. Activity IV: Technical Architecting <ul><li>Goal </li></ul><ul><ul><li>Produce the remaining architectural descriptions of the enterprise from a variety of views </li></ul></ul><ul><li>TOGAF Relationship </li></ul><ul><ul><li>ADM: Phases C, D </li></ul></ul><ul><li>Outputs </li></ul><ul><ul><li>Architecture Baseline Package </li></ul></ul><ul><ul><li>Executable model </li></ul></ul><ul><li>Subprocesses </li></ul><ul><ul><li>Develop/mature the defined DoDAF view products </li></ul></ul><ul><ul><li>Develop the defined additional architectural products </li></ul></ul><ul><ul><li>Ensure concordance between architectural products </li></ul></ul><ul><ul><li>Iteratively evolve an executable model </li></ul></ul><ul><li>Inputs </li></ul><ul><ul><li>Business Architecture </li></ul></ul><ul><ul><li>Customer vision, needs, & requirements documents </li></ul></ul><ul><ul><li>Domain expertise </li></ul></ul><ul><ul><li>Architecture principles </li></ul></ul><ul><ul><li>DoDAF AV-1, AV-2, OV-1, OV-5, TV-1 (and its referenced standards) </li></ul></ul>Activity IV Technical Architecting
  21. 21. Activity V: Architecture Validation <ul><li>Goal </li></ul><ul><ul><li>Ensure the architecture is ready to be implemented </li></ul></ul><ul><li>Outputs </li></ul><ul><ul><li>Completed architecture checklist </li></ul></ul><ul><ul><li>Simulation results </li></ul></ul><ul><ul><li>SEI’s Architecture Tradeoff Analysis Method SM results </li></ul></ul><ul><ul><li>Validated architecture </li></ul></ul><ul><li>Subprocesses </li></ul><ul><ul><li>Architecture checklist </li></ul></ul><ul><ul><li>ATAM SM </li></ul></ul><ul><ul><li>Quality attribute assessments </li></ul></ul><ul><li>Inputs </li></ul><ul><ul><li>Architecture Baseline Package </li></ul></ul><ul><ul><li>Executable model </li></ul></ul>Activity V Architecture Validation
  22. 22. Other Analysis Efforts <ul><li>Enterprise Architecting Tools </li></ul><ul><li>Object Management Group’s Model-Driven Architecture </li></ul><ul><li>UML 2.0 for Systems Engineering </li></ul><ul><li>OMB’s Federal Enterprise Architecture Reference Models </li></ul><ul><li>CMMI and IEEE-1471 Mappings </li></ul><ul><li>Standardized supplemental views </li></ul><ul><li>Agile Modeling </li></ul><ul><li>Open Systems Architectures </li></ul><ul><li>Certification Programs </li></ul>
  23. 23. Summary <ul><li>There are established industry and government standards to help us address enterprise-wide architectural alignment between customer mission, strategic goals, business rules, data, application systems, organization, and technology. </li></ul><ul><li>No one standard or framework addresses all the aspects of the architecting process. Unification is necessary to complete the picture. </li></ul>
  24. 24. Questions? Rolf Siegers Raytheon Intelligence and Information Systems Garland, Texas rolf _ siegers @ raytheon .com 972.205.5169
  25. 25. Reference Links <ul><li>The Open Group Architecture Framework, Version 8.0 </li></ul><ul><ul><li>http://www. opengroup .org/architecture/togaf8/index8. htm </li></ul></ul><ul><li>C4ISR Architecture Framework, Version 2.0 </li></ul><ul><ul><li>http://www. defenselink .mil/ nii /org/ cio /i3/AWG_Digital_Library/index. htm </li></ul></ul><ul><li>Department of Defense Architecture Framework, Version 1.0 </li></ul><ul><ul><li>(intermittent drafts appears on Mitre’s web site; final draft is currently out, but no formal release statement has been issued yet) </li></ul></ul><ul><li>Zachman Framework for Enterprise Architecture </li></ul><ul><ul><li>http://www. zifa .com </li></ul></ul><ul><ul><li>http://www. zachmaninternational .com </li></ul></ul><ul><li>Software Engineering Institute’s Architecture Evaluations </li></ul><ul><ul><li>http://www. sei . cmu . edu / ata / ata _ eval .html </li></ul></ul>