bannerd

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tabsetup
0Introduction
1Software Management Requirements
2Software Engineering Life Cycle Requirements
3Supporting Software Life Cycle Requirements
Info Boxes by color
Div
idtabs-1

1. Introduction

This page is a demonstration of how the SWEHBVD could be enhanced by adding a series of pages to contain links and content by work type. Work types are already defined in NPR 7150.2D in Chapters 2 through 5. These work types can be reused and enhanced in a collection of pages to present content and job aids to project teams. various options available in Confluence

Div
idtabs-2

2.

 Software Management Requirements

 Info Boxes by Color

The management of software project includes a significant effort by managers and supervisors on a project. 

Copy Chapter 3 from C. here

Div
idtabs-3

3. Software Engineering Life Cycle Requirements

The engineering of software includes a significant effort by developers, testers, and other professionals on a project. 

Copy Chapter 4 from C. here

color of the text boxes on the Requirements pages. 

HTML Table
stylewidth:100%;border:1px solid #aaa;padding:3px;border-radius:5px;background:#eaeada
Table Row (tr)
Table Cell (td)

(info) INSTITUTIONAL REQUIREMENTS (CHAPTER 2)

Chapter 2 describes the roles, responsibilities, and institutional requirements relevant to the requirements in this directive.This chapter describes the responsibilities for maintaining and advancing organizational capability in software engineering practices to effectively meet the scientific and technological objectives of the Agency. Chapter 2 defines the roles and responsibilities of key officials in software engineering management, the software development and management processes, and the software life cycle management processes. Specific software classification applicability, if any, for the requirements in Chapter 2 are contained in the requirement wording. The requirements in Chapter 2 are not part of the Requirements Mapping Matrix in Appendix C. Approval of any tailoring of requirements designated in Chapter 2 can be done by the appropriate organization per the defined roles and responsibilities.

Each SWE contains six tabs: 

  1. Requirement - along with the Notes (if any), and a link to the SWE history
  2. Rationale 
  3. Guidance - information on how the requirement may be satisfied
  4. Small Projects - how the requirement may be satisfied for small projects
  5. Resources - References and other associated information
  6. Lessons Learned
Div
idtabs-4

4. Supporting Software Life Cycle Requirements

The support of a software project includes a significant effort by support staff on a project. 

Copy Chapter 5 from C. here