This initiative encourages the uptake of new research results within real NASA missions. A key success feature is realized when a NASA Center adds the research product resulting from an initiative to its list of recommended practices. Table 1, NASA Research Infusion Initiative Completed Projects, shows a list of early initiative results.

                                                                                          Table 1.  NASA Research Infusion Initiative Completed Projects

Also in 2004, the Office of the Chief Engineer (OCE) conducted the first annual software inventory and issued the initial version of NPR 7150.2. The Office of Safety and Mission Assurance (OSMA) completed the updates to NASA-STD-8719.13, Software Safety Standard,

 and NASA-STD-8739.8, Software Assurance Standard.

Figure 2 highlights software training with callouts for the design of the software curriculum

DACUM (Developing a Curriculum) and the first offering of the software engineering management class (SWE 301)

a SCAMPI (Standard CMMI Appraisal Method for Process Improvement) Class "A" evaluation.

                                                                                  Table 2.  Completed SW Engineering Appraisals from FY07 - FY10

Currently, the "CMMI for Development, Version 1.3"

 is the approved version for process improvement and rating activities.

During the development of the NPR 7150.2, there was an intentional effort to minimize the size of the document by keeping it focused on the requirements. However, the 7150 team had developed a large amount of additional guidance material for the NPR, which they decided could be more effectively utilized in a NASA Handbook rather than in the NPR itself. Therefore, after the OCE released NPR 7150.2A,

 the effort to develop this electronic Handbook in wiki format was initiated.

Numerous other components and related tasks have been developed and executed under OCE sponsorship. Some of these include the development of a software engineering curriculum (see the discussion on the DACUM below), the development and tracking of the Top Ten Software Issues list, the inventory of the software development activities (see the Software Inventory Management System (SIMS) tool discussion below), and the implementation of the OCE surveys. Others include:

• NASA Study on Flight Software Complexity.

  sweref
  040 040

• NASA Assurance Process for Complex Electronics.

  sweref
  255 255

• Development of the Software Community of Practice.
• Development of the Software Electronic Handbook.
• Center Processes for NPR7150.2 implementation.

 in 2002. In coordination with Center software engineering improvement activities, the OCE defined a NASA-wide comprehensive approach for improving software engineering to quantifiable maturity levels commensurate with mission criticality to meet the software challenges of NASA.

The following key principles guide NASA's software improvement activities:

• Software engineering is a core capability and a key enabling technology for NASA's missions and supporting infrastructure.

• NPR 7150.2

  sweref
  039 039

•  supports the implementation of NPD 7120.4, NASA Engineering and Program/Project Management Policy.

  sweref
  057 057

• NPR 7150.2 provides a minimal set of requirements established by the Agency for software acquisition, development, maintenance, retirement, operations, and management.

• NPR 7150.2 is intended to help NASA programs and projects accomplish their planned goals, e.g., mission success, safety, schedule, and budget, while satisfying their specified requirements.

2.1 NSEI Scope

This initiative covers software process improvement, as well as items related to software research: software safety, reliability, and quality; attraction and retention of software engineers, and improvement of NASA's software engineering knowledge and skills. It applies to both mission-critical and non-mission-critical software.

• What is NSEI?
  • A NASA-wide comprehensive approach for improving software engineering processes and technology.

• Why are we doing NSEI?
  • To meet the challenges facing NASA in software engineering (schedule, cost, project commitments, ensuring the use of best practices...).

• Who is deploying NSEI?
  • OCE, in collaboration with each Center.
  • NASA Software Working Group (NSWG).
  • Center Management Steering Groups (MSGs) and Software Engineering Process Groups (SEPGs).

• What are the elements of the OCE's approach?
  • Component plans from each Center.
  • The use of the Software Engineering Institute's Capability Maturity Model Integration as a benchmark for assessments.
  • Increasing the availability of software engineering tools.
  • Software metrics.
  • The integration of sound software engineering principles and standards.
  • The enhancement of software engineers' knowledge and skills through training based on an agreed-upon curriculum.
  • Development of a Software Engineering Electronic Handbook.
  • Benchmarking of industry, government agencies, and academic institutions to learn about and share best practices.
  • Consolidation of Agency processes and practices.
  • Benchmarking and consolidation of best practices associated with cost estimation.
  • Small project implementation of requirements.

2.2 NSEI Elements

The NASA Software Engineering Initiative Implementation Plan (NSEIIP)

 requires NASA to:

• Implement a continuous software process and product improvement program across NASA and its contract community.
• Improve safety, reliability, and quality of software through the establishment and integration of sound software engineering principles and standards.
• Improve NASA's software engineering practices through research.
• Improve software engineers' knowledge and skills and attract and retain software engineers.

The baseline NSEIIP was approved in 2002 (see SWE-002). As part of the NSEIIP, each Center developed its own improvement plan for advancing the in-house software engineering capability (see SWE-003).

Center plans: The OCE allowed the individual Centers some latitude in implementing the NSEI to take into account the mission of their Center's activities. While the implementation varies across research and flight Centers, certain basic features can be found to be common to all Centers.

To address the key NSEI components, each Center uses one or more of the following to meet its objectives for the initiative:

• Center SEPG -This group is the primary organization responsible for developing software development process improvements and in creating, measuring, and interpreting software metrics.
• MSGs -These groups provide the basic guidance for software engineering practices and applications at the Centers.
• Software Policy – The key governing document

  sweref
  257 257

•  provides NASA policy for software.
• Training, CMMI appraisals, and career development.
• Software technology infusion.
• Engineering, assurance, and safety collaboration.

Process assessment: NASA chose to appraise its software engineering improvement activities against a common industry process framework. Initially, it selected the Software Engineering Institute's (Carnegie Mellon University) process model, the CMM. This was succeeded by the CMMI for Development, Version 1.3.

Tools: A key part of the NSEIIP to increase software developer skills and knowledge is the development of a set of tools useable in software development. Center and Agency repositories catalogue many of the tools used around the Agency. In addition, several tools have been developed to assist in achieving the above implementation elements:

• NASA Software Process Asset Library (PAL)

  sweref
  066 066

   (see SWE-098)
• NASA Software Inventory Management System (SIMS)

  sweref
  330 330

  web-based tool (sponsored by the OCE) (see SWE-006).
• Classification Tool and Safety-Critical Assessment Tool (see Topic 7.2 - Classification

• and Safety-Critical Assessment

• ).
• NASA Engineering Network

  sweref
  258 258

   (NEN), a repository for resources, tools, useful documentation.

The PAL provides for viewing of the Agency-level process assets. This library may contain information in many forms, including but not limited to processes, templates, web links, design principles, books, periodicals, presentations, tools, examples of documents, and conference descriptions.

NASA utilizes the SIMS tool to develop and maintain an inventory of software (see SWE-006 ) across the Agency for the purpose of facilitating strategic decisions with actual data. The analysis of the inventory results also directly supports NASA's Chief OSMA Officer and the IV&V Board of Advisors (IBA) in the selection of projects to receive IV&V services. (See SWE-131.)

Each SWE entry in this Handbook may include references to tools that have specific or related applicability to the SWE statement. The Resources section within each SWE description includes information as shown in the example panel below. The Handbook format allows users to suggest additional tools, as indicated in the second paragraph in the example panel. (Editor's note: the Tools sub-section in the Resources section normally is numbered as '5.1', which is shown in the panel.)

Metrics: Some basic measures are developed to assess the level and degree of improvement in software process activities across the Agency. Several activities and sources of measurement to form these metrics are used. The OCE conducts its assessments of Center progress by synthesizing and analyzing the information it gains through the conduct of Center surveys. (See the OCE Software Survey Instructions and Templates

 for details on the content, frequency, and content required for these events.) The OCE also authorizes appraisals against selected requirements of NPR 7150.2 (see SWE-129 ). In addition, the results of the CMMI Maturity Level 2 and Maturity Level 3 appraisals are collected and reported in a non-attributed manner to indicate, from both a Center and an Agency perspective, the process areas that are well-developed and those that need further training and development assistance.

The PAL also includes support materials for projects to set up software measurement collection, as well as templates to analyze metrics to determine accurately the status of software development.

Process integration: As the

NASA Software Engineering Initiative Implementation (NSEII) achieves results, it is important to collect and document these software process improvements. The integration of these achievements allows for the distribution of the best-in-class processes around the Agency. This Agency-wide distribution encourages the development of uniform process efforts, which, in turn, helps the efficiency of software development activities across NASA's programs and projects. One means of achieving this integration and dissemination is by using annual workshops. NASA-sponsored events such as the NASA Project Management

 from the OCE and the NASA Workshop on Validation and Verification

 from the NASA IV&V Facility serve this purpose. The NASA PM Challenge is an annual seminar designed to examine current program/project management trends, as well as to provide a forum for knowledge sharing and the exchange of lessons learned. The IV&V Workshop offers an understanding of the challenges that IV&V organizations face in assuring that systems software operates safely and reliably.

The use of the Agency PAL (see SWE-098) is another mechanism being employed for the distribution of the best-in-class processes around the Agency. This repository allows the efficient collection and storage of useful and best-in-class documents that are easily available through the NEN. The Headquarters, Center, and Facility representatives to the NSWG currently manage population of the PAL.

Training: One additional step in

the NSEII approach is the development of better informed software engineers through improved and readily accessible training opportunities. The NSEII recognizes that both the software discipline and other discipline abilities are necessary for the development of quality software (see SWE-017). Headquarters and Center training organizations provide the appropriate and prioritized training events (see SWE-101 and SWE-107). The OCE and the NSWG have sponsored the development of a NASA Software

Engineering DACUM  to assure an Agency perspective for its software training needs. OSMA and the NASA Safety Center have developed the SMA Technical Excellence Program (STEP)

 program, which includes extensive complementary training in software assurance. The DACUM

 on the NEN captures a curriculum has been developed for software engineering. The curriculum is contained in the Software Engineering Technical Excellence Training (SWEET) program. The program will provide courses that a software engineer can take to both learn and enhance knowledge in software engineering throughout a career. The NASA Academy of Program/Project & Engineering Leadership (APPEL) Training Master Schedule and Registration

 web site lists many of the more general training opportunities. The System for Administration, Training, and Educational Resources (SATERN) on-line training system provides employee, group, and individual learning opportunities for Center training initiatives.