 |
|
On-Line Slides
The
on-line presentations shown on this page are available
in one or more of the following formats: MS Office (PowerPoint);
PDF (viewable with Adobe Reader), and HTML (web pages).
To view an on-line presentation, click the icon for
the format that is available or, if multiple icons are
shown, for the format you prefer. Presentations with
a PowerPoint icon may be downloaded as well as viewed
on-line. |
|
| Course
# |
Title |
Instructor |
MS
Office Version |
PDF
Version |
HTML
Version |
| |
The Power of 10: Rules for Developing Safety-Critical Code |
Gerard J. Holzmann |
|
|
|
This paper describes how adherence to a set of 10 verifiable coding rules can make the analysis of critical software components more reliable.
|
| |
NPR 7150.2 Instructional Media Educator (NPRIME) |
N/A |
|
|
|
This on-line tutorial is a user-friendly way to learn the basic concepts of NPR 7150.2 and its requirements for the software you write. Navigation through the six chapters of the tutorial is easy thanks to a handy navigation bar and table of contents. Definitions of terms pop up when you mouse over underlined words, and there are useful links to relevant websites and documents. When you finish the tutorial, you can take the on-line quiz to test your understanding. Available to NASA users only.
|
| |
IV&V of Neural Networks |
n/a |
|
|
|
|
This course is intended for IV&V practitioners and managers that have projects
deploying neural networks. It is a collection of ten web-based, interactive
training modules designed to permit users to train at their own pace. Each module
is designed with audio instruction and visual examples to enhance the learning
experience. Each module takes approximately 45 to 60 minutes to complete
and provides a pre- and post-exam, learning objectives, and links to the IVVNN
Guidance. The entire IVVNN Course is estimated to take 5 hours to complete.
The ten modules are:
"Neural Network Types and their Functionality"
"An Overview of the V&V of Neural Network Processes, Activities, and Tasks"
"Modified Lifecycle for Developing Neural Networks"
"Requirements for Adaptive Systems and Neural Networks"
"Neural Network Hazard and Risk Analysis"
"Neural Network Rule Extraction"
"Neural Network Stability: What is it and Implementation Strategies"
"Neural Network Testing Considerations"
"Configuration Management of Neural Network Training and Design"
"How to Build an Effective Operational Monitor"
To register for the IVVNN Course, please fill out and submit the registration
form located at
http://www.isr.us/IVVNN. If your registration
is approved, you will automatically receive an e-mail containing a username
and password which grants you access to the IVVNN Course website. Please note
that the IVVNN Course is free of charge for government employees. Non-government
employees may be required to pay a fee for each course module.
|
| |
NASA Software Safety Standard |
Cynthia Calhoun |
|
|
|
An excellent overview of the new NASA Software Safety Standard
|
| |
CMMI Today and Process Maturity Profile |
Mike Phillips |
|
|
|
Presentation by Mike Phillips, SEI, Monday, Jan. 26, 2004.
|
| |
What is CMMI? |
Sally Godfrey |
|
|
|
Brief overview of CMMI. PowerPoint presentation.
|
| GSFC002 |
Technical Manager's Training |
Barbara Pfarr, et al. |
|
|
|
The TMT is a 6-day residential program that focuses on presenting a high level overview of how work gets done in the Goddard environment. The Course Objectives are to:
a) Learn about the Life Cycle of a project within the Goddard environment
b) Get familiar with principles of good Project Management, (How to plan, organize, implement, and control technical projects) and
c) Learn principles of how to increase effectiveness within work teams through collaborative team participation.
There is a two-hour orientation at Goddard Greenbelt, 6 full days at Wallops and an hour and a half wrap-up session the following week in Goddard Greenbelt. The course begins on a Sunday and ends on a Friday. Developmental activities begin on the bus ride to Wallops.
|
| GSFC003 |
Using CMMI for Improvement at GSFC |
Sally Godfrey |
|
|
|
Systems Engineering Lecture given on June 1, 2004.
|
| ISD003 |
Mission Software for Project Managers |
EPG |
Goddard
Civil Servant Entry |
[For GSFC Civil Servants
only]
This course presents an overview of mission software, especially the interaction between the software development project and the larger Project organized by a project timeline.
Formulation phase concepts include key early decisions that can set a Project on the right course; project management considerations; mission software architecture and requirements; acquisition; cost estimation; and software-related trades.
Development phase topics include software development considerations (software development life cycle, reviews, inspections and walkthroughs, testing considerations, and assurance considerations); managing software development (project planning, risk management, project monitoring and control, and post development support); improvement initiatives (including the Software Process Improvement Project); and recommendations for mission success for both software developers and Project management.
|
| JPL001 |
Quantitative Software Management |
JPL/CSC (Jairus Hihn & Bill Decker) |
|
|
|
This 2-day course trains software managers on the generation of software cost estimates and the use of software metrics in managing their software development activities. Cost estimation topics covered include software estimating methods and models, software development estimation, software development metrics, cost drivers, productivity, common errors in software estimation, rules of thumb, software productivity databases, and risk reduction and mitigation. The project measurement part of the class covers a variety of basic measures that are used to monitor software development including metrics for tracking growth and stability, resources and cost, schedule and progress, and quality. Additionally the class discusses how to analyze the measures, as well as how to plan for project/task monitoring.
|
| SEI013 |
CMMI v1.2 and Beyond |
Mike Phillips, SEI |
|
|
|
This tutorial provides an overview of CMMI V1.1 as of today, including adoption trends, transition status, and appraisal metrics, as well as an overview of the latest updates to the CMMI model, V1.2. This presentation covers the major themes behind the update, a comparison of V1.1 and V1.2, and the specific changes to the updated model.
|
| SWG002 |
Software Metrics Selection |
Carolyn Seaman |
|
|
|
This tutorial, which was sponsored by the NASA Software Metrics Group, presents a software measurement methodology that has been developed and tailored for NASA by the Fraunhofer Center - Maryland and the NASA Software Metrics Group. The tutorial explains this methodology and the mechanics of using it for software leads on NASA projects. It covers the motivation for software measurement, some practical examples of measurement, the steps that have already been taken within NASA to enable software leads to incorporate measurement into their projects, and the steps that software leads must take to plan and deploy software measurement. The tutorial also incorporates the measurement requirements of the new NPR for Software.
|
| SWG005 |
Learning Near-Optimum Inspection Policies |
Dr. Tim Menzies |
|
|
|
High assurance software requires extensive and expensive assessment. There are many forms of software assessment, ranging from manual inspections to automatic formal methods. These assessment methods differ in their effectiveness and the effort required to apply them. Typically, the more effective methods are more expensive. Hence, project managers often "bias" the assessment resources and apply more effort where they think that extra effort might be most useful.
If most of the assessment effort explores project artifacts A,B,C,D, then that leaves a "blind spot" in E,F,G,H,I, etc. Blind spots can compromise high assurance software. It is therefore important to discuss the bias introduced by the inspection policy. In a nutshell, we need to ask "how blinding is our bias?"
This talk (presented at GSFC on Feb. 15, 2008) contrasts three different kinds of "bias" in selecting what code modules to inspect:
1) manual methods such as "read the biggest thing first/last"
2) traditional data mining methods, such as those advocated by the author and those deployed in NASA-funded inspection tools
3) a new data miner called "WHICH."
We find that #1 usually outperforms #2. This result calls into question many years of research by the speaker (translation: "oh dear"). But we also find that #3 almost always out-performs #1 or #2 (translation: "phew!!"). In fact #3 works so well that we speculate that it could be used as a proxy for determining the actual number of defects remaining to be found, after inspecting Z% of the code.
|
|
|
|
