Automating the Synthesis of UML StateChart Diagrams from Multiple Collaboration Diagrams

Khriss, Isïl; Elkoutbi, Mohammed; Keller, Rudolf K.

doi:10.1007/978-3-540-48480-6_11

Cited by 33 publications

(36 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Each of these papers describes one formal treatment of unification of UCs into a statechart similar in semantics to our unified UC statechart 17 . Several others, including Somé et al [21], van Lamsweerde et al [25], Khriss et al [13], Somé [22], and Damas et al [3] describe algorithms and methods for synthesizing various domain models, including one in the statecharts notation, from UCs. Detailed comparisons of the three methods on which UCUM is based, among a number of other scenario and statechart unification methods, are offered by Saiedian et al [20] and by Liang et al [16].…”

Section: Related Workmentioning

confidence: 99%

Unified use case statecharts: case studies

et al. 2007

View full text Add to dashboard Cite

This paper presents the results of case studies evaluating a method of unifying use cases (UCs) to derive a unified statechart model of the behavior of the domain of a proposed computer-based system. An evaluation of the unification method, the obtained statechart model of the domain, the method's and model's feedback on the UCs themselves, and how the method is used in requirements engineering practice was carried out by examining 58 software requirements specifications produced by 189 upper-year undergraduate and graduate students. The results of these studies independently confirm some of the benefits of building a unified SC mentioned in the works of Glinz; Whittle and Schumann; and Harel, Kugler, and Pnueli.

show abstract

Section: Related Workmentioning

confidence: 99%

Unified use case statecharts: case studies

et al. 2007

View full text Add to dashboard Cite

show abstract

“…The objective of this activity is to integrate for each object of the system all its partial labeled StateDs into one single StateD [21,22]. We proceed by initially merging the StateDs at the use case level, and afterwards at the global level.…”

Section: Integration Of Partial Specificationsmentioning

confidence: 99%

“…However, our scenario integration algorithm can be configured to allow scenario interleaving and to capture more than the mere input scenarios. In this way, new scenarios may be generated from the already existing ones [21]. Note, however, that arbitrary scenario interleavings may not satisfy the semantics of the application.…”

Section: Scenario-based Approachmentioning

confidence: 99%

See 1 more Smart Citation

Automated Prototyping of User Interfaces Based on UML Scenarios

Elkoutbi¹,

Khriss

Keller³

2006

Autom Software Eng

Self Cite

View full text Add to dashboard Cite

Abstract. User interface (UI) prototyping and scenario engineering have become popular techniques. Yet, the transition from scenario to formal specifications and the generation of UI code is still ill-defined and essentially a manual task, and the two techniques lack integration in the overall requirements engineering process. In this paper, we suggest an approach for requirements engineering that generates a user interface prototype from scenarios and yields a formal specification of the application. Scenarios are acquired in the form of collaboration diagrams as defined by the Unified Modeling Language (UML), and are enriched with user interface (UI) information. These diagrams are automatically transformed into UML Statechart specifications of the UI objects involved. From the set of obtained specifications, a UI prototype is generated that is embedded in a UI builder environment for further refinement. Based on end user feedback, the collaboration diagrams and the UI prototype may be iteratively refined, and the result of the overall process is a specification consisting of the Statechart diagrams of all the objects involved, together with the generated and refined prototype of the UI. The algorithms underlying this process have been implemented and exercised on a number of examples.

show abstract

“…The new StateDs of the objects involved in affected CollDs are automatically obtained through an algorithm that we describe in Refs. [8,18,21]. For example, in the Mediator re®nement schema (a Mediator pattern de®nes an object that coordinates the interaction between a set of objects), each CollD, which speci®es interactions between objects of a set of highly interconnected classes, is automatically transformed in a way that the Mediator object, newly introduced, centralises the control of interactions.…”

Section: Overview Of Approachmentioning

confidence: 99%

Pattern-based refinement schemas for design knowledge transfer

Khriss

Keller²,

Hamid

2000

Knowledge-Based Systems

View full text Add to dashboard Cite

The transition from high-level to low-level design is a labour-intensive and time-consuming activity since it involves many iterations over design models to obtain a well-designed system. Moreover, it requires the knowledge and expertise of experienced developers. Design patterns provide proven design knowledge by capturing successful solutions to recurring problems which arise when building software systems. To transfer this design knowledge into detailed design, methodological support is needed. We provide such support with patternbased re®nement schemas.In this paper, we present a pattern-based approach to the correct stepwise re®nement of UML static and dynamic design models by application of re®nement schemas. A re®nement schema is composed of two compartments. The ®rst compartment describes the abstract model of the design, whereas the second compartment shows its corresponding detailed model after transformation and instantiation of one design pattern. We also propose a number of smaller transformations called micro-re®nements whose correctness is proven. These microre®nements can be composed into sequences to produce correct re®nement schemas. Our approach will allow for the construction of intelligent CASE tools that provide automatic support for the selection, management, and application of design patterns for the re®nement of design models. Such tool support will enable effective design knowledge transfer. q

show abstract

Automating the Synthesis of UML StateChart Diagrams from Multiple Collaboration Diagrams

Cited by 33 publications

References 9 publications

Unified use case statecharts: case studies

Unified use case statecharts: case studies

Automated Prototyping of User Interfaces Based on UML Scenarios

Pattern-based refinement schemas for design knowledge transfer

Contact Info

Product

Resources

About