Software system safety

Software itself is not hazardous, but since software and hardware share common interfaces there is an opportunity for software to create hazards. Further, these software systems are complex, and proven methods for the design, analysis, and measurement of software safety are not yet available. Some past software failures, future NASA software trends, software engineering methods, and tools and techniques for various software safety analyses are reviewed. Recommendations to NASA are made based on this review

Misalignment estimation software system

A system of computer software, spacecraft, and ground system activity is described that enables spacecraft startrackers and inertial assemblies to be aligned and calibrated from the ground after the spacecraft has achieved orbit. The system generates in the uplink flow an exercise designed to render misalignments visible, and sends the exercise to the spacecraft where the spacecraft inserts the misalignment into the information in the form of attitude sensor error. The information is downlinked for processing into misalignment estimates to be used for correcting spacecraft model at data base

The Expert System Software Application on Lecture Scheduling Based on Rule Based Reasoning

Method of Rule-Based Reasoning is one of the methods in decision support systems that may have had knowledge base. In this method of solving problems based on an artificial intelligence approach using problem-solving techniques based on the rules contained in the knowledge base that can solve the problem sequentially. With the approach, some rules that have been produced can be re-examined by an expert to be able to be repaired or modified to obtain better results. In addition, this method is also used when needed explanation of traces (steps) in getting an achievement of a solution. Research done is to build a knowledge base representation system using Rule-Based Reasoning. Implementation of the system was built using a desktop-based application

Software system integration - Middleware - an overview

The integration of different softwares written in different language and based on different platforms can be tricky. In that situation a middleware is necessary to enable the communication between different softwares. The middleware enables the software system not only to share data but also share the services. This paper gives an overview of some of middleware technologies which can be used to integrate different software systems

A MANAGED APPROACH OF INTERACTION BETWEEN AGILE SCRUM AND SOFTWARE CONFIGURATION MANAGEMENT SYSTEM

In current age the agile software development is one of the most popular software development methodology but due the mismanagement and lack of efficient handling of agile scrum and software configuration management system our software industry is facing a high rate of failed product, keeping this as my motivation, I have designed a efficient checklist which will help the industry to organized the interaction between agile scrum process and software configuration management system in a efficient and managed way and definitely that will increase the successful project in the software industry. Index-term : Agile Scrums, Software development, Software configuration management system, Checklist, Successful project

Knowledge-based reusable software synthesis system

The Eli system, a knowledge-based reusable software synthesis system, is being developed for NASA Langley under a Phase 2 SBIR contract. Named after Eli Whitney, the inventor of interchangeable parts, Eli assists engineers of large-scale software systems in reusing components while they are composing their software specifications or designs. Eli will identify reuse potential, search for components, select component variants, and synthesize components into the developer's specifications. The Eli project began as a Phase 1 SBIR to define a reusable software synthesis methodology that integrates reusabilityinto the top-down development process and to develop an approach for an expert system to promote and accomplish reuse. The objectives of the Eli Phase 2 work are to integrate advanced technologies to automate the development of reusable components within the context of large system developments, to integrate with user development methodologies without significant changes in method or learning of special languages, and to make reuse the easiest operation to perform. Eli will try to address a number of reuse problems including developing software with reusable components, managing reusable components, identifying reusable components, and transitioning reuse technology. Eli is both a library facility for classifying, storing, and retrieving reusable components and a design environment that emphasizes, encourages, and supports reuse

Small business preference for software package

Until late 2016, the majority of small business uses QuickBooks and Excel to do their accounting work. However, the functions of these accounting tools are insufficient, and also the demands of companies are increasing. It has become inefficient and antiquated to use the software. A small business looked for new accounting software, but found that choosing an accounting software system is not straightforward, as every software package consists of different functions for users. The aim of this research was to analyse small business’ perceptions and preferences for accounting software systems in New Zealand. This is followed by an analysis of why users might want to replace their previous accounting software systems. In addition, the requirements for selecting accounting software were analysed. The main method used was qualitative research. Three people were interviewed regarding the reason for replacing their previous accounting software system. The first interviewee had not changed their accounting software system previously, but their reason for replacing their current accounting software system was that their previous accounting software system lacked the functionality he wanted. The second interviewee said e she disliked that the system frequently crashed and that it lacked the features she wanted. The reason why the last interviewee changed her previous accounting software system was that MYOB system could not improve her work efficiency