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

4.6.1 The NASA Headquarters' Office of the Chief Engineer and Center training organizations shall provide and fund training to advance software engineering practices and software acquisition.

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

NPR 7150.2 does not include any notes for this requirement.

h2. 1.2 Applicability Across Classes

Appendix D of NPR 7150.2 does not include any notes for this requirement.


h1. 2. Rationale

NASA software development activities in support of projects often require a balanced blend of software engineering development expertise and knowledge. If software is contracted out, they also require knowledge of NASA's acquisition practices and regulations. The {term:OCE} and the Centers have committed to support these objectives by providing sufficient funding in support of the training.   In some instances, funding for training may be provided by multiple organizations if the training is beneficial to the communities they represent.

h1. 3. Guidance

Software engineer skills and expertise can be acquired through formal courses, on the job training, and specialized work assignments. While some of these skill enhancements come about while executing the project's activities (i.e., funded by the project), many need formal course work to achieve improvements in software engineering capability. 

{term:OCE} and Center funding provides an opportunity to build a foundation that supports software improvement activities as well as core courses across a software engineer's career. 

These courses typically are formally developed, and are usually found and maintained as part of the {term:DACUM} curriculum set by the OCE{^}4,5^ and Center training organizations.  The OCE partners in funding these courses with Centers to assure balanced offerings and availability around the Agency. The OCE funding supports training for courses associated with 1) CMMI appraisals that support the OCE Software Engineering Improvement Initiative, as well as 2) core software courses across a software engineer's career ( [|] ) . 

Software engineers use project training funds to develop specific skills and expertise in programming languages, design tools, operating systems, coding standards, etc.  Project funded training differs from OCE and Center-funded training in that it is generally focused on skills needed to produce software specific for its systems & subsystems.

OCE conducts an annual call with {term:SWG} representatives to plan the following year's needs and course offerings.

Additional guidance related to software training may be found in the following related requirements in this handbook:
| [SWE-017|SWE-017] | Project & Software Training |
| [SWE-101|SWE-101] | Center Software Training Plans |
| [SWE-107|SWE-107] | SW Training Plan Content |

h1. 4. Small Projects

Projects are not responsible for this requirement.

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  |] 
# [NASA APPEL Training Master Schedule and Registration|]
# [System for Administration, Training, and Educational Resources for NASA (SATERN)|]  \\


h2. 6. Lessons Learned

No Lessons Learned have currently been identified for this requirement.