Name and Description A use case is normally named as a verb-phrase and given a brief informal textual description. Requirements The requirements define the formal functional requirements that a use case must supply to the end user. They correspond to the functional specifications found in structured methodologies.
A use case model shows a view of the system from the user perspective, thus describing what a system does without describing how the system does it. UML can be used to analyze the use case model, and to derive system objects and their interactions with each other and with the users of the system.
Using UML techniques, you further analyze the objects and their interactions to derive object behavior, attributes, and relationships.
A use case provides developers with a view of what the users want. It is free of technical or implementation details. We can think of a use case as a sequence of transactions in a system.
The use case model is based on the interactions and relationships of individual use cases.
A use case always describes three things: In a use case, an actor using the system initiates an event that begins a related series of interactions in the system.
Use cases are used to document a single transaction or event. An event is an input to the system that happens at a specific time and place and causes the system to do something.
For more information about use case symbols and how to draw use case diagrams, see Chapter 2. Figure shown below is a use case example of student enrollment at a university.
Notice that only the most important functions are represented. The Add Student use case does not indicate how to add students, the method of implementation. Students could be added in person, using the Web, using a touch-tone telephone, or any combination of these methods.
The Add Student use case includes the Verify Identity use case to verify the identity of the student. The Purchase Textbook use case extends the Enroll in Class use case, and may be part of a system to enroll students in an online course.
A use case example of student enrollment. It may seem as if the Change Student Information use case is a minor system feature and should not be included on the use case diagram, but because this information changes frequently, administration has a keen interest in allowing students to change their own personal information.
The fact that the administrators deem this to be important not only justifies, but calls for, the use case to be written up.
Students would not be allowed to change grade point average, outstanding fees, and other information. This use case also includes the Verify Identity use case, and in this situation, it means having the student enter a user ID and password before gaining access to the system.
View Student Information allows students to view their personal information, as well as courses and grades. A use case scenario example is shown in the figure below. A use case scenario is divided into three sections:This example use case shows how a use case can be developed with incrementally increasing detail.
First, the name of the use case is identified, then a simple version of the use case is defined. Finally, a formal use case is defined. Use Case Templates. About This is a quick summary of how to write use cases. Advice.
The name should start with a strong verb. A use case is a set of scenarios. This Use Case Diagram is a graphic depiction of the interactions among the elements of University Admission Management System.
It represents the methodology used in system analysis to identify, clarify, and organize system requirements of University Admission Management System. System executes “enrolment in courses” component for the picked courses. System registers (saves) study year data for the student in question (“fees paid” not checked).
System executes “add to turma” component in case of 1st study year.
A use case diagram can identify the different types of users of a system and the different use cases and will often be accompanied by other types of diagrams as well. The use cases are represented by either circles or ellipses. UML CASE tool - UML diagrams, use case modeling, reverse engineering and more Visual Paradigm for UML (VP-UML) is a superior UML tool that supports full software lifecycle - analysis, design, construction, testing and deployment.