Earlier this year the new RIBACPD.com site went live. Below is a bit of background to how we went from requirements through to the finished product. Those readers of this blog from the construction industry will probably see some big parallels between software development and construction.
(and as always with these things - the hard work was not done by me - well done Chris and Chris and John the main designer, developer and QA-er behind this project).
Fig 1 below shows the main requirements document. This forms part of the project plan after a business case has been agreed. Requirements are testable - you cannot have a requirement if you cannot verify it has been met. Each requirement is categorised as "Must be done", "Should be done", "Could be done" or "Won't be done". The volume of comments and track changes in the document below clearly show what an important process this is.
|Fig 1 - A well commented fourteen page requirements document is where it all really starts|
|Fig 2 - Example concept sketch design on paper for the home page|
|Fig 3 - A detailed design document then gets down to the nitty gritty of how things work on each page|
|Fig 4 - And then through some clever software development the final site pops out|
|Fig 5 - Another example of concept designs - this time for the "basket"|
|Fig 6 - And the finished product - note that the "basket" changed to "shortlist"|