There’s an interesting thread on Seilevel’s requirements forum about why developers don’t read the specs and how to fix this problem. Sometimes the developers throw away the requirements. And that’s bad. But it is a symptom. Something is broken at a higher level.
Agile / Agile Project: Ratings / Requirements / Requirements Models / Software development / Use Cases
Posted on:
Nexus – Use Case Definition for Bundles
Yesterday, we identified the high priority goal for the third release of nexus to be supporting creation of bundles of articles. In this article, we will define the use cases we need to support.
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / UML Modeling
Posted on:
APR: Updated Domain Model
More iteration in our agile project. In this article, we make several updates to the domain model (UML class diagram) based upon discussions on all of the articles in the series. More than a couple dozen in the last day. Thanks to everyone who has helped with feedback and encouragement […]
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / UML Modeling
Posted on:
APR: Domain Model – UML Class Diagram
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 / Product Management / Requirements / Requirements gathering / Requirements Models / Software development / Software requirements specification / UML Modeling / Use Cases
Posted on:
APR: Mixing It Up With Design And Requirements
With a definition of the important use cases for our agile project, we can move to the logical next step – which is what exactly? Prototyping.
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Prioritizing Use Cases – Vote Three Times
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 […]
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Use Case Briefs
Each of the use cases defined as part of our use case names post is described at a high level of detail here. The goal is to get a broad view of the domain for our project so that we can focus on the most important elements. This is a […]
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Use Case Names
In our agile programming case study, we have two corporate goals, but one of them (learn Ruby on Rails) only drives constraints, not requirements. The other goal is to make it easier for people to find and read great content in our niche. This makes the documentation of goal-driven use […]
Business Analysis / Requirements / Requirements Models / Software development / Testing / Use Cases
Posted on:
The Difference Between Use Cases and Test Cases
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.