ER'97 Logo

16th International Conference on Conceptual Modeling (ER'97)

Los Angeles, California, USA

3 - 6 November 1997

Tutorial 1    Tutorial 2

There will be two half-day tutorials held Monday, November 3. Tutorials require an additional registration fee. Here is an ASCII registration form. Tutorial 1 will be held Monday morning from 8:00a.m. to 12:00p.m., and Tutorial 2 will be held Monday afternoon from 1:30p.m. to 5:30p.m. (See the Conference at a Glance.)

Tutorial 1
OML: A Metamodel & Notation for a Pure
Object-Oriented Software Development Environment

Brian Henderson-Sellers


What You Will Learn

The overall aims of the tutorial are to describe the details of the third generation OPEN methodology's preferred notation (COMN) and its underpinning metamodel (together known as OML).
Modelling an object-oriented system is facilitated by a sound metamodel and an accompanying notational representational tool which fully represents the pure object-oriented ideas. An extension of the COMMA metamodel intertwined with a notation devised on HCI principles is presented and the important modelling concepts underlying them highlighted.
A methodology, as well as producing "better" software engineered systems, should enable people to communicate more effectively about a problem and its solution. It should therefore include as a small yet vital component a modelling notation underpinned with a reliable metamodel. With today's emphasis on metamodelling through the Object Management Group's recent activities, some highlights of a major contribution to one of the initial submission, COMMA, and its main elaboration into the OPEN metamodel will contribute to an understanding of the standardization process currently under way. The accompanying notation, preferred by the OPEN method, is known as COMN or Common Object Modelling Notation.
The full methodology OPEN (OPEN stands for Object-oriented Process, Environment and Notation) (Henderson-Sellers, Graham et al., 1996) is an "umbrella" process-focussed approach created by the merger of a large number of OO methodologies and the ideas from a cohesive group of over 25 internationally recognized methodologists and researchers. Whilst the major merger is between MOSES (Henderson-Sellers and Edwards, 1994), SOMA (Graham, 1995) and Firesmith (1993), we have also significant involvement and contributions from the developers of ROOM, OOram, Synthesis and Mainstream Objects as well as additional research input from OO co and researchers worldwide. We also recognize the value and influences (even if no active involvement as yet) from RDD, OBA, BON and UML.
OPEN is the first third-generation full lifecycle OO methodology.

Overview of OPEN

The tutorial will focus on the formal underpinning of OPEN by means of the metamodel which itself derives from a year long study of the COMMA project (Henderson-Sellers and Bulthuis, 1997) in which all current methodologies were analyzed for their implicit metamodel and a formal proactive coalescence of ideas was created (Henderson-Sellers and Firesmith, 1997). This has been further elaborated into OML: a COMMA-enhanced metamodel plus the COMN notation.
The advantages of the OPEN third-generation methodology are that it
In this presentation, the contribution of OML to OPEN is highlighted. The tutorial provides sufficient information for the notation to be used in a business environment by the tutorial participants as well as providing a rationale why metamodelling is important as an underpinning to notations and methodologies.
This seminar may be complemented by the process focus of "Engineering the Object-Oriented Software Process: OPEN and MeNtOR" and by a discussion of OPEN's Tasks and Techniques in "OPEN: A Third Generation OO Methodology - Advanced Tasks and Techniques"

Previous Presentations

This tutorial has previously been given previously at Smalltalk Solutions in New York (March 1997) and is based on the recent OML book (Firesmith et al., 1997).
The work has evolved out of MOSES, SOMA and Firesmith and a large number of tutorials have been given on these individual methods and their notations and metamodels at international OO conferences (academic and commercial) around the world.

Who should attend

System developers, analysts and designers who require information on modern OOAD methodological thinking. Should be fully conversant with basic OO terminology and the need for a good metamodel and notation within a full lifecycle process methodology. Experience with OO methodologies advantageous.


D.G., Firesmith, Object-Oriented Requirements Analysis and Logical Design: A Software Engineering Approach. J. Wiley and Sons, New York, 575pp (1993)
D. Firesmith, B. Henderson-Sellers and I. Graham, OPEN Modeling Language (OML) Reference Manual, SIGS Books, NY (1997)
I.M. Graham, Migrating to Object Technology. Addison-Wesley, Wokingham, UK, 473pp (1995)
B. Henderson-Sellers and A. Bulthuis, Object-Oriented Metamethods, Springer, New York, in press (1997)
B. Henderson-Sellers and J.M. Edwards. BOOKTWO of Object-Oriented Knowledge. The Working Object. Prentice Hall, Sydney, 616pp (1994)
B. Henderson-Sellers and D. Firesmith, COMMA: Proposed core model, Journal of Object-Oriented Programming (Jan 1997)
B. Henderson-Sellers and I.M. Graham, with additional input from C. Atkinson, J. Bezivin, L.L. Constantine, R. Due, R. Duke, D. Firesmith, G. Low, J. McKim, D. Mehandjiska-Stavrova, B. Meyer, J.J. Odell, M. Page-Jones, T. Reenskaug, B. Selic, A.J.H. Simons, P. Swatman and R. Winder. OPEN: toward method convergence? IEEE Computer, 29(4), 86-89 (1996)

Tutorial 2
A Rapid, Metamodel-Based Methodology for Information Systems Modeling

David V. Kerner

This tutorial presents a unique approach to information systems modelling based on a generic data model that is customized to the management strategies of the organization. Not only is this approach faster than interview-based methods but it also allows a comparison with similiar organizations that can be very enlightening.

What You Will Learn

In this tutorial we will discuss how to customize the generic model and then we will explore how the data model can help the business to, better utilize its resources, to predict impact of strategic to, better utilize its resources, to predict impact of strategic direction on Information Technology, to address business problems, to insure correct measurement of Critical Success Factors, and to identify out of control data.
We will start by defining a fictitious company. Then we will tailor Business Information Technologies generic data model to closely represents the company. The tailoring will be accomplished by identifying the customers of the business and products or services they order. This combination of customers and products are called order types. We will ask questions about how the business manages these order types, and from the answers generate a tailored data model.
We will use the tailored data model for the following kinds analyses:
Accountability.   The organizations of the business are related to the data in the model. They are related to the model data by asking a series of questions about the organizations and their interface to the data. This often unearths problems with data management responsibilities.
Business Problems.   Purpose of the business problem activity is to insure that the organization takes into consideration the current problems. It is not uncommon to find that out of control data directly contributes to current business problems.
Business Strategies.   Purpose of the strategy activity is to determine how the future plans of the enterprise are going to affect its information requirements. From this exercise, the study team will be able to project which systems will not require change, which will have to be modified, or created to support the strategies.
Critical Success Factors (CSF).   The purpose of the CSF activity is to determine if the information required to measure a CSF is available and correct. By definition, CSF's have to be accomplished, or the enterprise will go out of business, or at the very least will be severely impacted. It is extremely important to know if the business is on track in its pursuit of its CSF's.
Data Stores.   The purpose of the data store activity is to begin identifying where the data described in the model physically resides in the enterprise. This can be used, among other things, to build a warehouse architecture.

About the Instructor

David Kerner has over 35 years experience in all aspects of data processing. He worked for IBM for 27 years, in programming, system engineering, marketing, planning, research, education and management. He has extensive experience in data modeling, and is the creator of Business Information Planning (BIP) a rapid enterprise modeling and analysis methodology that uses a pre-defined data model. Compared to more traditional approaches BIP will produce comprehensive results in weeks as opposed to months. Kerner has published and lectured extensively on data modeling and defining end user requirements based on business needs.
Kerner has worked with companies as small as fifteen people to the top Fortune 500. He has helped companies build application architectures to support total restructuring, to define business requirements for data warehousing, and to just having a better understanding of their business. He is founder and president of Business Information Technologies.


1. Hellenack, L.J., "Object-Oriented Business Patterns," Object Magazine, January 1997
2. Zachman, J.A., "Business Systems Planning and Business Information Control Study: A Comparison," IBM Systems Journal, 21(1), pp 31-53

Sponsored By

The ER Institute

In Cooperation With


More Information
ACM -- 50 Years

Last updated Wed Oct 22 10:54:16 MDT 1997
Stephen W. Liddle

Copyright © 1997, ER'97. All rights reserved.