Scenario construction tool based on extended UML metamodel

Authors:
Michał Śmiałek;Jacek Bojarski;Wiktor Nowakowski;Tomasz Straszak
Affiliations:
,Warsaw University of Technology, Warsaw, Poland;Warsaw University of Technology, Warsaw, Poland;Warsaw University of Technology, Warsaw, Poland;Warsaw University of Technology, Warsaw, Poland
Venue:
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Year:
2005

Citing 7
Cited 2

Supporting Scenario-Based Requirements Engineering

IEEE Transactions on Software Engineering
Object-oriented methods (3rd ed.): principles & practice

Object-oriented methods (3rd ed.): principles & practice
Writing Effective Use Cases

Writing Effective Use Cases
Against Use Case Interleaving

«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Use Cases Considered Harmful

TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
Requirements use case tool (RUT)

OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Open issues in industrial use case modeling

UML'04 Proceedings of the 2004 international conference on UML Modeling Languages and Applications

Requirements-Level Programming for Rapid Software Evolution

Proceedings of the 2011 conference on Databases and Information Systems VI: Selected Papers from the Ninth International Baltic Conference, DB&IS 2010
Complementary use case scenario representations based on domain vocabularies

MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

Scenario based notations are becoming more and more popular as means for user requirements elicitation. They can be used in more formal specifications as part of detailed use case templates or in agile processes to capture informal user stories. Despite their significance in software engineering, scenarios seem not to be properly supported by appropriate tools. This paper describes a scenario construction tool that offers clear separation of the actual story from notions used therein. The tool is constructed as an extension to visual notation of UML's use cases. It is based on an extended UML metamodel in the area of activities and classifiers. This formal basis makes the tool capable of supplying the existing UML tools with an additional layer of requirements models based on scenarios and notions. This layer makes it possible to transform requirements directly into design-level models. The tool offers such transformation capabilities based on a simple model mapping. This transformation supports human efforts to keep the system's design consistent with the user's needs expressed through scenarios.