Ask Pete Acquired Software Knowledge Project - Estimation- Tool - Effort Presented to the NASA OSMA SAS ‘01 NASA IV&V Facility September 5-7, 2001 Tim.

Slides:



Advertisements
Similar presentations
1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
Advertisements

Metrics for Process and Projects
1 SQA & Reuse Katerina Goseva-Popstojanova, WVU Aaron Wilson, NASA IV&V Kalynnda Berens & Richard Plastow, GRC Joanne Bechta Dugan, UVa David Gilliam JPL.
1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.
Stepan Potiyenko ISS Sr.SW Developer.
Software Measurement and Process Improvement
Grad Tools Pilot Grad Tools and The Dissertation Checklist CARAT Updates Presentation March 19, 2004 Presenters: Michelle Bejian Lotia, Duderstadt Center.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Software Fault Injection Kalynnda Berens Science Applications International Corporation NASA Glenn Research Center.
Project Management Methodology (PMM)
Civil Government Services Group 1 Return on Investment of Independent Verification and Validation: Indirect Benefits James B. Dabney, Gary Barber, Don.
Software Engineering Institute Capability Maturity Model (CMM)
Glenn Research Center at Lewis Field Software Assurance of Web-based Applications SAWbA Tim Kurtz SAIC/GRC Software Assurance Symposium 2004.
Introductions Jim Enzinna, Chief, Licensing Division Mark DiNapoli, Assistant Chief, Licensing Division Tracie Coleman, Head, Information Section Vince.
PMSS Final SOW May 22 nd, Statement of Work 2 GLENN RESEARCH CENTER PROJECT MANAGEMENT SUPPORT SERVICES (PMSS) The Contractor shall provide expert.
Complete and Integrated Lifecycle Management. Challenges 1.
Introduction to Information System Development.
SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al.
Process Modeling CS 4320 Fall Process Difficulties SW not a production line Each project is different—even within the same company No universally.
1SAS 03/ GSFC/SATC- NSWC-DD System and Software Reliability Dolores R. Wallace SRS Technologies Software Assurance Technology Center
What is SMEcollaborate Primarily developed for Small and Medium Companies who wish to collaborate together. It is a:- A resource center for collaborating.
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
Guidance Notes on the Investigation of Marine Incidents
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
This document is proprietary to Project Consulting Group, Inc. and contains confidential information which is solely the property of Project Consulting.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
How to Know That What You Want Has Been Done- 1 Claire Lohr Member, SESC Management Board Chair IEEE 829 Working Group How to Know That.
NASA Software Productivity Consortium Affiliation NASA Office of Safety and Mission Assurance Software Assurance Symposium September 5, 2001 Cynthia Calhoun.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
JLab Software Assurance Program A Risk Based Approach to Software Management.
V&V of COTS RTOS for Space Flight Projects The 1st Annual NASA Office of Safety and Mission Assurance (OSMA) Software Assurance Symposium (SAS) Michael.
SAS ‘05 Reducing Software Security Risk through an Integrated Approach David P. Gilliam, John D. Powell Jet Propulsion Laboratory, California Institute.
NASA Office of Safety & Mission Assurance IV&V Cost Estimation – A Joint NASA & US Navy Collaboration to Model & Automate the Process Software Assurance.
1 Fault-Based Analysis: Improving IV&V Through Requirements Risk Reduction '02 Jane Hayes Rama Bireddy D.N. American SAIC Department of Computer Science.
Optimizing NASA IV&V Benefits Using Simulation Grant Number: NAG David M. Raffo, Ph.D College of Engineering and Computer Science School of Business.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
August 2005 TMCOps TMC Operator Requirements and Position Descriptions Phase 2 Interactive Tool Project Presentation.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Architecture Risk Assessment (SARA) Tool Khader Shaik, Wallid Abdelmoez, Dr. Hanny Ammar Lane Department of Computer Science and Electrical Engineering,
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
Personal Design and Development Software Process PD 2 SP “The unexamined life is not worth living.” Plato.
Contents 1 Description of 1 Description of Initiative Initiative 3 Defining Inspection 3 Defining Inspection Perspectives Perspectives 2 Overview of 2.
California Institute of Technology 1 Operationalization and Enhancement of the Advanced Risk Reduction Tool (ARRT) Presentation to the 2 nd Annual NASA.
Glenn Research Center at Lewis Field Software Assurance of Web-based Applications SAWbA Tim Kurtz SAIC/GRC Software Assurance Symposium 2004.
1 SAS ‘04 Reducing Software Security Risk through an Integrated Approach David P. Gilliam and John D. Powell.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Planning for and Managing Software Verification & Validation (V&V) Quality Assurance Project Oversight Jeff Lewis, PMP The Æon Group, Inc.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
IV&V Facility 7/28/20041 IV&V in NASA Pre-Solicitation Conference/ Industry Day NASA IV&V FACILITY July 28, 2004.
Estimate Testing Size and Effort Using Test Case Point Analysis
Presented to the NASA OSMA SAS ‘01
Development Projects / Analysis Projects / On-site Service Projects
Raytheon Parts Management
HSE Case: Risk Based Approach.
Phase 1 Tollgate Review Discussion Template
Phase 1 Tollgate Review Discussion Template
Engineering Processes
Phase 1 Tollgate Review Discussion Template
© Oxford University Press All rights reserved.
Presentation transcript:

Ask Pete Acquired Software Knowledge Project - Estimation- Tool - Effort Presented to the NASA OSMA SAS ‘01 NASA IV&V Facility September 5-7, 2001 Tim Kurtz,  SAIC/NASA Glenn Research Center Principal Investigator  Martha Wetherholt Research funded by NASA OSMA and GSFC IV&V Facility

Overview Who, What, Where, When, How, Why? Control Levels IV&V Criteria Integration and Shared Data Future Plans Summary

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? Who… Pete is a computer application for: P rojects with software development E stimating duration, cost, schedule T ool for planning project, SPA and IV&V activities determining the E ffort (tasks) based on the COCOMO, SW reuse (COTS/GOTS), Control Levels, IV&V criteria and documentation

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …What… Ask Pete incorporates: COCOMO II SLOC or Function Points GRC’s Software Development Procedure & Control Levels NASA’s IV&V Criteria Plan Templates CMM Checklist

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …Where…

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …When… Pete is a Center Initiative sponsored by Code IT, initiated 3 years ago … Initially developed and updated by summer interns, Mike Johns & Shawn McCollum Has been available on the NASA WWW for three years Compared Pete’s projections with results from actual NASA projects (CM-1, DCE-1) with favorable results Continually gathering additional feedback via Ask Pete web site

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …How… An MS Access database contains: All the questions What are the potential effects to personnel due to failure of this software And answers No injury Minor injury Injury Severe Injury or temporary disability Loss of life or permanent disability Project information

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …How…(cont.) An MS Access database contains: The decision structure to determine Cost and schedule estimates Control Levels, which determine  Development activities  Documentation Need for Independent Assessment (IA) or IV&V, which determines the base set of IA or IV&V activities Recommended development activities Other report information

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …How…(cont.) The VB User Interface contains: Logic that Manages the interface to the database Generates tailored reports Real-time cues that show the effects of tradeoffs Help for the program and individual questions Links to the support web site and for assistance

Research funded by NASA OSMA and GSFC IV&V Facility Who, What, Where, When, How, Why? …Why?  Checklist of factors for planning  Estimates of effort  Identifies Control Level, documentation and activities  Software Project Plan  Planning SPA activities and effort  Control Level, docs & activities  Metrics for tracking project success Need for IA or IV&V Planning IA or IV&V activities and effort Estimated IV&V schedule Provides common basis for negotiations

Research funded by NASA OSMA and GSFC IV&V Facility Control Levels The GRC Software Development Procedure includes a matrix to determine the control requirements for the software Low control Medium control High control Critical control The resulting Control Level identifies Development lifecycle Development activities Documentation needs Can be easily modified in the database to suit individual Centers’ processes

Research funded by NASA OSMA and GSFC IV&V Facility Control Levels Utilizes weighted responses to COCOMO and Control Level questions to determine Control Level score Low Risk<= 100 Medium Risk 101 to 166 High Risk 167 to 266 Mission Safety/Critical >266 Identifies activities based on risk Verification and Validation CM and SQA Software Safety Software Risk Management Software Requirements

Research funded by NASA OSMA and GSFC IV&V Facility IV&V Criteria Recommendation for IA or IV&V is based on the IV&V criteria in NPG 8730 Incorporates criteria and matrix to determine consequences and probability of failure If IA or IV&V indicated, a base set of activities are included in the recommended development activities User may force IA or different levels of IV&V activities, regardless of the program’s recommendation for their project

Research funded by NASA OSMA and GSFC IV&V Facility Integration and Shared Data Integration… Ask Pete provides the results of project characterization to ARRT: SLOC, cost and schedule estimates Recommended development activities (and IV&V activities, if applicable) which are treated by ARRT as PACTS Results of certain questions which indicate the degree or lack of particular risks

Research funded by NASA OSMA and GSFC IV&V Facility Integration and Shared Data Integration…(cont.) ARRT allows the user to adjust the recommended activities (add, delete or replace) based on their knowledge of the project. The results of the ARRT session are provided to Ask Pete: The final tailored set of PACTS which are treated by Ask Pete as development activities. Incorporated in Ask Pete reports and plans

Research funded by NASA OSMA and GSFC IV&V Facility Integration and Shared Data …Shared Data Results of an Ask Pete session are stored in a shared database and available to ARRT and other applications Data includes General project information, I.e. cost, SLOC, etc. All possible activities by phase with recommended activities identified All facts, questions, (SEI risk taxonomy) risks Links between  facts and questions  questions and risks

Research funded by NASA OSMA and GSFC IV&V Facility Future Plans Develop and provide training and informational presentations at NASA centers Develop and finalize plan templates (SQA, IV&V, SDP) Implement ability to decompose/combine projects Investigate conversion to web-based application

Research funded by NASA OSMA and GSFC IV&V Facility Summary Answered Who, What, Where, When, How and Why? Incorporates (tailorable) Control Levels and IV&V criteria Integrated with ARRT and data is available for other applications Training sessions and presentations at NASA Centers next year Download your copy from Stop by and try it out on Friday