bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Error rendering macro 'alias'

null

SWE-100 - Software Training Funding

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. [SWE-100]

1.1 Notes

NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.

1.2 Applicability Across Classes

Class

  A_SC 

A_NSC

  B_SC 

B_NSC

  C_SC 

C_NSC

  D_SC 

D_NSC

  E_SC 

E_NSC

     F      

     G      

     H      

Applicable?

   

   

   

   

   

   

   

   

   

   

   

   

   

Key:    A_SC = Class A Software, Safety Critical | A_NSC = Class A Software, Not Safety Critical | ... | - Applicable | - Not Applicable
X - Applicable with details, read above for more | P(C) - P(Center), follow center requirements or procedures

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, the development activities also require knowledge of NASA's acquisition practices and regulations. The

<ac:macro ac:name="unmigrated-wiki-markup">
<ac:plain-text-body><![CDATA[

OCE

]]></ac:plain-text-body>
</ac:macro>

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.

3. Guidance

Software engineering 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. 

<ac:macro ac:name="unmigrated-wiki-markup">
<ac:plain-text-body><![CDATA[

OCE

]]></ac:plain-text-body>
</ac:macro>

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

<ac:macro ac:name="unmigrated-wiki-markup">
<ac:plain-text-body><![CDATA[

DACUM

]]></ac:plain-text-body>
</ac:macro>

curriculum set by the OCE 289 265 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. 289

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 and subsystems.

OCE conducts an annual call with

<ac:macro ac:name="unmigrated-wiki-markup">
<ac:plain-text-body><![CDATA[

SWG

]]></ac:plain-text-body>
</ac:macro>

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

Project and Software Training

SWE-101

Center SW Training Plans

SWE-107

SW Training Plan Contents


4. Small Projects

Projects are not responsible for this requirement.

5. Resources

5.1 Tools

Tools to aid in compliance with this SWE, if any, may be found in the Tools Library in the NASA Engineering Network (NEN).

NASA users find this in the Tools Library in the Software Processes Across NASA (SPAN) site of the Software Engineering Community in NEN.

The list is informational only and does not represent an “approved tool list”, nor does it represent an endorsement of any particular tool. The purpose is to provide examples of tools being used across the Agency and to help projects and centers decide what tools to consider.


6. Lessons Learned

No Lessons Learned have currently been identified for this requirement.

  • No labels