Rolf presented a valid critique and some questions on our previous article announcing the launch of nexus. I started writing a long response, and realized it would work well as an article for analysis of our process over the last month. Here it is.
APR: Naming Our Product
We’ve come up with a name for the site we’re creating as part of our agile project. Read on to see our rationale.
APR: First Prototype Almost Done
The first prototype is almost done – I just need to add a couple presentation elements (listing articles by date submitted, highest scoring). When I get the site up (I still need to read how to use Capistrano to deploy a Rails site), we’ll open it up for a few […]
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 […]
APR: Updating Our Vision
We defined the vision for our agile project last week, and in this article propose an addition.
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 […]
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.
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 […]
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 […]