Developing the NASA Systems Engineering Body of Knowledge

Abstract

Systems engineers across NASA needed a single place to go to find various assets to support them in their work, and to help ensure that their missions are successful. These assets ranged from templates and resources to various requirements and processes, as well as points of contact, etc. Hence, there was a need for a central NASA Systems Engineering Body of Knowledge (SEBoK) to store and provide access to systems engineering resources of all types.

Integrating Space Communication Network Capabilities via Web Portal Technologies

“…• wikis: collaborative user editable documentation • content management: web content definition and management, include workflows for staging and publishing • document management: storage and metadata for documents, also including workflows and versioning • blogs and blog aggregation • message boards • alerts and announcements, including RSS news feeds • shared and private calendars Portals have been developed and deployed in a variety of space science and operations contexts, including geophysics 7 , remote sensing 8 , and for the NASA System Engineering Body of Knowledge (SEBoK) 9 . Numerous commercial instances are in active use 6 .…”

Knowledge management in small software development organisations: A South African perspective

“…Garcia et al (2011) support the idea and argue that a central database supports easy retrieval and learning in agile teams. This system has effectively been used by the National Aeronautics and Space Administration Agency to store software engineering knowledge (Jansma & Means 2012).…”