In the Unified Modeling Language (UML), use cases describe the system from the user model view, also known asscenario view. Use case diagrams model the functionality of a system. The main components of a use case are the Title (goal), Primary Actor, Scope, Level, Story.
This article from Willem Van Galen outlines a standard approach for representing basic event-driven architecture (EDA) aspects in system use case models. He explains that there are two ways where use cases can be coupled: command-and-control and publish-and-subscribe. The article introduces the concept of Event Manager and describes the Event Manager use cases. His conclusion …
This blog post discusses the role of primary and secondary actors in UML use cases. Primary Actors are actor(s) using the system to achieve a goal. The Use Case documents the interactions between the system and the actors to achieve the goal of the primary actor. Secondary Actors are actors that the system needs assistance …
This article presents a tool for the reuse of use case diagrams by storing their information in OWL ontology and the use of Semantic Web technologies. Software reuse is defined as the use on a new project of any artifact created before. This practice has significant benefits in reducing costs and increasing quality and productivity …
This blog post discusses how and when to use UML use cases in Agile Scrum projects. Use cases are more specific and they describe how your system will act. User stories are focused on the result and the benefit of the thing you’re describing. According to the author use cases shouldn’t be used in Agile …