bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Versions Compared

Old Version 28

changes.mady.by.user System admin

Saved on

compared with

New Version 40

changes.mady.by.user Haigh, Fred Douglas. (HQ-KA000)[PEROT]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin


Alias
aliasSWE-100
Software Working Group (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:


Tabsetup
1. The Requirement
1. The Requirement
12. Rationale
23. Guidance
34. Small Projects
45. Resources
56. Lessons Learned


Div
idtabs-1

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


applicable
f1
g1
h1
ascansc1
anscasc1
bnsc1
csc1
bsc1
esc1
cnsc1
dscdnsc1
dnscdsc1
ensc1


Office of the Chief Engineer (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.
 Div
idtabs-2
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 
 Term
OCEOCE

 and 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 
 curriculum the DACUM (Developing a Curriculum) curriculum set by the OCE 
 Div
idtabs-3
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. 
 Term
OCEOCE
 Term
DACUMDACUM
sweref
289
289
sweref
265
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. 
sweref
289
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 
 Term
SWGSWG
SWE-017
Project and Software Training
SWE-101
Center SW Training Plans
SWE-107
SW Training Plan Contents



 Div
idtabs-4
4. Small Projects
Projects are not responsible for this requirement.

 Div
idtabs-5
5. Resources

refstable

toolstable

 Div
idtabs-6
6. Lessons Learned
No Lessons Learned have currently been identified for this requirement.

...



    
    






    
	

    
    
    



    




    
    

    
    
    






        



        

    

    



										
								
		        

		    



		
						
 











Page Editor: Tim Crumbley 

NASA Official: Tim Crumbley






NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer

 NASA Privacy Statement

______________________________________________________________________________