Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Reporting Requirements
Previous Previous
 
Next Next
New Post 2/27/2015 5:31 PM
User is offline tiffanyfr
1 posts
No Ranking


Reporting Requirements 

I am currently working on a contract where the customer has created the following requirements structure

  • Compound System Requirement (this is truly a Business Requirement),
  • System Requirement (this one level lower than the BR), and 
  • Derived Requirement (this is truly the functional requirement)

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.

 

 
New Post 3/3/2015 1:00 AM
User is offline Kimbo
447 posts
5th Level Poster


Re: 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

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Reporting Requirements

Community Blog - Latest Posts

Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses
Jason White
Jason White
New technology is in trend every day and striving to make its mark to be the best. It is not optional to stay exceptional, technology has made lives easy and uncluttered in so many ways that cannot be comprehended. With the latest technologies in the headlines every day, it is Artificial intelligence that is leading the race and being incorporated ...
0 Responses
Digvijaybook
Digvijaybook
The role of a business analyst is to manufacture a piece of art; the piece of art varies depending upon the methodology and techniques being used. Business analyst serves the project all through the beginning until the end and comes up with different pieces of art. It all depends on the case, the business analyst gets involved from the beginning of...
0 Responses






Latest Articles

66 Lessons from 50 Years of Software Experience
Jul 12, 2020
0 Comments
I spent a lot of time in the past half-century doing software work: requirements, design, user experience, programming, testing, project management, w...
Copyright 2006-2020 by Modern Analyst Media LLC