Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
{tabsetup:1. The Requirement|2. Rationale|3. Guidance|4. Small Projects|5. Resources|6. Lessons Learned}


h1. 1. Requirements The Center Software Training Plan shall include: 
      a. Responsibilities.
      b. Implementation.
      c. Records and forms. 
      d. Training resources.
      e. Minimum training requirements for software personnel.
      f. Training class availabilities.

h2. {color:#003366}{*}1.1 Notes{*}{color}

It is anticipated that there will be one Software Training plan per Center.

{note} EHB Editor note: SWE-101 requires that this plan be maintained, which means updated and reissued as appropriate. {note}

h2. 1.2 Applicability Across Classes

Class E and Not Safety Critical and Class H are labeled with "P (Center)".  P (Center) means that an approved center-defined process which meets a non-empty subset of the full requirement can be used to achieve this requirement.



h1. 2. Rationale

The requirement lists the minimum content needed for each Center training plan. The plan needs to communicate the roles and responsibilities to the appropriate personnel to assure needed training content is acquired and delivered in a timely manner. The collection in one place of available resources, class availabilities, and minimum training requirements makes the communication of this information more efficient. These elements of the plan will assure its usefulness to all who use it, not just the author.  Specifying content items also assures a degree of common software knowledge across Centers. 


h1. 3. Guidance

Each Center typically plans for its training on an annual cycle. Training plan input requests often occur during and as a part of the annual budget cycle. The Center produces a plan that integrates software training needs for organizations and individual career development. On rare occasions, additional plans or plan supplements may be developed to address unique or new needs.  

Software training planning often is performed as part of the overall Center training plan development cycle. Center 'calls" may be used by Center Training Offices, Agency Offices, engineering organizations, and the Center's Software Engineering Process Group (SEPG) to elicit and develop specific plans for software training for in-house work and to assist in software acquisition activities. Typically such 'calls' result in requests for training and resources that exceed the available funding that will be dedicated to software training activities. The SEPG and the Center engineering organization will collaborate to determine the priority and selection of training activities. These selections are based on known and anticipated software development activities needs, known shortfalls in resident expertise, and on projections of future losses in expertise (e.g., retirements or reassignments).

Once the inputs have been obtained and analyzed, the Center respond to the "calls" and capture approved training in an organized manner according to the following six topical sections.  This arrangement will enable comparisons to previous and future plans.  It will also enable the OCE to compare and make selections from among all the Centers to assure the Agency perspectives on training needs are included in funding distribution decisions.

The [NASA Engineering Network website|] includes an [abbreviated template|
] for a Center Software Training Plan within the [NASA Software Process Asset Library (PAL)|]. The cover page asks for a signature by the Center Director or designee.
The Center training plan document should include the following sections:

* Responsibilities—This sections lists what each Center, organization, or committee/working group needs to accomplish to develop, maintain, and implement the training activities. 

* Implementation—This section presents the strategy and organization for acquiring the appropriate training needs, for scheduling classes, and soliciting and approving participants.  Course materials and course presenters may be discussed in specific or general terms. 

* Records and forms—This section describes the manner in which course material will be presented and preserved. It covers selection documentation and attendance documentation (e.g., sign-in sheets). It also covers forms for course and presenter surveys and evaluations. 

* Training resources—This section describes training venues, classroom support resource requirements, handouts. It includes supplies, courses, Learning Center opportunities, university programs, and availability of on the job training. It may also provide expected funding resource information if available.

* Minimum training requirements for software personnel—This section describes minimum levels of training needed for specific roles or positions. It may reflect differences among levels for beginner, journeyman, and senior level positions.  Center tasks and projects will be the primary determinant of these requirements (see [SWE-032|SWE-022]). Consideration for unique project or customer needs may be a part of the overall determination of minimum levels. The HQ Office of Chief Engineer maintains a Software Engineering Excellence Training (SWEET) curriculum and the HQ Office of Safety and Mission Assurance maintains a [SMA Technical Excellence Program|] (STEP) containing software courses. These can be helpful in setting minimum Center training requirements for software personnel.

* Training class availabilities—This refers to schedules posted on the web sites ^4, 5, 6^, training curricula releases, restricted enrollment levels, email announcements, and information on availabilities at other Centers.

Additional guidance related to software training may be found in the following related requirements in this handbook:

|[SWE-017]|Project and Software Training|
|[SWE-100]|Software Training Funding|
|[SWE-101]|Center SW Training Plans|


h1. 4. Small Projects

The responsibility for this requirement resides with the Center and therefore does not apply at the project level.


h1. 5. Resources

# [NASA Systems Engineering Processes and Requirements with Change 1|], NPR 7123.1A, 2009
# [NASA Space Flight Program and Project Management Requirements|], NPR 7120.5D (NM-7120.81), 2009.
# ["CMMI for Development, Version 1.3"|], CMU/SEI-2010-TR-033, Software Engineering Institute, 2010
# [OCE Software Engineering Training and DACUM|]
# [NASA APPEL Training Master Schedule and Registration|]
# [System for Administration, Training, and Educational Resources for NASA (SATERN)|]
# OSMA/NSC's [SMA Technical Excellence Program|] (STEP) program



h2. 6. Lessons Learned
*Lack of Education and Training in the Use and Processes of Independent Verification & Validation (IV&V) for Software Within NASA. Lesson number 1173:*  While NASA has made major changes to emphasize the need to utilize IV&V on safety critical projects, the technology is not well understood by program managers and other relevant NASA personnel. 1-2-2001 []