Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / UML Modeling

APR: Domain Model – UML Class Diagram

Posted on:

Along with design sketches and requirements, as part of the concurrent design and requirements development for our agile project, we have created a UML class diagram representing the domain. This iterative process allows us to incorporate the benefits of each perspective rapidly with the others in our race to prototype […]

Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases

APR: Prioritizing Use Cases – Vote Three Times

Posted on:

In our agile project case study we defined corporate goals and user personas, and from our understanding created a list of use case names. We refined those use cases into use case briefs, filtering out some of the use cases (for the first revision) narrowing the list to six use […]

Business Analysis / Requirements / Requirements Models / Software development / Testing / Use Cases

The Difference Between Use Cases and Test Cases

Posted on:

People who are new to software, requirements, or testing often ask “What’s the difference between a use case and a test case?” This article answers that question, by building on earlier articles about use cases and use case scenarios. At the soundbite level, each use case has one or more scenarios, and each use case scenario would lead to the creation of one or more test cases.

Requirements / Requirements Models / Use Cases

What Are Use Case Scenarios?

Posted on:

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.