XML based requirements for xmlBlaster

[Marcel Ruff <ruff at swand.lake.de>]

Hi,

we will begin to document all xmlBlaster requirements
from now on!

Each requirement will be one xml file in the
  xmlBlaster/doc/requirement
directory.

About 5 tags should be enough to categorize a requirement
sufficiently.

All date of changes and who changed it is available
through cvs (as $Author$ and $Version$ tags).

Some XSL style sheet transforms the requirements to some
informative HTML outputs, or some nicely formatted
print outputs (if anybody needs such stuff :-)

Benefits:

- All features of xmlBlaster are clearly documented.
- The state of each requirement is query able (open/finished/..).
- Bugs are query able
- XSL styles lets define nice views on the fly.
- XPath allows queries.
- Each requirement has one to many references to the already
  existing test suite.
- Every requirement test is fully automatic implemented in
  the test suite.
- As everything is ASCII based, cvs can easily merge concurrent
  editing.
- Requirements may be edited in any XML capable browser.
- The system is totally simple, absolutely cheap and very extensible.

What do you think, any improvements?

Marcel



-- 
Marcel Ruff
ruff at swand.lake.de
http://www.lake.de/home/lake/swand/
http://www.xmlBlaster.org