Creating Dynamic Requirements Documents using Access

[gate2wire]

I've written a 19,000 word requirements document i.e. a corporate technical standard.



I wrote each specific requirement (knowledge packet) as a separate line in Excel then transferred the file into Access. I'd like to do two things with this dbase now:

- Create a relational database to link the requirements, examples, notes, comments, pictures to one another (based on the ontology structure I've created)
- Enable the dbase to create dynamic technical standards (in Word form, maybe in PDF?) - based on user input/choices e.g. maybe they're an internal associate interested in a document that shows examples of application vs a vendor that is looking for specific design requirements.

Main issue is that the technical standard will be long and overwhelming as Word document(s) and the broad target audience will need to weed through the whole thing just to find specific content.

Has anyone done something like this? This is not like the filling in fields on a Word document - this is more dynamic. And I can't find any info on how to begin to approach something like this.

[ranman256]

1. youd have your tReqs table of your documents.
2. a tProject table of your projects.
3. a tProjReqs table to add items from tReqs to the project.

tProjReqs table
----------------
ProjID
ReqID

[orange]

Can you show us a diagram of

requirements, examples, notes, comments, pictures to one another (based on the ontology structure I've created)

For your own benefit and for improved communications you might want to provide a written description/definition of each of these terms. For example, what is a note vs a comment?

A few sample records for each topic would be helpful to start.