NASA/WVU Software Research Laboratory, 1995

Innovations in Systems and Software Engineering, 2005

2011 Aerospace Conference, 2011

The NASA Independent Verification and Validation (IV&V) Facility objective is to identify potential defects in flight software using independent analysis techniques. This paper describes the tailored IV&V techniques that have been developed in support of critical interactions on the Mars Science Laboratory (MSL) project, scheduled to launch in November, 2011. The IV&V techniques for interface analysis use independently developed sequence diagrams of critical scenarios. The results from these analyses have had a positive impact on the requirements flow down, consistency amongst MSL requirements and identification of missing requirements. The results of these analyses and the positive impact to the MSL project are provided.

Applied technologies in space sector are performing complicated and challenging projects in comparison other industries. This complexity in the space sector requires new alternatives for business management and project development. Therefore, management strategies in an organization directly affect the project achievements. Project applications, improvement of economic earnings, relations among people in an organization, mentorships, motivation factors and international activities are other significant issues which are really crucial for space sector. To discuss these important issues, we were one of five groups at International Astronautical Congress, Young Professional Workshop in Beijing, 20th September 2013. Our relevant group topic was “What tools and project organization methodologies have been and can be implemented into the space sector from other industries and the YPs' experience (e.g. software, automotive)? “. As a group we have met several times prior to the workshop. Many ideas are emerged in consequence of meetings. Pre-meeting report helped us to prepare individual materials as members thru the workshop. These different reflections were: (1) agile software and engineering issues, (2) process improvement techniques and learning from manufacturing by multiple copies of the same space platform, (3) social activities of organizations for the internal motivation, (4) TRL improvement, (5) project management and system engineering certification the examples from NASA APPEL and Aerospace Corporation, (6) technology transfer among sectors just as military-space and biology-space, (7) Experience assessment of JAXA, (8) software tools that are being used across industries. During the workshop, we simplified these findings and made the final presentation. In addition, preliminary survey questions are listed and determined after the workshop. Finally, common grounds in our final report are summarized as (1) Software development tools, (2) Process improvement techniques, (3) Project management, system engineering education and certification, (4) Company organization structures and (5) Social Activities to improve sector interest. In the final report, group recommendations are given for the each topic and presented to the IAF YP Committee.

IEEE Transactions on Engineering Management, 1996

Technology transfer is of crucial concern to both government and industry today. In this paper, several software engineering technologies used within NASA are studied, and the mechanisms, schedules and efforts at transferring these technologies are investigated. The goals of this study are: (1) to understand the difference between technology transfer (the adoption of a new method by large segments of an industry) as an industry-wide phenomenon and the adoption of a new technology by an individual organization (called technology infusion), and (2) to see if software engineering technology transfer differs from other engineering disciplines. While there is great interest today in developing technology transfer models for industry, it is the technology infusion process that actually causes changes in the current state of the practice.

1989

The purpose of the grant is to study systems engineering methodologies in light of changing environments and changing needs. The results of this investigation are to be used to identify and validate new methodologies with potential applications to NASA's systems life-cycle planning processes. The study was designed to have two phases: Phase One, completed in November 1988 was a study of NASA's systems projects and the need for systems engineering methodologies; and Phase Two, this phase, involved evaluating methodologies, tools, and techniques with potential for application to NASA's systems projects, and making recommendations to NASA. This study is sponsored and managed by the Networks Division (ND) of the Mission Operations and Data Systems Directorate (MO&DSD). The primary methodology being used by the Division is described in the MO&DSD Systems Management Policy. This methodology, which has been developed for Directorate-wide application, has been evaluated with six others from government and industry for applicability to the ND's projects. ACKNO_rJI_(EI_8 The authors would like to thank the staff of the Networks Division, particularly the Network Control Systems Branch, for its cooperation and assistance throughout the effort. Special thanks to Mr. Adolph Goodson, National Aeronautics and Space Administration's (NASA's) Technical Officer, for his resourcefulness and dedication to the project. Thanks to Mr. Lee Saegesser, NASA's History Division and Ms. Monika Montgomery-Clingman of the Educational Publication Distribution Center for their assistance with information, including the identification of some not-so-obvious sources of data. Thanks also to the many speakers from industry and academia who participated and contributed to a series of very lively and enlightening seminars at Howard University and at Goddard Space Flight Center. A list of presenters for this phase of the project is presented in Appendix A. Very special thanks to Computer Sciences Corporation, Defense Systems Management College, Jet Propulsion Laboratory, HUGHES, Integrated Computer Systems, and the Center for Interactive Management for providing information on the methodologies being used by their professionals and/or their clients. Special thanks to Messrs. Charles Alleyne and Edwin Twum-Danzo and Misses Denise Caesar, Audrey Gates, and Serita Sanders [Graduate Students in the School of Engineering, Howard University] for their enthusiastic support with the acquisition and review of documents and compilation of the background information.

Blekinge Institute of Technology, 2009

Developing software for high-dependable space applications and systems is a formidable task. With new political and market pressures on the space industry to deliver more software at a lower cost, optimization of their methods and standards need to be investigated.

Advanced Software and Control for Astronomy II, 2008

Software development for the Chandra X-ray Center Data System began in the mid 1990's, and the waterfall model of development was mandated by our documents. Although we initially tried this approach, we found that a process with elements of the spiral model worked better in our science-based environment. High-level science requirements are usually established by scientists, and provided to the software development group. We follow with review and refinement of those requirements prior to the design phase. Design reviews are conducted for substantial projects within the development team, and include scientists whenever appropriate. Development follows agreed upon schedules that include several internal releases of the task before completion. Feedback from science testing early in the process helps to identify and resolve misunderstandings present in the detailed requirements, and allows review of intangible requirements. The development process includes specific testing of requirements, developer and user documentation, and support after deployment to operations or to users. We discuss the process we follow at the Chandra X-ray Center (CXC) to develop software and support operations. We review the role of the science and development staff from conception to release of software, and some lessons learned from managing CXC software development for over a decade.

Dynamics of Long-Life Assets, 2017

This chapter describes the Space cluster use case using the innovative Space Tug project as an example. It provides an overview of the objectives (customer in the loop, quicker technical response) and related methods to support foreseen improvements through a dedicated toolchain. The IT infrastructure used for the demonstration is used as an enabling and demonstrative system with a focus on modelling and collaboration aspects, as outlined in Chapter "Extending the System Model", on the flow of information, and on tool infrastructure and project costs. Descriptions of the developed tools are as follows: • A web-based toolchain that includes functional analysis, discipline analysis, 3D modelling and virtual reality for project team collaboration. • A workflow manager for collaboration between different companies. • Small devices called 'probes' to ensure security and data protection in intercompany collaboration. • A configurable customer front-end to ensure that the customer remains informed.

2015

This paper describes the approach used by Oerl ikon Aerospace since 1993 to define and implement software and systems engineering processes: First, the steps taken to assess and define a software process are described using the Software Engineering

IEEE Software, 2000