I am currently working on a contract where the customer has created the following requirements structure
The requirements are documented in IBM's requirements management tool called RRC. I have been documenting all the all the requirements for the application under the System and Derived requirements and performing tracing up to the Compound System Requirement. We are now starting to work on reports and I had mentioned that reporting requirements need to separated out and documented as Reporting Requirements so that they are easily distinguished from the application requirements in RRC.
i would like to get the thoughts of others and how others handle reporting requirements.
Hi Tiff,
Hmmm. Weird approach. I blame the BABoK and its insistence on putting requirements in predefined buckets.
Hope your Compound System requirements are real solution independent business requirements? In your brief description it looks like they assume a system solution. Perhaps I'm being unfair?
Personally I don't think it makes much difference where you put them. Maybe the functional requirement bucket or the Compound system bucket. You could even argue its in the system bucket as a solution to the compound bucket. Kind of proves this nonsense about classifying requirements.
Cheers,
Kimbo
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: