SEARCH · Search NASA
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.
The Space Operations Management Office Organizations will be described along with the responsibilities assigne to this office. The roles for the government and for the contractor will be discussed. This paper will describe the changes, approaches and anticipated benefits of this new approach to operations.
The authors describe in this paper the progress achieved to-date with the reengineering of the Earth Observing System (EOS) Data and Operations System (EDOS), the experience gained in the process and the ensuing reduction of ground systems operations costs. The reengineering effort included a major methodology change, applying to an existing schedule driven system, a data-driven system approach.
Programs in use today generally have all of the function and information processing capabilities required to do their specified job. However, older programs usually use obsolete technology, are not integrated properly with other programs, and are difficult to maintain. Reengineering is becoming a prominent discipline as organizations try to move their systems to more modern and maintainable technologies. The Johnson Space Center (JSC) Software Technology Branch (STB) is researching and developing a system to support reengineering older FORTRAN programs into more maintainable forms that can also be more readily translated to a modern languages such as FORTRAN 8x, Ada, or C. This activity has led to the development of maintenance strategies for design recovery and reengineering. These strategies include a set of standards, methodologies, and the concepts for a software environment to support design recovery and reengineering. A brief description of the problem being addressed and the approach that is being taken by the STB toward providing an economic solution to the problem is provided. A statement of the maintenance problems, the benefits and drawbacks of three alternative solutions, and a brief history of the STB experience in software reengineering are followed by the STB new FORTRAN standards, methodology, and the concepts for a software environment.
Improved process for development of flight-control software devised by integrating conventional software-development process with conventional control-system-analysis process. Reduces costs of development, eliminates need for reengineering, and almost eliminates production errors. Concept applicable to design of other control systems and of complicated hardware-and-software systems in general.
A cost effective introduction of software reuse techniques requires the reuse of existing software developed in many cases without aiming at reusability. This paper discusses the problems related to the analysis and reengineering of existing software in order to reuse it. We introduce a process model for component extraction and focus on the problem of analyzing and qualifying software components which are candidates for reuse. A prototype tool for supporting the extraction of reusable components is presented. One of the components of this tool aids in understanding programs and is based on the functional model of correctness. It can assist software engineers in the process of finding correct formal specifications for programs. A detailed description of this component and an example to demonstrate a possible operational scenario are given.
A cost effective introduction of software reuse techniques requires the reuse of existing software developed in many cases without aiming at reusability. This paper discusses the problems related to the analysis and reengineering of existing software in order to reuse it. We introduce a process model for component extraction and focus on the problem of analyzing and qualifying software components which are candidates for reuse. A prototype tool for supporting the extraction of reusable components is presented. One of the components of this tool aids in understanding programs and is based on the functional model of correctness. It can assist software engineers in the process of finding correct formal specifications for programs. A detailed description of this component and an example to demonstrate a possible operational scenario are given.
This paper presents an overview of a parametric cost model that has been built at JPL to estimate costs of future, deep space, robotic science missions. Due to the recent dramatic changes in JPL business practices brought about by an internal reengineering effort known as develop new products (DNP), high-level historic cost data is no longer considered analogous to future missions. Therefore, the historic data is of little value in forecasting costs for projects developed using the DNP process. This has lead to the development of an approach for obtaining expert opinion and also for combining actual data with expert opinion to provide a cost database for future missions. In addition, the DNP cost model has a maximum of objective cost drivers which reduces the likelihood of model input error. Version 2 is now under development which expands the model capabilities, links it more tightly with key design technical parameters, and is grounded in more rigorous statistical techniques. The challenges faced in building this model will be discussed, as well as it's background, development approach, status, validation, and future plans.
The objective of this project is two-fold. First to provide an evaluation of a commercially developed version of the ground processing scheduling system (GPSS) for its applicability to the Kennedy Space Center (KSC) ground processing problem. Second, to work with the KSC GPSS development team and provide enhancement to the existing software. Systems reengineering is required to provide a sustainable system for the users and the software maintenance group. Using the LISP profile prototype code developed by the GPSS reverse reengineering groups as a building block, we have implemented the resource deconfliction portion of GPSS in common LISP using its object oriented features. The prototype corrects and extends some of the deficiencies of the current production version, plus it uses and builds on the classes from the development team's profile prototype.
In an era of shrinking funds for space exploration, JPL is undergoing a significant reengineering effort designed to reduce costs of flight projects by 33 percent, and time to launch by 50 percent.
Current trends in the spacecraft mission operations area (spacecraft & mission complexity, project duration, required flexibility are requiring a breakthrough for what concerns philosophy, organization, and support tools. A major evolution is related to space operations 'informationalization', i.e adding to existing operations support & data processing systems a new generation of tools based on advanced information technologies (object-oriented programming, artificial intelligence, data bases, hypertext) that automate, at least partially, operations tasks that used be performed manually (mission & project planning/scheduling, operations procedures elaboration & execution, data analysis & failure diagnosis). All the major facets of this 'informationalization' are addressed at MATRA MARCONI SPACE, operational applications were fielded and generic products are becoming available. These various applications have generated a significant feedback from the users (at ESA, CNES, ARIANESPACE, MATRA MARCONI SPACE), which is now allowing us to precisely measure how the deployment of this new generation of tools, that we called OPSWARE, can 'reengineer' current spacecraft mission operations philosophy, how it can make space operations faster, better, and cheaper. This paper can be considered as an update of the keynote address 'Knowledge-Based Systems for Spacecraft Control' presented during the first 'Ground Data Systems for Spacecraft Control' conference in Darmstadt, June 1990, with a special emphasis on these last two years users feedback.
NASA Goddard Space Flight Center's "GMSEC" ground system architecture was presented at GSAW2003 as a concept being studied. GMSEC would utilize a publish/subscribe middleware framework and standardized interfaces to allow custom and COTS ground system components to plug-and-play. This capability, in turn, would reduce integration costs, allow for technology infusion over time, and encourage the development and sharing of common components across missions and organizations. At GSAW2004, GMSEC was presented at a breakout session as a system working well in the NASA lab and being applied as an integral piece of reengineering efforts for several GSFC missions. Today, GMSEC is supporting five satellites at GSFC and has been selected by several future missions. Over 30 plug-and-play components are now available to missions using the GMSEC approach. Other organizations, including Marshall Space Flight Center, Johns Hopkins University's Applied Physic Lab, and the Institute for Scientific Research are each developing GMSEC-compatible components. Based on the success of GMSEC and efforts at other NASA Centers, the message bus approach is now being evaluated as a NASA Agency-wide approach for many future missions involving multiple NASA Centers as we move towards the goals of NASA s new Exploration Initiative. The presentation will explain the basic technical concepts of using a publish/subscribe framework for mission operations support (and its applicability to flight systems as well). Lessons learned on NASA's GMSEC program will allow the audience to better understand the significant benefits of this architecture approach over the traditional "one-off" solution approach. The point of the presentation is to show the long-term benefits of using a ground system architecture which incorporates many of the successful GMSEC concepts - message bus, mix of COTS and custom software, standard interfaces, plug-and-play, etc. The implications for the development process will also be discussed.