As complicated as it sounds, the answer is YES!! We need to learn how to use and implement some requests from our clients, so we need to know what they will need, those, in a nutshell, are our use cases, let’s get down to business and start learning.
Last time we talked about USP, we now know that getting our requirements well defined and organized is crucial for us to get good results, so use cases will help us.
Use Cases -according to TechTarget– «is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal».
A use case has these characteristics:
- Organizes functional requirements.
- Models the goals of system/user interactions.
- Describes one main flow of events, and possibly other ones, called exceptional flows of events.
- Is multi-level, so that one use case can use the functionality of another one.
As we saw in the last definition, we need use cases in order to satisfy our client and get things done properly, now let’s see how we can draw a use case.
As seen in Visual Paradigm tutorial, we need these steps:
- Identify the Actors (role of users) of the system.
- For each category of users, identify all roles played by the users relevant to the system.
- Identify what are the users required the system to be performed to achieve these goals.
- Create use cases for every goal.
- Structure the use cases.
- Prioritize, review, estimate and validate the users.
So now you know what is a use case, why it is important and some crucial characteristics of them, if you want to know more, you can see this quick guide on how to draw them:
-RC
Profesional learning while enjoying 