Describing Use Cases with Activity Charts

Almendros-Jiménez, Jesús Manuel; Iribarne, Luís

doi:10.1007/11518358_12

Cited by 17 publications

(10 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is common to describe the sequence of events in structured language based on a pre-defined pattern, or by using Activity diagrams (Almendros-Jimenez and Iribarne, 2005), Sequence diagrams (Almendros-Jimenez and Iribarne, 2007), or Petri nets (Soares and Vrancken, 2008b). Within SysML, a Use Case may also be related to a SysML Requirements diagram.…”

Section: Sysml Use Case Diagrammentioning

confidence: 99%

User requirements modeling and analysis of software-intensive systems

Soares

Vrancken

Verbraeck

2011

Journal of Systems and Software

View full text Add to dashboard Cite

Section: Sysml Use Case Diagrammentioning

confidence: 99%

User requirements modeling and analysis of software-intensive systems

Soares

Vrancken

Verbraeck

2011

Journal of Systems and Software

View full text Add to dashboard Cite

“…Almendros-Jiménez and Iribarne [14] present a method to describe use case-based functional requirements with activity charts. The source models are use case diagrams and therefore their method is restricted to modeling sequences of use cases and not the behavior of each use case.…”

Section: Related Workmentioning

confidence: 99%

Transformation of aspect-oriented requirements specifications for reactive systems into aspect-oriented design specifications

Mussbacher

Kienzle

Amyot

2011

2011 Model-Driven Requirements Engineering Workshop

View full text Add to dashboard Cite

Model-driven engineering (MDE) promises faster and more reliable software development processes. A key factor of MDE is the transformation of models, allowing a software engineer to use the most appropriate modeling notation for a particular task. The earlier transformations can be applied during software development, the greater the potential cost savings. To that effect, we report on the transformation of aspect-oriented models for reactive systems development, i.e., from a scenario-based requirements model into a UML-based design model. We use Aspect-oriented Use Case Maps (AoUCM) as the requirements notation and Reusable Aspect Models (RAM) as the design notation. While AoUCM is ideally suited for the specification of the system workflow comprised of interactions between the environment and the system, RAM excels in providing a design view of system structure and defining the data dimension of the system including inputs and outputs. As the more abstract AoUCM models are transformed into more concrete RAM models, MDE ensures that the AoUCM workflow specifications do not have to be modeled again in RAM, thus avoiding a duplication of effort. We present transformation algorithms to show that an AoUCM-to-RAM mapping is indeed feasible and report on initial tool support for the transformation.

show abstract

“…The work presented in (Almendros-Jimenez and Iribarne, 2004) describes an approach to translate use case-based functional requirements to activity charts. The source models are use cases diagrams with support of inclusion and generalization relationships.…”

Section: Related Workmentioning

confidence: 99%

USER CONTEXT MODELS - A Framework to Ease Software Formal Verifications

2010

Proceedings of the 12th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Abstract:Several works emphasize the difficulties of software verification applied to embedded systems. In past years, formal verification techniques and tools were widely developed and used by the research community. However, the use of formal verification at industrial scale remains difficult, expensive and requires lot of time. This is due to the size and the complexity of manipulated models, but also, to the important gap between requirement models manipulated by different stackholders and formal models required by existing verification tools. In this paper, we fill this gap by providing the UCM framework to automatically generate formal models used by formal verification tools. At this stage of our work, we generate behavior models of environment actors interacting with the system directly from an extended form of use cases. These behavioral models can be composed directly with the system automata to be verified using existing model checking tools.

show abstract

Describing Use Cases with Activity Charts

Cited by 17 publications

References 15 publications

User requirements modeling and analysis of software-intensive systems

User requirements modeling and analysis of software-intensive systems

Transformation of aspect-oriented requirements specifications for reactive systems into aspect-oriented design specifications

USER CONTEXT MODELS - A Framework to Ease Software Formal Verifications

Contact Info

Product

Resources

About