Product Support BCA Exercise – JRATS/JTAMS

Slides:



Advertisements
Similar presentations
E-Commerce Unit 06 A/601/7313 LEVEL 3
Advertisements

JHP Case Study Introduction 1 UNCLASSIFIED notional data for notional program.
Prepared By: Certified Compliance Solutions, Inc. August 2012
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Stepan Potiyenko ISS Sr.SW Developer.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
UI Standards & Tools Khushroo Shaikh.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
SE 555 Software Requirements & Specification Requirements Management.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Engineering Institute Capability Maturity Model (CMM)
Resiliency Rules: 7 Steps for Critical Infrastructure Protection.
1 Configuration Management “The Cookbook Approach”
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
IRM304 CDR Course Manager: Denny Involved Competency Leads: 26 (Cybersecurity)-Denman, 19 (Measurement)-Denny, 7 (DBS)-Corcoran [Capability Planning],
Security Policies and Procedures. cs490ns-cotter2 Objectives Define the security policy cycle Explain risk identification Design a security policy –Define.
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Engineering Essential Characteristics Security Engineering Process Overview.
1 Technology Infusion of the Software Developer’s Assistant (SDA) into the MOD Software Development Process NASA/JSC/MOD/Brian O’Hagan 2008 Software Assurance.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
Software Engineering Process Models Models for Guiding the Development of Software.
C HU H AI C OLLEGE O F H IGHER E DUCATION D EPARTMENT O F C OMPUTER S CIENCE Preparation of Final Year Project Proposal Bachelor of Science in Computer.
aSSIstant secretary of the army ACQUISITION LOGISTICS AND TECHNOLOGY.
Configuration Control (Aliases: change control, change management )
 System Requirement Specification and System Planning.
 1- Definition  2- Helpdesk  3- Asset management  4- Analytics  5- Tools.
Advanced Software Engineering Dr. Cheng
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
JTAMS PRE-CDR IT/SIS ANALYSIS
Software Project Configuration Management
Supporting quality devices
Software Configuration Management (SCM)
Managing the Project Lifecycle
ISA 201 Intermediate Information Systems Acquisition
JTAMS MILESTONE A ANALYSIS
JTAMS POST-CDR IT/SIS ISSUES
JTAMS PRE-CDR IT/SIS ANALYSIS
ISA 201 Intermediate Information Systems Acquisition
JTAMS POST-CDR IT/SIS ISSUES
Figure 2: Overview of Program Protection Activities and Relationships
ISA 201 Intermediate Information Systems Acquisition
ISA 201 Intermediate Information Systems Acquisition
JTAMS PRE-MILESTONE B ANALYSIS
JTAMS PRE-MILESTONE B ANALYSIS
2 Selecting a Healthcare Information System.
Chapter 4 Systems Planning and Selection
CIS 339 Competitive Success/snaptutorial.com
CIS 339 Education for Service/snaptutorial.com
CIS 339 Teaching Effectively-- snaptutorial.com
Communicate the Impact of Poor Cost Information on a Decision
Engineering Processes
STATUS REPORT.
Communicate the Impact of Poor Cost Information on a Decision
PART SEARCH If the part is not visible at the time of call updation, following points need to be cross checked : Ensure the model name entered is correct.
AIS Manual (Doc 8126) Air Navigation Procedures for AIM Seminar
HART Technologies Process Overview
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Proposals & Project Specifications
Replies by the Task Force to the comments provided by GRVA members
Engineering Processes
HHS Child Welfare National IT Managers' Meeting
Configuration Management
JTAMS Post-Milestone C Analysis
Software Reviews.
JTAMS PRE-MILESTONE B ANALYSIS
Presentation transcript:

Product Support BCA Exercise – JRATS/JTAMS

Directions Task 1: Provide a brief overview of the scenario Student Tasks: Overview: Read the Exercise scenario and the Job Aids provided. Identify the 7 “IT” areas that should be included in the PS BCA and provide an overview of your assigned areas with a focus on JTAMS. Ensure you identify all references in your exercise briefing. (note – you should also use the DAG and search the internet for additional information to assist you in your analysis). Task 1: Provide a brief overview of the scenario Task 2: Provide an overview of the “IT” areas to include a brief description of the intent of each area. Task 3: Given the current scenario, propose specific OSA questions to be added to the BCA checklist to support the PEO/PM’s BCA effort Task 4: Software Engineering and Software Development Environment: Recommend areas that should be assessed for the BCA Task 5: Propose specific Software Security Architecture and Software Assurance questions/items to be added to the BCA checklist to support the PEO/PM’s BCA effort EXERCISE 4 SEE: Exercise 4 Product Support BCA Summary of the 7 areas: 1) Software Engineering Environment. When computing the software cost estimate of each product alternative, it is important to understand the software development environment. 2) Open Systems Architecture (OSA). Adherence to OSA principles directly impacts the supportability of each product during the Operations and Support (O&S) phase. 3) Intellectual Property (IP) Rights. Ease of support during the O&S phase is directly impacted by whether the government has the rights to update the software in the project’s architecture. Sharing Data, Information, and Information Technology (IT) Services. Data, information, and IT services will be made visible, accessible, understandable, trusted, and interoperable throughout their lifecycles for all authorized users. Data governance rules must be clear for data element maintenance purposes. Software Development Environment. The product support software development must replicate the original software development environment so the software applications can be improved easily 6) Software Security Architecture. The solution architecture for security should have been built in from the original design of each software item for ease of product support. 7) Software Assurance. The developers of the original software code must use secure coding practices to ensure ease of support during the O&S phase.

Task 1 Provide a brief overview of the scenario EXERCISE 4 SEE: Exercise 4 Product Support BCA\Job Aids

Task 2 Task 3: Provide an overview of the “IT” areas to include a brief description of the intent of each area. EXERCISE 4 SEE: Exercise 4 Product Support BCA\Job Aids Summary of the 7 areas: 1) Software Engineering Environment. When computing the software cost estimate of each product alternative, it is important to understand the software development environment. 2) Open Systems Architecture (OSA). Adherence to OSA principles directly impacts the supportability of each product during the Operations and Support (O&S) phase. 3) Intellectual Property (IP) Rights. Ease of support during the O&S phase is directly impacted by whether the government has the rights to update the software in the project’s architecture. Sharing Data, Information, and Information Technology (IT) Services. Data, information, and IT services will be made visible, accessible, understandable, trusted, and interoperable throughout their lifecycles for all authorized users. Data governance rules must be clear for data element maintenance purposes. Software Development Environment. The product support software development must replicate the original software development environment so the software applications can be improved easily 6) Software Security Architecture. The solution architecture for security should have been built in from the original design of each software item for ease of product support. 7) Software Assurance. The developers of the original software code must use secure coding practices to ensure ease of support during the O&S phase.

Rationale or Expected Benefit to Business Case TASK 3 Given the current scenario, propose specific OSA questions to be added to the BCA checklist to support the PEO/PM’s BCA effort Added to Checklist Rationale or Expected Benefit to Business Case EXERCISE 4 SEE: Exercise 4 Product Support BCA Part B\Job Aids NOTE: Use the BCA checklist to determine the type of question identified in other areas of the BCA. Use your understanding of IT systems, Open Systems Architecture, and the JTAMS scenario to identify relevant questions that should be asked to ensure OSA is one of the critical considerations in developing a recommendation during a Product Support BCA Note: See the Product Support BCA Guidebook, the Open Systems Architecture Contract Guidebook for Program Managers, Version 1.1, May 2013, and the SCRM and SwA Winter Update Feb 2015 Final

Rationale or Expected Benefit to Business Case TASK 4 Task 4: Software Engineering and Software Development Environment: Recommend areas that should be assessed for the BCA Propose specific Software Engineering and/or Development questions/items to be added to the BCA checklist to support the PEO/PM’s BCA effort Added to Checklist Rationale or Expected Benefit to Business Case SW Engineering and Development EXERCISE 4 SEE: Exercise 4 Product Support BCA\Job Aids NOTE: Use the BCA checklist to determine the type of question identified in other areas of the BCA. Use your understanding of IT systems, Open Systems Architecture, and the JTAMS scenario to identify relevant questions that should be asked to ensure OSA is one of the critical considerations in developing a recommendation during a Product Support BCA Note: See the Product Support BCA Guidebook, the Open Systems Architecture Contract Guidebook for Program Managers, Version 1.1, May 2013, and the SCRM and SwA Winter Update Feb 2015 Final

Rationale or Expected Benefit to Business Case TASK 5 Propose specific Software Security Architecture and Software Assurance questions/items to be added to the BCA checklist to support the PEO/PM’s BCA effort Added to Checklist Rationale or Expected Benefit to Business Case Software Security and Assurance EXERCISE 4 SEE: Exercise 4 Product Support BCA\Job Aids NOTE: Use the BCA checklist to determine the type of question identified in other areas of the BCA. Use your understanding of IT systems, Open Systems Architecture, and the JTAMS scenario to identify relevant questions that should be asked to ensure OSA is one of the critical considerations in developing a recommendation during a Product Support BCA Note: See the Product Support BCA Guidebook, the Open Systems Architecture Contract Guidebook for Program Managers, Version 1.1, May 2013, and the SCRM and SwA Winter Update Feb 2015 Final