Guidance, navigation, and control subsystem equipment selection algorithm using expert system methods

Enhanced engineering tools can be obtained through the integration of expert system methodologies and existing design software. The application of these methodologies to the spacecraft design and cost model (SDCM) software provides an improved technique for the selection of hardware for unmanned spacecraft subsystem design. The knowledge engineering system (KES) expert system development tool was used to implement a smarter equipment section algorithm than that which is currently achievable through the use of a standard data base system. The guidance, navigation, and control subsystems of the SDCM software was chosen as the initial subsystem for implementation. The portions of the SDCM code which compute the selection criteria and constraints remain intact, and the expert system equipment selection algorithm is embedded within this existing code. The architecture of this new methodology is described and its implementation is reported. The project background and a brief overview of the expert system is described, and once the details of the design are characterized, an example of its implementation is demonstrated

The crustal dynamics intelligent user interface anthology

The National Space Science Data Center (NSSDC) has initiated an Intelligent Data Management (IDM) research effort which has, as one of its components, the development of an Intelligent User Interface (IUI). The intent of the IUI is to develop a friendly and intelligent user interface service based on expert systems and natural language processing technologies. The purpose of such a service is to support the large number of potential scientific and engineering users that have need of space and land-related research and technical data, but have little or no experience in query languages or understanding of the information content or architecture of the databases of interest. This document presents the design concepts, development approach and evaluation of the performance of a prototype IUI system for the Crustal Dynamics Project Database, which was developed using a microcomputer-based expert system tool (M. 1), the natural language query processor THEMIS, and the graphics software system GSS. The IUI design is based on a multiple view representation of a database from both the user and database perspective, with intelligent processes to translate between the views

Object-Oriented Software Representation of Polymer Materials Information in Engineering Design

The software application POISE, Polymer Objects in a Smalltalk™ Environment, integrates knowledge representation, user interfaces, and data management; a system of tools for the materials domain expert involved in design. Engineering design solutions initially build from generalisations. POISE represents multiple levels of generalisations from classifications of polymer information. The class-instance paradigm classifies software objects. An object’s behaviour is an exclusive function of its class. Polymer’s behaviours are a function of multiple orthogonal factors, like chemistry and processing, therefore multiple orthogonal classes must represent polymers. Taxonomy only represents one of these factors. The Enhancer mechanism resolves this conflict between classification and representation. Polymer classification is not well established, with new materials evolving. The software compensates by evolving the classification schema. Guided with a specialised interface tool, the domain expert updates the schema by adding new polymer families and re-classifying existing classes. Through analysing the generalisations in the classification, the domain expert can develop an appropriate classification. This analysis relies on the engineering properties differentiating the principal material qualities. Standard properties do not distinguish specific structural differences in polymer materials, necessitating new properties. Material properties distinguish materials in the domain whereas the classes describe the properties of polymer objects. Domain experts add new properties to the polymer classes to distinguish polymer objects. Properties are independent objects that partially describe the class template; Partial Template Objects. Persistence of personal design information and management of shared data requires dichotomous database management. Shared data requires multi-user access, and consequently transaction management. Transaction management in object-oriented systems often holds resources for a long duration. Transaction declaration hinders transparent access to storage, and corrupts the representation. For single-user design information, transactions are implicit with access. Database proxies provide transparent per-object transaction management to persistent design information. The WorkBase is an object-storage utility that utilises Enhancers as proxies

A Design Support System for Crew System Automation

[[abstract]]The authors present a structured design methodology for automation requirements analysis, specification, prototype design, and product development, and describe the design and software implementation of a design support system for crew system automation that incorporates multidisciplinary computer-aided design and engineering procedures, tools, databases, and models. Future enhancements that impact the effectiveness and efficiency of designs produced using such a computer-aided engineering tool are discussed and contrasted with the labor-intensive manual methods of today. The major benefits of the design process and design support tools are summarized. Particular attention is given to the use of the modified Petri-net formalism. The capability of the expert model-based design methodology and the prototype design support systems to produce a superior crew system design are currently being demonstrated and evaluated in conjunction with a full-mission manned system simulation[[fileno]]2020419030008[[department]]工工

A model of software component interactions using the call graph technique

Interaction information that is related to operations between components is important, especially when the program needs to be modified and maintained. Therefore, the affected components must be identified and matched based on the requirement of the system. This information can be obtained through performing the code review technique, which requires an analyst to search for specific information from the source code, which is a very time consuming process. This research proposed a model for representing software component interactions where this information was automatically extracted from the source code in order to provide an effective display for the software components interaction representation. The objective was achieved through applying a research design methodology, which consists of five phases: awareness of the problem, suggestion, development, evaluation, and conclusion. The development phase was conducted by automatically extracting the components‘ interaction information using appropriate reverse engineering tools and supporting programs that were developed in this research. These tools were used to extract software information, extract the information of component interactions in software programs, and transform this information into the proposed model, which was in the form of a call graph. The produced model was evaluated using a visualization tool and by expert review. The visualization tool was used to display the call graph from a text format into a graphical view. The processed model evaluation was conducted through an expert review technique. The findings from the model evaluation show that the produced model can be used and manipulated to visualize the component interactions. It provides a process that allows a visualization display for analysts to view the interaction of software components in order to comprehend the components integrations that are involved. This information can be manipulated and improved the program comprehension, especially for other software maintenance purposes

The Disciplined Use of Simplifying Assumptions

Submitted to the ACM SIGSOFT Second Software Engineering Symposium: Workshop on Rapid Prototyping. Columbia, Maryland, April 19-21, 1982.Simplifying assumptions — everyone uses them but no one's programming tool explicitly supports them. In programming, as in other kinds of engineering design, simplifying assumptions are an important method for dealing with complexity. Given a complex programming problem, expert programmers typically choose simplifying assumptions which, though false, allow them to arrive rapidly at a program which addresses the important features of the problem without being distracted by all of its details. The simplifying assumptions are then incrementally retracted with corresponding modifications to the initial program. This methodology is particularly applicable to rapid prototyping because the main questions of interest can often be answered using only the initial program. Simplifying assumptions can easily be misused. In order to use them effectively two key issues must be addressed. First, simplifying assumptions should be chosen which simplify the design problems significantly without changing the essential character of the program which needs to be implemented. Second, the designer must keep track of all the assumptions he is making so that he can later retract them in an orderly manner. By explicitly dealing with these issues, a programming assistant system could directly support the use of simplifying assumptions as a disciplined part of the software development process.MIT Artificial Intelligence Laborator

Human Reliability Analysis using a Human Factors Hazard Model

Human Reliability Analysis (HRA) has found application within a diverse set of engineering domains, but the methods used to apply HRA are often complicated, time-consuming, costly to apply, specific to particular (i.e., nuclear) applications, and are not suitable for direct comparison amongst themselves. This paper proposes a Human Factors Hazard Model (HFHM), which builds an HRA method from the tools of Fault Tree Analysis (FTA), Event Tree Analysis (ETA), and a novel model of considering serial Human Error Probability (HEP) more relevant to psychomotor-intensive industrial and commercial applications such as manufacturing, teleoperation, and vehicle operation. The HEP approach uses Performance Shaping Factors (PSFs) relevant to human behavior, as well as specific characteristics unique to a system architecture and its corresponding operational behavior. The HFHM tool is intended to establish a common analysis approach, to simplify and automate the modeling of the likelihood of a mishap due to a human-system interaction during a hazard event. The HFHM is executed commercial software tools (MS Excel and SysML) such that trade and sensitivity studies can be conducted and iterated automatically. The results generated by the HFHM can be used to guide risk assessment, safety requirements generation and management, design options, and safety controls within the system design architecting process. Verification and evaluation of the HFHM through simulation and subject matter expert evaluation illustrate the value of the HFHM as a tool for HRA and system safety analysis in a set of key industrial applications

Reusability Challenges of Scientific Workflows: A Case Study for Galaxy

Scientific workflow has become essential in software engineering because it provides a structured approach to designing, executing, and analyzing scientific experiments. Software developers and researchers have developed hundreds of scientific workflow management systems so scientists in various domains can benefit from them by automating repetitive tasks, enhancing collaboration, and ensuring the reproducibility of their results. However, even for expert users, workflow creation is a complex task due to the dramatic growth of tools and data heterogeneity. Thus, scientists attempt to reuse existing workflows shared in workflow repositories. Unfortunately, several challenges prevent scientists from reusing those workflows. In this study, we thus first attempted to identify those reusability challenges. We also offered an action list and evidence-based guidelines to promote the reusability of scientific workflows. Our intensive manual investigation examined the reusability of existing workflows and exposed several challenges. The challenges preventing reusability include tool upgrading, tool support unavailability, design flaws, incomplete workflows, failure to load a workflow, etc. Such challenges and our action list offered guidelines to future workflow composers to create better workflows with enhanced reusability. In the future, we plan to develop a recommender system using reusable workflows that can assist scientists in creating effective and error-free workflows.Comment: Accepted in APSEC 202

A new model for the development of information systems

The most commonly used systems specification and design techniques in commercial computing are described and compared; Information Engineering as proposed by James Martin, A Framework for Information Definition-Muitiview proposed by Wood-Harper et al, Real-world Modeling as described by Jackson, Structured Analysis and Design as In Demarco, Yourdon and Constantine and Output-Oriented Structured Requirement Definition proposed by Orr. In addition, system prototyping is discussed, including the role of prototyping in large software development projects and as a tool for the design of human-computer interfaces. Other areas described and discussed include decision support systems (DSS) and knowledge based management support systems. The context is in the design and development approaches for DSS, prototyping for DSS, expert system for DSS and the integration of DSS and information system. The design and development of human-computer interface is also discussed in relation to user Interface complexity and adaptive interfaces. Further, the important issue of user involvement and support within the development process Is discussed. Thus, weaknesses of current approaches to the system development process are identified and a new model for the development of information system is proposed. In proposing the model, data and functional analysis structured method and methodology for decision support systems (DSS) development is presented including guidelines for the development of knowledge based DSS. The new proposed model is put to test in the design, development and implementation of large integrated commercial systems including DSS. Results and discussion on the use of the model is reported with special consideration to the users' and developers' view of the model. Finally the objectives of this research program are examined in relation to what has been achieved during this program of research. The prospect of using the model for the development of information systems are concluded with references to current and future goals

Specifications and Development of Interoperability Solution dedicated to Multiple Expertise Collaboration in a Design Framework

This paper describes the specifications of an interoperability platform based on the PPO (Product Process Organization) model developed by the French community IPPOP in the context of collaborative and innovative design. By using PPO model as a reference, this work aims to connect together heterogonous tools used by experts easing data and information exchanges. After underlining the growing needs of collaborative design process, this paper focuses on interoperability concept by describing current solutions and their limits. Then a solution based on the flexibility of the PPO model adapted to the philosophy of interoperability is proposed. To illustrate these concepts, several examples are more particularly described (robustness analysis, CAD and Product Lifecycle Management systems connections)