Software Project activities are conducted in a predictable sequence. This sequence may be a once through / "waterfall" cycle. Or, it may be an iterative or evolutionary series of cycles which build toward a final product. Regardless of the model chosen, individual activities in all these cycles are very similar.
The major activity groupings here give you a quick way to find guidance in the SWEHB to help you satisfy the needs of the development project while also satisfying the requirements of NPR 7150.2.
The activities associated with Software Engineering are listed in the tabs of this page. Each tab takes you to a list of links to pages where topics explain the activity in more detail. At the lowest level, there is a list of links to specific pages in the SWEHB where details of the activity are explained and more guidance is provided. These pages may be SWEs, Topics, or other Process Assets to help you in conducting the activity.
1.1 Activity Groupings
The tabs in this page initially will contain all of the activities in Ch 2 through 5 of NPR 7150.2. This is done to ensure that all SWEs are accounted for.
As the page matures, Topics, PATs, and other resources will be distributed to enrich the content of the activities.
SWEs from NPR 7150.2 are reproduced in a floatbox on the right to ensure that all SWEHB content is accounted for somewhere in the view.
The Management activities associated with Software Development Projects are listed as links below.
Management activities are typically conducted by those in leadership roles. Supervisors, managers and team leads are involved to varying degrees. Some activities even involve Support, Assurance and Safety roles. Interactions are explained in the activities.
2.1 OCE Roles in Software Process Improvement
The objective of the NASA Software Initiative is to support NASA programs and projects to accomplish their planned goals (e.g., mission success, safety, schedule, and budget) while satisfying their specified software requirements. Software engineering is defined as the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, i.e., the application of engineering to software. The associated objective is to establish and maintain a workforce that possesses state-of-the-art technical competencies. One of these is software engineering, which is considered to be a core competency for the Agency.
Capability Maturity Model® Integration (CMMI®) for Development (CMMI®-DEV) appraisals are the preferred benchmarks for objectively measuring progress toward software engineering process improvement at NASA Centers.
The Headquarters Office of the Chief Engineer (OCE) achieves this requirement by a number of methods including internal surveys and CMMI Appraisals.
SWE-032 - CMMI Levels for Class for Class A and B Software
SWE-032 - CMMI Levels for Class for Class A and B Software
nopanel
true
Div
id
tabs-3
3. Management
The Management activities associated with Software Development Projects are listed as links below.
Management activities are typically conducted by those in leadership roles. Supervisors, managers and team leads are involved to varying degrees. Some activities even involve Support, Assurance and Safety roles. Interactions are explained in the activities.
