If this page is used as a template, remove all of the "Note to editors" panels and associated Show-if macros. 

The title of the SWE has two parts. For Example: SWE-987 This Is the Title

• The SWE number is 7 characters and the numeric portion is always a 3 digit number. This is necessary for the referencing to work properly. See References in SWEHB for details
• The title portion is a text headline for the SWE telling the viewer what the SWE is all about

Consult SWE Maintenance Guide for details on SWE Maintenance and how the SWE number is used in References. 

1. Requirements

1.1 Notes

The Notes from the SWE in NPR7150.2 are copied here. In "paragraph" style with bullets as necessary. If there are no Notes, the statement below is the only note in this section. 

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

1.2 History

Click here to view the history of this requirement: SWE-050 History

1.3 Applicability Across Classes

2. Rationale

Provide a reason for the SWE in this section. 

3. Guidance

Provide additional guidance for the SWE in this section. 

Use numbering and bullets as necessary.

Graphics may be used also to explain concepts. A copy of the original artwork should be attached to the page so it can be used if the image needs to be revised. 

3.1 Additional sub headings

Use Heading 1 style for the initial heading in the tab. Use Heading 2 style for the next level of subheadings. If a lower heading style is needed, use Heading 3. Try to not have lower heading styles below 3. 

If a summary of referenced SWEs is appropriate, use a simple table of links like the one below. 

4. Small Projects

"No additional guidance is available for small projects."

OR, other statement on applicability of the requirement to small projects.

5. Resources

5.1 References

5.2 Tools

6. Lessons Learned

No lessons learned have currently been identified for this requirement.

OR, statement of lessons learned applicability is needed. 

6.1 NASA Lessons Learned

Lessons that appear in the NASA LLIS or Center Lessons Learned Databases.

• Lesson Title in bold. Lesson Number 9999:  ⁵⁶⁷  Extract from the lesson. Extract taken which points up the lessons that is appropriate to the SWE or Topic of this page. Add a SWEREF pointing back to the reference for the lesson. 

6.2 Other Lessons Learned (add this category only if appropriate)

Lessons that appear in the sources outside of NASA such as educational sources or industry sources.

• Lesson Title in bold. Lesson Number 9999:  ⁵⁶⁷ Extract from the lesson. Extract taken which points up the lessons that is appropriate to the SWE or Topic of this page. Add a SWEREF pointing back to the reference for the lesson. 

This tab is only appropriate for SWEs having SA tasking. It is not used for Institutional Requirements. 

7. Software Assurance

7.1 Tasking for Software Assurance

1. Tasking for software Assurance goes here. 

7.2 Software Assurance Products

• The list of SA products goes here

7.3 Metrics

• # of 
• # of

7.4 Guidance

Software assurance guidance for this SWE goes here.