If you haven't already read the article, "Building a Content Management System using Lotus Domino: the rise of XML," elsewhere in this issue of DominoPower, you should do so now. It will provide some valuable background on the rise of XML and the need of a generic Content Management System.

For the rest of you, let's move on!

First things first: functional requirements specification
You may have gathered from the previous article that the first task in designing this system was to think up the architecture. This isn't quite true.

Strictly speaking, the first step in software design is actually to understand and document the software functional requirements. How can you know what your software architecture is meant to be if you don't know what the requirements are? You can't.

In fact, I did the architecture and the functional requirements in a loose parallel. I was able to do this partly because I had already built several major custom built Content Management Systems and knew what I was trying to build. The software functional requirements came together with the architecture.

I'm also not going to pretend that the functional requirements specification was as well defined and complete as the one in this article. It wasn't. What you see here is the end result, finalized, and cleaned up for publishing. During the development, it was a growing and changing list of features and functions with new stuff being added and other stuff being deleted all the time. I seem to remember using Microsoft Excel as the requirements management tool. The important thing is that there was a functional requirements specification, and it was actually used to drive development.

The software functional requirements specification is an effective way of describing everything your software is meant to do. If you can tick off every requirement and verify that your software meets that requirement, then your software is complete (in theory anyway).