What Are Use Cases and how to identify it?
In my opinion, or you can say that in an easy manner a use case is a process that represents requirements for a software application. If you have analytical mindset then this work is for you.
But still the question is same that what is a usecase and how to write them so here I tried to make this puzzle solved by my this article. Of course my this article will be very useful for the trainee business analysts who are in the nurturing process to become a Business analyst.
What Are Use Cases?
See each and every company or customer have their business goals like brand value of the company, net worth, big market coverage , fast service, best product quality etc. They wants to achieve these targets so that they can accomplish their goals and for that they needs a system which can help them to achieve their goals. So an IT-solution given by a business analyst to the client or customer is bridge to crack their goals.
But achievement of target is not possible without getting proper requirements from customer so taking that requirements and implementation of these requirements into a useful system is an important task for a BA. Here we use Usecase which tell us that how a user will interact with a solution to achieve a specific goal. Even these usecase describes the step by step process a user goes through to complete that goal using a software system. In usecase we consider all possible way of interaction between a customer and system.
Identification of Usecase
Usecase identification is a very important task because the whole process is based on it. Identification is followed by the scenario-based elicitation process carry on by asking what externally visible, observable value that each actor desires. The process required few important things-
- The functions want by actors from system.
- System will store information and about what activities will be done by an actor means update, delete, read etc.
- Information transfer by system to actor for any change.
- About external events and what actor informs the system of those events?
How Do You Write a Use Case?
Before talking about usecase writing first we should discuss about the essential elements of usecase writing which is as follows:
Name – A clear verb/noun or actor/verb/noun descriptor that communicates the scope of the use case.
Brief Description – A small paragraph related to describing the scope of the use case.
Actors – Users who will interact with the system and who support them.
Preconditions – Assumption are includes into this part related to the process.
Basic Flow – For achieving the goals a step by step process taken by an actor even system behavior is also part of this scenario means how it will react to actor.
Alternate Flows – Apart of basic flow the uncommon part of user/system interactions, like being on a new computer and answering a security question.
Exception Flows – All the obstacle to achieving user its goal is to be consider in this part like providing an incorrect username and password.
Post Conditions – After usecase completion is about true condition.
Remember one thing use case is about what the system will do not about how it will do. Through a usecase diagram or usecase a development team can understand what they have to do. Use case is also about the business user needs to do , but it’s not about the software needs to do to support the business user.
A simple usecase diagrams and prototypes is easier way for stackholders to understand and for the project success.
Few things related to use case diagrams
- Always develop a usecase diagrams according to the primary actor’s prospective.
- A usecase diagram refines as the process goes on so it should be easier on start off by keeping highest views.
- Usecase diagram follows functionality not technicality means it should base on “What” process then “How”.
Use case levels
Use case level is about the granularity which means which information is organized within use case specifications, and to some extent and what level followed to wrote these Usecases. If the level of granularity is follow then it makes a communication easier between various stack holders.
For an example
Suppose for a Product if level is Cloud then summary is about High . Few are as follows for you-
|Sea||Sell furniture||User goal|
|Clam||Insert order line||Low level|