| Course
# |
Title |
Frequency |
Duration |
Instructor |
Sponsor |
| APPL001 |
Foundations of Project Management |
TBD |
5 days |
NASA/APPL |
NASA/HQ |
This course provides interesting and relevant instruction on the methodologies, techniques, terms and guidelines used to manage cost, schedules and technical aspects through the life cycle of a project. The course is invaluable for project control and support personnel who need a better grasp of the project world. For more details see: http://ohr.gsfc.nasa.gov/DevGuide/Home.htm.
|
| APPL002 |
Systems Requirements |
TBD |
3 days |
APPL/NET |
TBD |
This course will provide system engineers and other technical personnel with a proven process to obtain information needed before writing requirements and to write good requirements. The seminar has the following objectives: 1) To define the steps of a good requirements writing process (i.e., discuss how to ensure that the scope of the project (product) is defined and agreed upon before investing in writing requirements), as well as outline what information needs to be obtained and how to obtain it; 2) To learn what makes bad versus good requirements and how to more easily write good requirements that will not cause problems later in the process; and 3) To learn how to organize requirements into a specification and what other data is needed to capture in your specification to ensure life cycle management of requirements. The intended audience includes system engineers, engineers, scientists, and others whose responsibility includes writing or reviewing requirements for products, whether hardware, software, or systems. Highlights include lectures, hands-on exercises, and reviews of the participant's own projects and products so that participants can immediately improve their requirements process. Questions will also be answered on how to overcome existing problems.
|
| CSM002 |
CMMI Overview |
One class per year |
4 hours |
CSM |
APPEL |
The SEI Capability Maturity Model Integration (CMMI) describes a framework that organizations can use to determine their ability to develop and maintain systems. This framework provides guidance for improving an organization's processes and its ability to manage the development, acquisition and maintenance of products and services.
This four-hour briefing is recommended for Branch managers, project members, and others who want to learn about the CMMI, its costs and benefits, and what it will take to achieve a given level of certification. The course is also an excellent initiation for project teams beginning a process improvement effort. It includes a brief history of process improvement efforts and the CMMI; describes the intent and structure of the model, including all 25 Process Areas; and provides a detailed description of the Maturity Level 2 and 3 requirements, along with the implications and typical associated costs of implementing a successful improvement program. The primary difference between this four-hour class and the two-hour "CMMI for Executives" briefing is in the number of Process Areas that will be covered and the depth in which they'll be discussed.
|
| CSM003 |
SEPG/EPG Workshop |
TBD |
2 days |
CSM |
NASA/HQ OCE |
The description for this course is not yet available.
|
| CSM004 |
Introduction to PIID Workshop |
Class(es) for current year have been held |
4 hours |
Trish Freeman and Gail Borotto, CSM |
NASA/HQ |
The Introductory PIID Workshop defines and describes the Practice Implementation Indicators Description (PIID) spreadsheet issued by the Software Engineering Institute (SEI) for use in SCAMPI appraisals. The PIID spreadsheet is populated by the process and project teams during the preparation phase of an appraisal as part of the activities completed before the on-site phase of an appraisal begins. CSM Lead Appraisers have prepared this briefing to help process and project teams identify and document their processes and artifacts.
This workshop consists of two sessions. Session 1 describes the PIID spreadsheet, the terms used, and examples of how the CMMI model is used, together with knowledge of the process and project teams, to identify direct and indirect evidence artifacts for the appraisal. Session 2 covers best practices and suggestions for planning work for and completing the PIID including: estimates of time based on appraisal scope, roles and responsibilities, expert support, and review methods prior to appraisal.
Participants should take away knowledge of what types of artifacts are appropriate for direct and indirect appraisal evidence. Participants should also understand fundamental planning and population approaches to completing the PIID so that they can decide which one is appropriate for their team.
|
| CSM005 |
CMMI for Executives |
One class per year |
2 hours |
CSM |
APPEL |
This course is a 2-hour overview for senior decision makers who want to learn about the CMMI, its costs and benefits, and what it will take to achieve a given level of certification. The course is recommended for project managers, members of the Management Oversight Group (MOG), and other executives. It includes a brief history of process improvement efforts and the CMMI; describes the intent and structure of the model, including all 25 Process Areas (PAs); and outlines the Maturity Level 2 and 3 requirements, along with the implications and typical associated costs of implementing a successful improvement program. This overview will help you understand the CMMI, what is needed to implement it in an organization, and how it can help improve a workgroup's processes to better meet project and product business objectives.
|
| FSW001 |
FSW Developer Training |
Planned |
TBD |
ISD-FSB |
NASA/GSFC ISD-FSB |
The description for this course is not yet available.
|
| FSW002 |
FSW Development Lead Training |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW003 |
FSW Manager Training |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW004 |
FSB SPI Deployment Plan Presentation |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW005 |
FSW Sustaining Engineering Preparation Training |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW006 |
FSW Systems Engineering Training |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW007 |
FSW Test Lead Training |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW008 |
FSW Tester Training |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| FSW009 |
Introduction to Flight Software |
Planned |
4 hours |
ISD-FSB |
TBD |
For new Flight Software Branch personnel.
|
| FSW010 |
FSW Process Awareness |
Planned |
TBD |
ISD-FSB |
TBD |
The description for this course is not yet available.
|
| GSFC001 |
Continuous Risk Management |
TBD |
2 days |
NASA/GSFC |
NASA/HQ |
This 2-day course familiarizes the student with the fundamentals of Continuous Risk Management (CRM) and provides for interactive learning through the use of various methods and tools and a hypothetical space flight project case study. The second day is dedicated to organization-specific activities that will:1)establish and organization-specific risk baseline; 2)practice the functions of CRM paradigm; 3) promote teambuilding and a more cohesive work environment, and 4) provide risk information that can be acted on immediately upon completion of the course. Emphasis can be placed on the creation of Risk Management Plan as deemed necessary by each organization. For more details see: http://ohr.gsfc.nasa.gov/DevGuide/Home.htm.
|
| GSFC002 |
Technical Manager's Training |
TBD |
6 days |
Barbara Pfarr, et al. |
TBD |
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.
|
| GSFC004 |
Software Quality Assurance |
TBD |
2 days |
GSFC, Code 300 |
TBD |
The description for this course is not yet available.
|
| GSFC005 |
Introduction to NASA Technology Transfer |
Planned |
3 hours |
TBS |
NASA/GSFC OTT |
This course familiarizes NASA personnel with NASA policies and procedures related to technology transfer, including Goddard-specific practices. The course provides participants with a resource for working with the Goddard Office of Technology Transfer, as well as concepts to guide them through future technology transfer activities.
Objectives:
1) Outline the technology transfer process
2) Explain the different mechanisms NASA uses to partner with organizations
3) Identify factors that influence the transfer potential of a technology
4) Explain how NASA measures the impact of technology transfer activities
5) Identify the benefits of reporting technology.
|
| HQ001 |
Requirement Engineering Workshop |
TBD |
3-4 days |
Ivy Hooks |
NASA/HQ OCE |
The description for this course is not yet available.
|
| HQ002 |
Basic Principles of Practical Configuration Management |
Three classes per year |
3 1/2-day sessions (12 hours) |
SSCI |
NASA/HQ OCE |
This class provides course participants with a foundation in sound CM principles. Participants are presented the four high-level CM process elements that can be used as a springboard for defining and improving their own CM-related processes, roles, methods, and tools. This course will help participants develop basic CM skills for identifying configuration items, determining levels of control and baselines within a product life cycle, identifying an appropriate structure for a configuration library, and conducting audits to maintain baseline integrity. This class is led by an instructor via a Webex interface. The intended audience for this course includes process participants, individuals with CM responsibilities, such as project configuration managers, configuration management team members, and members of Change Control Boards. This course will also be valuable to project managers and project team members, such as requirements analysts, designers, developers, and testers, process developers and process improvement personnel, such as SEPG and Process Action Team (PAT) members. For information on registration, please contact Susan Sekira at 301 286-6160.
|
| HQ003 |
Software Inspections |
Three classes per year |
2 days |
Forrest Shull, Fraunhofer Center |
NASA/GSFC EPG |
Software inspection is a well-defined review process for finding and fixing defects in work products from all phases of software development. Inspections have proven time and again to be one of the most effective practices available for ensuring quality software and on-time deliveries. Many studies have demonstrated their benefits, both within NASA and across the industry. The rework effort saved not only pays for the effort spent on inspections, but also provides additional cost savings on the project. By removing defects at their origin, inspections prevent them from propagating through multiple phases and work products, and reduce the overall amount of rework necessary on projects. Side-effects of inspection meetings include improved team communication and education of project members in effective development practices.
This training course provides all the information needed for conducting software inspections on a project. The course 1) describes the process, roles, and responsibilities involved and 2) provides experience-based guidance on all activities. These guidelines are based on the experiences and lessons learned from literally hundreds of inspections at NASA Centers.
Since all projects are different, an emphasis in this course is on tailoring the processes to a team's particular needs, maximizing project benefit. Interactive sessions are included that use previous experience and past defect histories to best focus the inspections on the issues that really matter. The training also includes a hands-on workshop, where the process is applied to a work product from the participants' current project. The participants leave with a list of real defects identified and clear guidance on how to proceed.
|
| HQ004 |
IEEE/EIA 12207 Software Life Cycle Processes |
One class per year |
1-3 days (1 day overview + optional workshop) |
Lewis Gray, Abelia Corp. |
NASA/HQ OCE |
IEEE/EIA 12207 is the United States implementation of ISO/IEC 12207, "Software Life Cycle
Processes." IEEE/EIA 12207 is packaged in three volumes: IEEE/EIA 12207.0-1996 (the base
standard), IEEE/EIA 12207.1-1997 (IEEE guide to over 100 life cycle data items), and IEEE/EIA 12207.2-1997 (IEEE guide to life cycle process implementation).
This training begins with a stand-alone, one-day introduction to IEEE/EIA 12207 for managers and personnel who need to be, or want to be, familiar with the standard. You may sign up for this one-day course only.
For those who may eventually have to use IEEE/EIA 12207 for system acquisition, there will be an additional two-day workshop.
Each student in the one-day course will receive a copy of all three volumes of the IEEE/EIA 12207 standard, and a copy of the instructor's compact 170-page Guidebook to IEEE/EIA 12207 (ISBN 0-9719895-0-8) published by Abelia. In addition, participants in the workshop will receive a Microsoft Excel-based tailoring record tool, sample information item descriptions for use with IEEE/EIA 12207, and the solution to an example tailoring exercise.
|
| HQ006 |
Software Safety ViTS |
Three classes per year |
Approx. 55 hours |
Dr. Nancy Leveson, MIT |
NASA/HQ OCE |
Software allows unprecedented levels of complexity and new failure modes that are starting to overwhelm the standard approaches to ensuring safety. The causes of accidents are even changing. This class will focus on the unique problems involved in building software-controlled systems. Emphasis will be on procedures and techniques that are practical enough to be applied to projects today. Real-project experiences with these techniques in different application areas will be described and recent software-related accidents will be reviewed and analyzed. The goal of this class is not to learn how to satisfy various standards but rather how to design a tailored program that will be most effective for your project. The class size will be limited to encourage interaction. Students will work on example problems in small groups.
|
| HQ007 |
Earned Value Management |
Scheduled |
3 days |
Dorothy Tiffany, PMP and Walt Majerowicsz, PMP |
NASA/HQ |
NASA's project management environment is both challenging and exciting. One of the challenges is the proper integration of the cost, schedule, and technical elements of the projects. One of the exciting things is the use of Earned Value Management to accomplish this integration. Have you ever wondered: How to develop a detailed plan and accurately measure performance against it? What it means to be $550K "behind schedule"? How to forecast, with a high level of precision, a project's final cost and schedule results? What to do if the prime contractor on your cost-plus project "found" $7M in actual cost "missing" from its accounting system? How to determine in advance possible cost overruns? What is a "replan" and how is one prepared? Why a contractor's estimate of final cost would be lower than its actual cost? What are the eleven types of cost and schedule reserves available to a flight project? This 3-day Earned Value Management course will address these questions and many others, while providing a solid foundation in: 1) The latest federal government and NASA EVM policy; 2) Developing a performance measurement baseline; 3) Assessing Earned Value; 4) Understanding the relationship between Planned Value, Earned Value, and Actual Cost; 5) Analyzing data from the Earned Value Management System; 6) Maintaining the accuracy and integrity of the baseline; 7) Forecasting impacts to cost and schedule. Lecture, discussions, class exercises, a case study, and actual EVM experiences from NASA in-house projects and major contracts will make this an interesting class for both technical and business project personnel. Participants should obtain and read "Earned Value Project Management", 3rd edition, by Fleming & Koppelman. Contact Marge Rich at 301-286-7805 for additional information and registration.
|
| ISD001 |
Earned Value (Progress Tracking w/ Earned Value or Point Counting) |
Planned |
TBD |
ISD-EPG |
NASA/GSFC EPG |
This course presents Earned Value strategies and methods for the first time user of the Excel-based workbook tool. For more details see: http://software.gsfc.nasa.gov/training.htm.
|
| ISD002 |
Management Steering Committee Briefing |
TBD |
2 hours |
CSM |
NASA/HQ |
The description for this course is not yet available.
|
| ISD003 |
Mission Software for Project Managers |
Five classes per year |
4 hours |
EPG |
TBD |
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.
|
| ISD004 |
Mission Software Risk Management |
Planned |
TBD |
ISD-EPG, FSB |
TBD |
The description for this course is not yet available.
|
| ISD005 |
Process and Product Quality Assurance |
Planned |
TBD |
TBD |
TBD |
The description for this course is not yet available.
|
| ISD006 |
Project Monitoring & Control |
Two classes per year |
TBD |
TBD |
TBD |
The description for this course is not yet available.
|
| ISD007 |
Project Planning |
Two classes per year |
TBD |
TBD |
TBD |
The description for this course is not yet available.
|
| ISD008 |
Requirements Management Workshop |
TBD |
2 days |
Teraquest |
TBD |
The description for this course is not yet available.
|
| ISD009 |
Software Requirements Development |
Three classes per year |
TBD |
TBD |
TBD |
The description for this course is not yet available.
|
| ISD010 |
Software Requirements Management |
Three classes per year |
TBD |
TBD |
TBD |
The description for this course is not yet available.
|
| ISD011 |
Software Testing Management Workshop |
TBD |
2 days |
Teraquest |
TBD |
The description for this course is not yet available.
|
| ISD012 |
Software Testing Practices Workshop |
TBD |
2 days |
Teraquest |
TBD |
The description for this course is not yet available.
|
| ISD013 |
Systematic Decision Making |
Planned |
TBD |
TBD |
TBD |
The description for this course is not yet available.
|
| ISD014 |
Systematic Software Testing |
Planned |
3 days |
SQE |
TBD |
The description for this course is not yet available.
|
| ISD015 |
Process Overview |
Scheduled |
2 hours |
SPI Project |
NASA/GSFC EPG |
This training provides a high-level overview of the Information Systems Division's (ISD's) software processes. All GSFC Class B software projects should begin to use these processes to move towards compliance with NASA software engineering requirement, NPR 7150.2. These processes are also key to the achievement of Capability Maturity Model Integrated (CMMI) Level 2.
The training will cover the following processes: Project Planning; Project Monitoring & Control; Risk Management; Requirements Management; Configuration Management; Process and Product Quality Assurance; Measurement and Analysis; and Acquisition. Guidelines on how to apply these concepts to projects will be included.
|
| ISD016 |
Mentor Training |
Planned |
TBD |
ISD |
TBD |
The description for this course is not yet available.
|
| ISD017 |
ISD Configuration Management |
Planned |
TBD |
ISD |
TBD |
The description for this course is not yet available.
|
| ISD018 |
ISD Metrics |
Planned |
TBD |
ISD |
TBD |
The description for this course is not yet available.
|
| JPL002 |
Software Project Planning and Control |
One class per year |
2 days |
JPL |
TBD |
Software Project Planning and Control (SPPC)
JPL's Software Quality Improvement (SQI) Project offers a 16-hour course entitled Software Project Planning and Control (SPPC). The purpose of the course is to provide both managers and software engineers with relevant information on understanding various software issues that may affect the success of their projects. The goals of this course are that participants will have an increased understanding of the software issues relative to the planning and control of software projects, and that they will be able to more effectively oversee the software aspects of their projects. Topics covered in the course include:
Software Management Overview
Software Life-Cycles
NASA and JPL Standards
Software Planning and Tracking
Staffing Considerations
Software Acquisition
Software Development Environments
Systems Engineering Considerations
COTS Software and Reuse of Software
Software Cost Estimation Software
Software Requirements Management
Software Testing
Software Quality
Software Configuration Management
|
| JPL003 |
System Software Reliability |
Scheduled |
3 days |
JPL |
TBD |
This three-day course is designed for reliability engineers, systems engineers, quality assurance engineers, software engineers and testers, to provide them with hands-on exposure to software reliability measurement, analyses and design concepts. You will learn the concepts for predicting failure rates or Mean Time To Failure (MTTF) by categories of criticality, methods for determining how much testing will be needed prior to the start of development, as well as how to combine software and hardware measures prior to the start of development or testing. You will also learn how to perform a root cause analysis on software, how to allocate system reliability to software, and the application of fault trees Failure Modes and Effects Analysis (FMEA) to software.
Topics covered include: Definition of software reliability; Myths about software reliability; Factors that impact software reliability; Overview of software reliability models; Software reliability prediction models; Software reliability estimation models; Software fault trees; FMEA; System reliability software redundancy; Improving software reliability, and Managing software reliability.
Upon completion of this course you will be able to: 1) Predict software failure rates, Mean Time to Failure (MTTF), availability, reliability, and fielded defects as early as concept phase of the software product development life cycle; 2) Estimate the reliability growth during software and systems testing by using observed failure data; 3) Determine when it is okay to stop testing; 4) Perform a root cause analysis on software, and 5) Improve software measures using techniques such as software fault trees and Failure Modes and Effects Analysis (FMEA).
|
| QIC001 |
Defining World Class Processes |
TBD |
5 days |
Tim Olson |
NASA/HQ |
The description for this course is not yet available.
|
| QIC002 |
Process Documentation |
TBD |
|
Tim Olson |
NASA/GSFC EPG |
The description for this course is not yet available.
|
| SEI001 |
Defining Software Processes |
TBD |
3 days |
SEI |
TBD |
The description for this course is not yet available.
|
| SEI002 |
Intermediate Concepts of CMMI |
One class per year |
5 days |
SEI |
NASA/HQ |
The Intermediate Concepts of Capability Maturity Model-Integrated (CMMI) course provides participants with a deeper understanding of the CMM®-Integrated Model and its fundamental concepts. The course discussion emphasizes deep understanding of the five maturity levels and the grouping of process areas (PAs) and of the six capability levels and the categories of PAs. The course is based on Version 1.0 of the CMMI SE/SW released in summer of 2000.
This five day-course describes a framework that organizations can use to determine their ability to develop and maintain well-engineered systems; it is a model for organizational improvement. The course is composed of lectures and class exercises with ample opportunity for participant demonstration, questions, and discussions.
|
| SEI004 |
Introduction to the CMMI |
One class per year |
3 days |
CSMSoft |
APPEL |
This three-day course introduces systems and software engineering managers and practitioners, appraisal team members, and engineering process group (e.g., SEPG, EPG) members to Capability Maturity Model® Integration (CMMI®) fundamental concepts. CMMI models are tools that help organizations improve their ability to develop and maintain quality products and services. CMMI models are an integration of best practices from proven process improvement models, including the CMM® for Software, EIA 731, and the Integrated Product Development CMM. This course focuses on the CMMI models with a continuous representation.
The course is composed of lectures and class exercises with ample opportunity for participant questions and discussions. After attending the course, participants will be able to understand how CMMI models can apply to their organization's process improvement program. The course covers CMMI process area categories and their characteristic process areas.
Successful completion of this course is a prerequisite for Intermediate Concepts of CMMI, SCAMPI Lead Appraiser Training, and CMMI Instructor Training. Successful completion of the course requires active participation and attendance throughout the full three days.
|
| SEI005 |
Managing Technological Change |
Scheduled |
3.5 days |
SEI |
NASA/HQ |
This course provides participants with skills and knowledge that will help them introduce new technology or continuous improvement initiatives smoothly and effectively. During this course, participants learn a structured approach for dealing with the organizational and human aspects of technology transition, including the key concepts of change management, communication, and managing resistance.
This course consists of a set of carefully focused lectures, integrated with hands-on exercises that allow participants to apply the lecture content.
|
| SEI006 |
Mastering Process Improvement |
TBD |
5 days |
SEI |
NASA/HQ |
Mastering Process Improvement presents a structured compendium of best practices in CMM-based process improvement. This five-day course addresses the intertwined challenges facing change agents. These challenges include both technical issues (e.g., process and metrics) and social issues (e.g., resistance, buy-in, and institutionalization). The course presents an approach to CMM-based process improvement called the Process Change Methodology (PCM). The PCM focuses on process improvement activities that occur following a CMM-Based Appraisal. There is a special emphasis on how new SEPGs can work towards achieving Maturity Level 2 while positioning the organization for the future challenges of Maturity Level 3.
Attendees will receive lectures on each of the eight stages of the PCM with focus on techniques and skills that are enablers for success. Each module includes an exercise where individuals and/or small groups of students will work with PCM tools and instruments to address process improvement scenarios and practice new skills. Course modules will conclude with a debriefing of the exercise with presentations and a discussion of the primary issues.
The concepts, techniques, experiences, and examples described in the course are drawn from numerous client partnerships between the Software Engineering Institute (SEI) and organizations in government and industry.
|
| SEI007 |
Standard CMMI Appraisal Method for Process Improvement (SCAMPI) Lead Appraiser Training |
TBD |
5 days |
CSM |
NASA/HQ |
The description for this course is not yet available.
|
| SEI008 |
Consulting Skills Workshop |
Scheduled |
5 days |
SEI |
TBD |
The Consulting Skills Workshop provides managers responsible for organizational change with a practical, six-phase model for working effectively with client groups - those who implement and are affected by the change. Particular attention is paid to managing expectations among change agents, managers, executives, and other members of the organization.
This workshop teaches participants to act as internal consultants to their own organizations, working to involve clients in all phases of problem identification and solution. At the end of a consulting assignment, clients are able to sustain the changes in their organization.
Participants learn techniques and methods to use every day, such as forming collaborative working relationships, negotiating roles and expectations with clients, collecting and using data effectively throughout the consultation process, and handling difficult situations that occur when circumstances change in the organization.
Role plays, discussion of current situations faced by participants, and an extended case study provide opportunities to practice newly learned skills.
|
| SEI009 |
Software Architecture: Principles and Practices |
Scheduled |
2 days |
SEI |
NASA/HQ |
This course introduces the basic concepts of software architecture. A software architecture is an abstract view of a software system distinct from the details of implementation, algorithms, and data representation. Architecture is an increasingly crucial part of a software organization's business strategy. Software architectures can: a) provide flexibility and adaptability in changing markets; b) allow for interoperability with other players in the marketplace; c) provide leverage in a marketplace;
d) help developers focus on a niche in the marketplace;
e) be used as a sales and marketing tool; f) help reduce maintenance costs and amortize development costs; g) help in workforce organization and for project oversight and control; h) establish a common corporate vocabulary; i) shorten learning time.
This two-day course emphasizes the importance of the business (or mission) context in which systems are designed and introduces participants to software architectures in a real-world setting. "Industrial-strength" case studies illuminate the key technical and organizational issues regarding software architectures. This course is based on the book Software Architecture in Practice, 2nd Edition.
|
| SEI010 |
Implementing Goal-Driven Software Measurement |
Scheduled |
3 days |
SEI |
NASA/HQ |
This three-day course describes a method for identifying and defining indicators (graphical displays) and measures that directly support an organization?s business goals related to product development, process improvement, and project management. Using lectures and exercises, participants learn how to determine success, progress, and analysis indicators that show traceability from an organization?s high-level business goals right down to the precise data collected. With useful examples, real-life experiences from the field, and a class notebook filled with helpful checklists, templates, and reference materials?participants walk away with the tools necessary to lead goal-driven software measurement processes at their own organizations. Relevant ties to the Measurement and Analysis process area of Capability Maturity Model® Integration (CMMI®) are also explored. This PowerPoint slide provides a graphical overview of the course.
|
| SEI012 |
Software Acquisition Survival Skills |
Scheduled |
3 days |
SEI |
NASA/HQ OCE |
This three-day course is designed for program managers and their staff members. It presents an integrated, unique acquisition perspective on key topics in software system acquisition, including risk management, requirements management, pre-award activities, systems engineering, software architecture, technical evaluation, project metrics, and process management. The course provides a broad overview of the skills needed in a program office to manage software acquisition, enabling program managers to recognize the needs of their programs in relation to the skills of their staff. More in-depth knowledge of many of these topics can be obtained through related SEI course offerings.
During the course, participants are presented with common problems that affect real acquisition programs. The course explores the nature and the impact of each problem, along with ways to recognize the symptoms, avoidance methods, and recovery techniques. Composed of lectures and class exercises, this course allows ample opportunity for questions and discussions and provides actionable tips and a set of tools and reference resources to help in the management of current and future projects.
Before enrolling in this course, participants should have some knowledge of DoD or federal acquisition processes and practices, basic project management skills, and the fundamentals of software acquisition. The course helps participants to: 1) understand some of the major problems encountered when acquiring software-intensive systems; 2) identify the symptoms of these problems; 3) recognize the potential impact of these problems; 4) use proven techniques to avoid these problems before they become critical, and 5) exercise "recovery methods" when these problems challenge the project. Contact Sanjeev Sharma at GSFC X67792 for further information and registration.
|
| SEI013 |
CMMI v1.2 and Beyond |
Class(es) for current year have been held |
2 hours |
Mike Phillips, SEI |
NASA/HQ |
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.
|
| SEI014 |
CMMI v1.2 Upgrade Training |
Scheduled |
7 hours |
SEI |
NASA/GSFC EPG |
To be supplied
|
| SMA-SOFT-NSC-1005 |
Software Safety for Practitioners |
Scheduled |
1 week (30 hrs.) |
Martha Wetherholt and Janie Hill |
NASA/HQ |
This is an intermediate, practical, hands-on course tailored towards the direct needs of NASA based on the NASA Software Safety Standard NASA-STD-8719.13B and Guidebook, NASA-GB-8719.13. Experience in software engineering or completion of an introductory software engineering course is a pre-requisite for this course. This course is taught in a team-oriented manner that integrates instructor-led practice exercises and a main team exercise with the lectures to emphasize key aspects. This allows the students to practice the concepts in a learning environment. If desired, the Center can identify specific projects for use during the exercises to help provide a real-world setting. At the end of each day, feedback will be gathered from the students in order to tailor adjustments to the specific class.
Topics covered are: 1) Software Safety Planning; 2) Safety Analyses and Activities During the Software Development Lifecycle (including preliminary hazard analysis, fault trees, failure modes and effects analysis, litmus test, safety-critical software, and tailoring); 3) Safety of OTS, COTS, GOTS, Heritage, Legacy and Reuse; 4) Safety Traceability; 5) Requirements and Design for Safety; 6) Safety Certification 7) Safety Reviews (including safety panels, safety boards, and Safety Panel conduct); 8) Hazard Analyses and Reports: 9) Safety Verification & Validation and Tracking Safety Problems, Discrepancies, and Failures; 10) A final exercise to pull all of the above together.
|
| SQE001 |
Mastering the Requirements Process |
TBD |
3 days |
SQE |
TBD |
The description for this course is not yet available.
|
| SRE 101 |
Introduction to Software Reliability Engineering |
Scheduled |
1 day |
JPL |
NASA/HQ |
This course is an introduction that teaches you the basic concepts and activities of software reliability engineering. The overall purpose of this course is to provide practical suggestions instead of theoretical discussions on software reliability. The target audiences of this course are software assurance managers and software, system and hardware engineers at NASA. The course covers the basic SW Reliability concepts of design, and analytical techniques and methods used to assess and improve the reliability of software systems. Major themes are as follows. 1) Design software to be fault tolerant, i.e., make a software system tolerant of faults that manifest themselves during operation. This emphasizes building into software the means to detect, isolate and recover from or minimize the effects of failures. 2) Use analytical techniques that help prevent, detect, and gauge software system faults and vulnerabilities, thus leading to software designs with improved reliability. 3) Assess software reliability by the application of qualitative and, when possible, quantitative statistical methods. The goal is to base assessments and decisions on a foundation of experimentation, observation and empirical evidence throughout the lifecycle. The course is comprised of six lessons: Introduction and definitions; examples of software problems that have caused failures; designing reliable software; analytical techniques for software reliability; quantitative assessment of software reliability; and examples of how fault tolerance is used in reliable computing.
|
| SS-219722_ENG |
Programming Techniques and Strategies |
Online via SATERN |
2.08 hours |
via SATERN |
NASA/HQ |
The goal of this course is to outline the high-level considerations for producing good code. It is recommended for application developers or programmers with at least 2 years experience, who want to learn the latest recommended techniques for developing high quality software.
|
| SS-219736_ENG |
General Coding Best Practices |
Online via SATERN |
3.58 hours |
via SATERN |
NASA/HQ |
Purpose: To outline the best practices for writing high quality methods, expressions, variables, arrays, loops, and if statements, and to describe recommended practices for writing readable code; Audience: Professional application developers or programmers, with at least 2 years experience, who want to learn the latest recommended techniques for developing high quality software
|
| SS-PROJ0354 |
Managing the Execution and Control of IT Projects |
Online via SATERN |
5.5 hours |
via SATERN |
NASA/HQ |
Did you know that the average IT project has cost overruns of nearly 200 percent, and that almost 30 percent of all IT projects fail? Why do you think IT projects are so vulnerable to cost overruns and failure? How can you ensure that your project does not end up as one of these statistics? You can avoid being a statistic by managing project scope, cost, and scheduling. As you go through this course, you will learn valuable strategies for managing your project. You will learn about tools to manage scope, time, and cost that will aid in the successful control and execution of your project. This course is specifically targeted at project managers and IT professionals preparing to take on IT project management responsibilities. Managers who support IT project managers, top management, and high-level executives will also benefit from this course.
|
| SS-PROJ0532 |
Controlling Project Scope |
Online via SATERN |
2 hours |
via SATERN |
NASA/HQ |
Projects can quickly get out of control if the appropriate actions aren't taken initially. Scope management plays a key role by helping to define and maintain the boundaries of the project throughout the project life cycle. This course will highlight the importance of project scope management to project performance. Through interactive learning strategies and real-life scenarios, the learner will explore these concepts and gain a better understanding of the project management processes of the Scope Management knowledge area. This course will cover the project inputs, tools and techniques, and outputs of the scope management processes that deal with creating work breakdown structures, accepting the completed project scope, and controlling changes to the scope of the project. This course is aligned with "A Guide to the Project Management Body of Knowledge" (PMBOK® Guide) - Third Edition, published by the Project Management Institute (PMI®), Inc., 2004. Copyright and all rights reserved. Material from this publication has been reproduced with the permission of PMI®.
|
| SS-PROJ0601 |
Planning Project Procurement and Requesting Seller Responses |
Online via SATERN |
2.5 hours |
via SATERN |
NASA/HQ |
If project success is to be achieved, products, services, or results often must be purchased or acquired from elsewhere within, or outside of, the organization. This process of acquisition and purchasing is Project Procurement Management, and it is a critical aspect of any project. As you advance in this course, you will gain an understanding of what processes are involved in Project Procurement Management, and how these processes interact with the overall project life cycle. You will also obtain the skills and knowledge required to enable you to: plan purchases and acquisitions, document contractual requirements, identify potential sellers, and get the relevant information, quotations, and proposals from potential sellers--all vital processes that ensure that you are able to procure the products, services, or results that will enable you to achieve project success. This course is aligned with "A Guide to the Project Management Body of Knowledge" (PMBOK® Guide) - Third Edition, published by the Project Management Institute (PMI®), Inc., 2004. Copyright and all rights reserved. Material from this publication has been reproduced with the permission of PMI®.
|
| SWE301 |
Software Engineering Management 301 |
Scheduled |
5.5 days |
CSC |
APPEL |
The Software Engineering Management course is designed for novice- and intermediate-level software project managers and others who want to improve their understanding of project management activities. This intensive 5½ -day course includes classroom lectures and group workshops that allow the application of skills learned. Some workshops include evening work. Learning will be accomplished through lecture, class discussion, and participation in group workshops that use role play. Participants will be divided into four project teams that will plan a project and respond to changes that occur over various phases of the project life cycle. Each participant will serve as project manager for the team in at least one of the workshops. All team members will practice management skills during each workshop and interact with senior management and customer representatives. Participants should be familiar with creating a WBS, activity scheduling, staffing profiles, and project monitoring. Upon completion of this course, participants will be able to plan a software project; apply progress monitoring and controlling techniques, including the concepts of earned value; find NASA polices, standards, and directives; understand the requirements documented in NPR 7150.2; develop a software Build Plan; manage stakeholder relationships; apply negotiation techniques, and respond effectively to customer changes throughout the software development life cycle. For further information, contact Sally Godfrey at (301) 286-5706 or Sara.H.Godfrey@nasa.gov.
|
| SWG001 |
Software Engineering Technology ViTS |
Scheduled |
4 hours |
TBD |
TBD |
Introduction to preview opportunities through which software engineering practitioners and researchers may collaborate in an effort to demonstrate the benefit of using new technologies on development projects. Discover low-risk opportunities for your software development team to benefit from recent, applied software engineering research technologies in areas such as: requirements analysis, usability analysis, cost estimation and budget risk assessment, state-of-the-art code inspection, technical risk assessment, automated code analysis, advanced testing techniques. Find out what new software engineering technologies are available right now to help your project reduce risk, produce higher quality code, and still meet tough deadlines. The Research Infusion strategy of the NASA Software Engineering Initiative out of the Office of the Chief Engineer has a limited number of opportunities for pilot collaborations between software engineering practititioners and software engineering researchers -- and the emphasis is on demonstrating benefit to your development project. Collaborations can be structured to meet your project's requirements, some may be externally funded to cover technology transfer costs, including training, installation, and support for your team by the technology developers. Intended audience is anyone with responsibility and authority to collaborate on infusing software engineering tools and technology into a new or existing software development/ maintenance activity, or who can influence the decision makers, for example: Team leads, software project managers, program managers; SEPG and SWG representatives; mission planning team members, SQA personnel, software developers: mission assurance managers.
|
| SWG002 |
Software Metrics Selection |
TBD |
4 hours |
Carolyn Seaman |
NASA/HQ OCE |
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.
|
| SWG003 |
Managing Projects with Metrics |
Class(es) for current year have been held |
6 hours |
Fraunhofer Center |
NASA/HQ |
The purpose of this course is to enable NASA software project managers, team leads, and support personnel to apply software metrics to increase the efficiency and effectiveness of their projects and produce higher quality software. Covered topics include the NASA infrastructure and environment for software measurement, metrics selection, metrics planning, data collection and analysis, data interpretation and decision making, and lots of examples. Upon completion of this course, you will be able to:
1) Select software metrics related to project schedule and budget, software quality, requirements volatility, software functionality, and project characteristics, that are appropriate for a particular software project and that contribute to reporting requirements.
2) Develop a measurement plan for a software project.
3) Collect and analyze software metrics data.
4) Interpret software metrics data to make management decisions.
|
| SWG004 |
Formal Inspections: A Perspective-Based Approach |
Scheduled |
1.5 days |
Forrest Shull, Fraunhofer Center |
NASA/HQ |
Software inspection is a well-defined review process for finding and fixing defects in work products from all phases of software development.
Inspections have proven time and again to be one of the most effective practices available for ensuring quality software and on-time deliveries. Many studies have demonstrated their benefits, both within NASA and across many industrial organizations. Studies have shown that the rework effort saved not only pays for the effort spent on inspections, but also provides additional cost savings on the project. By removing defects at their origin, inspections prevent them from propagating through multiple phases and work products, and reduce the overall amount of rework necessary on projects. Side-effects of inspection meetings include improving team communication, more quickly bringing new members up to speed, and educating project members about effective development practices.
This training course provides all the information needed for conducting software inspections on a project. The course describes the process, roles, and responsibilities involved and provides experience-based guidance on all activities, including planning and scheduling the inspections, preparing for and moderating the meetings, and closing the identified defects in a timely manner.
The training includes a 1-day lecture, followed by a half-day hands-on workshop where the process is applied to a work product from the participants' current project. The participants leave with a list of real defects identified and clear guidance on how to proceed.
|
| SWG005 |
Learning Near-Optimum Inspection Policies |
Class(es) for current year have been held |
1 hour |
Dr. Tim Menzies |
NASA/GSFC EPG |
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.
|
