Archive of Agile Project: Ratings Articles

Download the screenshots of the first iteration (build 0060) of the ratings site in this article.

Sorry about not going live over the weekend. I’ve been fighting with some deployment issues in getting things running on our host server. In some sense, this is to be expected, as we’ve never done it before, and there is a whole lot of new technology for us. So, we’ve found some folks with Ruby on Rails experience, and they are going to help us debug whatever we were doing wrong.

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 people to start playing with it.

Just a quick update on the prototype for our agile project. We’ve dramatically improved test coverage, implemented authentication-restriction for some functionality, and refactored a litte of the code. Read on for the latest stats on coverage and testing.

Made some progress on the prototype for our agile project, getting Users and Articles (see the domain model) mostly implemented and partially tested, and some other parts of the application completed. Ruby has some interesting features for tracking statistics. Read on if you’re interested in that sort of thing.

This morning I finished up the infrastructure setup for our project. A bunch of under the hood work. Definitely required some propeller-head skills. The goal of this work is to get us to a working prototype as soon as possible. There are a couple links to some good agile testing articles, and the rest of this one is a quick list of what we did on Friday and today.

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 - just awesome!

We defined the vision for our agile project last week, and in this article propose an addition.

Our agile project is to create a site that lets you rate articles. In our corporate goals, we defined the goal to make it easier for people to find and read great content. Last night I was doing some research on social networks and thinking about the nature of our ratings approach. In this article I share some of those thoughts, and the reason for changing the ratings approach relative to previous designs.

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 a working site.

This article reviews the domain model.