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
450 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

m_anst
m_anst
What Does Success Look Like? I challenge Business Analysts to view requestors’ requirements as an opportunity to define success. Too often, teams fall into a trap focused on requestors’ prescriptive requirements that are meant to serve as roadmaps for developers and testers. When you limit your view of requirements to this prescripti...
0 Responses
Mariya Kotsupalova
Mariya Kotsupalova
They say the best criteria of Business Analyst’s success are a happy customer (business) and a happy engineering team. But what does it mean? How can we break down happiness and measure it? These are precisely the questions my 8 BAs team and I tried to answer this year. The result was a surprisingly efficient pair of surveys we developed and ...
0 Responses
Rajesh-N
Rajesh-N
Explore the Benefits of RPA's Adoption Across Segments In the past few years, we have seen steady growth in Robotic Process Automation (RPA). It gathered momentum in 2019 and became a hot topic in IT and business circuits in 2020. The power of process automation will be felt even more strongly, propelling its adoption as a replacement f...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC