1. Presented to the NASA OSMA SAS ‘01
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, e
SAIC/NASA Glenn Research Center
Principal Investigator e Martha Wetherholt
Research funded by NASA OSMA and GSFC IV&V Facility

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

3. Who, What, Where, When, How, Why? Who…
Pete is a computer application for:
Projects with software development
Estimating duration, cost, schedule
Tool for planning project, SPA and IV&V activities
determining the Effort (tasks) based on the COCOMO, SW reuse (COTS/GOTS), Control Levels, IV&V criteria and documentation

4. 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

5. Who, What, Where, When, How, Why? …Where…

6. 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

7. 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

8. 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

9. 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

10. Who, What, Where, When, How, Why? …Why?
Proj Mgr
SPA
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
Negotiate
IV&V
Need for IA or IV&V
Planning IA or IV&V activities and effort
Estimated IV&V schedule
Provides common basis for negotiations

11. 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

12. Control Levels
Utilizes weighted responses to COCOMO and Control Level questions to determine Control Level score
Low Risk <= 100
Medium Risk to 166
High Risk to 266
Mission Safety/Critical >266
Identifies activities based on risk
Verification and Validation
CM and SQA
Software Safety
Software Risk Management
Software Requirements

13. 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

14. 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

15. 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

16. 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

17. 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

18. 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