Design of the software development and verification system (SWDVS) for shuttle NASA study task 35

An overview of the Software Development and Verification System (SWDVS) for the space shuttle is presented. The design considerations, goals, assumptions, and major features of the design are examined. A scenario that shows three persons involved in flight software development using the SWDVS in response to a program change request is developed. The SWDVS is described from the standpoint of different groups of people with different responsibilities in the shuttle program to show the functional requirements that influenced the SWDVS design. The software elements of the SWDVS that satisfy the requirements of the different groups are identified

A Framework for Evaluating Model-Driven Self-adaptive Software Systems

In the last few years, Model Driven Development (MDD), Component-based Software Development (CBSD), and context-oriented software have become interesting alternatives for the design and construction of self-adaptive software systems. In general, the ultimate goal of these technologies is to be able to reduce development costs and effort, while improving the modularity, flexibility, adaptability, and reliability of software systems. An analysis of these technologies shows them all to include the principle of the separation of concerns, and their further integration is a key factor to obtaining high-quality and self-adaptable software systems. Each technology identifies different concerns and deals with them separately in order to specify the design of the self-adaptive applications, and, at the same time, support software with adaptability and context-awareness. This research studies the development methodologies that employ the principles of model-driven development in building self-adaptive software systems. To this aim, this article proposes an evaluation framework for analysing and evaluating the features of model-driven approaches and their ability to support software with self-adaptability and dependability in highly dynamic contextual environment. Such evaluation framework can facilitate the software developers on selecting a development methodology that suits their software requirements and reduces the development effort of building self-adaptive software systems. This study highlights the major drawbacks of the propped model-driven approaches in the related works, and emphasise on considering the volatile aspects of self-adaptive software in the analysis, design and implementation phases of the development methodologies. In addition, we argue that the development methodologies should leave the selection of modelling languages and modelling tools to the software developers.Comment: model-driven architecture, COP, AOP, component composition, self-adaptive application, context oriented software developmen

Sophisticated software systems for small self-contained space shuttle payload G285

The increasing development of small microprocessor systems has allowed the use of more advanced software in the area of control systems. This paper discusses the development of software for small Space Shuttle Getaway Special Project payloads using payload G285 as a case example. The development process behind a space related software package (as in any software package) is a major factor. The design process for G285 is discussed in some detail along with the general scheme behind data acquisition and thermal environmental control for a space related payload. Additionally, key concepts in a software system concern the implementation of redundant systems, error detection, and error response. All of these factors are discussed

NorthStar, a support tool for the design and evaluation of quality improvement interventions in healthcare

Background: The Research-Based Education and Quality Improvement (ReBEQI) European partnership aims to establish a framework and provide practical tools for the selection, implementation, and evaluation of quality improvement (QI) interventions. We describe the development and preliminary evaluation of the software tool NorthStar, a major product of the ReBEQI project. Methods: We focused the content of NorthStar on the design and evaluation of QI interventions. A lead individual from the ReBEQI group drafted each section, and at least two other group members reviewed it. The content is based on published literature, as well as material developed by the ReBEQI group. We developed the software in both a Microsoft Windows HTML help system version and a web-based version. In a preliminary evaluation, we surveyed 33 potential users about the acceptability and perceived utility of NorthStar. Results: NorthStar consists of 18 sections covering the design and evaluation of QI interventions. The major focus of the intervention design sections is on how to identify determinants of practice (factors affecting practice patterns), while the major focus of the intervention evaluation sections is on how to design a cluster randomised trial. The two versions of the software can be transferred by email or CD, and are available for download from the internet. The software offers easy navigation and various functions to access the content. Potential users (55% response rate) reported above-moderate levels of confidence in carrying out QI research related tasks if using NorthStar, particularly when developing a protocol for a cluster randomised trial Conclusion: NorthStar is an integrated, accessible, practical, and acceptable tool to assist developers and evaluators of QI interventions

A preliminary design and implementation of the low-thrust simulation and trajectory search program (LOWTRAJ)

The results are presented of one phase of research conducted for the JPL Solar Electric Propulsion (SEP) Navigation Software System development program. It deals only with the problem of designing the flight quality trajectory program, which is a major subset of the entire navigation software system. In this phase of research (breadboard development phase), attempts were made to assess the SEP trajectory software functional requirements, to investigate the program design method satisfying these requirements, to identify the primary anticipated problem areas, and to provide solutions to these problem areas. These efforts culminated in the development of a compact breadboard program. A functional description and the mathematical formulation of the program are presented

A dashboard-based approach for efficient requirements change management

Requirements gathering and documentation are important first steps for a successful software engineering project. The documented requirements act as a guideline for design and development of software products. Requirements also represent customer expectations for the end product. Since these documented requirements serve important purposes for many stakeholders, managing requirement changes effectively plays a major role in the overall success of any project. Changes in requirements are very common in software engineering and can occur during any phase of software development lifecycle (SDLC). Though the impact of requirement changes differs depending on the SDLC phase in which it occurred, there is almost always a setback that happens in terms of the project timeline. This scenario is common in projects that follow both Agile/Scrum methodology and ones that follow the more traditional Waterfall model. In this report, I will first present two case studies of how requirement changes impacted the timelines of two projects (one following Agile/Scrum methodology and another following Waterfall methodology). In the second part of this report, I will propose and design a user-friendly dashboard, which could be used to speed up the delays caused by changing requirements.Electrical and Computer Engineerin

Use of an agile bridge in the development of assistive technology

Engaging with end users in the development of assistive technologies remains one of the major challenges for researchers and developers in the field of accessibility and HCI. Developing usable software systems for people with complex disabilities is problematic, software developers are wary of using user-centred design, one of the main methods by which usability can be improved, due to concerns about how best to work with adults with complex disabilities, in particular Severe Speech and Physical Impairments (SSPI) and how to involve them in research. This paper reports on how the adoption of an adapted agile approach involving the incorporation of a user advocate on the research team helped in meeting this challenge in one software project and offers suggestions for how this could be used by other development teams