Timed Use Case Maps

Hassine, Jameleddine; Rilling, Juergen; Dssouli, Rachida

doi:10.1007/11951148_7

Cited by 13 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Hassine [55,56] annotates the scenario notation of Timed Use Case Maps (TUCM) [57] and its underlying architecture with timing-relevant effects. The annotated TUCM model is transformed into an Abstract State Machine model [14] that is simulated in an external tool, similarly to our approach.…”

Section: Analysis Of Timed Scenario-based Modelsmentioning

confidence: 99%

Early timing analysis based on scenario requirements and platform models

2022

View full text Add to dashboard Cite

Distributed, software-intensive systems (e.g., in the automotive sector) must fulfill communication requirements under hard real-time constraints. The requirements have to be documented and validated carefully using a systematic requirements engineering (RE) approach, for example, by applying scenario-based requirements notations. The resources of the execution platforms and their properties (e.g., CPU frequency or bus throughput) induce effects on the timing behavior, which may lead to violations of the real-time requirements. Nowadays, the platform properties and their induced timing effects are verified against the real-time requirements by means of timing analysis techniques mostly implemented in commercial-off-the-shelf tools. However, such timing analyses are conducted in late development phases since they rely on artifacts produced during these phases (e.g., the platform-specific code). In order to enable early timing analyses already during RE, we extend a scenario-based requirements notation with allocation means to platform models and define operational semantics for the purpose of simulation-based, platform-aware timing analyses. We illustrate and evaluate the approach with an automotive software-intensive system.

show abstract

Section: Analysis Of Timed Scenario-based Modelsmentioning

confidence: 99%

Early timing analysis based on scenario requirements and platform models

2022

View full text Add to dashboard Cite

show abstract

“…Hassine et al also provided a formal semantics for UCM, but this time based on Abstract State Machines (ASM, [38]), with tool support for simulation [88]. They further investigated the use of quantitative time constraints in UCM models with a UCM extension called Timed Use Case Maps, for which they provided additional semantics based on more appropriate formalisms, namely timed automata [90], clocked transition systems [89], and again ASM [86]. Hassine's thesis [85] is the best document where these extensions and semantics are used, and a recent survey provides a comparison with related timed scenario languages [92].…”

Section: Formalizationmentioning

confidence: 99%

User Requirements Notation: The First Ten Years, The Next Ten Years (Invited Paper)

Amyot¹,

Mussbacher²

2011

JSW

110

View full text Add to dashboard Cite

The User Requirements Notation (URN), standardized by the International Telecommunication Union in 2008, is used to model and analyze requirements with goals and scenarios. This paper describes the first ten years of development of URN, and discusses ongoing efforts targeting the next ten years. We did a study inspired by the systematic literature review approach, querying five major search engines and using the existing URN Virtual Library. Based on the 281 scientific publications related to URN we collected and analyzed, we observe a shift from a more conventional use of URN for telecommunications and reactive systems to business process management and aspect-oriented modeling, with relevant extensions to the language being proposed. URN also benefits from a global and active research community, although industrial contributions are still sparse. URN is now a leading language for goal-driven and scenario-oriented modeling with a promising future for many application domains.

show abstract

“…• It provides a novel approach to describe availability requirements into UCM models in a flexible manner. • It extends our ongoing research towards the construction of a UCM-based framework to describe, simulate and analyze real-time systems [2] [3] [4] [5] [8]. The remainder of this paper is organized as follows.…”

Section: Introductionmentioning

confidence: 99%

“…The standard UCM language [1] does not describe semantics involving time, allowing for different interpretations of timing information, such as the time needed for a transition or a responsibility to complete. To tackle this issue, we have extended the UCM language with timing constraints [2] [3] allowing for quantitative analysis (such as Schedulability Analysis) at a high level of abstraction [4] [5]. In a related work, Petriu et al [6] have augmented UCM language with performance related data such as arrival characteristics for start points, probabilities/weights on branches, plugins and dynamic stubs.…”

Section: Introductionmentioning

confidence: 99%

Early Availability Requirements Modeling Using Use Case Maps

Hassine

2011

2011 Eighth International Conference on Information Technology: New Generations

Self Cite

View full text Add to dashboard Cite

The design and implementation of distributed real-time systems is often dominated by non-functional considerations like timing, distribution and fault tolerance. As a result, it is increasingly recognized that non-functional requirements should be considered at the earliest stages of system development life cycle. The ability to model nonfunctional properties (such as timing constraints, availability, performance and security) at the system requirement level not only facilitates the task of moving towards real-time design, but ultimately supports the early detection of errors through automated validation and verification. This paper introduces a novel approach to describe availability features in Use Case Maps (UCM) specifications. The proposed approach relies on a mapping of availability architectural tactics to UCM components. We illustrate the applicability of our approach using the ISSU (In Service Software Upgrade) feature on IP routers.

show abstract

Timed Use Case Maps

Cited by 13 publications

References 9 publications

Early timing analysis based on scenario requirements and platform models

Early timing analysis based on scenario requirements and platform models

User Requirements Notation: The First Ten Years, The Next Ten Years (Invited Paper)

Early Availability Requirements Modeling Using Use Case Maps

Contact Info

Product

Resources

About