Name
Abstract | ||
|---|---|---|
A diagrammatic approach to the semantics of OO modelling notations is proposed. This is based on an innovative and expressive notation dubbed "constraint diagrams", which can be used to precisely characterise a range of sophisticated, static constraints on OO models. Other notations, such as those found in UML, can be viewed as projections of constraint diagrams. Work on using constraint diagrams at the core of a 3D modelling notation is also briefly described as a means of similarly providing the semantics of diagrams imposing constraints on dynamic behaviour. 1I ntroduction This paper outlines a pictorial approach to constructing a precise semantics for object- oriented modelling notations. There are at least four reasons why one might want to build a precise semantics: 1. To clarify meaning leading to refinements of the notation. 2. To clarify meaning for developers using the notation. 3. To clarify meaning for tool developers, thereby increasing the likelihood of inter- operability between tools at a semantic level (e.g. code generated from different tools for the same model has the same behaviour). 4. To support semantic checking of models, automated if possible. This includes checking that implementations meet their specifications, checking internal con- sistency of components, and checking for inconsistencies and conflicts between components. (1) just requires the semantics to be written down in a precise form. (2) and (3) require it to be written down in a form which developers and tool developers can easily under- stand. In addition, it would be desirable for (3) to provide a semantics in a form which directly assists the construction of tools, e.g. the automation of (4). We propose that the semantics is given in terms of an expressive and innovative dia- grammatic modelling notation, dubbed constraint diagrams, which can be used to pre- cisely characterise a range of sophisticated, static constraints on OO models and which is particularly targeted on (2) and (3) (with some impact on (1) and (4)). A 3D notation based on constraint diagrams may be similarly used to characterise the semantics of dynamic behaviour. In essence, our notation is rich enough to characterise a model that would otherwise require many different kinds of diagram. The latter can then be viewed as projections of this model. |
Year | DOI | Venue |
|---|---|---|
1997 | 10.1007/3-540-69687-3_38 | European Conference on Object-Oriented Programming |
Keywords | Field | DocType |
dynamic behaviour,expressive notation,modelling notation,static constraint,oo modelling notation,constraint diagram,diagrammatic approach,oo model,code generation | Notation,Programming language,Unified Modeling Language,Diagrammatic reasoning,Computer science,State diagram,Theoretical computer science,Abstract syntax,Computer programming,Semantics | Conference |
ISBN | Citations | PageRank |
3-540-64039-8 | 2 | 0.54 |
References | Authors | |
3 | 5 | |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Stuart Kent | 1 | 886 | 137.53 |
| Ali Hamie | 2 | 76 | 15.49 |
| John Howse | 3 | 756 | 107.01 |
| Franco Civello | 4 | 64 | 9.39 |
| Richard Mitchell | 5 | 2 | 0.54 |