A Use Case Description Tutorial For The Business Analyst
What Are Use Case Studies?
The purpose of Use Case studies are to show the situation(s) in which a program is going to be used by the end user.
It is like a story board in that it tells a story, describing how the program is going to work and the input of the user.
A Use Case does not document how the program is developed. There is also no detail about any of the programming. The aim is to express the concept behind the creation.
The Types Of Use Case Study
Generally a use case comes in two types, which are:
1.The essence use case
This is created at the beginning of the project. Its purpose is to show what a program is going to do. With this case there are no technical terms or jargon used, or mention of any programming.
2.The Real Use Case
This will give you a more hands on description of the application. There will be slides which show how the system is to be operated. The Real Use Case is put together mid-way through the programs development.
The real use case will give the stakeholders a glance of how instrumental the program will be.
It is good practice that a Use Case will be written for all the possible scenarios, the development team can think of.
The constant devising of Use Cases ensures that the application is thoroughly put through its paces. With in the case studies notes and suggestions can be made for the betterment.
Again this gives the stake holders the ability to see the end result of the program before it happens, which can save time and money in the long run.
While the Business Analyst writes the uses cases it’s their job to ask for suggestions. Getting input from the IT department is also essential.
They also take into account what the end user wants. The Business Analyst will always draw up scenarios with the stakeholders in mind.
Key benefits of Use Case studies
As you may have gathered the Use Case is a communication tool. It gives the end user the chance to give their thoughts on what is needed in the system.
It allows the stakeholders to see the users interactions with the system and then suggest improvements.
The Use Case is the best way to communicate to the IT department what the system will be used for. It describes in a hands on manner how the application will be used within the system.
It gives the user the chance to say if the system is doing what is intended or not. It also gives the IT department the same opportunity.
It allows everybody the chance to know what will be expected when the program is complete.
The case study will allow stakeholders, the IT department and end users the chance to be satisfied before completion and outcome of the project.
Use Case Studies For More Than Just Scenarios
It’s also important to note that a Use Case study can be more than just a means to show scenarios of an application. They can also be a pivotal part of training and crucial documentation.
After the project is done the end user or stakeholders may want to keep the Use Case studies for a guide to help develop training manuals. This is great news for the business Analyst that takes the time to present the use case studies clearly and succinctly.