Guidance for Use-Case Templateĭocument each use-case using the template given in the end of this chapter. Post Condition : Describe the state of the system after a use-case has run its course. Pre-condition : Conditions that must be met prior to starting the use-case.įlow of events : Description of interaction between the system and the actor. Name : Descriptive name that illustrates the purpose of the use-case.ĭescription : Describes what the use-case does in couple of sentences.Īctor : List any actors that participate in the use-case. Use-case engage the user in the requirement process. Use-cases force developers to think from the end user perspective. Use-cases are relatively easy to write and read compared to the traditional requirement methods. It is an easy means of capturing the functional requirement with a focus on value added to the user. Benefits of a Use-CaseĪ use-case provides the following benefits − It is more concerned with what is performed by the system in order to perform the sequence of actions. The actor can be a human or an external system.Ī use-case specifies the flow of events in the system.
Use case diagram program free software#
In software and systems engineering, a use-case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal.
The actor is the Who of the system, in other words he the end user. The use-case describes the system’s behavior under various conditions as it responds to a request from one of the stakeholders, called the primary actor.
What is a Use-Case?Ī use-case describes a sequence of actions, performed by a system that provides value to an actor. As we know there are various phases in the development cycle and the most used phase for Use-cases would be during the requirements gathering phase. It is basically used in Software life cycles. These are not only important but necessary requirement for software projects. One of the nine diagrams of UML’s are the Use-case Diagram.
0 kommentar(er)
