Software Program: Software Management Guidebook

The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project

The Importance of 'Risk Radar' in Software Risk Management: A Case of a Malaysian Company

‘Risk radar’ is applied to a company in Malaysia, a discussion on the implementation, implications and recommendation highlighted in this paper. The scope of this study has been an analysis of risk management and risk exposure of software projects practices in the company. This study also provided the evident that the successes of the several software that goes into the Malaysian market, depending on how risk management and its plan in software development as in the case of the selected company. It also exposed on how significant is the risk management contributing to cost effective and growth. Findings also included using 80/20 rules or Pareto Principle, 80% of the risks item listed by Boehm in Ten (10) Top Risks are due to 20% of sources (i.e. soft risks). Empirical studies have shown that 80% of the software rework comes from 20% of the problems, and that many of these critical problems involve neglect of off nominal requirements and all these negligence are caused by human (soft risk) (Boehm, 1989; Boehm-Basili, 2001; Standish Group Chaos Study Report (STANDISH), 1995).The company must implement the propose system to ensure that good practice and successful implementation of software risk management is the key factor to successful creation of software that are marketable and high quality benchmarking of plant industrial solutions. It could contribute to gain competitive advantage by at least 50% of project cost due to risks such as rework, budget overruns cost overrun, content deficiencies and etc.; ability to sustain due to minimum impact by software risks; and ability to own the technology rather than uses the technology with reasonable cost in development and always meet or exceed customer requirements

Software Engineering Laboratory Series: Proceedings of the Twenty-Second Annual Software Engineering Workshop

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document

Large project experiences with object-oriented methods and reuse

The SSVTF (Space Station Verification and Training Facility) project is completing the Preliminary Design Review of a large software development using object-oriented methods and systematic reuse. An incremental developmental lifecycle was tailored to provide early feedback and guidance on methods and products, with repeated attention to reuse. Object oriented methods were formally taught and supported by realistic examples. Reuse was readily accepted and planned by the developers. Schedule and budget issues were handled by agreements and work sharing arranged by the developers

Safety and Mission Assurance Acronyms, Abbreviations, and Definitions

This NASA Technical Handbook compiles into a single volume safety, reliability, maintainability, and quality assurance and risk management terms defined and used in NASA safety and mission assurance directives and standards. The purpose of this handbook is to support effective communication within NASA and with its contractors. The definitions in this handbook are updated when the definition of the acronym or term is updated in the originating document

Software Formal Inspections Standard

This Software Formal Inspections Standard (hereinafter referred to as Standard) is applicable to NASA software. This Standard defines the requirements that shall be fulfilled by the software formal inspections process whenever this process is specified for NASA software. The objective of this Standard is to define the requirements for a process that inspects software products to detect and eliminate defects as early as possible in the software life cycle. The process also provides for the collection and analysis of inspection data to improve the inspection process as well as the quality of the software

The Use of Standards on the LADEE Mission

The Lunar Atmosphere Dust Environment Explorer (LADEE) was a small explorer class mission that launched Sept 7, 2013 and successfully de-orbited and impacted the moon's surface on April 17, 2014. The spacecraft was the first to launch from a Minotaur 5 and was the first deep space mission to launch from the Wallops flight facility. Figure 1 shows the famous image of a frog unlucky enough to be launched from the facility at the same time as LADEE. The science mission for the spacecraft was to determine the density, composition and variability of the lunar exosphere. In addition, it performed a first-of-a-kind demonstration of laser-based communications from deep space that exhibited a record downlink rate of 622 megabits per second from the moon. In order to perform the lunar dust surveys, the spacecraft was placed in a retrograde equatorial orbit with periapsis between 20 and 60 kilometers. The mission was granted an extension in which final science surveys were performed at altitudes as low as 2 kilometers over the moon's surface. The cadence for spacecraft operations was demanding: the moon's highly inhomogeneous gravity field distorted the orbit, the regular maneuvers were subject to strict payload-induced pointing requirements, and there were periodic attitude changes to keep the spacecraft thermally safe. This led to a need for high reliability in the operation of the spacecraft while obeying strict budget and schedule guidelines