ISA 201 Intermediate Information Systems Acquisition

Slides:



Advertisements
Similar presentations
1 May 2009 ver. 5.5 Materiel Development Decision (MDD) MDA: Approves AoA Study Guidance Determines acquisition phase of entry Identifies initial review.
Advertisements

Phase B Exit Criteria Issues Resolved or Addressed Technical Reviews / Readiness Reviews, Audits Initiate Milestone C Program Review Planning Process Initiate.
“Common Process for Developing Briefings for Major Decision Points” INSTRUCTIONS Provide Feedback via to: Lois Harper PEO C4I and Space
Adjusting EPLC to your Project Colleen Robinson & Teresa Kinley Friday, February 6, 2009.
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
Initiate Technology Development Finalize AoA Plan, AS, ICD, TDS, Develop CDD, and TEMP Initiate Milestone B Program Review Planning Process Initiate Acquisition.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
IRM304 CDR Course Manager: Denny Involved Competency Leads: 26 (Cybersecurity)-Denman, 19 (Measurement)-Denny, 7 (DBS)-Corcoran [Capability Planning],
1 1 Nunn-McCurdy Legislation/Program Impacts Della McPhail Chief Financial Officer 308 ARSW DISTRIBUTION STATEMENT A: Approved for public release; distribution.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
2.1 ACQUISITION STRATEGYSlide 1 Space System Segments.
Principal Investigator ESTCP Selection Meeting
ISA 201 Information System Acquisition
JTAMS PRE-MILESTONE B ANALYSIS
DoD Template for Application of TLCSM and PBL
CMGT 410 aid Education Begins/cmgt410aid.com
CLE Introduction to Agile Software Acquisition
Office 365 Security Assessment Workshop
Technology Readiness Assessment (TRA)
Life Cycle Logistics.
JTAMS PRE-CDR IT/SIS ANALYSIS
Competitive Prototyping – the New Reality
ISA 201 Intermediate Information Systems Acquisition
MDD to Milestone A Requirements Management Activities
ISA 201 Intermediate Information Systems Acquisition
JTAMS MILESTONE A ANALYSIS
ISA201 Version June 2017 Deployment Overview
ISA 201 Information System Acquisition
Lesson 5 Materiel Solution Analysis (MSA) Exercise Team#
ISA 201 Information System Acquisition
Software Configuration Management
Milestone A to Milestone B Requirements Management Activities
ISA 201 Information System Acquisition
Principal Investigator ESTCP Selection Meeting
Milestone A to Milestone B Requirements Management Activities
JTAMS MILESTONE A ANALYSIS
Identify the Risk of Not Doing BA
JTAMS PRE-CDR IT/SIS ANALYSIS
ISA 301 Advanced Enterprise Information Systems Acquisition
ISA 201 Intermediate Information Systems Acquisition
JTAMS POST-CDR IT/SIS ISSUES
ISA 301: Advanced Enterprise Information Systems Acquisition
Intermediate Small Business Programs, Part B SBP 202 Lesson 1: Introduction February 2017 Lesson 1: Introduction.
Subcontracting SBP 210 Lesson 1: Introduction
JTAMS MILESTONE A ANALYSIS
TechStambha PMP Certification Training
ISA 201 Intermediate Information Systems Acquisition
ISA 201 Intermediate Information Systems Acquisition
JTAMS PRE-MILESTONE B ANALYSIS
Lesson 2: SBP Review Lesson 2: SBP Review February 2017
JTAMS PRE-MILESTONE B ANALYSIS
MDD to Milestone A Requirements Management Activities
JTAMS PRE-CDR ANALYSIS
Phase 2 Tollgate Review Discussion Template
Phase 1 Tollgate Review Discussion Template
Engineering Processes
General Services Department
Project Management Process Groups
8 Tech Processes Drive Acquisition
Employee engagement Delivery guide
Principal Investigator ESTCP Selection Meeting
Engineering Processes
AICT5 – eProject Project Planning for ICT
Executive Project Kickoff
Principal Investigator ESTCP Selection Meeting
JTAMS PRE-MILESTONE B ANALYSIS
JTAMS PRE-CDR ANALYSIS
JTAMS PRE-MILESTONE B ANALYSIS
Project Name Here Kick-off Date
Presentation transcript:

ISA 201 Intermediate Information Systems Acquisition

Lesson 11 Practicum 2 Lesson Point of Contact: Name: Mike Thorne Phone: 256-922-8745 Email: Mike.thorne@dau.mil Read-Ahead N/A Length of Presentation: Presentation: .5 hours Class Exercise: 3 hours LO(s): TLO 2.1.X Given a notional Information Technology (IT) system, analyze the needed documentation and decisions necessary for an Information Technology (IT)/Software Intensive System (SIS) to support a Milestone decision. ELO 27.1.1.3 Given a DoD acquisition scenario, asses required aspects of DoD SE technical reviews, technical processes, and technical management processes. ELO 27.1.1.4 Given a DoD acquisition scenario, apply System Engineering Lessons Learned and Best Practices when dealing with software. ELO 7.1.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset.  ELO 8.1.2.1 Recognize the benefits to the enterprise of the Information Support Plan.  ELO 1.1.1.10 Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle.  ELO 20.1.1.5 Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario ELO 10.1.1.2 Given an IT acquisition scenario, identify the most appropriate software methodology (or a combination of methodologies) to meet the expectations of the government. ELO 6.x.x.x Given a notional Information Technology (IT) system, complete a cost estimate using the provided exercise scenario.  ELO 19.1.2.1 Given a scenario, identify program IT decision information requirements.  ELO 19.1.2.2 Create a set of program IT measures that are linked to the program decision information requirements. ELO 26.1.1.8 Given an IT acquisition scenario, choose the appropriate controls for a system based on confidentiality, integrity, or availability requirements. ELO 26.1.1.9 Apply the Program Protection Plan to an IT Acquisition Scenario. ELO 8.1.1.14 Describe the Modular Open Systems Approach (MOSA). Major Takeways: N/A Quiz questions: N/A

Today you will learn to (1 of 2): Given an IT/SIS acquisition program, apply a cost estimation methodology to recommend appropriate strategies for budget execution within the legislation and guidance of PPBE. Apply a cost estimation methodology to the analysis of an acquisition program to determine the status of budget execution throughout the acquisition life cycle, Explain the DoD Systems Engineering Process in the context of an IT/SW Development. Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle. Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. Identify relevant considerations that influence the acquisition lifecycle of a software-reliant system. SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: TLO 2.1.1  Given a Department of Defense (DoD) Information Technology (IT) acquisition scenario, create appropriate acquisition strategies to promote the most effective technical and business solution.   ELO 6.1.1.1 Given an IT/SIS acquisition program, apply a cost estimation methodology to recommend appropriate strategies for budget execution within the legislation and guidance of PPBE. ELO 6.1.1.2 Apply a cost estimation methodology to the analysis of an acquisition program to determine the status of budget execution throughout the acquisition life cycle, ELO 27.1.1.1 Explain the DoD Systems Engineering Process in the context of an IT/SW Development. ELO 1.1.1.10 Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle. ELO 7.1.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. ELO 18.1.1.3 Identify relevant considerations that influence the acquisition lifecycle of a software-reliant system. ELO 19.1.2.1 Given a scenario, identify program IT decision information requirements. ELO 19.1.2.2 Create a set of program IT measures that are linked to the program decision information requirements. ELO 19.1.2.3 Apply the measurement results to support IT program decisions. ELO 20.1.1.4 Identify risks inherent to Information Technology (IT) system acquisition. ELO 20.1.1.5 Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario ELO 26.1.1.9 Apply the Program Protection Plan to an IT Acquisition Scenario. ELO 26.1.1.8 Given an IT acquisition scenario, choose the appropriate controls for a system based on confidentiality, integrity, or availability requirements. Practicum 2

Today you will learn to (1 of 2): Given a scenario, identify program IT decision information requirements. Create a set of program IT measures that are linked to the program decision information requirements. Apply the measurement results to support IT program decisions. Identify risks inherent to Information Technology (IT) system acquisition. Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario Apply the Program Protection Plan to an IT Acquisition Scenario. Given an IT acquisition scenario, choose the appropriate controls for a system based on confidentiality, integrity, or availability requirements. SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: TLO 2.1.1  Given a Department of Defense (DoD) Information Technology (IT) acquisition scenario, create appropriate acquisition strategies to promote the most effective technical and business solution.   ELO 6.1.1.1 Given an IT/SIS acquisition program, apply a cost estimation methodology to recommend appropriate strategies for budget execution within the legislation and guidance of PPBE. ELO 6.1.1.2 Apply a cost estimation methodology to the analysis of an acquisition program to determine the status of budget execution throughout the acquisition life cycle, ELO 27.1.1.1 Explain the DoD Systems Engineering Process in the context of an IT/SW Development. ELO 1.1.1.10 Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle. ELO 7.1.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. ELO 18.1.1.3 Identify relevant considerations that influence the acquisition lifecycle of a software-reliant system. ELO 19.1.2.1 Given a scenario, identify program IT decision information requirements. ELO 19.1.2.2 Create a set of program IT measures that are linked to the program decision information requirements. ELO 19.1.2.3 Apply the measurement results to support IT program decisions. ELO 20.1.1.4 Identify risks inherent to Information Technology (IT) system acquisition. ELO 20.1.1.5 Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario ELO 26.1.1.9 Apply the Program Protection Plan to an IT Acquisition Scenario. ELO 26.1.1.8 Given an IT acquisition scenario, choose the appropriate controls for a system based on confidentiality, integrity, or availability requirements. Practicum 2

Acquisition Activities Review Lesson Plan Acquisition Activities Review 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 SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Note: Instructions/recommendations for conducting this Practicum are included on the notes page of the “Marching Orders” slide later in the brief. Please read. Note that this is a graded exercise (as are all Practicums) —please be very familiar with the grading approach and the grading rubric provided. Every student must brief to graduate. Additionally, the practicums are based on a scenario that is updated throughout the 2 weeks and across the 4 Practicums. Please read the scenarios and be thoroughly familiar with them. Also review the Job Aids folders for each Practicum and be familiar with all of the artifacts and documents that are provided. Additionally, I recommend you print out the Instructor Answer briefings and read over them prior to having the students brief. You will also need to know how to use the cost estimating tool found in the Practicum tools folder. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2 March 2014

Technology Maturation and Risk Reduction PURPOSE: to reduce technology, engineering, integration, and life cycle cost risk to the point that a decision to contract for EMD can be made with confidence in successful program execution for development, production, and sustainment ENTER: MDA approved materiel solution and Acquisition Strategy, initial major program documentation and funding in the FYDP ACTIVITIES: Competitive prototyping of critical subsystems, SE Trade-off analysis, develop contracting strategy, conduct Capability Development Document (CDD) Validation conduct Preliminary Design Review (PDR), conduct Development Request For Proposal (RFP) Release Decision, begin source selection for Engineering Manufacturing Development (EMD) EXIT: Demonstration that risks have been adequately mitigated to support a commitment to design for production, Validated capability requirements, full funding in the Future Year Defense Plan (FYDP), and compliance with affordability goals for production and sustainment SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: DRFPRD Regarded by the USD (AT&L) as the most important decision in the program’s lifecycle Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2

Milestone B MDA approves*: Program Initiation (for most programs) Entry into EMD Acquisition Program Baseline LRIP quantities Exit criteria for next phase Type of Contract Milestone B Certification (10 USC 2366b) Acquisition Decision Memorandum SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Most requirements for this milestone should be satisfied at the Development RFP Release Decision Point; however, if any significant changes have occurred, or if additional information not available at the Development RFP Release Decision Point could impact this decision, it must be provided at the Milestone B. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2

JRATS/JTAMS Update Lesson Plan Status Acquisition Activities Review Marching Orders SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2 March 2014

JRATS and JTAMS Update Joint Reconnaissance and Targeting System (JRATS) Congrats, we passed Milestone A! Please see the Milestone A ADM in your Job Aids. We are now getting ready for Milestone B. First, we need to understand our requirements, create a build-to performance specification (System-Sub-System Specification (SSS)), create a Software Requirements Specifications (SRS) that supports the SSS, and an Interface Requirements Specification (IRS) that is the basis for our Allocated Baseline. Our Focus will be on understanding the requirements and risks of a pre-milestone B JTAMS You will analyze Requirements documents Identify risks SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2

Practicum 2 Timeline SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2 10 10

Joint Training and Maintenance System (JTAMS) Increment 1 Government Roadmap Schedule SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: The Government Roadmap Schedule shows one way a program office can quickly organize parallel events for presentation and planning purposes. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Note that we are planning on two MRES prototypes Engineering Design Models (EDM) Practicum 2 11

Marching Orders Lesson Plan Status Acquisition Activities Review JRATS/JTAMS Update Marching Orders SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2 March 2014

Practicum 2 Instructions Each team will develop the practicum solution slide package using the templated slides provided, the given scenario and the artifacts, and the Job Aids folder. All slides will be submitted to the instructors electronically (Blackboard/Shared Drive) and hard copy (printed 2 slides per page and double sided) Each team will designate a PM and Deputy PM to present the results of the analysis prepared by the team. The student templates identify specific slides to be included in the formal student presentation . You will have 1.5 hours for research and development of the practicum solution. The PM and Deputy PM will have 5 minutes each to present their designated slides. SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Student Instructions: Each team will develop the practicum solution slide package using the templated slides provided, the given scenario/artifacts –additional info is in the Job Aids folder. All slides will be submitted to the instructors electronically (Blackboard/Shared Drive) and hard copy (printed 2 slides per page and double sided) Each team will designate a PM and Deputy PM to present the results of the analysis prepared by the team. You will have 1.5 hours for research and development of the practicum solution. The PM and Deputy PM will have 5 minutes to present their designated slides. Instructor Notes: The 5 teams will each brief the selected slides and the instructor will grade the individual briefers for an individual “PM” grade according to the rubric. Each team will have 2 briefers per practicum. Instructors will also grade the entire package for the team grade according to the rubric – this will be done after the presentation time. All practicums are followed by in-class homework time for the students so the instructors can take that 30 minutes to execute the team and individual grading. The 5 teams will be divided up so that both instructors will take briefings – since there are 5 teams and normally 2 instructors, one instructor will take 3 teams (6 briefers) and the other instructor will take 2 teams (4 briefers). I recommend the instructor taking the 3 teams stay in the classroom and condense their feedback during the actual session. The instructor taking the 2 teams can use the required “team room” and can take that opportunity to elaborate on the major takeaways and other learning points. There is no penalty IAW the rubric for students exceeding the 5 minutes per brief – however, it is important for the instructors to enforce this time limit especially if you do not have a separate team room and/or a 2d instructor. There is sufficient time in the schedule to conduct all briefings in one classroom. Additionally, there is the option of not having some students brief – if you elect this option, you can designate the students that did not brief P1-P3 to brief during P4 or grade the student during the Discussion Panel brief (the DP option should be the option of last resort) Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2 March 2014 13

Scope of Presentation During this exercise, each team will be required to perform Level II Information Technology/Software Acquisition Management tasks that would typically be conducted in a government program office. PM DPM: Presentation Intro/Overview SSR Analysis Requirements Analysis JTAMS PDSS Risk Assessment Risk Mitigation Plan/Analysis Presentation Intro/Overview Measurement Analysis Revised Cost Analysis Program Protection Plan Analysis Security Control Analysis SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: These are the required slides the students will prepare. All sections of the practicum requirement will be submitted for grading electronically and hard copy. Instructors are free to modify this requirement as they see fit. The instructor slide template has suggested answers and the grading rubric identifies the grading approach. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Summary/ Recommendations – PM and DPM All slides will be submitted to the instructors electronically (Blackboard/Shared Drive) and hard copy (printed 2 slides per page and double sided) See the file “Practicum 2 Situation and applicable artifacts” See the Student Template Slides for the practicum requirements Practicum 2

Marching Orders Remember, you are members of the JTAMS PMO – you must select a PM and DPM. Go to your Student CD and open the folder for this Practicum. Start by reading “Practicum 2 Situation and applicable artifacts” found in the Practicum 2 folder and by reviewing artifacts or tools found in the Job Aids Time Event Misc 1200 - 1220 Practicum Intro Instructor 1220 - 1350 Research and prepare analysis* Student teams 1350 Submit entire analysis Submit electronically on BB or shared drive AND hard copy 1350 - 1515 Student PM/DPM Presentations Students present selected slides by team IAW the slide templates 1515 - 1530 Instructor Wrap up SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: Given a notional Information Technology (IT) system, analyze the needed documentation and decisions necessary for an Information Technology (IT)/Software Intensive System (SIS) to support a Milestone decision. *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: The student teams will be divided up between the instructors if possible for the presentations (on instructor gets 2 teams and the other will have 3). This will take two locations – the CRD has been updated as follows: "FY17 Desired: 2 Breakout Rooms/FY18 Required: 2 Breakout Rooms“ – so for the remainder of FY17, we might have to do all presentations in one classroom. The hard copy submissions will include the entire practicum submission for grading. Instructors can use the hard copy of the student slides to take notes during the presentation. Actual grading, etc can be done during the student homework time following the practicum. Reinforce that each team needs to select 2 briefers who will present (and be graded) in accordance with the requirements found in the templated slides and in keeping with the grading rubric. Also reinforce that those not briefing will need the assistance of others on the team to be successful. Everyone will brief a Practicum in order to graduate. It is best to have the students put the contents of the Student CD on their Desktops for better access to the material. This is especially true for the team that does the cost estimating. The only area that is a little complex is the cost estimating section. Be aware that the students may come up with different numbers than those in the instructor answer. As long as they are in the ballpark, that’s OK – please do not grade them down for providing slightly different numbers. During the student presentations, I recommend you offer feedback after every presentation to reinforce the learning points or to correct areas where the students may have missed the mark. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: *Allow time to ensure the presenters are familiar with the material Practicum 2 March 2014 15

Today we learned to (1 of 2): Given an IT/SIS acquisition program, apply a cost estimation methodology to recommend appropriate strategies for budget execution within the legislation and guidance of PPBE. Apply a cost estimation methodology to the analysis of an acquisition program to determine the status of budget execution throughout the acquisition life cycle, Explain the DoD Systems Engineering Process in the context of an IT/SW Development. Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle. Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. Identify relevant considerations that influence the acquisition lifecycle of a software-reliant system. SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2

Today we learned to (2 of 2): Given a scenario, identify program IT decision information requirements. Create a set of program IT measures that are linked to the program decision information requirements. Apply the measurement results to support IT program decisions. Identify risks inherent to Information Technology (IT) system acquisition. Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario Apply the Program Protection Plan to an IT Acquisition Scenario. Given an IT acquisition scenario, choose the appropriate controls for a system based on confidentiality, integrity, or availability requirements. SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: N/A *Policy / Directive / Standard / DTM ID: N/A ********************************************************************************************************************************************************** Key Points: Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Practicum 2