This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

DocBook in Requirements Specifications?


Greetings!

I'm looking for some thoughts from the list on the use of DocBook in the
context of producing requirements documentation. Business requirements,
use cases, and functional and non-functional requirements, all pulled
together in a software requirements specification, are what I'm looking
to produce. I can see the easy process of producing a shell document for
an analyst to fill out and link in diagrams and references, etc.;  I
struggle with the use of the right tags and/or attributes to embed
requirements metadata that I could later process using a combination of
a script (pick your favorite language) or an XSL stylesheet with some
filtering to extract requirements and status for reporting and
traceability. I suppose I could give up and use a
"Requirements Management Tool" AKA M$ Word souped up...but I'd rather
not :-).

Terry.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]