By Topic

Scenarios and State Machines, 2007. SCESM '07: ICSE Workshops 2007. Sixth International Workshop on

Date 20-26 May 2007

Filter Results

Displaying Results 1 - 6 of 6
  • Sixth International Workshop on Scenarios and State Machines - Cover

    Page(s): c1
    Save to Project icon | Request Permissions | PDF file iconPDF (161 KB)  
    Freely Available from IEEE
  • Sixth International Workshop on Scenarios and State Machines - TOC

    Page(s): v
    Save to Project icon | Request Permissions | PDF file iconPDF (105 KB)  
    Freely Available from IEEE
  • On Generating EFSM Models from Use Cases

    Page(s): 1
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (250 KB) |  | HTML iconHTML  

    Use case-based behavior modeling of applications provides a modeler with an intuitive way of capturing requirements and therefore is considered to be more usable than other conventional behavior modeling techniques. However, such models lack sufficient structure to allow them to be analyzed and processed automatically. In this paper, we demonstrate how a combination of use case diagrams and UML class diagrams can be converted to extended finite state machine model. This algorithm addresses all standard UML 2.0 use case constructs as well as additional concerns such as conditional updates and exceptions. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Designing Tool Support for Translating Use Cases and UML 2.0 Sequence Diagrams into a Coloured Petri Net

    Page(s): 2
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (444 KB) |  | HTML iconHTML  

    Using a case study on the specification of an elevator controller, this paper presents an approach that can translate given UML descriptions into a Coloured Petri Net (CPN) model. The UML descriptions must be specified in the form of Use Cases and UML 2.0 Sequence Diagrams. The CPN model constitutes one single, coherent and executable representation of all possible behaviours that are specified by the given UML artefacts. CPNs consitute a formal modelling language that enables construction and analysis of scalable, executable models of behaviour. A combined use of UML and CPN can be useful in several projects. CPN is well supported by CPN Tools and the work we present here is aimed at building a CPN Tools front-end engine that implements the proposed translation. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Generating Code from Scenario and State Based Models to Address Crosscutting Concerns

    Page(s): 3
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (213 KB) |  | HTML iconHTML  

    Core application concerns are often modeled using either scenarios or state machines. Crosscutting concerns can also be modeled using either scenarios or state machines. Both scenario and state machine models can be used to generate code. When core and crosscutting concern models are the same type it is relatively straightforward to weave them together and generate code. However, when they are of dissimilar types a new approach must be taken. This paper describes how a core concern modeled as a scenario can be used with a crosscutting concern modeled with a state machine (and vice versa) to generate code. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Specifying Use Case Sequencing Constraints Using Description Elements

    Page(s): 4
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (194 KB) |  | HTML iconHTML  

    The ability to express sequencing constraints is critical to use case based software development. These constraints are needed to effectively compose use case behavior and support verification and validation activities such as simulation and testing. In this paper, we consider the addition of use case description elements to explicitly express sequencing constraints between use cases. We introduce two complementary constructs. One allows to specify which use cases need to precede a use case and how these preceding use cases are synchronized. The second construct allows to specify which use cases are enabled from a use case and how these use cases execute concurrently. We relate the introduced elements to UML activity diagrams and implicit sequencing based on preconditions and postconditions. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.