Welcome
This site is under development. You can follow the navigation above to explore the site. If you have any questions, please contact Jon Verville
at 301-286-8741.
We are glad you have come to the NASA Software Engineering Handbook site. The purpose of this site is to provide key insights to you, a Software Engineering professional. We plan on two phases of release: the first with 30% material in February 2011, and with 80% material in October 2011.
To view a presentation that was given on the handbook development to the Software Engineering Working Group in August 2010, [click here|^7150handbook-swgf2f-_jonv_REV-C.ppt].
How is this different than any other NASA handbook?
The Software Engineering handbook will have two components. A PDF/printable version for those who wish to use the material in a more traditional way. We are also developing this web version as an interactive and dynamic version of the same material. We plan on utilizing web technologies, such as tagging (folksonomies), social commenting, and web editability and versioning to enhance the experience of what a paperback handbook provides.
Special Topic Material
There are a total of 37 special topics which will be chapters within the handbook. A partial list is as follows:
7.1 - 7150.2A Definitions & References, 7.2 - Classification Tool and Safety Critical Assessment Tool, 7.3 - Lifecycle Management, 7.4 - Entrance / Exit Criteria for 7150.2A, 7.5 - Documentation Products Maturity (List of material maturity by phase of mission), 7.6-8 - 7150.2A's Traceability to Other NPRs, 7.9 - Software Acquisition, 7.10 - P(Center) Guidance, 7.11 - Use of COTS, GOTS, MOTS, 7.12 - Flow down of NPR requirements on contracts and to other centers in multi center projects, 7.13 - Present requirements by class and include safety critical and assurance requirements, 7.14 - Overview and history of the SPI effort, 7.15 - Peer review and inspections including checklists, 7.16 - Transitioning to a higher class, 7.17 - Explanation of enforcement of NPR requirements, 7.18 - Compliance matrices
Material by SWE Requirement Number
The NASA Software Engineering standards are laid out in the NPR 7150.2A document (click here to view it on the web
). Within the document, there are requirements numbering up to 130. We will be producing material for each of these requirements in the following areas: Guidance, Rationale, Tools Available, Links, and Guidance for Small Projects.
Current Material
Below is a list of all the material in this electronic handbook so far. Use discretion, as this material is in various stages of development.
| 7.1 | 7150.2A Appendicies (Definitions, References, etc.) | | | | Lee | Jon | Lee | John K. | Jon/Greg | Lee | | | | |
7.2 |
Classification Tool and Safety Critical Assessment Tool |
|
Flow diagrams of the classification tool |
Actual interactive online tool |
Tommy |
Dave/Kevin/Kathy |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.3 |
Lifecycle Management |
|
|
|
Kathy |
Kevin |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.4 |
Entrance / Exit Criteria for 7150.2A |
Kathy Malnick's criteria charts |
|
TODO: Write narrative intro to each section (like SEHandbook) |
Kathy |
Kevin/ Sally G./ Dave Retherford |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.5 |
Documentation Products Maturity |
List of material maturity by phase of mission |
|
|
Kathy |
Multiple Reviewers |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.6 |
7150.2A's Traceability to Other NPRs |
|
|
|
Kathy |
Kevin/John K. |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.7 |
Traceability to 7123.2 (NASA Systems Engineering Processes and Requirements) |
|
|
|
Kathy |
Kevin |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.8 |
Traceability to NPR 7120.5D (NASA Space Flight Program and Project Management Requirements) |
|
|
|
Kathy |
Kevin |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.9 |
Software Acquisition |
|
|
|
Kathy |
Kevin |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.10 |
P(Center) Guidance |
|
|
|
Tommy |
Kevin |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.11 |
Use of COTS, GOTS, MOTS |
|
|
|
Dave |
Multiple Reviewers |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.12 |
Flow down of NPR requirements on contracts and to other centers in multi center projects |
|
|
|
Dave |
Tim |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.13 |
Present requirements by class and include safety critical and assurance requirements |
|
|
|
Kevin |
Pat S. |
|
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.14 |
Overview and history of the SPI effort |
|
|
|
Kevin |
John K. |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.15 |
Peer review and inspections including checklists |
|
|
|
Kevin |
Dave |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.16 |
Transitioning to a higher class |
|
|
|
Kathy |
Kevin |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.17 |
Explanation of enforcement of NPR requirements |
|
|
|
Tommy |
Kevin |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.18 |
Compliance matrices |
|
|
|
Kevin |
Kathy |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.19 |
Developing WBS structures which include Software |
|
|
|
Dave |
Kathy |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.21 |
Qualification of flight software |
|
|
|
Dave |
Kevin |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.22 |
Architecture development and assessment |
|
|
|
Dave |
Kevin |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.23 |
Accrediting software models/sims and analysis tools - These topics have not been addressed |
|
|
|
Dave |
Kevin |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.24 |
Use of development, management and testing tools |
|
|
|
Dave |
Kevin |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.25 |
Implementing metrics requirements and analysis plus examples |
|
|
|
Kevin |
Sally G. |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.26 |
Cost Estimation |
|
|
|
Kevin |
Dave |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.27 |
Use of multiple classification within a project (eg. Libraries) |
|
|
|
Kevin |
Kathy |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.28 |
Accrediting software tools |
|
|
|
Kevin |
Dave |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.29 |
Tailoring of Reqt's based on Project Risk. Could tailoring be done to match a payload class? |
|
|
|
Kevin |
Tim |
Lee |
John K. |
Jon/Greg |
Kevin |
|
|
|
|
7.30 |
Model based development and auto-generated code |
|
|
|
Kathy |
Kevin |
Lee |
John K. |
Jon/Greg |
Kathy |
|
|
|
|
7.31 |
Coding standards with examples, Design patterns |
|
|
|
Dave |
Tommy |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.32 |
Distinguishing A-E from F-H |
|
|
|
Tommy |
Kevin |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.33 |
Applicability of requirements to Models and Sims including overlap and underlap of 7150 vs. 7009 |
|
|
|
Tommy |
Dave |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.34 |
Data only projects |
|
|
|
Tommy |
Kevin |
Lee |
John K. |
Jon/Greg |
Tommy |
|
|
|
|
7.35 |
Static and dynamic testing tools, et. when to use? |
|
|
|
Dave |
Kevin |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.36 |
Software testing, estimates, levels of testing |
|
|
|
Dave |
Kevin |
Lee |
John K. |
Jon/Greg |
Dave |
|
|
|
|
7.37 |
Choosing SW vs. Complex electronics |
|
|
|
Kevin + Tim |
John K. |
Lee |
John K. |
Jon/Greg |
Kevin + Tim |
