The goal of this workshop is to foster precise and explicit OO specifications of business and system semantics, independently of any (possible) realization. Substantial progress has been made in these areas, both in academia and in industry. However, in too many cases only lip service to these ideas has been provided, and as a result the systems we build or buy are all too often not what they are supposed to be. Doing better than that requires both a clear understanding of the semantics of the problems together with their business and technological environments, and abstract, precise and explicit specifications of that semantics. The specific theme this year is on serving the customer. As in our previous workshops, we want to bring together theoreticians and practitioners to report their experience with making semantics precise, clear, concise and explicit in OO business specifications, business designs, and system specifications. Papers can range from academic research to industrial ``war stories.''
The Proceedings will be available at the Workshop.
The Table of Contents and Index are now available.
The continuing theme of the OOPSLA Workshop Series on Behavioral Semantics is to foster precise and explicit OO specifications of business and system semantics. The specific emphasis this year -- the eleventh year of the Workshop -- is on serving the customer. Many decision makers in the business technology field recently stressed that the trust and the patience of our customers have been exhausted due to poor quality of our products and services and mismatched expectations.
In order to serve customers, we need to understand their needs. However, business and IT organizations often express themselves in very different ways. In order to create information management systems that serve the needs of complex, non-trivial and rapidly changing businesses, effective communication is imperative. In order to communicate effectively, a small collection of shared, clearly defined concepts and constructs with clearly defined semantics is essential. These concepts and constructs -- basic patterns of reasoning -- facilitate understanding and therefore bridge the gap between business and IT. They ought to be used as a basis of all kinds of specifications, such as of traditional businesses and of middleware artifacts.
A small, well-structured collection of basic elegant concepts and constructs has been around in programming and modeling for decades. Some have been used in other areas of human endeavor, like engineering, business and law. This collection of concepts was described in an international (ISO) standard, the Reference Model of Open Distributed Processing (RM-ODP). The approach of concept reuse is not unique to OO or even to information technology. For example, ordinary businesses in the US use the Uniform Commercial Code not only as a set of reusable patterns of reasoning and acting, but also as a law.
The basic patterns of reasoning are much more stable than technological artifacts -- languages, methodologies and tools -- used to represent them. Therefore such technological artifacts as various versions of UML and XML ought to be assessed from the viewpoint of their support (or otherwise) of the semantics of the concepts and constructs which have to be represented using these artifacts.
The essentials of comprehensible OO specifications of business and of system artifacts ought to be used by, and therefore understandable to, all customers of these specifications -- business subject matter experts, decision makers, analysts, IT architects and developers. These documents have to be abstract (avoid irrelevant details, and thus avoid avoidable complexity), precise and explicit. They have to be understood in the same manner by all stakeholders. Since the tacit assumptions of different stakeholders are often different, OO specifications should not rely on such assumptions including ``meaningful names.''
As in all the workshops in this series, it is our goal to be a focal point of bringing together theoreticians and practitioners to report their experience with making semantics precise, clear, concise and explicit in (OO) business specifications, business designs, and system specifications. We invite papers varying from academic research (especially dealing with transferring theory into practice) to industrial ``war stories.''
As in all the workshops in this series, it is our goal to be a focal point of bringing together theoreticians and practitioners to report their experience with making semantics precise, clear, concise and explicit in (OO) business specifications, business designs, and system specifications. We invite papers varying from academic research (especially dealing with transferring theory into practice) to industrial ``war stories.'' This year there is an emphasis on revisiting the classics both to ``set the record straight'' and to recapture insights and ideas that might otherwise slip into oblivion.
(Books  and  were based on the previous OOPSLA and ECOOP workshops on specification semantics.)
the invitation to submit will be posted in various newsgroups and mailing lists. Invitations will also be emailed to past participants in this workshop series. Submitted papers (5-10 pages) will be reviewed by the organizers. The accepted papers, after rework by the authors, will be published, again as usual, in the Workshop Proceedings. These Proceedings will be distributed before the workshop.
Please send submissions by September 1, 2002 to Haim Kilov <firstname.lastname@example.org>
Ordinary (transparency) projector, 2 flipcharts.
Related Web Pages