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
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
Available from: scirp.org
- "A case study is discussed by a formal verification method for Cooperative Composition Modeling Language (CCML) in . In , semantic translation from statechart diagrams to Object-Z specifications is presented. Information is captured using sequence and use case diagrams as a functional model by taking a case study. "
[Show abstract] [Hide abstract]
ABSTRACT: Requirements analysis and design specification are serious issues in systems development because of the semantics in-volved in transformation of real world problems to computer software systems. Although unified modeling language (UML) is now accepted as a de facto standard for design and specification of object oriented systems but its structures have various disadvantages. For example, it lacks of defining semantics of the systems to be developed. Formal meth-ods are proved powerful, particularly, at requirement specification and design level. To address and realize the benefits of UML and formal methods our project on "formalization of UML diagrams using Z notation" is under progress. This paper is continuation of the same project in which some important diagrams namely use case, class and sequence dia-grams are selected for critical analysis. Merits and demerits of the diagrams are addressed after a brief introduction. Applications of the diagrams are observed reducing complexity and proposing a good design of a system. Finally, a treatment to link diagrams with appropriate approaches is suggested to enhance modeling power of UML for facilitating the systems development.
Intelligent Information Management 01/2012; 04(05). DOI:10.4236/iim.2012.45034
Available from: psu.edu
- "Furthermore, among the latter, only a limited number attempt at the same time to deal with TCS. To the best of our knowledge the approaches that are the closest to the direction of work that we have pursued are France et al.'s translation of Octopus models into Z specifications , Jia's pragmatic approach for combining the strengths of object-oriented and formal notations, specifically UML and Z , Noe and Hartrum's extension of Rational Rose for the inclusion of formal specifications  and Kim and Carrington's combination of UML and Object-Z . The only tool developed commercially to support an object-oriented modeling approach that combines the advantages of graphical, semi-formal notations with those of formal notations is RoZeLink, produced by Headway Software Inc.  (RoZeLink provides a bridge between the UML notation supported by Rational Software Corporation's Rose environment  and the ZEST objectoriented formal specification language supported by Logica's Formaliser ). "
[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: Formal modeling notations and visual modeling notations can complement each other when developing software models. The most frequently adopted approach is to define transformations between the visual and formal models. However, a significant problem with the currently suggested approaches is that the transformation itself is often described imprecisely, with the result that the overall transformation task may be imprecise, incomplete and inconsistent. This paper presents a metamodel-based transformation between UML and Object-Z. In the paper, the two languages are defined in terms of their metamodels, and a systematic transformation between the models is provided at the meta-level. As a consequence, we can provide a precise, consistent and complete transformation between a visual model in UML and a formal model in Object-Z. In a case study, we illustrate how the metamodel-based transformation enables us to create a UML visual representation of an Object-Z specification.
Human-Centric Computing Languages and Environments, 2001. Proceedings IEEE Symposia on; 02/2001
Data provided are for informational purposes only. Although carefully collected, accuracy cannot be guaranteed. The impact factor represents a rough estimation of the journal's impact factor and does not reflect the actual current impact factor. Publisher conditions are provided by RoMEO. Differing provisions from the publisher's actual policy or licence agreement may be applicable.