Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Where to put Reporting requirements?
Previous Previous
 
Next Next
New Post 12/24/2009 12:52 AM
User is offline Newbert
5 posts
10th Level Poster


Re: Where to put Reporting requirements? 

Hello Andy,

It's a personal choice and I assume that the clearest most understandable format for communication to those who contribute, review and accept the document is your desired result.

With this in mind, my reporting (and enquiry) requirements have found a home in their own section named 'Informational Requirements' that is sandwiched between the Functional and Quality of Service / Non-Functional sections. Alternatively, they could reside in their own 'reporting' sub-section of the non-functionals requirements - but personally I would not include them amongst the Functional Requirements as I believe they obscure the view of what the system does. Besides the data / information provided is the end and not the means.

Hope this helps,

Joe

 

 

 
New Post 3/4/2010 6:56 AM
User is offline KIERANC
22 posts
9th Level Poster




Re: Where to put Reporting requirements? 

 Andy,

I think they should go in the non functional category and Use Cases can decribe most type of Reporting Requirements. Normally there are two main types of reports; ‘Pre-canned’ reports and ‘ad-hoc reports’. Pre-canned reports are those that are specified up-front by the stakeholders, with the input parameters that are available for that report defined along with the expected output of the report. The normal interaction between the Actor and the system to generate a pre-canned report is to select the report they want to run, enter/alter the parameters of the report, select the output format and select the date/time at which the report should be produced. The provision of Ad-hoc reports is usually handled by an MI tool that pulls data from one or more data sources or a data warehouse.

Use Cases do not lend themselves well to describing the functionality needed to provide ad-hoc reporting capabilities. Use Cases should be used however to describe the requirements of pre-canned reports. Pre-canned reports can be run on-demand or in batch mode i.e. generated at a particular date/time as set up in some kind of scheduler, or as a result of a particular condition. A separate Use Case should be used to describe the flow of events of a report generated on-demand, and a report generated as part of a batch run. In this case the initiating Actor is different and therefore the flow of events of the Use Case differ, hence the need for two separate Use Cases. A separate artefact should be used should be used to provide the following information for each Report that can be generated as a result of performing the Use Case.

Reports may be produced as part of the flow of events of a Use Case. Again, a Report Specification should be produced corresponding to that Use Case to describe all reports that are produced as a result of execution of that Use Case.

 K

 

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

Community Blog - Latest Posts

Salesforce has established itself as one of the most reputable CRM platforms, providing important customer data to assist businesses in effectively managing their operations. Salesforce is the world's best CRM platform that helps businesses to keep up the data in an arranged or structured manner. Salesforce is the world's most popular...
There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC