Conference Paper

An integrated framework with UML and Object-Z for developing a precise and understandable specification: the light control case study.

Dept. of Comput. Sci. & Electr. Eng., Queensland Univ., Brisbane, Qld.;
DOI: 10.1109/APSEC.2000.896705 Conference: 7th Asia-Pacific Software Engineering Conference (APSEC 2000), 5-8 December 2000, Singapore
Source: DBLP

ABSTRACT Presents a framework that integrates a graphical specification technique (UML) with a formal specification technique (Object-Z) to support requirements elicitation and analysis activities. Various UML diagrams are used to specify the system from different concerns during the early requirements elicitation and analysis stage. The information captured in the diagrams is used to develop a complete Object-Z specification. This paper presents a semantic translation from statechart diagrams to Object-Z specifications. Finally, based on information captured in sequence diagrams and use case diagrams, a functional model of the whole system is formally defined. The case study used in this paper is a real-time, interactive and embedded system: a light control system

  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Graphical notations have traditionally played an important role in the process of software development, particularly during the analysis and design phases. However, in applications in which the reliability of the software is a primary concern a graphical notation such as UML needs to be complemented by a formal language in order to provide enhanced support for pragmatic and rigorous development of specifications. Although many authors have envisaged the advantages of combining informality (or semi-formality) with formality in software construction, there are few reports that address the issue in the context of object-orientation and project its solution over the canvas of time-constrained systems. In this paper we present an integrated environment, entitled Harmony, which supports the combined utilization of two notations, the visual UML and the formal Z++, and thus assists the rigorous object-oriented development of systems on which temporal constraints are placed.
  • [Show abstract] [Hide abstract]
    ABSTRACT: The Unified Modeling Language (UML) has been developed as a standard language for object-oriented designs. Through its graphical and intuitive diagrams, software analysis and design process become easy. However, this graphical notation lacks precisely defined semantics. It is difficult to determine whether the design is consistent, unambiguous and complete. This paper provides a method of formalizing UML models. It gives the transforming rules from UML models to Object-Z constructs. With this method, the semantics of UML models are directly expressed in formal language Object-Z. The UML class, sequence and statechart diagrams are formalized using this method. A tool OZRose is developed to automate the transforming process.
    Formal Methods and Software Engineering, 4th International Conference on Formal Engineering Methods, ICFEM 2002 Shanghai, China, October 21-25, 2002, Proceedings; 01/2002
  • [Show abstract] [Hide abstract]
    ABSTRACT: A Unified Modeling Language (UML) use case diagram is a visual tool that provides a way for developers to come to a common understanding with system's end users and domain experts. The behavior of a use case can be specified by describing a flow of events in text for an outsider to understand it easily. The flow of events of a use case is specified in an informal structured text. Therefore, it is not possible to automate the verification of tracking requirements captured in a use case diagram in the design phase. On the other hand, Z is a formal language, which is non-executable, but, a strongly typed specification language. We here propose a structured-expandable format of a use case, which is expressed in Z notation and then represented visually using an Entity-Relationship diagram. Implementation of our approach would bridge the gap between a formal language, which is mathematical and difficult to understand and UML use case diagram that is visual, easy to comprehend and that is used widely to capture requirements. Development of a tool based on this approach will produce a visual representation of a formalized UML use case diagram, from which automated traceability and verification of the design phase can be achieved.
    Computing & Informatics, 2006. ICOCI '06. International Conference on; 07/2006