Monday, June 17, 2002|
SDMagazine.com: Project and Process Management Forum I posted my Enterprise vs. Project Requirements Management question here. 2:48:25 PM  comment [] Google It!
|
|
Rational Software RUP Forum Here's where I posted my last Enterprise-level RM post. 1:53:07 PM comment [] Google It!
|
|
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. |
|
Dave, aka Mr. Scripting News Is In the Hospital Best wishes for recovery from whatever ails you. Kind of sounds serious if he's going to be in the hospital til next weekend. 12:30:16 PM comment [] Google It!
|
|
Test Tech Post Test Post 12:19:07 PM comment [] Google It!
|
|
Optimize Magazine: Errors Are Simply Not An Option "Not very many people would tolerate a car, no matter how elegant, that worked only some of the time. Software is no different. We're well beyond the era of being amazed at what computers can do. Instead, we expect them to function as promised right out of the gate. The smart CIO will view as job No. 1 doing everything possible to fulfill that expectation."
I wonder if our CIO reads these kind of things? What would he say if read this? I think all managers needs weblogs to tell their folks what they are thinking and reading. Get's us all on the same wavelength. |
Last update: 6/13/2003; 6:38:47 AM .
