Search DominoPower's 11,323 Lotus-related article archive 
Home
EasyPrint
News details Click here for the RSS feed's XML code. This is not a browser URL.
Articles-only Click here for the RSS feed's XML code. This is not a browser URL.
Twitter Feed Click here for the Twitter feed.
PROGRAMMING POWER
Building a Content Management System using Lotus Domino: software architecture and system requirements
By Andrew Stuart

About this series
Andrew Stuart's previous articles have dealt with little bits of code designed to get tiny tasks done and to add small features to your systems. He's now going to start at the other end and examine the process of building a full software application from the start. This is the second in a series of articles in which he will relate the story of how he went about designing and developing an XML-based CMS (Content Management System) for Lotus Domino. In this segment, he goes into the designing of the software architecture and specifying the system requirements. Future articles will get down to the nuts and bolts of putting it all together.

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.

"Hey you! Stop nodding off! This is important stuff."

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).


1  ·  2  ·  3  ·  Next »
Other articles you might like
Home > Internet Technologies > XML (11 articles)
   How to create a Web service to extract data from XML documents
   Building an XML based Content Management System using Lotus Domino: wrapping it up
   Building an XML based Content Management System using Lotus Domino: overview of the content administration system
Home > Strategies > Content Management (10 articles)
   Lotus acquires Aptrix, announces Lotus Workplace Content Development
   Building an XML based Content Management System using Lotus Domino: wrapping it up
   Building an XML based Content Management System using Lotus Domino: overview of the content administration system
Get Weekly Email Updates
Subscribe to our regular weekly email newsletter. It's packed with tips, reviews, deep analysis, and the latest news.
 
Recent DominoPower Articles
Lotusphere 2010: mobility and collaboration
2010: A Lotusphere of change
Five trends for 2010
DominoPower TV Episode 1: Inside a strategy session with Teamstudio
More about Domino log files
Say goodbye to the Uh-Ohs. Long live the Tens.
Why your log.nsf might not be purging properly
Latest Lotus Headlines
Recommended Maintenance - Lotus Notes Traveler
Here are the slides and other materials from our Lotusphere session
Microsoft OCS awareness in Lotus Connections and Websphere Portal?
SnTT: XPages Blank Calendar Control (Part 2), adding data
Have your Lotus Notes calendar display multiple time zones
Sample Database for Microsoft Office and Lotus Symphony Integration
Symphony 3.0 beta signals another attack on Office
>> Read all the news
More from the ZATZ journals
Computing Unplugged: The iPad: Apple's latest heartbreaker
David Gewirtz Online: CNN commentary and analysis
OutlookPower: Running auto-respond rules when Outlook is closed
-- Advertisement --

Power Tools 6.0 is a set of 90 administrative utilities for Lotus Notes & Domino
Power Tools simplifies management of the Notes/Domino environment by automating routine tasks. Power Tools can manage or monitor mail files, groups, ACLs, agents, LOG.NSF, templates and more.

Download a trial version from helpsoft.com.
-- Advertisement --

Mark your calendar for in-depth Lotus training, May 12-14, Boston
Join experts and peers May 12-14 in Boston for educational and networking events that deliver real-world Lotus training so you can increase productivity and efficiency in your company, advance your skills, and squeeze the most from your current environment. One registration gets you into THE VIEW's Admin2010 and Lotus Developer2010.

Register by December 31 to save $350.
ZATZ Home  ·  News  ·  Back Issues  ·  Credits/Trademarks ·  Link To Us
Copyright © 1998-2010, ZATZ Publishing. All rights reserved worldwide.
Editor's Login