Timed Use Case Maps

Jameleddine Hassine*, Juergen Rilling, Rachida Dssouli

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

11 Scopus citations


Scenario-driven requirement specifications are widely used to capture and represent functional requirements. Use Case Maps are being standardized as part of the User Requirements Notation (URN), the most recent addition to ITU-T's family of languages. UCM models focus on the description of functional requirements and high-level designs at early stages of the development process. How a system is executed over time and how this may affect its correctness and performance, however, are introduced later in the development process which may require considerable changes in design or even worse at the requirement analysis level. We believe that timing aspects must be integrated into the system model, and this must be done already at an early stage of development. This paper introduces an approach to describe timing constraints in Use Case Maps specifications. We present a formal semantics of Timed UCM in terms of Clocked Transition Systems (CTS).We illustrate our approach using an example of a simplified wireless system.

Original languageEnglish
Title of host publicationSystem Analysis and Modeling
Subtitle of host publicationLanguage Profiles - 5th International Workshop, SAM 2006, Revised Selected Papers
Number of pages16
StatePublished - 2006
Externally publishedYes

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume4320 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


  • Clocked Transition Systems
  • Performance
  • Timed UCM
  • Timing aspects
  • Use Case Maps
  • User Requirements Notation

ASJC Scopus subject areas

  • Theoretical Computer Science
  • General Computer Science


Dive into the research topics of 'Timed Use Case Maps'. Together they form a unique fingerprint.

Cite this