Managing Software Requirements in the Context of Scientific Enterprise
Explore the source record for details and available documents.
Software requirements software engineering↗
SEARCH · Search NASA
Results for “requirement management”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Earth Observations to Assess Impact of Hurricane Katrina on John C. Stennis Space Center
The peril from hurricanes to Space Operations Centers is real and is forecast to continue; Katrina, Rita, and Wilma of 2005 and Charley, Frances, Ivan, and Jeanne of 2004 are sufficient motivation for NASA to develop a multi-Center plan for preparedness and response. As was demonstrated at SSC (Stennis Space Center) in response to Hurricane Katrina, NASA Centers are efficiently activated as local command centers, playing host to Federal and State agencies and first responders to coordinate and provide evacuation, relocation, response, and recovery activities. Remote sensing decision support provides critical insight for managing NASA infrastructure and for assisting Center decision makers. Managers require geospatial information to manage the federal city. Immediately following Katrina, SSC s power and network connections were disabled, hardware was inoperative, technical staff was displaced and/or out of contact, and graphical decision support tools were non-existent or less than fully effective. Despite this circumstance, SSC EOC (Emergency Operations Center) implemented response operations to assess damage and to activate recovery plans. To assist Center Managers, the NASA ASP (Applied Sciences Program) made its archive of high-resolution data over the site available. In the weeks and months after the immediate crisis, NASA supplemented this data with high-resolution, post-Katrina imagery over SSC and much of the affected coastal areas. Much of the high-resolution imagery was made available through the Department of Defense Clear View contract and was distributed through U.S. Geological Survey Center for Earth Resources Observation and Science "Hurricane Katrina Disaster Response" Web site. By integrating multiple image data types with other information sources, ASP applied an all-source solutions approach to develop decision support tools that enabled managers to respond to critical issues, such as expedient access to infrastructure and deployment of resources, provision of temporary shelter, logistical control of critical supplies, and the mobilization and coordination of assets from ground crews to aircraft/airspace management. Furthermore, ASP developed information products that illustrate risks to SSC's infrastructure from surge, inundation, and flood. Current plans include developing wind-risk prototype products for refinement and adoption into EOC plans.
Graham, William D.↗
LSE-61: Rubin Observatory Data Management System (DMS) Requirements
This document contains the top-level requirements for the Data Management subsystem of the LSST, when combined with the Data Management-related requirements in the LSST System Requirements (LSR, LSE-29) and Observatory System Specifications (OSS, LSE-30).
79 ASTRONOMY AND ASTROPHYSICS↗
Implementing an Objectives-Driven, Risk-Informed, and Case-Assured Approach to Safety and Mission Success at NASA
NASA is developing a “Standard for Assurance of Space Flight Safety and Mission Success” that implements an objectives-driven, risk-informed, and case-assured approach to safety and mission success (S&MS) for NASA space flight programs and projects. The standard aligns with the philosophy of risk leadership that has recently been established in NASA policy to assure acceptable levels of flight crew safety and mission success risk. It is consistent with existing NASA risk management requirements and is compatible with NASA program management and systems engineering requirements. The methodology described in the standard is presented in terms of an S&MS assurance framework that is designed to allow substantial flexibility in the specific means by which programs and projects achieve acceptable mission S&MS risk. Such flexibility is necessary to accommodate the increasingly broad range of acquisition strategies employed by NASA, including commercial transportation services, as well as to accommodate the increasingly rapid evolution of space flight-related technologies and practices. A key feature of the S&MS assurance framework is the specification of S&MS success criteria for each life-cycle review (LCR). The S&MS assurance case is structured around these criteria, the satisfaction of which indicates that the program/project is adhering to the S&MS risk posture. This enables the evolving S&MS assurance case to be used as a fundamental program/project submittal at each LCR, where its inherent structure of argument, supported by evidence, directly supports the evaluation of the program/project with respect to the S&MS success criteria, and by extension, the S&MS risk posture. As such, the S&MS assurance case is integral to program/project systems engineering, risk management, and S&MS oversight activities, and provides the principal basis for S&MS risk acceptance by the Decision Authority throughout the program/project life cycle.
Risk Posture↗
Implementing an Objectives-Driven, Risk-Informed, and Case-Assured Approach to Safety and Mission Success at NASA
NASA is developing a “Standard for Assurance of Space Flight Safety and Mission Success” that implements an objectives-driven, risk-informed, and case-assured approach to safety and mission success (S&MS) for NASA space flight programs and projects. The standard aligns with the philosophy of risk leadership that has recently been established in NASA policy to assure acceptable levels of flight crew safety and mission success risk. It is consistent with existing NASA risk management requirements and is compatible with NASA program management and systems engineering requirements. The methodology described in the standard is presented in terms of an S&MS assurance framework that is designed to allow substantial flexibility in the specific means by which programs and projects achieve acceptable mission S&MS risk. Such flexibility is necessary to accommodate the increasingly broad range of acquisition strategies employed by NASA, including commercial transportation services, as well as to accommodate the increasingly rapid evolution of space flight-related technologies and practices. A key feature of the S&MS assurance framework is the specification of S&MS success criteria for each life-cycle review (LCR). The S&MS assurance case is structured around these criteria, the satisfaction of which indicates that the program/project is adhering to the S&MS risk posture. This enables the evolving S&MS assurance case to be used as a fundamental program/project submittal at each LCR, where its inherent structure of argument, supported by evidence, directly supports the evaluation of the program/project with respect to the S&MS success criteria, and by extension, the S&MS risk posture. As such, the S&MS assurance case is integral to program/project systems engineering, risk management, and S&MS oversight activities, and provides the principal basis for S&MS risk acceptance by the Decision Authority throughout the program/project life cycle.
42 ENGINEERING↗
Spaceport operations for deep space missions
Space Station Freedom is designed with the capability to cost-effectively evolve into a transportation node which can support manned lunar and Mars missions. To extend a permanent human presence to the outer planets (moon outposts) and to nearby star systems, additional orbiting space infrastructure and great advances in propulsion system and other technologies will be required. To identify primary operations and management requirements for these deep space missions, an interstellar design concept was developed and analyzed. The assembly, test, servicing, logistics resupply, and increment management techniques anticipated for lunar and Mars missions appear to provide a pattern which can be extended in an analogous manner to deep space missions. A long range, space infrastructure development plan (encompassing deep space missions) coupled with energetic, breakthrough level propulsion research should be initiated now to assist in making the best budget and schedule decisions.
Holt, Alan C.↗
Lessons Learned in Systems Engineering Availability and Recommendations for Mission Technical Leaders
In spaceflight missions at Goddard Space Flight Center (GSFC), the Mission System Engineer (MSE) is the technical leader of the overall engineering team and also is the Independent Engineering Technical Authority. The responsibility of this role includes the definition of the mission design architecture, concept of operations, and mission requirements, management of risk throughout the development, and verification and validation of the final system performance and function amongst other duties. This responsibility inherently requires time management, enabling focus on a balanced development with appropriate risk. Time is the most valuable resource of the MSE. The system engineer’s availability to interact with the development team (often product or component design leads and technicians, often in different worksites) to discover and mitigate mission risks during development is key to mission success. This paper presents examples from Lunar Reconnaissance Orbiter, Landsat 9, and Neutron star Interior Composition ExploreR (NICER) which represent in-house and out-of-house hardware builds. These examples demonstrate how interactions between the Mission Systems Engineers and other project and partner engineers result in discovery of critical risks, leading to early mitigation with significant cost and performance savings. These three missions would have suffered test failures or on-orbit failures had their MSEs not set aside time to visit engineers and technicians that were working on key pieces of space flight hardware. Availability is more than just time; it is openness to listen to concerns and questions. It begins by building a level of trust in the team that it is safe to ask questions or share concerns without the fear of blame or additional workload. It also requires enabling informal conversations (over lunch, coffee, in the clean room, or at the team members desk, etc.) where key information can be exchanged, and team members may even provide an easy-to-implement mitigation idea for another subsystem. Availability is a highly valuable commodity and completely non-obvious to protect and optimize. The natural tendency of engineers is to keep themselves busy with solving problems that they know about. This paper is encouraging MSEs to resist this tendency to try and solve all the complex problems themselves and actively devote daily time to learning and solving problems that are found with informal communications with other team members.
Lessons Learned↗
Space shuttle booster Data Management system (DMS) requirements analysis. Volume 1: Study summary
Analysis of functional requirements for data management systems used with space shuttle - Vol. 1
Lutes, C. L.↗
Management Approach for NASA's Earth Venture-1 (EV-1) Airborne Science Investigations
The Earth System Science Pathfinder (ESSP) Program Office (PO) is responsible for programmatic management of National Aeronautics and Space Administration's (NASA) Science Mission Directorate's (SMD) Earth Venture (EV) missions. EV is composed of both orbital and suborbital Earth science missions. The first of the Earth Venture missions is EV-1, which are Principal Investigator-led, temporally-sustained, suborbital (airborne) science investigations costcapped at $30M each over five years. Traditional orbital procedures, processes and standards used to manage previous ESSP missions, while effective, are disproportionally comprehensive for suborbital missions. Conversely, existing airborne practices are primarily intended for smaller, temporally shorter investigations, and traditionally managed directly by a program scientist as opposed to a program office such as ESSP. In 2010, ESSP crafted a management approach for the successful implementation of the EV-1 missions within the constructs of current governance models. NASA Research and Technology Program and Project Management Requirements form the foundation of the approach for EV-1. Additionally, requirements from other existing NASA Procedural Requirements (NPRs), systems engineering guidance and management handbooks were adapted to manage programmatic, technical, schedule, cost elements and risk. As the EV-1 missions are nearly at the end of their successful execution and project lifecycle and the submission deadline of the next mission proposals near, the ESSP PO is taking the lessons learned and updated the programmatic management approach for all future Earth Venture Suborbital (EVS) missions for an even more flexible and streamlined management approach.
Guillory, Anthony R.↗
NASA's acquisition requirements for configuration management
A viewgraph presentation on NASA's acquisition requirements for configuration management (CM) goes over CM requirements for single mission and multi-mission orientations, CM automation and CALS implementation initiatives, NASA implementation of DOD standards and DID's (data item descriptions), impact of traceability in NASA CM support, NASA's CM efforts in modifying/upgrading equipment, and CM control of multi-vendor hardware.
Coletta, Mark P.↗
Space shuttle program: Shuttle Avionics Integration Laboratory. Volume 7: Logistics management plan
The logistics management plan for the shuttle avionics integration laboratory defines the organization, disciplines, and methodology for managing and controlling logistics support. Those elements requiring management include maintainability and reliability, maintenance planning, support and test equipment, supply support, transportation and handling, technical data, facilities, personnel and training, funding, and management data.
Source record↗
Baseline experimental investigation of an electrohydrodynamically assisted heat pipe
The increases in power demand and associated thermal management requirements of future space programs such as potential Lunar/Mars missions will require enhancing the operating efficiencies of thermal management devices. Currently, the use of electrohydrodynamically (EHD) assisted thermal control devices is under consideration as a potential method of increasing thermal management system capacity. The objectives of the currently described investigation included completing build-up of the EHD-Assisted Heat Pipe Test bed, developing test procedures for an experimental evaluation of the unassisted heat pipe, developing an analytical model capable of predicting the performance limits of the unassisted heat pipe, and obtaining experimental data which would define the performance characteristics of the unassisted heat pipe. The information obtained in the currently proposed study will be used in order to provide extensive comparisons with the EHD-assisted performance observations to be obtained during the continuing investigation of EHD-Assisted heat transfer devices. Through comparisons of the baseline test bed data and the EHD assisted test bed data, accurate insight into the performance enhancing characteristics of EHD augmentation may be obtained. This may lead to optimization, development, and implementation of EHD technology for future space programs.
Duncan, A. B.↗
Electrical, Electronic, and Electromechanical (EEE) parts management and control requirements for NASA space flight programs
This document establishes electrical, electronic, and electromechanical (EEE) parts management and control requirements for contractors providing and maintaining space flight and mission-essential or critical ground support equipment for NASA space flight programs. Although the text is worded 'the contractor shall,' the requirements are also to be used by NASA Headquarters and field installations for developing program/project parts management and control requirements for in-house and contracted efforts. This document places increased emphasis on parts programs to ensure that reliability and quality are considered through adequate consideration of the selection, control, and application of parts. It is the intent of this document to identify disciplines that can be implemented to obtain reliable parts which meet mission needs. The parts management and control requirements described in this document are to be selectively applied, based on equipment class and mission needs. Individual equipment needs should be evaluated to determine the extent to which each requirement should be implemented on a procurement. Utilization of this document does not preclude the usage of other documents. The entire process of developing and implementing requirements is referred to as 'tailoring' the program for a specific project. Some factors that should be considered in this tailoring process include program phase, equipment category and criticality, equipment complexity, and mission requirements. Parts management and control requirements advocated by this document directly support the concept of 'reliability by design' and are an integral part of system reliability and maintainability. Achieving the required availability and mission success objectives during operation depends on the attention given reliability and maintainability in the design phase. Consequently, it is intended that the requirements described in this document are consistent with those of NASA publications, 'Reliability Program Requirements for Aeronautical and Space System Contractors,' NHB 5300.4(1A-l); 'Maintainability Program Requirements for Space Systems,' NHB 5300.4(1E); and 'Quality Program Provisions for Aeronautical and Space System Contractors,' NHB 5300.4(1B).
Source record↗
NASA Space Flight Program and Project Management Handbook
This handbook is the companion document to NPR 7120.5F, NASA Space Flight Program and Project Management Requirements. It represents the accumulation of knowledge on managing program and projects derived from NASA’s human, robotic, and scientific missions. It incorporates the “corporate knowledge” for existing and future NASA space flight programs and projects, including NASA’s Artemis missions to establish a sustainable human presence on the Moon through collaboration with commercial and international partners, NASA’s James Webb Space Telescope (JWST) mission, and NASA’s robotic missions on Mars. The practices discussed have evolved as a function of NASA’s core values of safety, integrity, teamwork, excellence, and inclusion, and may also prove a resource for other agencies, the private sector, and academia. The knowledge gained from the Agency’s victories and defeats, including the checks and balances and initiatives to better control cost and risk, provides a foundation for continuing an exciting and healthy space program. This handbook provides implementation guidance for NPR 7120.5F and includes the changes and updates to key procedural requirements in NPR 7120.5F since NPR 7120.5E. The goal of the NPR requirements is to ensure programs and projects are developed and successfully executed in the most cost-effective and efficient manner possible. This handbook provides context, rationale, and explanation to facilitate the application of requirements and to pass on some of the hard-won best practices and lessons learned.
Tracy L Osborne↗
An approach to improve management visibility within the procurement and financial group at Goldstone
Improvements in the operational efficiency of the data management systems at the Goldstone Deep Space Communications Complex (GDSCC) are discussed. This addresses the existing procurement and financial management data system at GDSCC, identifies management requirements for better visibility, describes a proposed computerized data management system, summarizes results to data, and identifies plans for future development.
Maiocco, F. R.↗
Data management for Computer-Aided Engineering (CAE)
Analysis of data flow through the design and manufacturing processes has established specific information management requirements and identified unique problems. The application of data management technology to the engineering/manufacturing environment addresses these problems. An overview of the IPAD prototype data base management system, representing a partial solution to these problems, is presented here.
Bryant, W. A.↗
Using expert systems to implement a semantic data model of a large mass storage system
The successful development of large volume data storage systems will depend not only on the ability of the designers to store data, but on the ability to manage such data once it is in the system. The hypothesis is that mass storage data management can only be implemented successfully based on highly intelligent meta data management services. There now exists a proposed mass store system standard proposed by the IEEE that addresses many of the issues related to the storage of large volumes of data, however, the model does not consider a major technical issue, namely the high level management of stored data. However, if the model were expanded to include the semantics and pragmatics of the data domain using a Semantic Data Model (SDM) concept, the result would be data that is expressive of the Intelligent Information Fusion (IIF) concept and also organized and classified in context to its use and purpose. The results are presented of a demonstration prototype SDM implemented using the expert system development tool NEXPERT OBJECT. In the prototype, a simple instance of a SDM was created to support a hypothetical application for the Earth Observing System, Data Information System (EOSDIS). The massive amounts of data that EOSDIS will manage requires the definition and design of a powerful information management system in order to support even the most basic needs of the project. The application domain is characterized by a semantic like network that represents the data content and the relationships between the data based on user views and the more generalized domain architectural view of the information world. The data in the domain are represented by objects that define classes, types and instances of the data. In addition, data properties are selectively inherited between parent and daughter relationships in the domain. Based on the SDM a simple information system design is developed from the low level data storage media, through record management and meta data management to the user interface.
Roelofs, Larry H.↗
Closed Loop Requirements and Analysis Management
Effective systems engineering involves the use of analysis in the derivation of requirements and verification of designs against those requirements. The initial development of requirements often depends on analysis for the technical definition of specific aspects of a product. Following the allocation of system-level requirements to a product's components, the closure of those requirements often involves analytical approaches to verify that the requirement criteria have been satisfied. Meanwhile, changes that occur in between these two processes need to be managed in order to achieve a closed-loop requirement derivation/verification process. Herein are presented concepts for employing emerging Team center capabilities to jointly manage requirements and analysis data such that analytical techniques are utilized to effectively derive and allocate requirements, analyses are consulted and updated during the change evaluation processes, and analyses are leveraged during the design verification process. Recommendations on concept validation case studies are also discussed.
Lamoreaux, Michael↗