User Interface Prototyping Based on UML Scenarios and High-Level Petri Nets

Elkoutbi, Mohammed; Keller, Rudolf K.

doi:10.1007/3-540-44988-4_11

Cited by 34 publications

(21 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Figure 16 provides an example illustrating this setting (scenarios are represented as StateDs In order to solve this problem, we associate to each scenario a distinct color and introduce a "chameleon token" [10] (token that belongs to all integrated scenarios). After firing a transition of the integrated scenario, this token will take the color that is the intersection between its set of colors and the set of the state colors.…”

Section: Resolving the Interleaving Problemmentioning

confidence: 99%

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

Section: Resolving the Interleaving Problemmentioning

confidence: 99%

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

show abstract

“…Another similar work to our contribution is [EK00,EKK99] in which state machines and Petri-nets are used to specify GUI in UML. In the quoted approaches they specify user interaction but they also lack of use case relationships handling.…”

Section: A Case Study For Gui Designmentioning

confidence: 96%

“…In particular, they describe the presentation logic of an applet-based system (similar to [EK00,EKK99]), in which a set of applet windows are shown to the user, and the user interacts with them in order to put and get data from the system. With respect to this choice, our aim is not to constraint the implementation to a particular window system but the acceptance of the JAVA swing classes between developers allows us to assume the reader is familiarized with the implementation details of the GUIs.…”

Section: A Case Study For Gui Designmentioning

confidence: 99%

Describing Use Cases with Activity Charts

Almendros-Jiménez

Iribarne

2005

Metainformatics

View full text Add to dashboard Cite

Abstract. The Model-Driven Development (MDD) describes and maintains models of the system under development. The Unified Modeling Language (UML) supports a set of semantics and notation that addresses all scales of architectural complexity by using a MDD perspective. Use Cases and Activity Charts are two modeling techniques of the UML. The first one helps the designers to identify the requirements of the system discovering its high level functionality. The second one helps them to specify the internal behaviour of a certain entity or subsystem of the software developed, such as a database, a graphical interface, a software component, or any specific software. However, there is not a direct way to relate/model the requirements (use cases) with their internal behavior (activity charts). In this paper we present a method for describing use cases with activity charts. Our technique also allow us to identify the two main use case relationships -include and generalization-by means of activity charts. As a case study, we will show how to use the activity charts to describe graphical user interfaces (GUI) from use cases. In particular, we will show an Internet book shopping system example.

show abstract

“…They have a number of limitations, and, in many cases, there are substantial technical reasons to prefer CP-nets over, e.g., UML state machines. The latter lack a well-defined execution semantics, do not support modelling of multiple instances of classes, and do not scale well to large systems [30,55]. CP-nets may be seen as a convenient supplement to the well-established UML diagram types such as sequence diagrams and class diagrams.…”

Section: Introductionmentioning

confidence: 99%

Application of Coloured Petri Nets in System Development

Kristensen

Jørgensen

Jensen

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Coloured Petri Nets (CP-nets or CPNs) and their supporting computer tools have been used in a wide range of application areas such as communication protocols, software designs, and embedded systems. The practical application of CP-nets has also covered many phases of system development ranging from requirements to design, validation, and implementation. This paper presents four case studies where CP-nets and their supporting computer tools have been used in system development projects with industrial partners. The case studies have been selected such that they illustrate different application areas of CP-nets in various phases of system development.

show abstract

User Interface Prototyping Based on UML Scenarios and High-Level Petri Nets

Cited by 34 publications

References 10 publications

Automated Prototyping of User Interfaces Based on UML Scenarios

Automated Prototyping of User Interfaces Based on UML Scenarios

Describing Use Cases with Activity Charts

Application of Coloured Petri Nets in System Development

Contact Info

Product

Resources

About