TAE Plus: Transportable Applications Environment Plus tools for building graphic-oriented applications

The Transportable Applications Environment Plus (TAE Plus), developed by NASA's Goddard Space Flight Center, is a portable User Interface Management System (UIMS), which provides an intuitive WYSIWYG WorkBench for prototyping and designing an application's user interface, integrated with tools for efficiently implementing the designed user interface and effective management of the user interface during an application's active domain. During the development of TAE Plus, many design and implementation decisions were based on the state-of-the-art within graphics workstations, windowing system and object-oriented programming languages. Some of the problems and issues experienced during implementation are discussed. A description of the next development steps planned for TAE Plus is also given

Actionbase system for manufacturing control

A modern computerized manufacturing control system must manage production data, coordinate control actions, and provide user-friendly interfaces. An actionbase management system (ABMS) is a general software system that facilitates implementations of actionbase systems that provide these capabilities for different applications. Besides an ordinary data management facility, our ABMS includes action control and user interface subsystems implemented as active object systems (AOSs). An AOS is a transition-based object-oriented system suitable for the design of various concurrent systems. The behavior of each active object is defined by the transition rules, the equational assignment statements, and the event routines provided in its class definition. An active object can be constructed from its component active objects through structural composition as if it were a hardware object. The user interface management subsystem of the ABMS allows us to provide declarative descriptions of views for active objects. These views provide user interfaces for an actionbase system.Key Words and Phrases: manufacturing control, flexible manufacturing system, actionbase system, active-object system, software IC, object-oriented concurrent system, graphical user interface, active-object user interface

Control and monitoring of flexible manufacturing systems with active-object user-interface management system

To achieve the maximum benefits of a flexible manufacturing system (FMS), its effec­tive monitoring is crucial. The user's ability to interpret the actions of an FMS is signifi­cantly enhanced by effective monitoring provided by a well-designed graphical user interface (GUI). The Active-Object User-Interface Management System (AOUIMS) is a graphical user interface management system (GUIMS) for structural active-object systems (SAOSs), which are transition-baed object-oriented systems. AOUIMS is suitable for implementing GUIs for concurrent systems including FMSs. The implementation of AOUIMS follows the SAOS approach, supporting active user-interface objects (AUIOs) that can be structurally and hierarchically composed from their component AUIOs. A GUI built with AOUIMS can be easily integrated with the control program of an FMS implemented as a SAOS, allowing a GUI that effectively monitors an FMS to be quickly constructed.Key Words and Phrases: user interface management system, graphical user interface, active object system, structural composition, hierarchical composition, object composition, software IC, transition rul

ARGES: an Expert System for Fault Diagnosis Within Space-Based ECLS Systems

ARGES (Atmospheric Revitalization Group Expert System) is a demonstration prototype expert system for fault management for the Solid Amine, Water Desorbed (SAWD) CO2 removal assembly, associated with the Environmental Control and Life Support (ECLS) System. ARGES monitors and reduces data in real time from either the SAWD controller or a simulation of the SAWD assembly. It can detect gradual degradations or predict failures. This allows graceful shutdown and scheduled maintenance, which reduces crew maintenance overhead. Status and fault information is presented in a user interface that simulates what would be seen by a crewperson. The user interface employs animated color graphics and an object oriented approach to provide detailed status information, fault identification, and explanation of reasoning in a rapidly assimulated manner. In addition, ARGES recommends possible courses of action for predicted and actual faults. ARGES is seen as a forerunner of AI-based fault management systems for manned space systems

User interface system based on active objects

An active-object user interface system (AOUIS) is a user interface system implemented as an active object system (AOS). An AOS is a transition-based object-oriented system suitable for the design of various concurrent systems. In an AOUIS, user interface objects, which are sometimes called "widgets", are represented as active user interface objects (AUIOs). The behavior of an AUIO is defined by the transition rules, the equational assignment statements, and the event routines provided in its class definition. Furthermore, an AUIO can be constructed from its component AUIOs through structural composition as ifit were a hardware object. Thus, AUIOs are better encapsulated and provide more flexible communication protocols than ordinary user interface objects. In addition, declarative descriptions of multiple views can be provided for each AUIO.Key Words and Phrases : user interface management system, active object system, production system, structural composition, software IC, subject/view

A human-machine interaction tool set for Smalltalk 80.

This research represents an investigation into user acceptance of computer systems. It starts with the premise that existing systems do not fully meet user requirements, and are therefore rejected as 'difficult to use'. Various problems and influences affecting user acceptance are identified, and improvements are suggested. Although a broad range of factors affecting user acceptance are discussed, emphasis is given to the impact of actual computer software.Initially, both general and specific user interface software influences are examined, and it is shown how these needs can be met using new software technology. A new Intelligent Interface architecture model is presented, and comparisons are made to existing interface design approaches.Secondly, the role of empirical work within the field of Human Computer Interaction is highlighted. An investigation into the usability and user. acceptance of a large working library database system is described, and the results discussed. The role of Systems Analysis and Design and its effect upon user acceptance is also explored. It is argued that despite improvements in interface technology and related software engineering techniques, a software application is also a product of the Systems Analysis and Design process. Traditional Systems Design approaches are examined, and suitable improvements suggested based upon experience with emerging separable software architectures.Thirdly, the research proceeds to examine the potential of Quantitative User Modelling, and describes the implementation of an example object oriented Quantitative User Model. This is then evaluated in order to determine new knowledge, concerning the major issues surrounding the potential application of user modelling to interface design.Finally, attention is given to the concept of interface and application separation. An object oriented User Interface Management System is presented, and its implementation in the Smalltalk 80 programming language discussed. The proposed User Interface Management System utilises a new software architecture which provides explicit user interface separation, using the concept of a Pluggable View Controller. It also incorporates an integrated design Tool-set for Direct Manipulation interfaces. The proposed User Interface Management System and software architecture represents the major contribution of this project to the growing body of Human Computer Interaction research. In particular, the importance of explicit interface separation is established, and the proposed software architecture is critically evaluated to determine new knowledge concerning the requirements, constraints, and potential of proper user interface separation. The implementation of an object oriented Part Hierarchy mechanism is also presented. This mechanism is related to the proposed User Interface Management System, and is critically evaluated in order to add to the body of knowledge concerning object oriented systems

DAS: a data management system for instrument tests and operations

The Data Access System (DAS) is a metadata and data management software system, providing a reusable solution for the storage of data acquired both from telescopes and auxiliary data sources during the instrument development phases and operations. It is part of the Customizable Instrument WorkStation system (CIWS-FW), a framework for the storage, processing and quick-look at the data acquired from scientific instruments. The DAS provides a data access layer mainly targeted to software applications: quick-look displays, pre-processing pipelines and scientific workflows. It is logically organized in three main components: an intuitive and compact Data Definition Language (DAS DDL) in XML format, aimed for user-defined data types; an Application Programming Interface (DAS API), automatically adding classes and methods supporting the DDL data types, and providing an object-oriented query language; a data management component, which maps the metadata of the DDL data types in a relational Data Base Management System (DBMS), and stores the data in a shared (network) file system. With the DAS DDL, developers define the data model for a particular project, specifying for each data type the metadata attributes, the data format and layout (if applicable), and named references to related or aggregated data types. Together with the DDL user-defined data types, the DAS API acts as the only interface to store, query and retrieve the metadata and data in the DAS system, providing both an abstract interface and a data model specific one in C, C++ and Python. The mapping of metadata in the back-end database is automatic and supports several relational DBMSs, including MySQL, Oracle and PostgreSQL.Comment: Accepted for pubblication on ADASS Conference Serie

Flight dynamics software in a distributed network environment

As with all NASA facilities, the announcement of reduced budgets, reduced staffing, and the desire to implement smaller/quicker/cheaper missions has required the Agency's organizations to become more efficient in what they do. To accomplish these objectives, the FDD has initiated the development of the Flight Dynamics Distributed System (FDDS). The underlying philosophy of FDDS is to build an integrated system that breaks down the traditional barriers of attitude, mission planning, and navigation support software to provide a uniform approach to flight dynamics applications. Through the application of open systems concepts and state-of-the-art technologies, including object-oriented specification concepts, object-oriented software, and common user interface, communications, data management, and executive services, the FDD will reengineer most of its six million lines of code

Object oriented databases in software development for structural analysis

A technique for using object-oriented technologies to write structural analysis software has been developed. The structural design information of an individual building is stored in an object-oriented database. A global database provides general design values as material data and safety factors. A class library for load elements has been evolved to model the transfer of loads in a building. This class library is the basis for the development of further classes for other structural elements such as beams, columns or slabs. A software has been developed to monitor the forces transferred from one structural member to another in a building for load cases and combinations according to Eurocode 1. The results of the analysis are stored in the projects database from which a structural design report may be generated. The software was developed under Microsoft Visual C++. The Microsoft Foundation Class Library (MFC) was used to program the Graphical User Interface (GUI). Object Linking and Embedding (OLE) technology is useful to include any type of OLE server objects for example texts written with a word processor or CAD drawings in the structural design report. The Object-Oriented Database Management System (OODBMS) ObjectStore provides services to store the large amount of objects

Visual interaction techniques for courseware production and presentation.

by Lam Shing Yung, Anton.Thesis (M.Phil.)--Chinese University of Hong Kong, 1991.Includes bibliographical references.Chapter I. --- Introduction --- p.1Chapter 1.1. --- Motivations for Presentation System --- p.2Chapter 1.2. --- Shortcomings of Traditional Method --- p.2Chapter 1.3. --- Computerized Courseware Production and Presentation System --- p.5Chapter 1.4. --- Hardware Advances --- p.7Chapter 1.5. --- "Windowed, Graphical Applications" --- p.9Chapter 1.6. --- Interaction Techniques --- p.10Chapter 1.7. --- Research Objectives --- p.12Chapter II. --- Existing Products and Related Research --- p.13Chapter 2.1. --- Existing Products --- p.13Chapter 2.1.1. --- PRESENT Slide Presentation System --- p.14Chapter 2.1.2. --- Harvard Graphics --- p.15Chapter 2.1.3. --- HyperCard --- p.15Chapter 2.1.4. --- Macromind Director --- p.16Chapter 2.1.5. --- Authorware Professional --- p.17Chapter 2.1.6. --- "PageMaker, Ventura and MacDraw" --- p.19Chapter 2.1.7. --- Summary --- p.20Chapter 2.2. --- Related Research --- p.20Chapter 2.2.1. --- Authoring Systems --- p.20Chapter 2.2.2. --- User Interface Management System (UIMS) --- p.23Chapter 2.2.3. --- Visual Programming --- p.24Chapter III. --- User's Model --- p.27Chapter 3.1. --- A Simple User's Model --- p.27Chapter 3.1.1. --- Object-0riented Presentation Material --- p.27Chapter 3.1.2. --- Frame -Based Presentation --- p.29Chapter 3.1.3. --- Presentation Styles --- p.29Chapter 3.2. --- Novice Users vs Experienced Users --- p.30Chapter IV. --- Design of the Courseware Production and Presentation System --- p.31Chapter 4.1. --- Overview --- p.31Chapter 4.2. --- Object Oriented Design --- p.31Chapter 4.3. --- Object Oriented Graphics --- p.31Chapter 4.3.1. --- Modification of Object --- p.32Chapter 4.3.2. --- Clipboard --- p.34Chapter 4.3.3. --- Stacking of Objects --- p.35Chapter 4.3.4. --- Group Together and Break Apart --- p.36Chapter 4.3.5. --- Hierarchy of Grouping --- p.38Chapter 4.3.6. --- Storage Requirements --- p.39Chapter 4.4. --- Operations --- p.39Chapter 4.4.1. --- Manipulative Operations --- p.39Chapter 4.4.2. --- Frame Control Operations --- p.39Chapter 4.4.3. --- Timer Operation --- p.40Chapter 4.5. --- Active-Object-Set Model --- p.40Chapter 4.5.1. --- Importance of Objects --- p.41Chapter 4.5.2. --- Active Object --- p.42Chapter 4.5.3. --- Active Set --- p.43Chapter 4.5.4. --- The Timer Event --- p.43Chapter 4.6. --- Properties of Visual Objects --- p.45Chapter 4.6.1. --- Physical Attributes --- p.45Chapter 4.6.1. --- Event-Handling Operations --- p.45Chapter 4.6.2. --- Private Status --- p.46Chapter 4.7. --- Object Class --- p.47Chapter 4.8. --- User-Defined Object Classes --- p.47Chapter 4.9. --- User-Defined Operations --- p.47Chapter V. --- Interaction Techniques for Defining New Object Classes and Operations --- p.49Chapter 5.1. --- Interaction Techniques --- p.49Chapter 5.2. --- Object Creation --- p.49Chapter 5.3. --- Operations --- p.51Chapter 5.3.1. --- Direct Manipulation --- p.51Chapter 5.3.2. --- Menu Selection --- p.51Chapter 5.3.3. --- Parameter Selection --- p.51Chapter 5.4. --- New Object Class Definition --- p.52Chapter 5.4.1. --- Definition through Drawing --- p.53Chapter 5.4.2. --- Creating New Object Instances of the New Object Classes --- p.54Chapter 5.5. --- New Operations Definition --- p.55Chapter 5.5.1. --- Specification of Parameter Type --- p.55Chapter 5.5.2. --- Selection and Sequencing of Primitive Operations …… --- p.57Chapter 5.5.3. --- Using the New Operations --- p.60Chapter 5.6. --- Binding of Operations to an Object --- p.61Chapter 5.7. --- Default Operations for User-Defined Classes --- p.63Chapter VI. --- Implementation Issues --- p.64Chapter 6.1. --- Operating Environment --- p.64Chapter 6.1.1. --- The User Interface --- p.64Chapter 6.1.2. --- The Operating System --- p.66Chapter 6.1.3. --- The Hardware Requirement --- p.66Chapter 6.1.4. --- The Final Choice --- p.67Chapter 6.2. --- Representation of Objects --- p.68Chapter 6.2.1. --- Basic Objects --- p.68Chapter 6.2.2. --- Group and User-Defined Objects --- p.69Chapter 6.2.3. --- Set of Active Objects --- p.70Chapter 6.3. --- Object-Oriented Graphics Management Subsystem --- p.71Chapter 6.4. --- Multiple Editing Window --- p.73Chapter 6.5. --- Clipboard --- p.73Chapter 6.6. --- Graphical Menu --- p.73Chapter 6.7. --- Font Management --- p.74Chapter 6.8. --- Mapping of the Active-Object-Set Model to the Implementation --- p.75Chapter 6.9. --- Representation of Operations --- p.76Chapter VII. --- Future Work and Conclusions --- p.79Chapter 7.1. --- Limitations --- p.79Chapter 7.1.1. --- Direct Manipulations --- p.79Chapter 7.1.2. --- Multiple Presentation Windows --- p.79Chapter 7.1.3. --- Editing of User-Defined Operations --- p.80Chapter 7.2. --- Future Work --- p.80Chapter 7.2.1. --- Maintaining Relationship Through Constraint Satisfaction --- p.80Chapter 7.2.2. --- Functions for System Status/Values Query --- p.82Chapter 7.2.3. --- "Private Status Flag, Pre-Conditions and Conditional Execution" --- p.82Chapter 7.2.4. --- Object Oriented Programming --- p.85Chapter 7.3. --- Other Related Application Areas --- p.86Chapter 7.3.1. --- Visual-Object Oriented Systems --- p.86Chapter 7.3.2. --- User Interface Management Systems --- p.89Chapter 7.4. --- Conclusions --- p.89References --- p.9