Resending note of 05/01/96 11:59
Dear Jim,
In reponse to the Call for Contributions for the Seattle workshop on data and process modelling, I am appending herewith an abstract which falls into the category of an industry expert contribution.
It seems possible from the Call for Contributions that this abstract should be submitted by a "national body" - in my case BSI. I have raised this issue with BSI. In view of the very short time available, I have been given authorization to submit directly to you. Another problem is that BSI's email system is not functioning at this time.
I look forward to hearing from you further on this matter.
Yours, Martin
Title: Abstract and Outline - On Modelling in the context of Information Systems
Date: 30 April, 1996
Source: Martin King
Project: JTC1 Workshop on Standards for the use of Models that Define the Data and Processes of Information Systems
Status:Submission from industry expert for consideration for inclusion at the Workshop, supported by UK national body
Abstract
The objective of this paper is to propose some principles and guidelines for those interested in standardising any form of modelling facility or language. It examines aspects of various activities commonly described as modelling in the context of information systems. It attempts to clarify the senses in which something can model something else. These provide a basis for the proposed guidelines.
The basic concept of modelling is simple: one thing, the model, represents in some sense something else, the original. While this is simple to state, it appears to be open to very different interpretations. The paper sets out some basic principles of modelling and the relationship between the model and what is modelled. The range of uses of models is discussed. A model is generally built with a particular purpose in mind; it may or may not be suitable for different uses.
A distinction is drawn between a "direct" and an "indirect" model. The later involves in some sense a model which primarily relates to one thing, and that in turn is seen as modelling another. While a model in some sense represents something else, a thing which represents something else is not necessarily a model, for example a name. This distinction is clarified and identified as a potential source of complexity and confusion.
Any information system can be considered to serve a purpose within a context. Typical contexts include businesses, government or other non-profit organizations, or may be some mechanical or technical process or other more limited context within an organization. The word enterprise is chosen to refer to any such wider or more limited context. The nature of these contexts or enterprises is explored. Some sources of complexity and general principles relevant to modelling are identified. The need to be able to model any relevant aspects of an enterprise is highlighted.
The essentially linguistic nature information systems is discussed. The presence of many levels of representation and the potential of this for causing confusion is explored. The motivation and evolution of modelling and the concept of meta-models is reviewed.
Against the foregoing, the challenge of modelling in the context of information systems is compared with that of modelling in other contexts. The conclusion is that modelling in the context of information systems is particularly complex. Additional complexity is identified in the inherent nature of large enterprises, information technology, and environmental change. The risk is of confusion caused by complexity. It is argued that it is vital to be clear in any modelling what is being modelled and that the model is constructed in a way that preserves this clarity.
A list of principles or criteria for evaluating the objectives and positioning of any modelling facility or language is proposed. These will include the following:
Various IS projects are reviewed against the identified criteria. These include:
The paper concludes with a proposal for the wider use of the identified criteria for evaluating standardisation activity within the scope of the workshop.
Outline