
Our customers are government and military. We have projects where there are multiple instances of a Class (e.g. SRS). What is the best way to do this? Would you just dump all SRS requirements in the SRS Class and create however many "Collections" as are required. Could each of these collections then be baselined as SRS-A, SRS-B, etc. Would the collections exist as hard, tangible documents, as opposed to the volatile results of scripts? Our customers require documentation according to IEEE-12207, MIL-STD-498, etc.
Thanks for any help.
Comments
A different approach is to have the SRS class and use Doc View to create the different documents for each of the products creating snapshots for each baseline release.
The one I like the best is to use the single SRS class with Category for each project. You then have security at the project level to ensure only those assigned to the project are changing the projects requirements. If required you can even limit read access by project (category). Then with a project specific view of the SRS the user would have many different ways to report on that information. Please let me know if you need more information.Cheers,Tom
X78815
Reply to this Comment