Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Publishing a DoDAF EA Description? Provide a Meaningful Narrative

98 views

Published on

If you will publish an architectural description following the DoD Architecture Framework, provide a meaningful narrative. A recommended document outline is presented, with complete mapping to the DoDAF views.

Published in: Government & Nonprofit
  • Login to see the comments

Publishing a DoDAF EA Description? Provide a Meaningful Narrative

  1. 1. PUBLISHING AN ENTERPRISE ARCHITECTURE DESCRIPTION? PROVIDE A MEANINGFUL NARRATIVE Ben Bovée © 10 April 2017 Principal, Patterndigm
  2. 2. CONTENTS How NOT to write an architectural description (A.D.) How NOT to group the A.D. views How NOT to sequence the A.D. views How TO group and sequence the A.D. views Appendices  Appendix A: Abbreviations  Appendix B: References © 10 April 2017, Ben Bovée Slide 2
  3. 3. HOW TO NOT WRITE AN ARCHITECTURAL DESCRIPTION (A.D.) I’ve seen all of these:  Don’t provide rationale and relevance for architectural framework (AF)  Don’t identify (ID) intended purpose or uses for the architectural description (A.D.)  Don’t ID applicability of the A.D.—governed, responsible, accountable, consulted, informed (GRACI)  Don’t ID the scope of the A.D. (context and time period of effectiveness)  Don’t relate the A.D. to any reference architectures (RA), or do and exclude variances and extensions  Don’t ID maturation goals for the enterprise architecture (EA)  Don’t ID alternatives for EA maturation  Don’t ID prospective risks, rewards, costs, benefits and effects (desired and side effects) of alternatives  Don’t ID questions to be answered or—worse---don’t answer questions presented  Don’t relate the A.D. to key processes (e.g., DAS, JCIDS, OPS, PPBE, PfM, SE) [see DoDAF pp. 8, 9]  Don’t establish a baseline; and  Don’t reference any A.D. approval or change control procedures. Slide 3 © 10 April 2017, Ben Bovée
  4. 4. HOW TO NOT GROUP AN A.D. VIEWS I’ve seen all of these: There are multiple possible ways to group views; by:  A hierarchical organization of the views (a hierarchy may indicate):  An ontology (sets of item instances);  A composition taxonomy (matter in the items);  Grouping by meta-model concepts;  A structural taxonomy (sets of data elements describing the items); or  Dynamics (item behavior patterns); and Very likely the hierarchy is only partially consistent.  The type of relations between elements:  Ordination (“super-sub”)—sub identified by hierarchy type—see above  Before-after—after is subsequent to, or dependent on, the before Slide 4 © 10 April 2017, Ben Bovée
  5. 5. HOW TO NOT SEQUENCE THE A.D. VIEWS This minimally reads like a story:  In AF View ID-ascending sequence—unfortunately, very common. Slide 5 © 10 April 2017, Ben Bovée
  6. 6. HOW TO GROUP & SEQUENCE A.D. VIEWS Recommended A.D. Outline: 1 Introduction 1.A Purpose 1.B Applicability (Scope, Stakeholders, Goals, Desired Effects) 2 Technical Positions and Forecasts (LRPs and Guidance) 3 Outward-looking Service Rule and Communication Patterns 4 Inward-looking Patterns 4.A Operations Structures, Rules, and Flow Patterns 4.B Operations Concepts and Data Structures 5 Cross-Boundary Patterns 5.A Event-Based Dynamic Behavior Scenarios 5.B System Measures, Rule and Communication Patterns 6 Integrated Data Dictionary and Traceability Slide 6 © 10 April 2017, Ben Bovée
  7. 7. MAPPING OF [DODAF VIEWS] TO RECOMMENDED A.D. SECTIONS Recommended A.D. Outline: 1 Introduction 1.A Purpose [AV-1] 1.B Applicability (Scope, Stakeholders, Goals, Desired Effects) [CV-1, OV-1] 2 Technical Positions and Forecasts (LRPs and Guidance) [StdV-1, StdV-2, CV-3, CV-4, SvcV-8, SvcV-9, SV-8, SV-9, PV-2, PV-3] 3 Outward-looking Service Rule and Comm. Patterns [SvcV-1, SvcV-2, SvcV-4, SvcV-10a, SvcV-10b] 4 Inward-looking Patterns 4.A Operations Structures, Rules, and Flow Patterns [CV-2, OV-2, OV-4, OV-5a, OV-5b, OV-6a, OV-6b, PV-1] 4.B Operations Concepts and Data Structures [DIV-1, DIV-2, DIV-3] 5 Cross-Boundary Patterns 5.A Event-Based Dynamic Behavior Scenarios [OV-6c, SvcV-10c, SV-10c] 5.B System Measures, Rule and Communication Patterns (SV-1, SV-2, SV-3, SV-4, SV-7, SV-10a, SV-10b) 6 Integrated Data Dictionary and Traceability [AV-2, CV-5, CV-6, CV-7, OV-3, SvcV-3a, SvcV-3b, SvcV-7, SV-5a, SV-5b, SV-6, FFP RA Alignment] Slide 7 © 10 April 2017, Ben Bovée
  8. 8. MATRIX OF [DODAF VIEWS] TO RECOMMENDED A.D. SECTIONS AVs CVs OVs StdVs PVs DIVs SVs SvcVs 1 1.A 1.B 1.B 2 4.A 4.B 5.B 3 2 6 4.A 4.A 2 2 4.B 5.B 3 3 (n/a) 2 6 (n/a) 2 4.B 5.B (n/a) 3a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 3b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 4 (n/a) 2 4.A (n/a) (n/a) (n/a) 5.B 3 5 (n/a) 6 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 5b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 6 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 6 6 6a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6c (n/a) (n/a) 5.A (n/a) (n/a) (n/a) (n/a) (n/a) 7 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 5.B 6 8 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 9 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 10a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10c (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.A 5.A Slide 8 © 10 April 2017, Ben Bovée
  9. 9. MATRIX OF [DODAF VIEWS] TO RECOMMENDED A.D. SECTIONS AVs CVs OVs StdVs PVs DIVs SVs SvcVs 1 1.A 1.B 1.B 2 4.A 4.B 5.B 3 2 6 4.A 4.A 2 2 4.B 5.B 3 3 (n/a) 2 6 (n/a) 2 4.B 5.B (n/a) 3a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 3b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 4 (n/a) 2 4.A (n/a) (n/a) (n/a) 5.B 3 5 (n/a) 6 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 5b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 6 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 6 6 6a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6c (n/a) (n/a) 5.A (n/a) (n/a) (n/a) (n/a) (n/a) 7 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 5.B 6 8 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 9 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 10a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10c (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.A 5.A 1 Introduction 3 Outward-looking Service Rule and Comm. Patterns 2 Technical Position and Forecasts Slide 9 © 10 April 2017, Ben Bovée
  10. 10. MATRIX OF [DODAF VIEWS] TO RECOMMENDED A.D. SECTIONS AVs CVs OVs StdVs PVs DIVs SVs SvcVs 1 1.A 1.B 1.B 2 4.A 4.B 5.B 3 2 6 4.A 4.A 2 2 4.B 5.B 3 3 (n/a) 2 6 (n/a) 2 4.B 5.B (n/a) 3a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 3b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 4 (n/a) 2 4.A (n/a) (n/a) (n/a) 5.B 3 5 (n/a) 6 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 5b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 6 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 6 6 6a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6c (n/a) (n/a) 5.A (n/a) (n/a) (n/a) (n/a) (n/a) 7 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 5.B 6 8 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 9 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 10a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10c (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.A 5.A 4 Inward- looking Patterns 5 Cross- Boundary Patterns Slide 10 © 10 April 2017, Ben Bovée
  11. 11. MATRIX OF [DODAF VIEWS] TO RECOMMENDED A.D. SECTIONS AVs CVs OVs StdVs PVs DIVs SVs SvcVs 1 1.A 1.B 1.B 2 4.A 4.B 5.B 3 2 6 4.A 4.A 2 2 4.B 5.B 3 3 (n/a) 2 6 (n/a) 2 4.B 5.B (n/a) 3a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 3b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 4 (n/a) 2 4.A (n/a) (n/a) (n/a) 5.B 3 5 (n/a) 6 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 5b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 6 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 6 6 6a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6c (n/a) (n/a) 5.A (n/a) (n/a) (n/a) (n/a) (n/a) 7 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 5.B 6 8 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 9 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 10a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10c (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.A 5.A 6 Integrated Data Dictionary and Traceability 6 Integrated Data Dictionary and Traceability Slide 11 © 10 April 2017, Ben Bovée
  12. 12. MATRIX OF [DODAF VIEWS] TO RECOMMENDED A.D. SECTIONS AVs CVs OVs StdVs PVs DIVs SVs SvcVs 1 1.A 1.B 1.B 2 4.A 4.B 5.B 3 2 6 4.A 4.A 2 2 4.B 5.B 3 3 (n/a) 2 6 (n/a) 2 4.B 5.B (n/a) 3a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 3b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 6 4 (n/a) 2 4.A (n/a) (n/a) (n/a) 5.B 3 5 (n/a) 6 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 5b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) 6 (n/a) 6 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 6 6 6a (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6b (n/a) (n/a) 4.A (n/a) (n/a) (n/a) (n/a) (n/a) 6c (n/a) (n/a) 5.A (n/a) (n/a) (n/a) (n/a) (n/a) 7 (n/a) 6 (n/a) (n/a) (n/a) (n/a) 5.B 6 8 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 9 (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 2 2 10a (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10b (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.B 3 10c (n/a) (n/a) (n/a) (n/a) (n/a) (n/a) 5.A 5.A 1 Introduction 3 Outward-looking Service Rule and Comm. Patterns 2 Technical Position and Forecasts 6 Integrated Data Dictionary and Traceability 6 Integrated Data Dictionary and Traceability 5 Cross- Boundary Patterns 4 Inward- looking Patterns Slide 12 © 10 April 2017, Ben Bovée
  13. 13. APPENDIX A: ABBREVIATIONS Abbrev Represents First Page Note A.D. Architectural Description 2 AF Architecture Framework 2 DAS Defense Acquisition System 2 See References DoD Department of Defense Appendix A DoDAF DoD Architecture Framework Appendix A See References EA Enterprise Architecture 2 FFP Fit-for-purpose (view) 7 GRACI Governed, responsible, accountable, consulted, informed 2 ID Identify or Identifier 2 JCIDS Joint Capability Integration Development System 2 See References LRP Laws, regulations and policies 6 OPS Operations 2 PPBE Planning, Programming, Budgeting and Execution 2 See References RA Reference Architecture 3 PfM Portfolio Management 2 For Capabilities and IT. SE Systems Engineering 2 See References This list excludes references cited in the references listed. Slide 13 © 10 April 2017, Ben Bovée
  14. 14. APPENDIX B: REFERENCES [DAS] Defense Acquisition Regulations System (http://www.acq.osd.mil/dpap/dars/index.html, accessed) 10 April 2017. [DoD RA] DoD Reference Architecture Description (http://dodcio.defense.gov/portals/0/documents/diea/ref_archi_description_final_v1_18 jun10.pdf, accessed 10 Apr 2017), 18 June 2010 [DoDAF] DoDAF: DoD Architecture Framework Version 2.02 (dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf, accessed 10 Apr 2017), DoD Deputy Chief Information Officer, 3 Mar 2011. [JCIDS] JCIDS Process (www.acqnotes.com/acqnote/acquisitions/jcids-overview, accessed) 10 April 2017. [PPBE] PPBE Process (www.acqnotes.com/acqnote/acquisitions/ppbe-overview, accessed) 10 April 2017. [SE] DoD Systems Engineering (www.acq.osd.mil/se/, accessed) 10 April 2017. Slide 14 © 10 April 2017, Ben Bovée

×