Domain-oriented architecture design for production control software

this paper, we present domain-oriented architectural design heuristics for production control software. Our approach is based upon the following premisses. First, software design, like all other forms of design, consists of the reduction of uncertainty about a final product by making design decisions. These decisions should as much as possible be based upon information that is certain, either because they represent laws of nature or because they represent previously made design decisions. An import class of information concerns the domain of the software. The domain of control software is the part of the world monitored and controlled by the software; it is the larger system into which the software is embedded. The software engineer should exploit system-level domain knowledge in order to make software design decisions. Second, in the case of production control software, using system-level knowledge is not only justified, it is also imposed on the software engineer by the necessity to cooperate with hardware engineers. These represent their designs by means of Process and Instrumentation Diagrams (PIDs) and Input-Output (IO) lists. They do not want to spend time, nor do they see the need, to duplicate the information represented by these diagrams by means of diagrams from software engineering methods. Such a duplication would be an occasion to introduce errors of omission (information lost during the translation process) or commission (misinterpretation, misguided but invisible design decisions made during the translation) anyway. We think it is up to the software engineer to adapt his or her notations to those of the system engineers he or she must work with. Third, work in patterns and software architectures started from the programminglanguage level and is now moving..

Using NLP tools in the specification phase

The software quality control is one of the main topics in the Software Engineering area. To put the effort in the quality control during the specification phase leads us to detect possible mistakes in an early steps and, easily, to correct them before the design and implementation steps start. In this framework the goal of SAREL system, a knowledge-based system, is twofold. On one hand, to help software engineers in the creation of quality Software Requirements Specifications. On the other hand, to analyze the correspondence between two different conceptual representations associated with two different Software Requirements Specification documents. For the first goal, a set of NLP and Knowledge management tools is applied to obtain a conceptual representation that can be validated and managed by the software engineer. For the second goal we have established some correspondence measures in order to get a comparison between two conceptual representations. This information will be useful during the interaction.Postprint (published version

Knowledge-based control of an adaptive interface

The analysis, development strategy, and preliminary design for an intelligent, adaptive interface is reported. The design philosophy couples knowledge-based system technology with standard human factors approaches to interface development for computer workstations. An expert system has been designed to drive the interface for application software. The intelligent interface will be linked to application packages, one at a time, that are planned for multiple-application workstations aboard Space Station Freedom. Current requirements call for most Space Station activities to be conducted at the workstation consoles. One set of activities will consist of standard data management services (DMS). DMS software includes text processing, spreadsheets, data base management, etc. Text processing was selected for the first intelligent interface prototype because text-processing software can be developed initially as fully functional but limited with a small set of commands. The program's complexity then can be increased incrementally. The intelligent interface includes the operator's behavior and three types of instructions to the underlying application software are included in the rule base. A conventional expert-system inference engine searches the data base for antecedents to rules and sends the consequents of fired rules as commands to the underlying software. Plans for putting the expert system on top of a second application, a database management system, will be carried out following behavioral research on the first application. The intelligent interface design is suitable for use with ground-based workstations now common in government, industrial, and educational organizations

Multimedia and Knowledge-based Computer-aided Architectural Design

It appears by now fairly accepted to many researchers in the field of the Computer Aided Architectural Design that the way to realize support tools for these aims is by means of the realization of Knowledge Based Assistants. This kind of computer programs, based on the knowledge engineering, finds their power and efficaciousness by their knowledge bases. Nowdays this kind of tools is leaving the research world and it appears evident that the common graphic interfaces and the modalities of dialogue between the architect and the computer, are inadequate to support the exchange of information that the use of these tools requires. The use of the knowledge bases furthermore, presupposes that the conceptual model of the building realized by others, must be made entirely understandable to the architect . The CAAD Laboratory has carried out a system software prototype based on Knowledge Engineering in the field of hospital buildings. In order to overcame the limit of software systems based on usual Knowledge Engineering, by improving architect-computer interaction, at CAAD Lab it is refining building model introducing into the knowledge base two complementary each other methodologies: the conceptual clustering and multimedia technics. This research will make it possible for architects navigate consciously through the domain of the knowledge base already implemented

Enriching APSI with Validation Capabilities: the KEEN environment and its use in Robotics

This paper presents the KnowledgE ENgineering (KEEN) design support system in which Validation and Verification (V&V) methods are used to strengthen onground development of software for plan-based autonomy. In particular, the paper describes a collection of verification methods, based on Timed Game Automata (TGA), deployed for the design and development of timeline-based Planning and Scheduling (P&S) applications within the APSI-TRF framework. The KEENs V&V functionalities are illustrated describing software development to synthesize plans for a planetary rover

Information engineering of a software engineering ontology

In this paper, we describe the preliminary result of the development and implementation of a Java-based system for information gathering, knowledge extraction and maintenance of software engineering ontology. The system is capable of manipulative ontology instances from the information repositories and information sources. Design of Software Engineering Ontology through the use of the body of software engineering knowledge together with Prof Ian Sommerville's book, as well as project management experiences, has not been a difficult task. However, the maintenance of the software development ontology and security of the Ontology are issues

Modeling software design diversity

Design diversity has been used for many years now as a means of achieving a degree of fault tolerance in software-based systems. Whilst there is clear evidence that the approach can be expected to deliver some increase in reliability compared with a single version, there is not agreement about the extent of this. More importantly, it remains difficult to evaluate exactly how reliable a particular diverse fault-tolerant system is. This difficulty arises because assumptions of independence of failures between different versions have been shown not to be tenable: assessment of the actual level of dependence present is therefore needed, and this is hard. In this tutorial we survey the modelling issues here, with an emphasis upon the impact these have upon the problem of assessing the reliability of fault tolerant systems. The intended audience is one of designers, assessors and project managers with only a basic knowledge of probabilities, as well as reliability experts without detailed knowledge of software, who seek an introduction to the probabilistic issues in decisions about design diversity