ISA 201 Intermediate Information Systems Acquisition Lesson 9

ISA 201 Intermediate Information Systems Acquisition

Lesson 9 Architecture

Learning Objectives Today we will learn to: • • • Describe the Joint Information Environment (JIE) Identify the benefits of the JIE Recognize the application of a set of architectural data is used within the acquisition process. Recognize the relationship between Enterprise Architecture and a Solution Architecture. Diagram one of the following: “All, Operational, System and Standards Views” of the Do. D Architecture Framework (Do. DAF). Describe the Modular Open Systems Approach (MOSA). From a list identify the elements of the Global Information Grid (GIG) Technical Guidance-Federation (GTG-F)/DOD Information Technology Standards Registry (DISR). Given a scenario, determine which Do. DAF views support achieving Net. Ready Key Performance Parameter Identify the five (5) key areas of the Global Information Grid (GIG) / Do. D Information Network (DODIN). Recognize the benefits to the enterprise of the Information Support Plan. . Architecture 3

Lesson Overview Lesson Plan • • • Architecture Basics (Video Homework) Enterprise Architecture in IT Acquisitions Do. D Architectures Architecture 4

The Winchester House Similarities • • • Construction of systems goes on continuously Vast budgets are allocated to the IT organization Collection of systems with odd features More interfaces and bridges than there are systems Major projects not completed Data: Redundant, inconsistent, and inaccessible Architecture 5

Architecture 6

Question? • What if we don’t have an Architecture for a existing system and want to make a modification? Architecture 7

What is the Best Option? Architecture 8

Lesson Overview Lesson Plan Status • Architecture Basics (Video Homework) • Enterprise Architecture in IT • Acquisitions Do. D Architectures Architecture 9

Managing by Architecture 10

Architecture Products in Acquisition Process REFERENCES: Do. DD 5000. 1, Do. DI 5000. 02, Do. DD 4630. 5, Do. DI 4630. 8, CJCSI 3170. 01 H, Do. DAF 2. 0 Architecture 11

Do. DAF 2. 0 Vision • Views for Other Stakeholders • Structured Knowledge Base—Common Model • Views for the Architect “Key process owners will decide what architectural data is required, generally through Do. DAF-described Models or Fit-for-Purpose Views. However, other regulations and instructions from the Do. D and the CJCS have particular presentation view requirements. ” *DODAF Architecture 2. 02 12

Questions? • • Why do we need an architecture? - Tool in decision making (e. g. , identify risk) What is the purpose of our architecture? - “We” define the purpose—if you don’t know what you are going to use it for, there is a good chance it won’t be useful Identify and understand the different purposes of different stakeholders Architectures can be expensive to build so it doesn’t make sense to build if you don’t plan to use it! Architecture 13

A View of the Do. D Enterprise Architecture https: //www. intelink. gov/wiki/Do. D_CIO/Do. D_EA Solution Architectures Guided and constrained by the architectures that make up the Do. D EA 14

Enterprise vs. Solution Architecture • If your architecture work is about cross-organizational and/or strategic integration and/or standardization, then it is Enterprise Architecture • If your architecture work is aimed at addressing specific problems and requirements, usually through the design of specific systems or applications, then it’s Solution Architecture. • Think of city planning vs. designing and building a skyscraper. 15 Graphic adapted from Wikipedia at http: //en. wikipedia. org/wiki/File: Architectural_Levels_and_Attributes. jpg

Example Capability Management Questions Question Required Data Types Viewpoints Vision Goals How do the capabilities Desired Effects relate to enterprise Capabilities strategy and goals? Relationship between capabilities and goals Capability Vision (CV-1) Are there dependencies among the capabilities? Capabilities Relationships among capabilities, including dependencies Capability Dependencies (CV-4) How will capability performance be measured? Capabilities Performance Measures Relationships of capabilities to performance measures Capability Taxonomy (CV 2) Architecture 16

All Viewpoint (AV) • • Provide information pertinent to the entire Architectural Description rather than representing a distinct viewpoint Contains two models - AV– 1—Overview and Summary - Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Effects (Outcomes), and produced objects AV– 2—Integrated Dictionary - Architectural data repository with definitions of all terms used throughout the architectural data and presentation Architecture 17

Architectures To Document Mission Threads Do. DAF Operational Viewpoints (OV) Who are the players? What information do they exchange (Operational IERs)? What they do with the information? Architecture 18

Architectures to Describe Mission Threads Do. DAF System Viewpoints (SV) What system functions support the mission thread? How are the systems connected? How well do the systems perform? Architecture 19

Exercise to Build Architecture • • • Read Exercise 1 Material Develop Purpose for Architecture - What architecture to be used for / Intent of architecture Develop OV-2 Performers (formerly Node) Based on scenario describe Information Needs between Operational Nodes Discuss how we can apply this information to decision making Read JTAMS Overview Architecture 20

Stakeholder Issues • Who are the Key Stakeholders for JTAMS? • What are some of the stakeholder issues from the scenario update? Architecture 21

What is the purpose of the architecture? • • • What questions need to be answered? Are there specific strategic objectives to be satisfied? Are there specific trade offs to be considered? What critical issues need to be addressed? How is the EA used to support key decision making processes? What types of analysis need to be supported? Architecture 22

Example Solution Architecture Question Architecture 23

JTAMS OV-1 Architecture 24

JTAMS OV-2 Architecture 25

Example Solution Architecture Question Architecture 26

Relationships Between OV– 2 and SV– 1 (Svc. V– 1) Put IT in Context with Mission Operations Architecture 27

Model: Std. V– 1 • • • Name: Standards Profile Product Definition: - Rules that govern System Implementation and Operation Technical Standards that apply to the Architecture Additional Considerations: - Time-phased to allow for: - Focus on relevant Services within Service Areas - Emerging Technologies - Technology Evolution Architecture 28

Standards Profile Identifies Implementation Criteria That Govern the Given Architecture 29

“Fit for Purpose” Architecture Descriptions Architecture 30

Modular Open System Approach (MOSA) Do. D's definition of open systems is a system that has these 5 key principals: 1. Employs modular design 2. Enterprise investment strategies 3. Lower development risk through transparency 4. Transformation of the life cycle sustainment strategies — Technology Insertion 5. Strategic use of data rights MOSA is a strategic “Business and Technical” acquisition approach that leverages the commercial market-place in a way to control and optimize design features to ensure that a level-field of competition provides the best valued product for our war-fighter. Architecture 31

Modular Open Systems Why How What Goals Interoperability Approaches Modular Design Tech Refresh Competition Defined Interfaces Standards Process Accessible Data Innovation Open Interfaces IP Rights • • Modular Technical Design Approaches Design severable modules Define interfaces between modules Publish consensus-based standards Define, standardize & describe data models Open System Business Approaches • Use open standards & specs for interfaces • Recognize the relevant technical community • Acquire necessary data & license rights Cost Savings Supporting the goals for MOSA implementation are methods, processes and tools which underpin the approach 32

Do. D Information Technology Standards Registry (DISR) • • • Online repository for a minimal set of primarily commercial IT standards. Describes current technical standards and emerging standards Can be used to populate the Standards Models (Std. V– 1 and Std. V– 2), conversely, the Standards Models can identify additional or new standards that need to be added to DISR Puts you on the ROAD to Interoperability; DISR does NOT Guarantee interoperability! https: //gtg. csd. disa. mil/disr/dashboard. html Architecture 33

Information Support Plan (ISP) • • Purpose: used by program authorities to document IT needs, objectives, and interface requirements in sufficient detail to enable testing and verification of requirements. Enhanced Information Support Plan (EISP) “Tool”: - Formats ISP. Captures the architecture data describing the critical Information Exchange Requirements (IER). Critical IERs need to be managed like any other aspect of a program. Identify and demonstrate the risk mitigation of those IERs. Do. D CIO shall participate in ACAT I and Do. D ISP Special Interest ISP reviews, and shall provide concurrence, concurrence with comment, or non-concurrence with the ISP for consideration by the Do. D Component, MDA, or cognizant fielding authority for final approval. … Teresa Takai, Do. D CIO Architecture 34

Lesson Overview Lesson Plan Status • • Architecture Basics (Video Homework) Enterprise Architecture in IT Acquisitions • Do. D Architectures Architecture 35

Do. D Architectures Architecture 36

Department of Defense Information Network (DODIN) Department of Defense information network (DODIN) - The set of information capabilities, and associated processes for collecting, processing, storing, disseminating, and managing information ondemand to warfighters, policy makers, and support personnel, …, including owned and leased communications and computing systems and services, software (including applications), data, security services, other associated services, and national security systems. … JP 1 -02 “The crossroad is now in our rearview mirror, and cyber security and defense and the Do. D Information Network (Do. DIN) are now a central part of our daily operations as the premier IT Combat Support Agency” … DISA Strategic Vision Architecture 37

GIG v 2. 0 Vision “… single coherent, secure, and consolidated information environment which represents a fundamental shift in how we design, implement, manage, operate, and maintain Do. D information technology (IT) and network capabilities at all levels by focusing first on the technical, functional, and operational agility required by those at the tactical edge” (GIG 2. 0 Operational Reference Architecture, V 1. 1, October 13, 2008) Technical Architecture 38

GIG v 2. 0 • • • Provides a non-material solution to influence material solutions to transform the current federated GIG concept into a unified net–centric environment Developed incrementally over a period of years 5 Key Areas: - Global Authentication, Access Control, and Directory Services Information and Services from the Edge Joint Infrastructure Common Policies and Standards Unity of Command Architecture 39

Do. D Information Enterprise Architecture (Do. D IEA) v 2. 0 • • • The Do. D Information Enterprise Architecture (Do. D IEA) is the authoritative capstone architecture that sets the operational context and vision of the Information Enterprise (IE) Provides a common, enterprise foundation to guide and inform IT planning, investment, acquisition and operational decisions Enables alignment of Do. D architectures with the IE vision, drives enterprise solutions, promotes consistency and complements the IT Enterprise Strategy and Roadmap Do. D IEA enables Do. D decision-makers to have informed discussions on key issues driving evolution of Do. D’s information environment. —“Business Model” http: //dodcio. defense. gov/Portals/0/Documents/DIEA/Do. D%20 IEA%20 v 2%200_Volume%20 II_Description%20 Document_Fin al_20120806. pdf Architecture 40

Do. D IEA Concept Map • • • The Mission Areas (Warfighting, Business, Intelligence, and Enterprise Information Environment) provide warfighting Operational Requirements. The warfighting Operational Requirements are transformed into IE Requirements. CIO Vision shapes the content of the IE. Capabilities are described through Activities that are performed. The Activities are the basis for defining the scope of what Services need be implemented. An important activity for the CIO is to specify, based on common enterprise-wide services and improved. interoperability, Enterprisewide Reference Architectures. • “The The. Do. D Solutions are developed to meet mission needs. IEA will underpin all information architecture development to realize the JIE. Program Managers must develop solution architectures that comply with the Do. D Information Enterprise Architecture, …“ DODI 5000. 02, 7 Jan 2015 Architecture 41

Service Oriented Architecture (SOA) Definition—Service Oriented Architecture (SOA) is the body of standard design and engineering processes, tools, and best practices that leverage the modularity and composability of services to support objectives. • Extends the EA and defines the implementation of the architecture in terms of its technical approach. Architecture 42

Do. D IT Future: Joint Information Environment (JIE) The JIE will be the trusted reference model and framework that will enable us to share information when needed, with any mission partner, regardless of location, device, or service provider. To achieve this goal: • Transition from Network-Centric to Data-Centric solutions • Rapid delivery and use of integrated cloud services accessible by all means from anywhere • Interdependent information environment providing real time cyber situational awareness • Scalable platform allowing flexibility and mission partnering • Secure where it needs to be, resilient throughout, and appropriately consolidated JIE is not: • Program of Record /Joint Program Office • Turn key solutions • Independent way of doing things JIE Graphical Illustration Architecture 43

Benefits of the JIE • • Provides Joint Force Commander a shared, secure information framework that delivers responsive, versatile and decisive actions on any device, anytime, from anywhere on the globe Provides near immediate communication with all Joint and Coalition partners on any device, anytime, from anywhere Cybersecurity Situational Awareness Reduced Cybersecurity Attack Surface (less places to attack and secure) Centralized Configuration Management A flexible, fused data-centric environment enabling access to information at the point of need (Smart Services) Ability to adapt and include new technology into the JIE easily, quickly and affordably Architecture 44

NR-KPP Key Elements • NR KPP process defined in 12 Feb 2015 JCIDS Manual - NR KPP certification defined in CJCSI 5123. 01 G - CJCSI 6212. 01 F cancelled • Still use the Wiki page: https: //www. intelink. gov/wiki/Net_Ready_Key_Performance_P arameter_(NR_KPP)_Manual • NR KPP Key Principals - Defines three attributes focused on performance measures Incorporates MOE/MOP objective and threshold values No Tailored Information Support Plan (TISP) NR KPP architecture development methodology (copied Do. DAF 6 -step process). Requirement to align with Do. D Information Enterprise Architecture, the current Do. DAF, JIE and Joint Common System Function List (JCSFL) Architecture 45

NR KPP Attributes for Certification: 1. IT must be able to support military operations 2. IT must be able to be entered and managed on the network 3. IT must effectively exchange information JCIDS Manual, 12 Feb 2015 , including errata as of 12 Jun 2015 Table D-E-1 46

CV-1, CV-2, CV-4, CV-6, OV-1, OV-5 a OV-1, OV-2, OV-3, OV-5 b SV-7, Svc. V-7 OV-5 a&b AV-1, OV-6 a 32 SV-1 OV-2, OV-3, SV-6, Svc. V-6 OV-2 47

Tell me how you fit in Do. D. Prove to me you’ve thought out how we’ll operate this. Prove to me you’re in the JCA’s future plans. Trace activities to capability fulfillment. Tell me how you’ll measure success or failure. Tell me how this system evolves JCIDS Manual, 12 Feb 2015, including errata as of 12 48 (Evolutionary Acq). Jun 2015, Table D-1

Teach me your language. Tie your business to its data. Prove to me you’re in someone’s portfolio. What are the key data and their important attributes? What resources are flowing in/out of your system? With who do you need interoperable interfaces? 49 JCIDS Manual, 12 Feb 2015 , including errata as of 12 Jun 2015, Table D-E-4

CL Architecture-related Courses Include • • CLE 012—Do. D Open Systems Architecture CLE 041—Software Reuse CLE 068—Intellectual Property CLR 252 – Developing KPPs Architecture 50

Summary Today we learned to: • • • Describe the Joint Information Environment (JIE) Identify the benefits of the JIE Recognize the application of a set of architectural data is used within the acquisition process. Recognize the relationship between Enterprise Architecture and a Solution Architecture. Diagram one of the following: “All, Operational, System and Standards Views” of the Do. D Architecture Framework (Do. DAF). Describe the Modular Open Systems Approach (MOSA). Describe the Global Information Grid (GIG) Technical Guidance-Federation (GTG-F). Given a scenario and determine which Do. DAF views should be provided to support achieving Net-Ready Key Performance Parameter Identify the five (5) key areas of the Global Information Grid (GIG) / Do. D Information Network (DODIN). Recognize the importance to the enterprise of the Information Support Plan. Architecture 51