An evaluation of timed scenario notations

Hassine, Jameleddine; Rilling, Juergen; Dssouli, Rachida

doi:10.1016/j.jss.2009.09.014

Cited by 8 publications

(6 citation statements)

References 79 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Beyond the explanations regarding the analysis of timed models in general above, most approaches described in this section annotate scenario-based requirements formalisms with real-time requirements as well as timing effects induced by the platform resources (cf. [58] for an overview on timed scenario notations). Furthermore, these approaches provide different non-simulative techniques for their respective timing analyses.…”

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

“…Scenarios are usually described using message sequence charts (MSC) and UML sequence diagrams, including a variety of timed scenario notations, see, e.g., [13]. One of the main challenges in using scenarios for testing is to ensure that the chosen test scenarios are consistent and sufficiently formal to allow executable tester's generation.…”

Section: Model-based Testingmentioning

confidence: 99%

Model-based testing of software and systems: recent advances and challenges

Petrenko

Simão²,

Maldonado³

2012

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

show abstract

“…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

115

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

An evaluation of timed scenario notations

Cited by 8 publications

References 79 publications

Early timing analysis based on scenario requirements and platform models

Early timing analysis based on scenario requirements and platform models

Model-based testing of software and systems: recent advances and challenges

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

Contact Info

Product

Resources

About