Showing papers presented at "Conference on Advanced Information Systems Engineering in 1990"

Experiences with the use of CASE-tools in The Netherlands

Abstract: In April of 1989 the working group "Experiences with the use of CASE-tools" of the Dutch User Group of Structured Development Methodologies conducted an inquiry into the use of CASE-tools among 834 Dutch organizations This paper presents the most interesting results of this survey The results are grouped into five major sections: the characteristics of CASE-tool users, the selection criteria for CASE-tools, the implementation in organizations, the actual usage of CASE-tools and future expectations for the use of CASE-tools

How to combine tools and methods in practice—a field study

Abstract: In spring 1989 we surveyed the experiences of some Finnish companies in methodology modelling (metamodelling) and adaptation of tools and methodologies to each other (methodology adaptation). The companies represented software production, banking, wood and metal industry, and wholesale trade. The study was carried out as a field study where we interviewed method developers, systems analysts and their supervisors. The goal of the survey was to find out whether there was need for metamodelling or methodology adaptation in general and how this need had been satisfied. The study shows that a little experience had been gained in adapting data dictionaries to methodologies but no such attempts had been made with CASE tools. One reason for this was that few methodological guidelines were extensively employed and supported in organisations. In general no systematic approach had been followed in the adaptation. We also explored possible causes for encountered difficulties and conditions for successful metamodelling and methodology adaptation. A crucial success factor was the adaptability and ease of use of the tool. In general the causes for the success are similar to those of information systems development in general. These include sufficient resources and management support, concrete benefits for those who do the actual work and friendly user interfaces.

Automated support of the modelling process: a view based on experiments with expert information engineers

Abstract: A trend can be discerned clearly indicating that current developments in methodologies concentrate on an ongoing structuring and integration of modelling techniques. Automated support is the prime mover of this trend. In this article it is argued that a lack of explicit knowledge about the process of model construction has resulted in problems with CASE-tools concerning adequate support in the form of verification and navigation. We present a view on modelling processes which has been applied in experiments with expert information engineers. The key concepts of this view are strategy and natural level of consistency. It is argued that adequate support can be realized for navigation and verification on the basis of (1) knowledge about tasks and decisions part of a strategy and (2) knowledge about the natural level of consistency of tasks. The experiments with expert information engineers have been performed as part of the realization of a knowledge acquisition approach for modelling knowledge. From each expert we have been able to extract detailed knowledge about the modelling process studied. The last part of this paper describes an architecture of modelling support systems, as well as a prototype that is capable of supporting the presented aspects of modelling processes.

Requirements specification in TEMPORA

Abstract: The use of formal language is a way to introduce rigour in the specification of the requirements for information systems. This stage is traditionally considered as the most informal one of the life-cycle stages. Thus, the choice of a model best suited for this purpose is still an open issue.

Rule-based requirements specification and validation

Abstract: Requirements specification has only recently been acknowledged as one of the most important phases in the overall software life cycle. Since the statement of a complete and consistent set of requirements involves user participation, our approach investigates how user oriented formalisms and techniques could be employed for the specification and capturing of requirements. We propose the use of rules as a natural means for expressing the application domain knowledge, and introduce a number of techniques such as semantic prototyping and animation for the validation of the requirements.

A design tool for object oriented databases

Abstract: This paper describes a design methodology for an object oriented database, based on a semantic network. This approach is based on the assumption that semantic data models are more powerful and more easy to use than current proposed object oriented data models. They are especially more powerful in representing integrity constraints and various relationships. Object oriented data models are generally based only on class hierarchies and inheritance, plus their ability to represent the behaviour of objects. But this latter capability is generally provided through an algorithmic language which cannot be considered as a conceptual language. In this paper, we combine the two categories of data models and give a procedure on how to translate the conceptual model to the logical model.

A communication oriented approach to conceptual modelling of information systems

Abstract: Informata are introduced as a subclass of information systems. The SMARTIE framework is presented which supports the conceptual modelling of informata. The core of the framework is an automaton, which can be viewed as a generalization and an extension of the finite state machine, but which also draws on results of language philosophical research. A model of a system in this framework is called a communication model, as opposed to the conventional process model. Several techniques supporting the modelling and the specification of systems in the SMARTIE framework are presented. To demonstrate the practical applicability of the modelling principles, a traffic control system is taken as an example.

A natural language interpreter for the construction of conceptual schemas

Abstract: The problem of designing a relational database for an information system is a complex one; it involves the analysis of an informal, and often incomplete, statement about some enterprise and then formal application of the established theories.

IRIS—a mapping assistant for generating designs from requirements

Abstract: The problem of generating information system designs from requirements specifications is addressed, with the presentation of a framework for representing requirements and a mapping assistant, IRIS3, that facilitates the design generation process. Requirements are viewed as knowledge bases and the knowledge representation formalism for the prototype, also the language for implementing IRIS, is Telos which provides facilities for describing entities and relationships and for representing and reasoning with temporal knowledge. The generation of a design is achieved with a mapping process from requirements which is: (i) Locally guided by dependency types determining allowable mappings of an element of a requirements model, (ii) globally guided by non-functional requirements, such as accuracy and security requirements on the intended system, represented as goals describing desirable properties of the intended system and used to guide local decisions.

RECAST: a tool for reusing requirements

Abstract: Reuse of development documents regarding application requirements makes the application development process more efficient and reliable. The REquirements Collection And Specification Tool (RECAST) being developed in the framework of the ESPRIT ITHACA project aimed at reusability under an object-oriented approach for Information System applications is presented in the paper. Two types of application developers interact with RECAST: the Application Engineer, who maintains the knowledge about reusable components, and the Application Developer, who develops specific applications; their interaction with RECAST is presented. RECAST guides these developers using design knowledge stored in a Software Information Base (SIB).

CASE tools and software factories

Abstract: The present paper addresses CASE tools as they are today, and what we believe will be the next generation CASE tools — Software Factories (or IPSEs — Integrated Project Support Environment, or ISDEs — Integrated Software Development Environments).

The conceptual task model: a specification technique between requirements engineering and program development (extended abstract)

Abstract: In current practice of information system development, as well as in its support tools, there exists a gap between the informal requirements engineering activities and the more formal program development stage. To overcome this, a specification technique, called the Conceptual Task Model (CTM), is introduced, that is related explicitly to the results of the global requirements specification, i.e. process models and data models, and that can be input to code generation. The CTM technique is based on and defined in terms of Predicate\transition nets. CTM integrates the specification of the data manipulation function with control structures and local and global data models. The possibilities for the automated support of CTM are discussed. Finally, the precise relation with the process model and some other theoretical issues are presented.

Correction of conceptual schemas

Abstract: This paper presents the interim results of a research project aimed at the prototyping of an automatic tool, Rubis, to aid in the development of, validate and correct the conceptual specification of information systems.

Software process modelling in EPOS

Abstract: EPOS is an instrumentable, kernel Software Engineering Environment (SEE). It consists of facilities for management of versioned products (configurations) through file-based workspaces attached to a versioned DBMS. EPOS will also manage the associated software development processes (tasks), being the subject of this paper.

Selecting system development tools: some experiences

Abstract: Case-tool market is quite unstructured and not mature. It is no wonder that buyers are more than blurred. Several acquisitions have so far been based on false or insufficient data, which has led to lost money and other resources.

Software prototyping: implications for the people involved in systems development

Abstract: This paper explores the adoption of systems prototyping and, in particular, concentrates on the various ways in which this may affect those people associated with systems development.

Software configuration management for medium-size systems

Abstract: Software configuration management for large real systems is an ugly task. For such systems large-scale software configuration management systems are necessary. Small systems don't need software configuration management except a way to backup. This paper describes a simple software configuration management system (called SCMB) for real medium-size systems.