Sys Req Specification Generation NOT using RTF

[bioform]

Just wanted to start a separate topic for discussions about requirement specification generation NOT using EA's RTF capability (or very little of it...)

I have had some significant success with generation of a SRS for projects, using:

1. MS Word Document - Contains ONLY the documents formatting and structure defined in the "template" file, and using embedded links to MS Word "Sub Documents" for the section's boilerplate, database fields to pull information directly/indirectly from the EAP project on a RDMS, and modifying through VBA code embedded RTF documents containing EA information (either generated from EA, or using MS Access)

2. MS Access – Contains queries, reports, code and serves as a front-end to the RDMS EA project's information. From this I pull EA data, massage it, and update and/or EA and generate documentation in the form of a RTF files for use by MS Word.

3. MS Excel - Format EA Relationship Traceability Matrix output, for inclusion in MS Word as an embedded object.

Anyone else interested in discussing different approaches, and sharing their success stories and bits of wisdom?

[«Midnight»]

Yes.

What 'forum' do you think would be best? Perhaps the Wiki or something would be better suited.

David

[bioform]

Actually, we might think about getting started here, and mirroring the information to the Wiki?

It seems like the wiki or the "old" share-point site might be a good place to provide artifacts?

I would not even mind "working" maybe on an open-source kinda approach to this in the long-term? Think we could get some interest in something like that?

[«Midnight»]

Probably. Almost certainly from me at least.

I am just finishing something up (I hope) and may have a bit of time. You can touch base on the back channel in a couple of days and we'll see if we can't get something rolling.

David