ISA 201Intermediate

Information Systems Acquisition

Lesson 3Architecture

Learning Objectives

3Architecture

Overall: Given a DoD IT/SW acquisition scenario, provide IT/SW inputs into the Program’s Information Support Plan (ISP).• Recognize how to apply architectural data within the DoD acquisition process.• Identify the laws and policies requiring the use of Enterprise Architecture tools and

concepts.• Recognize the relationship between Enterprise Architecture and Solution

Architecture.• Diagram one of the following: "All, Operational, Systems and/or Standards Views"

of the DoD Architecture Framework (DoDAF). • Recognize that the Global Information Grid (GIG) Technical Guidance-Federation

(GTG-F) DoD Information Technology Standards Registry (DISR) is used to build the solution architecture.

• Recognize the management benefits of the Information Support Plan (ISP).• Identify five (5) key areas of the Global Information Grid (GIG)/DoD Information

Network (DODIN). • Describe the Joint Information Environment (JIE).• Identify the benefits of the Joint Information Environment (JIE).

Today we will learn to:

Lesson Overview

4Architecture

• Architecture Basics (Video Homework) Review

• Enterprise Architecture in IT Acquisitions• Enterprise vs

Solution Architectures• DoDAF – The DoD

Architecture Language• DoD Management

Tools• DoD Enterprise

Architectures

Lesson Plan

5Architecture

• 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

The Winchester House Similarities

6Architecture

Architecture

Lesson Overview

7Architecture

• Architecture Basics (Video Homework) Review

• Enterprise Architecture in IT Acquisitions• Enterprise vs

Solution Architectures• DoDAF – The DoD

Architecture Language• DoD Management

Tools• DoD Enterprise

Architectures

Lesson Plan Status

8Architecture

Managing by Architecture

MANDATED

9Architecture

Architecture Products in DoD Acquisition Process

REFERENCES:DoDD 5000.1, DoDI 5000.02, DoDD 4630.5,DoDI 4630.8, CJCSI 3170.01H, DoDAF 2.0

10Architecture

• Views for Other Stakeholders

• Structured Knowledge Base—Common Model

• Views for the Architect

DoDAF 2.0 Vision

“Key process owners will decide what architectural data is required, generally through DoDAF-described Models or Fit-for-Purpose Views.

However, other regulations and instructions from the DoD and the CJCS have particular presentation view requirements.” *DODAF 2.02

11Architecture

“Fit for Purpose” Architecture Descriptions

12Architecture

Question Required Data Types Viewpoints

How do the capabilities relate to enterprise strategy and goals?

VisionGoalsDesired EffectsCapabilitiesRelationship between capabilities and goals

Capability Vision (CV-1)

Are there dependencies among the capabilities?

CapabilitiesRelationships among capabilities, including dependencies

Capability Dependencies (CV-4)

How will capability performance be measured?

CapabilitiesPerformance MeasuresRelationships of capabilities to performance measures

Capability Taxonomy (CV-2)

Example Capability Management Questions

Lesson Overview

13Architecture

• Architecture Basics (Video Homework) Review• Enterprise Architecture in IT Acquisitions

• Enterprise vs Solution Architectures• DoDAF – The DoD

Architecture Language• DoD Management

Tools• DoD Enterprise

Architectures

Lesson Plan Status

14Architecture

Architectures can be expensive to build so it doesn’t make sense to build if you don’t plan to use it!

• 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• What are the two major typesof architectures in DoD?

- Enterprise Architectures- Solution Architectures

Questions?

15

A View of the DoD Enterprise ArchitectureSolution Architectures

Guided and constrained by the architectures

that make up the D

oD EA

https://www.intelink.gov/wiki/DoD_CIO/DoD_EA

• The BEA is the enterprise architecture for the DoD Business Mission Area- Reflects DoD business

transformation priorities;- Business capabilities

required to support those priorities;

- Enterprise systems and initiatives

- Supports use of information within an End-to-End (E2E) framework

DoD Business Enterprise Architecture

http://dcmo.defense.gov/Products-and-Services/Business-Enterprise-Architecture/

17

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.Graphic adapted from Wikipedia at http://en.wikipedia.org/wiki/File:Architectural_Levels_and_Attributes.jpg

Lesson Overview

18Architecture

• Architecture Basics (Video Homework) Review• Enterprise Architecture in IT Acquisitions• Enterprise vs Solution Architectures

• DoDAF – The DoD ArchitectureLanguage

• DoD Management Tools• DoD Enterprise

Architectures

Lesson Plan Status

19Architecture

• 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 architecturaldata and presentation

All Viewpoint (AV)

20Architecture

Who are the players?

What information do they exchange (Operational IERs)?

What they do with the information?

Architectures To Document Mission ThreadsDoDAF Operational Viewpoints (OV)

21Architecture

What system functions support the mission thread?

How are the systems connected?

How well do the systems perform?

Architectures to Describe Mission ThreadsDoDAF System Viewpoints (SV)

22Architecture

Read JTAMS Overview

• 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

Exercise to Build Architecture

Lesson Overview

23Architecture

Lesson Plan Status

• Architecture Basics (Video Homework) Review• Enterprise Architecture in IT Acquisitions• Enterprise vs Solution Architectures• DoDAF – The DoD Architecture Language

• DoD ManagementTools

• DoD Enterprise Architectures

24Architecture

https://gtg.csd.disa.mil/disr/dashboard.html

DISR Puts you on the ROAD to Interoperability; DISR does NOT Guarantee interoperability!

• 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 (StdV–1 and StdV–2), conversely, the Standards Models can identify additional or new standards that need to be added to DISR.

DoD Information Technology Standards Registry (DISR)

25Architecture

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.• Allows for sharing of applications

and data across an enterprise• Defines the implementation of the

architecture in terms of its technical approach. For example, specific DISR SOA protocols like Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI).

DISR Example: Service Oriented Architecture (SOA)

26Architecture

DoD CIO shall participate in ACAT I and DoD ISP Special Interest ISP reviews, and shall provide concurrence, concurrence with comment, or non-concurrence with the ISP for consideration by the DoD Component, MDA, or cognizant fielding authority for final

approval. … Teresa Takai, DoD CIO

• 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.

Information Support Plan (ISP)

Lesson Overview

27Architecture

Lesson Plan Status

• Architecture Basics (Video Homework) Review• Enterprise Architecture in IT Acquisitions• Enterprise vs Solution Architectures• DoDAF – The DoD

Architecture Language • DoD Management

Tools

• DoD Enterprise Architectures

28Architecture

DoD IEA enables DoD decision-makers to have informed discussions on key issues driving evolution of DoD’s information environment.

—“Business Model” http://dodcio.defense.gov/Portals/0/Documents/DIEA/DoD%20IEA%20v2%200_Volume%20II_Description%20Document_Fin

al_20120806.pdf

• The DoD Information Enterprise Architecture (DoD 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 DoD architectures with the IE vision, drives enterprise solutions, promotes consistency and complements the IT Enterprise Strategy and Roadmap

DoD Information Enterprise Architecture (DoD IEA) v 2.0 – The VISION

29Architecture

• 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, Enterprise-wide Reference Architectures.

• The Solutions are developed to meet mission needs.

DoD IEA Concept Map

“The DoD IEA will underpin all information architecture development to realize the JIE. Program Managers must develop solution architectures that comply

with the DoD Information Enterprise Architecture, …“ DODI 5000.02, 7Jan2015

30Architecture

Technical Architecture

“… single coherent, secure, and consolidated information environment which represents a fundamental shift in how we design, implement, manage, operate, and maintain DoD 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, V1.1, October 13, 2008)

GIG v2.0 Vision

31Architecture

• 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

GIG v2.0

32Architecture

Department of Defense information network (DODIN) - The set of information capabilities, and associated processes for collecting, processing, storing, disseminating, and managing information on-demand 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 DoD Information Network (DoDIN) are now a central part of our daily operations as the premier IT Combat Support Agency”

… DISA Strategic Vision

Department of Defense Information Network (DODIN) – The Realization

33ArchitectureJIE Graphical Illustration

Coalition Forces

WorkMobile

(TDY/Deploy)

“Enterprise Information Environment”

Home

??

“Enterprise Information Environment”

Deployed Environment

Future devices

Computing

Data

Data

Computing

Applications

AT21Navy ERP DCO

iEHR EnterpriseEmail

Defense Travel

APEX AFATDS

Airman

FundamentalsClose

Combat TM

Mission Applications

JIE is not: • Program of Record

/Joint Program Office • Turn key solutions• Independent way of

doing things

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

DoD IT Future: Joint Information Environment (JIE)

34Architecture

• 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

Benefits of the JIE

35Architecture

• CLE 041—Software Reuse• CLE 068—Intellectual Property• CLE 075 – Introduction to DoD Cloud Computing• CLR 252 – Developing KPPs

CL Architecture-related Courses Include

Summary

36Architecture

Today we learned to:Overall: Given a DoD IT/SW acquisition scenario, provide IT/SW inputs into the Program’s Information Support Plan (ISP).• Recognize how to apply architectural data within the DoD acquisition process.• Identify the laws and policies requiring the use of Enterprise Architecture tools and

concepts.• Recognize the relationship between Enterprise Architecture and Solution

Architecture.• Diagram one of the following: "All, Operational, Systems and/or Standards Views"

of the DoD Architecture Framework (DoDAF). • Recognize that the Global Information Grid (GIG) Technical Guidance-Federation

(GTG-F) DoD Information Technology Standards Registry (DISR) is used to build the solution architecture.

• Recognize the management benefits of the Information Support Plan (ISP).• Identify five (5) key areas of the Global Information Grid (GIG)/DoD Information

Network (DODIN). • Describe the Joint Information Environment (JIE).• Identify the benefits of the Joint Information Environment (JIE).