Enterprise-level Regulatory Analysis and Requirements Management (PDF)
"The endstate will be a systematic and readily
retrievable corporate memory regarding the rational for
including/excluding a requirement, for a particular
interpretation, or allocation to systems and subsystems."
The first article I've seen looking at requirements management from an enterprise viewpoint as opposed to a project viewpoint. They discuss the process and benefits of taking "1000's of requirements documents with approximately 100 requirements each" and putting them in a database, with links to original documents, implementing systems, people, facilities, etc.
In looking at requirement management tools and processes from the aspect of enterprise-wide analysis, it seems obvious that you would need access to enterprise-wide requirements to correctly determine impact of requirement changes (and new requirements) on existing systems. But with a project viewpoint of RM, the requirements for even one individual system are spread out over the documents generated by the multiple projects (initial, enhancement, maintenance) that implemented the system.
1:42:39 PM
|
|