Content tagged with: use cases
Use Cases are a classical format used in UML to describe user scenarios and document requirements. They have been mostly replaced by user stories when software development teams adopt Agile approaches like Scrum. This article by Paul Raymond discusses how classical use cases can be use to expand user stories during requirements elicitation in Scrum sprints.
Modelling is rarely at the forefront of discussions when looking at agile and the agile way of working. This is surprising because it has so many benefits with respect to communication and understanding.
The use cases model is used to capture requirements. The use case model is a part of UML (Unified Modeling Language), a standardized design notation for the design and development of object-oriented software. Its simplicity in terms of notations and expressiveness makes it easier to use both by customers and developers.
Eliciting requirements and sharing the vision about the end-product are vital tasks in Business Analysis that facilitates developing quality applications. Use Case analysis is one of the most powerful elicitation techniques prevalently used by Business Analysts.
This Unified Modeling Language (UML) tutorial shows how to start with a use case and how to elaborate it into activity, class, sequence, and communication diagrams. This tutorial is a must for beginners who want to understand the relationships between different UML diagrams! It introduces the life cycle and evolution of a granular business case.
The control-flows for five kinds of UML use cases are analyzed: for common use cases, variant use cases, component use cases, specialized use cases and for ordered use cases. The control-flow semantics of use cases – and of the uses-relation, the extends-relation and the precedes relation between use cases – is described in terms of flowgraphs. Sequence diagrams of use cases are refined to capture the control-flow adequately. Guidelines are given for use case descriptions to attain a well-defined flow of control.
In an Unified Modeling Language (UML) use case diagram, an include dependency is a generalization relationship that describes the inclusion of the behavior described by another use case. A UML use case can include more than one use cases and it can be included in multiple use cases.
Starting from the relationship between the requirements and the test cases, Raul Rugiero proposes in this article to improve the notation of UML uses cases to achieve a better management of the relationship between UML uses cases their related test cases.
This short tutorial explain how to draw a UML use case diagram for an ATM system. A use case diagram can portray the different types of users of a system and the various ways that they interact with the system.
This short tutorial shows how to model the elements of a use case diagram: use cases, actors, associations, system.