Reliability Analysis of Complex NASA Systems with Model-Based Engineering

The emergence of model-based engineering, with Model- Based Systems Engineering (MBSE) leading the way, is transforming design and analysis methodologies. The recognized benefits to systems development include moving from document-centric information systems and document-centric project communication to a model-centric environment in which control of design changes in the life cycles is facilitated. In addition, a single source of truth about the system, that is up-to-date in all respects of the design, becomes the authoritative source of data and information about the system. This promotes consistency and efficiency in regard to integration of the system elements as the design emerges and thereby may further optimize the design. Therefore Reliability Engineers (REs) supporting NASA missions must be integrated into model-based engineering to ensure the outputs of their analyses are relevant and value-needed to the design, development, and operational processes for failure risks assessment and communication

Deep Learning Relevance: Creating Relevant Information (as Opposed to Retrieving it)

What if Information Retrieval (IR) systems did not just retrieve relevant information that is stored in their indices, but could also "understand" it and synthesise it into a single document? We present a preliminary study that makes a first step towards answering this question. Given a query, we train a Recurrent Neural Network (RNN) on existing relevant information to that query. We then use the RNN to "deep learn" a single, synthetic, and we assume, relevant document for that query. We design a crowdsourcing experiment to assess how relevant the "deep learned" document is, compared to existing relevant documents. Users are shown a query and four wordclouds (of three existing relevant documents and our deep learned synthetic document). The synthetic document is ranked on average most relevant of all.Comment: Neu-IR '16 SIGIR Workshop on Neural Information Retrieval, July 21, 2016, Pisa, Ital

GCS programmer's manual

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities

Design guide for high pressure oxygen systems

A repository for critical and important detailed design data and information, hitherto unpublished, along with significant data on oxygen reactivity phenomena with metallic and nonmetallic materials in moderate to very high pressure environments is documented. This data and information provide a ready and easy to use reference for the guidance of designers of propulsion, power, and life support systems for use in space flight. The document is also applicable to designs for industrial and civilian uses of high pressure oxygen systems. The information presented herein are derived from data and design practices involving oxygen usage at pressures ranging from about 20 psia to 8000 psia equal with thermal conditions ranging from room temperatures up to 500 F

Solar Splash Senior Design Project

Indiana University Purdue University IndianapolisThe Solar Splash senior project is the first attempt at creating an entirely solar propelled watercraft. The initial project intent was to design and create a supplement meets the specifications and compete in the competition. With this in mind, a budget approach was taken in order to be able to fund the task at hand. As the project progressed toward the end of the low-level design phase it was evident that the competition would not occur. At the midpoint of the project, the goals and objectives had changed entirely. The new focus was targeted at proving the operation of the systems involved in the watercraft. Having been faced with a new series of objectives and an entirely new scope, the project began to appear doable. The primary focus of the project at this point entirely relied on simulation data and data analysis. The idea was not reinventing the wheel but rather verifying that the wheel rolled. Using the designed propulsion, solar and sensors systems, with the help of a combination of software programs, the idea of a budget solution can be seen. The software used tell the story of the boat that would have been created had the project continued down the original proposed path. As systems were tested and analyzed, they were also adjusted and improved upon. The analysis process consumed a lot of time but acted as a highlighter for all the flaws that the system suffered from. This document introduces the design concepts and schematics of the Solar Splash senior design project. Within are detailed drawings and diagrams for the electrical systems devised for the construction operation of the watercraft. This report is a means of displaying the layout of the final product and how all systems tie together. The report will contain detailed information on not only hardware aspects but also software and how those will bridge together. The report is meant to be in layman’s terms and should be easily interpreted at all levels. The bulk of the information found in the report will be found in the testing sections where analysis of a theoretical boat is done. The motor design, solar design, and fluid dynamic analysis of the boat hull and propeller can be found in their respective section. The innerworkings, testing processes and thoughts behind each decision can also be found in these sections. The document begins with a table of contents identifying each main and subcategory of information. The next page is the document identification, revision history, and lesser known definitions. Following that is the introduction and scope. Specification requirements for the ‘general requirements’, ‘electrical requirements’ and ‘mechanical requirements’ are found on the following page. A system flowchart can be found in the high-level Design along with the design decision matrices for each system. The design portion then begins starting with the System-wide design changes and decisions. The hardware and software designs and schematics follow and cover the proposed schematics and drawings for the system. Cost breakdowns for each individual system are also found in the low-level section. Testing methodologies, results and an explanation of the testing software can be found after the low-level design. A summation of all these testing results is found near the tail of the document. Conclusions, recommendations, and appendixes can be found as the last three sections, respectively.Electrical Engineering Technolog

DOCUMENT PROCESSING IN THE AUTOMATED OFFICE: IMPLICATIONS FOR MIS RESEARCH AND EDUCATION

Document processing is an integral part of the automated office. Because document-based information systems are composed largely of unstructured text as opposed to structured data, the techniques which have been successfully applied to the design of current database systems are not adequate for the design of office information systems. The paper identifies issues related to the storage and retrieval of office documents, and the management of information in the automated office. Strategies for broadening MIS research and education to address these issues are suggested

The approach to the design of information systems document management in public administration

Розглянуті підходи та принципи проектування інформаційних систем документообігу для органів державного управління. Описана методика дослідження предметної облас-ті, запропонована модель документообігу в розподіленій системі, розроблена концепція визначення інформаційних характеристик документів. Запропонований підхід формалі-зує процес проектування інформаційних систем діловодства. Наведено приклад запро-вадженої системи, проектування якої здійснено з використанням цього підходу.Approach to development workflow information systems for Government bodies activity is described. Method to research the workflow field is considered, workflow model for distrib-uted systems is suggested, conception for information documents characteristics is developed. Suggested approach formalizes the information system development. The example running system is presented. Its development was based on this approach

Entropy as a Measure of Quality of XML Schema Document

In this paper, a metric for the assessment of the structural complexity of eXtensible Markup Language schema document is formulated. The present metric ‘Schema Entropy is based on entropy concept and intended to measure the complexity of the schema documents written in W3C XML Schema Language due to diversity in the structures of its elements. The SE is useful in evaluating the efficiency of the design of Schemas. A good design reduces the maintainability efforts. Therefore, our metric provides valuable information about the reliability and maintainability of systems. In this respect, this metric is believed to be a valuable contribution for improving the quality of XML-based systems. It is demonstrated with examples and validated empirically through actual test cases