1. 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
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Use this exercise to develop an OV-2 model.
Then Discuss with students how the model can be used to understand more about the user requirements and identify risks.
At this point—Have the students read the exercise material, then work as a team to build the purpose for our architecture, then bring class together to build the performers on the white board and draw out the need lines.
NOTE–there are exercise “answer” slides that the instructor can use to walk the students through to the solution
Will need to conduct a Static Analysis—to capture Information Needs
• Static Analyses—which could include capability audit, interoperability analysis, or functional analysis. These analyses are often performed using simple analysis tools such as paper-based comparisons and database queries.
• Dynamic Analyses–sometimes referred to as executable models, these analyses typically examine the temporal, spatial, or other performance aspects of a system through dynamic simulations. For example, these analyses might be used to assess the latency of time sensitive targeting systems or conduct traffic analyses on deployed tactical networks under a variety of loading scenarios.
• Experimentation—the use of tactical capability requirements, such as the Coalition Warrior Interoperability Demonstration (CWID), sponsored annually by the JCS, and various battle labs to provide the ability to conduct human-in-the-loop simulations of operational activities.
Differing degrees of live versus simulated systems can be deployed during these experiments and there is a high degree of control over the experiment variables. These can be used for a variety of purposes.
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Read Scenario Update
Architecture-Exercise-Instructor Solution

2. JTAMS Case Study Overview
Achieved Milestone A.
The JRATS program will provide unmanned, autonomous air and ground vehicle robots to support joint counterinsurgency operations in a defensive role, primarily against Improvised Explosive Devices (IEDs) and to conduct reconnaissance, surveillance, and target acquisition (RSTA) in a variety of hazardous, high payoff scenarios.
Program Office will focus on development and sustainment of the Joint Training and Maintenance System (JTAMS), which is a tailored version of the Army’s Training and Maintenance System (TAMS) providing logistics support.
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Once they have read the scenario update, use this slide as a review
Architecture-Exercise-Instructor Solution

3. JTAMS Purpose
Provide JRATS logistics business management system which will provide for Onboard Diagnostics System (OBD), Parts Management System (PMS),Training and Help System (THS) and monitor, and interface with the JUGV, FUAV and JCCS systems
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Use this as an opportunity to help the students understand they will be functioning as the JTAMS Program Office.
So as described in the scenario update–we can use this as a framework for the purpose for our program office system
Architecture-Exercise-Instructor Solution

4. Stakeholder Issues Who are the Key Stakeholders for JTAMS?
What are some of the stakeholder issues from the scenario update?
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: This is meant to be a short instructor facilitated example of “Analysis” from the scenario update of how an architect would delve into what is essentially requirements analysis to build architecture. Understanding who are the stakeholders and what are their issues will help ensure we can describe the purpose of our architecture. Consider inserting the instructor solution slides here to help in your facilitated discussion.
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Who are the Key Stakeholders for JTAMS?—Answer should include JCS, Army, Marine Corps, Air Force at a minimum … use your discretion for any others
What are some of the key stakeholder issues (in the form of a question). There issues will be addressed in the CONOPS, use cases, etc. In the case of this exercise, we will draw on the scenario update. These questions below are some that I
Will the new business processes and applications allows for the “just-in-time” logistics concept to be achieved?
What types of logistics data are required?
Who needs what data and who should provide the data?
How do the new processes improve confidence in logistics? (Measures include speed, availability, and consistency of data)
Lead short discussion on who are some of the stakeholders and could their issues / priorities differ.
• Static Analyses–which could include capability audit, interoperability analysis, or functional analysis. These analyses are often performed using simple analysis tools such as paper-based comparisons and database queries.
• Dynamic Analyses–sometimes referred to as executable models, these analyses typically examine the temporal, spatial, or other performance aspects of a system through dynamic simulations. For example, these analyses might be used to assess the latency of time sensitive targeting systems or conduct traffic analyses on deployed tactical networks under a variety of loading scenarios.
• Experimentation–the use of tactical capability requirements, such as the Coalition Warrior Interoperability Demonstration (CWID), sponsored annually by the JCS, and various battle labs to provide the ability to conduct human-in-the-loop simulations of operational activities.
Differing degrees of live versus simulated systems can be deployed during these experiments and there is a high degree of control over the experiment variables. These can be used for a variety of purposes.
Architecture-Exercise-Instructor Solution

5. Stakeholder Issues Who are the Key Stakeholders for JTAMS?
JCS, Army, Marine Corps, Air Force … any others?
Will the new business processes and applications allows for the “just-in-time” logistics concept to be achieved?
What types of logistics data are required?
Who needs what data and who should provide the data?
How do the new processes improve confidence in logistics? (Measures include speed, availability, and consistency of data)
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: This is meant to be a short instructor facilitated example of “Analysis” from the scenario update of how an architect would delve into what is essentially requirements analysis to build architecture.
These questions are just some that I would come from scenario update
Lead short discussion on who are some of the stakeholders and could their issues / priorities differ.
• Static Analyses–which could include capability audit, interoperability analysis, or functional analysis. These analyses are often performed using simple analysis tools such as paper-based comparisons and database queries.
• Dynamic Analyses–sometimes referred to as executable models, these analyses typically examine the temporal, spatial, or other performance aspects of a system through dynamic simulations. For example, these analyses might be used to assess the latency of time sensitive targeting systems or conduct traffic analyses on deployed tactical networks under a variety of loading scenarios.
• Experimentation–the use of tactical capability requirements, such as the Coalition Warrior Interoperability Demonstration (CWID), sponsored annually by the JCS, and various battle labs to provide the ability to conduct human-in-the-loop simulations of operational activities.
Differing degrees of live versus simulated systems can be deployed during these experiments and there is a high degree of control over the experiment variables. These can be used for a variety of purposes.
Architecture-Exercise-Instructor Solution

6. 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?
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Another key step for the architect is to understand the purpose of the intended architecture.
In the students case, they are representatives of the JTAMS Program Office, so they will be building a solution architecture (build on the slide).
Ask the students what they would like their architecture purpose to be.
A program office would do analysis to determine the purpose of their architecture. At this point, they will need to conduct a Static Analysis—to capture Information Needs
The graphic should help them focus on one of the aspects of the architecture is to develop a solution architecture (that aligns with higher level architecture)
Remember they should challenge the Architect to develop architecture models to help them build a system that will serve the users and manage their program risk.
DoDI states: “A program’s solution architecture should define capability and interoperability requirements, establish and enforce standards, and guide security and cybersecurity requirements.”
Schoolhouse answer is:
The purpose should be to develop a solution architecture which will:
Define logistics business processes for JRATS
Define Capability Requirements
Provide guidance for the acquisition of the set of applications and common database to support these upgraded business processes
Supports decision making in key risk areas (e.g., cost, interfaces, immature technology, re-use, etc.)
Manage LC Cost (e.g., Open System Architecture)
Provide interoperable system
Guide Security and cybersecurity requirements
Use this as an opportunity for learning discussion: Ask student’s Why is purpose important?
Architecture is a tool to support decision making
If you don’t know what you are going to use it for, there is a good chance it won’t be useful
You need to identify and understand the different purposes of different stakeholders
Architectures can be expensive to build
Doesn’t make sense to build one if you don’t plan to use it!
Architecture-Exercise-Instructor Solution

7. The purpose Develop a solution architecture which will:
Define logistics business processes for JRATS
Provide guidance for the acquisition of the set of applications and common database to support these upgraded business processes
Supports decision making in key risk areas (e.g., cost, interfaces, immature technology, re-use, etc.)
Manage LC Cost (e.g., Open System Architecture)
Provide interoperable system
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Another key step for the architect is to understand the purpose of the intended architecture.
In the students case, they are representatives of the JTAMS Program Office, so they will be building a solution architecture (build on the slide).
Ask the students what they would like their architecture purpose to be.
A program office would do analysis to determine the purpose of their architecture. At this point, they will need to conduct a Static Analysis—to capture Information Needs
The graphic should help them focus on one of the aspects of the architecture is to develop a solution architecture (that aligns with higher level architecture)
Remember they should challenge the Architect to develop architecture models to help them build a system that will serve the users and manage their program risk.
DoDI states: “A program’s solution architecture should define capability and interoperability requirements, establish and enforce standards, and guide security and cybersecurity requirements.”
Schoolhouse answer is:
The purpose should be to develop a solution architecture which will:
Define logistics business processes for JRATS
Define Capability Requirements
Provide guidance for the acquisition of the set of applications and common database to support these upgraded business processes
Supports decision making in key risk areas (e.g., cost, interfaces, immature technology, re-use, etc.)
Manage LC Cost (e.g., Open System Architecture)
Provide interoperable system
Guide Security and cybersecurity requirements
Use this as an opportunity for learning discussion: Ask student’s Why is purpose important?
Architecture is a tool to support decision making
If you don’t know what you are going to use it for, there is a good chance it won’t be useful
You need to identify and understand the different purposes of different stakeholders
Architectures can be expensive to build
Doesn’t make sense to build one if you don’t plan to use it!
Architecture-Exercise-Instructor Solution

8. Example Solution Architecture Question
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Next couple of slides are intended to help students understand which architecture products are needed to meet our purpose. An architect will focus on answering key operational questions and data types through a series of Operational Views (OV)
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Architecture-Exercise-Instructor Solution

9. JTAMS OV-1
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: This high level OV-1 is given in the scenario update. This is one of the most seen architecture viewpoints and is intended to give a “General Officer (G.O.)” level “picture” of the system; however this viewpoint is not a model.
It is useful as a general overview on the concept of operations …
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Architecture-Exercise-Instructor Solution

10. JTAMS OV-2
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points:
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
- ***INSTRUCTOR SLIDE ONLY***–
Recommend building OV-2 on white board … have students find Operational Performers from scenario update. Then discuss information needs for each Need Line (NL)
The OV-2 depicts the operational performers within JRATS program, with the JTAMS Operational (Joint Maintenance) performer as the focus. Army management is an external performer, depicted in burnt orange oval, while all other performers are internal to JRATS depicted by light green ovals.
The Need Lines are used to describe the information needs to support operations between the operational performers / nodes.
NL_1 and NL_2—Health of JUGV, Location of JUGV, etc.
NL_3 and NL_4—Operational status (e.g., FMC, PMC, etc.) of JUGV, FUAV, parts, Estimated Time to Repair (ETR), etc.
NL_5 and NL_6—Parts requisitions, parts status, maintenance records, etc
NL_7 and NL_8—Health of FUAV, Location of FUAV, etc
Once develop OV-2–Ask Students
What risks can be identified from this model? E.g., discuss the importance of using architecture to assess risks and define requirements. You could Ask students to describe what Engineers can learn from OV-2, potential answers:
Define system requirements (e.g., bandwidth)
Define interface requirements
Refine IA requirements
Define additional risks
Etc.
What is useful from this model for SE our system? System of sytems? (Lead in to next slide discussion of systems views)
Architecture-Exercise-Instructor Solution

11. JTAMS OV-2 - ***INSTRUCTOR SLIDE ONLY***–
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points:
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Recommend building OV-2 on white board … have students find Operational Performers from scenario update. Then discuss information needs for each Need Line (NL)
The OV-2 depicts the operational performers within JRATS program, with the JTAMS Operational (Joint Maintenance) performer as the focus. Army management is an external performer, depicted in burnt orange oval, while all other performers are internal to JRATS depicted by light green ovals.
The Need Lines are used to describe the information needs to support operations between the operational performers / nodes.
NL_1 and NL_2—Health of JUGV, Location of JUGV, etc.
NL_3 and NL_4—Operational status (e.g., FMC, PMC, etc.) of JUGV, FUAV, parts, Estimated Time to Repair (ETR), etc.
NL_5 and NL_6—Parts requisitions, parts status, maintenance records, etc
NL_7 and NL_8—Health of FUAV, Location of FUAV, etc
Once develop OV-2–Ask Students
What risks can be identified from this model? E.g discuss the importance of using architecture to assess risks and define requirements. You could Ask students to describe what Engineers can learn from OV-2, potential answers:
Define system requirements (e.g., bandwidth)
Define interface requirements
Refine IA requirements
Define additional risks
Etc.
What is useful from this model for SE our system? System of sytems? (Lead in to next slide discussion of systems views)
Architecture-Exercise-Instructor Solution

12. Example Solution Architecture Question
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: This slide reflects the Architects questions and data types that will be documented in the service or system level views. The questions should be a natural lead in to the next slide and continued discussion of how the architect will build systems views from the operational views to help the program office manage risk.
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Architecture-Exercise-Instructor Solution

13. Relationships Between OV-2 and SV-1 (SvcV-1) Put IT in Context with Mission Operations
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: This is a notional graphic, which should be used to show how the architect will relate operational views to systems views … in this case OV-2 to SV-1
This is a good slide to show how the operational performers host systems. So the work they did building the OV-2 (in the exercise just finished) is now used to build systems and interfaces. Point out interfaces between system locations as this shows how the architecture can be a tool to identify risk so we can manage it.
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Architecture-Exercise-Instructor Solution

14. Model: StdV-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:
Emerging Technologies
Technology Evolution
Focus on relevant Services within Service Areas
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Technical standards that apply to the architecture. DoD Architecture is foundation for GIG??
Standards View is formerly called Technical View. It will appear as a spread sheet that outlines current and emerging standards.
A good way to describe is by using Beta versus VHS … as commercial industry coalesced around VHS it became the standard. A more recent example would be HD-DVD versus Blue Ray.
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Architecture-Exercise-Instructor Solution

15. Standards Profile Identifies Implementation Criteria That Govern the Given Architecture
SLIDE INFORMATION***************************************************************************************************************************
*Slide Type: Content (Content or Exercise)
*Supporting ELOs ID:
ELO Describe the architectural relationship between weapons systems and their embedded information technology.
*Policy / Directive / Standard / DTM ID:
**********************************************************************************************************************************************************
Key Points: Standards profiles are used to put “constraints” on system and Identifies Implementation Criteria That Govern the Given Architecture
Key Questions to Ask and Anticipated Answers:
Terms \ Definitions \ Acronyms:
Architecture-Exercise-Instructor Solution