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

...

idtabs-1

1. Requirements

5.1.6.1 The Center Software Training Plan shall include: [SWE-107]
      a. Responsibilities.
      b. Implementation.
      c. Records and forms.
      d. Training resources.
      e. Minimum training requirements for software personnel.
      f. Training class availabilities.

1.1 Notes

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

Note

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

1.2 Applicability Across Classes

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

...

f1
g1
hp
ansc1
asc1
bnsc1
csc1
bsc1
esc1
cnsc1
dnsc1
dsc1
enscp
Div
idtabs-2

2. Rationale

The requirement lists the minimum content needed for each Center Software 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 to the author. Specifying content items also assures a degree of common software knowledge across Centers.

...

idtabs-3

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(s) 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 projections of future losses in expertise, e.g., retirements or reassignments.

Once the inputs have been obtained and analyzed, the Center responds to the "calls" and captures approved training in an organized manner according to the six topical sections discussed below. This arrangement will enable comparisons to previous and future plans. It will also enable the OCE (Office of the Chief Engineer) 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 Center training plan document usually includes 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 for 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, and 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.

...

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

Div
idtabs-4

4. Small Projects

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

...

idtabs-5

5. Resources

...

toolstable

...

idtabs-6

6. Lessons Learned

A documented lesson from the NASA Lessons Learned database notes the following: 

...