Use case description template dennis

An effective Use Case should provide a detailed step-by-step description of how the system will be used by its actors to achieve the planned outcome.

The purpose of the Use Case is to tie the business needs of the system to the design parameters of the system to ensure that the completed system achieves the goals established by the business requirements. The level of detail in Use Cases may vary greatly depending on the size and complexity of the system being designed. ABC Corp. SAP to help manage material ordering and inventory management. Use Case formats and contents may vary based on system requirements, organizational standards, or unique situations.

However, a majority of Use Cases consist of some fundamental contents which may be applied across a wide range of system types. This section will provide explanations for each section of the Use Case. Name of Use Case: Provide a short name for the use case which should lend itself to the objective of the system. Description: This section should provide a description of both the reason for using the use case and the expected outcome of the use case. Actors: Actors may be primary or secondary.

Primary actors are the people who will be initiating the system described in the use case. Secondary actors are those will participate in the completion of the use case. Precondition: This section should describe any conditions that must be true or activities that must be completed prior to executing the use case.

Postcondition: This section should describe the state of the system at the conclusion of the use case. Postconditions may include conditions for both successful and unsuccessful execution of the use case. Use cases add value because they help explain how the system should behave and in the process, they also help brainstorm what could go wrong.

They provide a list of goals and this list can be used to establish the cost and complexity of the system. Project teams can then negotiate which functions become requirements and are built.

Depending on how in depth and complex you want or need to get, use cases describe a combination of the following elements:. Write the steps in a use case in an easy-to-understand narrative. Kenworthy outlines the following steps:.

Below, are examples of three use cases with increasing levels of complexity. For our purposes we have defined them as Simple, Middleweight and Heavyweight use case for doing the laundry. In each of these types of uses cases you will see that:.

Skip to main content. Improving the User Experience. Use Cases A use case is a written description of how users will perform tasks on your website. Benefits of Use Cases Use cases add value because they help explain how the system should behave and in the process, they also help brainstorm what could go wrong.

Welcome to the Reimagined HHS. They are a powerful tool — and I hope you find this tutorial useful in applying use cases in your analytical work today. First of all, why would you write a use case?

What is this for? Why do you need to do it? How do I communicate with my software developers to make sure I get what I want out of the software system? Both business and technical users should be able to really understand them and provide feedback on them. As business analysts, we use them as a communication tool, really, to literally bridge that gap or really connect people together, in terms of a common technique, common language about what the software will do.

What is a use case? How does it solve these problems for us as analysts, as technical people, as business users? This is really important. Use case is very specific and dialed in, in terms of how that user actually interacts with that software system to achieve a goal.

This is a more granular goal. Very specific and concrete things that a user can do with the software system, and it captures all the ways that that user and system can interact. All those variations of what can go wrong in variant paths in the scope of the system only.

This is what allows us to get at the software requirements. What is included in a use case? You can take notes if you want, but you can also download our template. There should also be a link below this video. You want to start with a name , and just like with a business process, you want that name to be verb-noun.

Next is a brief description , and one of the things I really like to include in my brief description is a sentence that really gets clear about the scope. The actors : who are the users, or the roles, or the types of actors that might use the system?

Multiple people can fill that role with the system. Are you a purchaser?