Coherent models for object-oriented analysis

Hayes, Fiona; Coleman, Derek

doi:10.1145/117954.117968

Cited by 35 publications

(4 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Lano und Haughton [15] geben eine Sammlung von Fallstudien des ersten Ansatzes. Beispiele für den zweiten Ansatz sind in [5,8,11,13] zu finden. Beide Ansätze sind jedoch nicht befriedigend: Die Aufnahme objektorientierter Konzepte in eine formale Methode liefert noch nicht den notwendigen Prozeß zur Entwicklung objektorientierter Software.…”

Section: Notwendigkeit Einer Formalen Objektorientierten Methodeunclassified

Formale objektorientierte Softwareentwicklung mit ${\cal F}{{\scriptstyle{\cal O}{\cal X}}}$

Achatz¹,

Schulte²

1997

Informatik - Forschung und Entwicklung

View full text Add to dashboard Cite

Zusammenfassung. Wir stellen die neue Methode FOX vor, die auf die formale Entwicklung sequentieller, objektorientierter Softwaresysteme abzielt. FOX ist eine synergetische Kombination aus der semiformalen Methode Fusion und der formalen Spezifikationssprache Object-Z. Die Methode unterscheidet ausdrücklich Analyse und Entwurf, um die Komplexität und die unterschiedlichen Aufgaben der Softwareentwicklung zu bewältigen. In jeder Entwicklungsphase werden Zustands-und Verhaltensspezifikationen in graphischer oder textueller Form erstellt. Wir geben Beweisverpflichtungen an, um zu gewährleisten, daß die entwickelten Spezifikationen formal konsistent und vollständig sind, und daß das resultierende System zur Ausgangsspezifikation konform ist. Wir illustrieren die Anwendung von F OX an einem einfachen Beispiel, einem Grapheditor.Abstract. We present a new method, called F OX , which aims at the formal development of sequential, object-oriented software systems. F OX is a synergetic combination of the semi-formal Fusion method and the formal specification language Object-Z. To manage complexity and to foster separation of concerns, F OX distinguishes between analysis and design. In each phase structure and behaviour specifications are developed step-by-step. The specifications may be graphical or textual. We give proof obligations to guarantee that the developed models are formally consistent and complete, and that the resulting system conforms to the original specification. By walking through a simple example -a graph editor -we illustrate the application of FOX.

show abstract

Section: Notwendigkeit Einer Formalen Objektorientierten Methodeunclassified

Formale objektorientierte Softwareentwicklung mit ${\cal F}{{\scriptstyle{\cal O}{\cal X}}}$

Achatz¹,

Schulte²

1997

Informatik - Forschung und Entwicklung

View full text Add to dashboard Cite

show abstract

Section: Related Workmentioning

confidence: 99%

“…In [49][50][51] formalizations are reported that tackle the precursors of UML, namely Rumbaugh's Object Modeling Technique (OMT) diagrams [52] and Jacobson's Object-Oriented Software Engineering [53]. In [49] the authors propose a FOL based formalization for OMT's diagrams and in particular for the object models (OMT's and OOSE's equivalent of UML class diagrams). In [50] the authors formalize an object model in terms of an algebraic specification and its instance diagram 22 in terms of an algebra: the semantics of the object model is the set of algebras which are consistent which the algebraic specification of that model.…”

Section: Related Workmentioning

confidence: 99%

Reasoning on UML class diagrams

Berardi

Calvanese

Giacomo

2005

Artificial Intelligence

397

360

View full text Add to dashboard Cite

UML is the de-facto standard formalism for software design and analysis. To support the design of large-scale industrial applications, sophisticated CASE tools are available on the market, that provide a user-friendly environment for editing, storing, and accessing multiple UNIL diagrams. It would be highly desirable to equip such CASE tools with automated reasoning capabilities, such as those studied in Artificial Intelligence and, in particular, in Knowledge Representation and Reasoning. Such capabilities would allow to automatically detect relevant formal properties of UML diagrams, such as inconsistencies or redundancies. With regard to this issue, we consider UML class diagrams, which are one of the most important components of UML, and we address the problem of reasoning on such diagrams. We resort to several results developed in the field of Knowledge Representation and Reasoning, regarding Description Logics (DLs), a family of logics that admit decidable reasoning procedures. Our first contribution is to show that reasoning on UML class diagrams is EXPTIME-hard, even under restrictive assumptions; we prove this result by showing a polynomial reduction from reasoning in DLs. The second contribution consists in establishing EXPTIME-membership of reasoning on UML class diagrams, provided that the use of arbitrary OCL (first-order) constraints is disallowed. We get this result by using DLR(ifd), a very expressive EXPTIME-decidable DL that has been developed to capture typical features of conceptual and object-oriented data models. ne last contribution has a more practical flavor, and consists in a polynomial encoding of UML class diagrams in the DL ALCQI, which essentially is the most expressive DL supported by current state-of-the-art DL-based reasoning systems. Though less expressive than DLR(ifd), the DL ALC QI preserves enough semantics to keep reasoning about UML class diagrams sound and complete. Exploiting such an encoding, one can use current DL-based reasoning systems as core reasoning engines for a next generation of CASE tools, that are equipped with reasoning capabilities on UML class diagrams. (c) 2005 Elsevier B.V. All rights reserved

show abstract

“…The Rigorous Object-Oriented Analysis (ROOA) [15] formalizes object-oriented analysis notations in terms of the LOTOS specification language, with an emphasis on requirements analysis capabilities. Hayes and Coleman [9] have used a VDM-like [11] notation to perform a preliminary formalization of a designspecific subset of the object model of OMT, with an emphasis on incorporating implementation details. Latella, et.…”

Section: Related Workmentioning

confidence: 99%

UML-based analysis of embedded systems using a mapping to VHDL

McUmber

Cheng

Proceedings 4th IEEE International Symposium on High-Assurance Systems Engineering

View full text Add to dashboard Cite

Methods for developing and modeling embedded systems and rigorously verifying behavior before committing to code are increasingly important. A number of objectoriented techniques and notations have been introduced, but recently, it appears that the Unified Modeling Language (UML) could be a notation broad enough in scope to represent a variety of domains and gain widespread use. Currently, however, UML is only a notation, with no formal semantics attached to the individual diagrams. In order to address this problem, we have developed a framework for deriving VHDL specifications from the class and state diagrams in order to capture the structure and the behavior of embedded systems. The derived VHDL specifications enable us to perform behavior simulation of the UML models.

show abstract

Coherent models for object-oriented analysis

Cited by 35 publications

References 5 publications

Formale objektorientierte Softwareentwicklung mit ${\cal F}{{\scriptstyle{\cal O}{\cal X}}}$

Formale objektorientierte Softwareentwicklung mit ${\cal F}{{\scriptstyle{\cal O}{\cal X}}}$

Reasoning on UML class diagrams

UML-based analysis of embedded systems using a mapping to VHDL

Contact Info

Product

Resources

About