Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Where to put Reporting requirements?
Previous Previous
 
Next Next
New Post 12/13/2009 11:17 PM
User is offline Andy
2 posts
No Ranking


Where to put Reporting requirements? 
Modified By Andy  on 12/14/2009 1:21:51 AM)

Hi All,

I'm very much a fan of the Volere style of gathering and producing requirements e.g. Business events > businsess use cases > system use cases > req's. however, I find it difficult to decide where to put reporting requirments within this model - functional req's, non-functional or their own section?

An example would be 3 entities - say warehouse operations, marketing admin and a client - all make use of the same inventory report. This makes it difficult to fit into a functional partition, and i'm not even really sure that reports should even come under the "functional" heading anyway.

I currently record reporting requiremetns in thier own section, but i'm perhaps wondering if they should instead come under a sub-section of non-functional requirments.

I would love to hear any suggestions on where I should be putting my reporting requirments within the reqs documents.

 

Thanks, Andy

 

 
New Post 12/14/2009 2:18 AM
User is offline Kimbo
426 posts
5th Level Poster


Re: Where to put Reporting requirements? 
Modified By Kimbo  on 12/14/2009 4:02:39 PM)

 Hi Andy,

I record each report as a use case. The report is an activity undertaken by a user that does something of value to the user, hence its a use case.

Then after identifying all your use cases, the next step in the elaboration process is to model the screens and reports that realise your use cases. Note that as with screens, the relationship between use cases and reports is many to many. The report spec has the layout, fields, groupings, sorting, parameters, etc. 

Having said that, from a behavioural point of view, most reports behave the same, so I tend to take short cuts with the reporting use cases and maybe only have one use case and list the reports I've identified in the description. Its cheating but quicker.

Kimbo

 
New Post 12/14/2009 2:18 AM
User is offline Peter Herring
13 posts
10th Level Poster


Re: Where to put Reporting requirements? 

Hi Andy,

I would normally put them into a non functional category. I've worked on a project before with a vast anmount of non functional requirments. In that situation we put them into their own document. But in other smaller projects I've just added them to the back of the use case specs under a "non functional" heading.  

 
New Post 12/15/2009 4:26 AM
User is offline suzanner
2 posts
No Ranking


Re: Where to put Reporting requirements? 

 Hello Andy,

A report shows up first on the Work Context Diagram. Going one level down, each report is output from a Business Use Case (BUC). This is typically  triggered by a temporal business Event.  in other words the business event happens because there is some functional work-related need for a report. When you decide the product/system boundary for the BUC then the report is output from one of the Product Use Cases (PUCs) linked to that BUC. The detailed requirements for producing the report are atomic functional requirements that are linked to the PUC.

The definition of the data content of the report should be defined in the data dictionary right down to elemental level. 

The non-functional requirements that relate to the report (performance, usability, look and feel....etc.) should also be linked to the PUC that produces the report.

If there are any screen designs, prototypes, interface behaviour specifications then they can also be linked to the PUC. They are design requirements and belong in Section 8 of the Volere template. In the next version of the template this section will be expanded to provide more explicit guidance.  

There is a Volere Requirements Linked in group where you can talk to other Volere users.

http://www.linkedin.com/e/vgh/2491512/

Regards

Suzanne

 
New Post 12/15/2009 5:00 PM
User is offline Andy
2 posts
No Ranking


Re: Where to put Reporting requirements? 
Modified By Andy  on 12/15/2009 7:03:48 PM)

Thank you everyone for your great replies.

I capture reporting in the context diagrams, business & product use cases, and both functional and non-functional req's, but I think I've been getting stuck by always trying to find a way to fit reporting into it's own nice neat section.

I'm assuming that Suzanne, you are of 'Mastering the Requirements Process' fame. I wanted to say what a fantastic book you guys have written. It is one of my BA go-to books, and I consider it my requirements "bible". I love how you logically break down each of the stages of gathering and producing requirements - it's very intuitive. I wish i'd come across the book - and the volere template - years ago when I first took on the BA role.

 

Thanks, Andy

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Where to put Reporting requirements?

Community Blog - Latest Posts

Limor Wainstein
Limor Wainstein
The title of this article poses a pertinent question for modern enterprises that increasingly make use of powerful high-end analytic data engines, such as Hadoop clusters and cloud-based data warehouses (see this article by Forbes, which deals with similar questions). The challenge for enterprises that use analytic engines is one of data movement...
0 Responses
EA Learning
EA Learning
I recently walked into a large shopping centre on a mission to buy a christening present for a friends son. I was very clear on what I wanted I just needed to find it… I was on my lunch break so I need to get the job done as I had a meeting that I needed to attend back in the office straight after lunch! I am not a frequent shopper and to b...
0 Responses
BusinessAnalysisHub
BusinessAnalysisHub
Have you woken up in the middle of night thinking how am I going to steer my team, give them the direction that they need but at the same time not constraint in what they want to build/deliver. I recently went through one of these night- I have joined an interesting project where we have very tight timescale to deliver a tech product to operational...
0 Responses


Upcoming Live Webinars



Latest Articles

Defining Enterprise Agility
Dec 10, 2017
0 Comments
Enterprise Agility means the ability to adapt easily to change. In the business perspective, agility refers to a distinct quality that allows institut...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC