bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Versions Compared

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:SWE-100} {tabsetup:1. The Requirement|2. Rationale|3. Guidance|4. Small Projects|5. Resources|6. Lessons Learned} {div3:id=tabs-1} h1. 1. Requirements
Wiki Markup
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. h2. {color:#003366}{*}

acquisition. [SWE-100]

1.1

Notes{*}{color} NPR

Notes

NPR 7150.2

does not include any notes for this requirement. h2.

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

1.2

Applicability

Across

Classes Appendix D of NPR 7150.2 does not include any notes for this requirement. {applicable:asc=1|ansc=1|bsc=1|bnsc=1|csc=1|cnsc=1|dsc=1|dnsc=1|esc=1|ensc=1|f=1|g=1|h=1} {div3} {div3:id=tabs-2} 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. {div3} {div3:id=tabs-3} 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 {sweref:289}, {sweref: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 ( [https://nen.nasa.gov/web/software/training|https://nen.nasa.gov/web/software/training] ) .  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 | \\ {div3} {div3:id=tabs-4} h1. 4. Small Projects Projects are not responsible for this requirement. {div3} {div3:id=tabs-5} h1. 5. Resources {refstable} {toolstable}\\ {div3} {div3:id=tabs-6} h1. 6. Lessons Learned No Lessons Learned have currently been identified for this requirement. {div3} {tabclose}

Classes


applicable
f1
g1
h1
ansc1
asc1
bnsc1
csc1
bsc1
esc1
cnsc1
dnsc1
dsc1
ensc1



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

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 DACUM (Developing a Curriculum) curriculum set by the OCE

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 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:


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.