In my opinion, or you can say that in an easy manner a use case is a technique that captures 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 the brand value of the company, net worth, big market coverage, fast service, best product quality etc. They want to achieve these targets so that they can accomplish their goals and for that, they need 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 a bridge to crack their goals.
But the achievement of a target is not possible without getting proper requirements from the 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.
How Do You Write a Use Case?
Before talking about usecase writing first we should discuss 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 brief paragraph of text describing the scope of the use case.
Actors – A list of the types of users who can engage in the activities described in the use case. Actor names should not correspond to job titles.
Preconditions – Anything the solution can assume to be true when the use case begins.
Basic Flow – The set of steps the actors take to accomplish the goal of the use case. A clear description of what the system does in response to each user action.
Alternate Flows – Capture the less common user/system interactions, such as being on a new computer and answering a security question.
Exception Flows – The things that can happen that prevent the user from achieving their goals, such as providing an incorrect username and password.
Post Conditions – Anything that must be true when the use case is complete.
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.
In my opinion, a simple workflow diagram and user interface wireframes nicely complement the content of a use case and make them even easier for stakeholders to understand and provide feedback on.