Post on 05-Jul-2020
ISA 201Intermediate
Information Systems Acquisition
Lesson 12Practicum 1
Learning Objectives
3Practicum 1
Today we will learn to:
• Given the decision to develop a DoD IT/SW system, analyze an analysis of alternatives (AoA) to make recommendations.• Given a Department of Defense (DoD) Information Technology (IT) acquisition scenario, recognize characteristics of the IT Box concept.• Given a DoD IT/SW acquisition scenario, apply appropriate laws, policies, directives and guidebooks to guide the acquisition.• Given a DoD IT/SW system scenario, develop the software program office lifecycle cost and schedule effort projections for budget purposes.• Given a DoD IT/SW acquisition scenario and the Practical Software and Systems Measurement (PSM) methodology, identify appropriate measures that allow program/enterprise leadership to make effective decisions. • Apply cybersecurity analysis throughout acquisition lifecycle phases.• Given a DoD IT/SW scenario, describe the requirements management process for successful software acquisition.• Recognize how to apply architectural data within the DoD acquisition process.• Apply the eleven (11) compliancy requirements of Title 40/CCA to a given DoD IT System. • Identify relevant considerations that influence the acquisition strategy of a software-reliant system. • Recognize that Software Reuse must be considered when engineering a software design and development.
Lesson Overview
4Practicum 1
• Practicum Overview • Joint Training and Maintenance System (JTAMS)
Introduction- We will use JTAMS throughout both weeks as we walk the
Defense Acquisition Life-Cycle for Information Technology Software Intensive Systems (IT/SIS)
• Marching Orders
Lesson Plan
5Practicum 1
1. The Practicums are a threaded exercise that track the progress of a notional program throughout the lifecycle.
2. The intent is to reinforce the Major Takeaways (MT) of each lesson in keeping with the ELO’s and to assess the level of knowledge of the students.
3. The Practicums provide a deeper understanding of the IT systems acquisition Life Cycle process by applying concepts we are learning throughout the course.
4. Each Practicum includes an update to the scenario along with supporting artifacts that allow.
5. The Practicums require the team as a whole to prepare a set of templated slides for submission to the instructors for a team grade - Teams earn up to 40 points for the team submission
Overall Practicum Overview
6Practicum 2
Practicum Timeline
Vers 5
Project StartMar FY0
JROC CDDJROC ICD
ASRNov FY1
JRATS
ITRJul FY0
JRATS
Sep FY1
Practicum 1 Creating/establishing a new Information Technology (IT) program (MS A & MS B)
JTAMSMRESPDR#1
Mar FY2
JTAMSSSR#1
Dec FY2
SRRMay FY1
JRATS
SFROct FY2 JRATS
- Significant JTAMSEvents
DRAFT JROC CDD
Oct FY3 Practicum 2 Managing IT
program development
(up to CDR)
JTAMSCDR
Feb FY3
JTAMSPDR#2Oct FY3
PDRMar FY2
JRATS
JTAMSSSR#2Jul FY2
PDROct FY3
JRATS
CDRMar FY3
JRATS
JROC CPD
Practicum 3 Post-CDR and Post MS C aspects of an IT/SIS Program
PRRApr FY4
JRATS
JTAMSIncrement #1
IOCMar FY4
IOCSep FY8
FOCFY12
Engineering and Manufacturing Development
Operations &
Support
MaterielSolutionAnalysis
FRP DecisionReview
Materiel Development Decision
ADMApr FY2 Apr FY6
ADMADMNov FY1
ADM
AJRATS-JTAMS
BJRATS-JTAMS
CJRATS-JTAMS
Technology Maturation and Risk Reduction
CDD-V
DRFPRD
Production & Deployment
FRP-DR
Lesson Overview
7Practicum 1
• Practicum Overview
• Joint Training and Maintenance System (JTAMS) Introduction- We will use JTAMS throughout both weeks as we walk the
Defense Acquisition Life-Cycle for Information Technology Software Reliant Systems
• Marching Orders
Lesson Plan Status
8Practicum 1
• Joint Reconnaissance and Targeting System (JRATS):- Remember Firebird? It is now a part of a System of Systems:
- The USMC Joint Unmanned Ground Vehicle (JUGV) and the Army Firebird Unmanned Aerial Vehicle (FUAV) are working together to support the warfighter.
- They are controlled by the Air Force’s Joint Command and Control System (JCCS) and monitored logistically by the Joint Training and Maintenance System (JTAMS).
JRATS and JTAMS Background
• Our Focus will be on JTAMS (an IT/SW Reliant System):- JTAMS is an ACAT IAM program (because of the Joint ICD that made
all programs under it JROC Special Interest)- JRATS is a PEO and JTAMS is one of four major programs- JTAMS has four (4) major subsystems:
- Onboard Diagnostics (OBD), Part and Maintenance (PAMS), Training and Help (THS) and Mission REhearsal System (MRES)
9Practicum 2
Joint Training and Maintenance System (JTAMS) Increment 1
Government Roadmap Schedule
Lesson Overview
10Practicum 1
• Practicum Overview• Joint Training and Maintenance System (JTAMS)
Introduction- We will use JTAMS throughout both weeks as we walk the
Defense Acquisition Life-Cycle for Information Technology Software Intensive Systems (IT/SIS)
• Marching Orders
Lesson Plan Status
11Practicum 1
• You are members of the JTAMS PMO - You will have 2+ hours for research and development of the practicum solution.
• Go to Blackboard or your Student CD and open the folder for this Practicum.• Start by reading “Practicum 1 Situation and applicable artifacts” found in the
Practicum 1 folder and by reviewing artifacts or tools found in the Job Aids• See the Student Template Slides for the practicum requirements• Remember to leverage course material from previous lessons in preparing
your answers
Practicum Marching Orders
Time Event Misc1210 - 1240 Practicum Intro Review Instructor
1240 - 1510 Research and prepare analysis Student teams
1510 Submit entire analysis Submit electronically on BB/shared drive AND hard copy
1510 - 1600 Instructor led discussion/facilitation Instructor reinforces the learning objectives
12Practicum 1
• STUDENT TEMPLATE SLIDE OVERVIEW
Student Template Slides
Summary
13Practicum 1
Today we learned to:
• Given the decision to develop a DoD IT/SW system, analyze an analysis of alternatives (AoA) to make recommendations.• Given a Department of Defense (DoD) Information Technology (IT) acquisition scenario, recognize characteristics of the IT Box concept.• Given a DoD IT/SW acquisition scenario, apply appropriate laws, policies, directives and guidebooks to guide the acquisition.• Given a DoD IT/SW system scenario, develop the software program office lifecycle cost and schedule effort projections for budget purposes.• Given a DoD IT/SW acquisition scenario and the Practical Software and Systems Measurement (PSM) methodology, identify appropriate measures that allow program/enterprise leadership to make effective decisions. • Apply cybersecurity analysis throughout acquisition lifecycle phases.• Given a DoD IT/SW scenario, describe the requirements management process for successful software acquisition.• Recognize how to apply architectural data within the DoD acquisition process.• Apply the eleven (11) compliancy requirements of Title 40/CCA to a given DoD IT System. • Identify relevant considerations that influence the acquisition strategy of a software-reliant system. • Recognize that Software Reuse must be considered when engineering a software design and development.