It is easy to mix up the definitions of use case and use case scenario. A use case represents the actions that are required to enable or abandon a goal. A use case has multiple “paths” that can be taken by any user at any one time. A use case scenario is a single path through the use case. This article provides an example use case and some diagrams to help visualize the concept.
Category Archives: Use Cases
Sample Use Case Example
Here’s an example of a use case that has some system complexity. The user interacts with the main system that we are describing. The system also interacts with two external systems. This use case example shows how to describe the steps that demonstrate all interactions with the system.
Agile Development of Use Cases
We proposed a strategy for developing use cases as part of an agile development methodology last week. In this article, we will look in more detail at that proposal, and also look at a specific way to apply agile techniques to the development of the use cases. What we propose is essentially incremental development of use cases, and starting what comes next as soon as you can.
Posted in Agile, Requirements, Requirements Models, Requirements gathering, Software development, Use Cases
Tagged managing data
2 Comments
How To Start The Use Case Process For Agile Software Development
One of the goals of agile software development is to deliver value quickly and iteratively. One of the most effective ways to begin the software development process is with use cases. To deliver with agility, you start with the most valuable use case, bang it out, and then move on to the next most valuable use case. How do you know which use case is the most valuable if you haven’t defined all the use cases first?
Posted in Agile, Business Analysis, Prioritization, Product Management, Project Management, Requirements, Requirements Models, Requirements gathering, Software development, Use Cases
Tagged agile development, agile requirements, agile requirements process, agile software development, managing data, software development process, use case process, use cases, user centric design
5 Comments
Posted in Business Analysis, Product Management, Requirements, Requirements Models, Requirements gathering, UML Modeling, Use Cases
Tagged business requirements, Business Rules, business use case, managing data, requirements management, sample use case, statecharts, UML Modeling, uml statechart, use case analysis, use case example, use cases
6 Comments
Use Case vs. Process Flow – Failure Handling
Should you use use cases or process flow diagrams to document business requirements? At some level, they both document the same thing, they just document it differently. The best requirements will come from doing both – but what if you are forced to choose one? What are the tradeoffs between use cases and process flows? In this article we look at the documentation of failure handling.
Posted in Business Analysis, Business Process Modeling, Product Management, Requirements, Requirements Models, Requirements gathering, Use Cases
Tagged Business Process Modeling, failure handling, managing data, process modeling, requirements management, sample use cases, use case examples, use case extensions, use cases
13 Comments
Writing Use Cases For Estimation
You write use cases to define the scope of your project. Use cases describe what people are using your product to accomplish. Use cases provide a framework for defining the details of the product. You can estimate your project effort with use cases. But you have to write the use cases at the right level of detail.
How To Write Use Case Preconditions and Triggers
Use case writing is key to effective requirements management. Each use case represents a single idea or logically grouped behaviors. When you define a use case, there are several mistakes you can make. Preventing those mistakes is the first order of business. The second order of business is making sure that the use cases in the system work together. This requires an understanding of the context in which the use case happens. To fully understand a use case you have to know what is promised to be true before the use case happens, as well as what causes the use case to happen. These are subtly different.
Posted in Business Analysis, Product Management, Project Management, Requirements, Requirements Models, Use Cases
Tagged business process, business use case, cost estimates, cost estimation software, cost estimation techniques, free excel spreadsheet, free excel spreadsheets, managing data, project cost estimation, Requirements, software cost estimation, software requirements management, use case analysis, use case development, use case estimate, use case modeling, Use Cases, use cases
6 Comments
Software Cost Estimation With Use Case Points – Final Calculations
The final step in project cost estimation with use case points is to do the math. First you identify the technical and environmental factors that influence your environment and describe your team. Then you analyze the use cases and actors that describe the expectations of the software and who has them. Finally, you bring it all together to do the math.
Posted in Business Analysis, Product Management, Project Management, Requirements, Requirements Models, Use Cases
Tagged business process, business use case, cost estimates, cost estimation software, cost estimation techniques, managing data, project cost estimation, Requirements, software cost estimation, software requirements management, use case analysis, use case development, use case estimate, use case modeling, Use Cases, use cases
10 Comments
Latest Articles
Comments on all Articles
