HELP! Why are reporting requirements so difficult. The user seems to need to see the report before they can tell me what they need. Does anyone have any comments, suggestions to make this process easier.
Submitted by smojumder on Tue, 2009-12-15 12:18. *
I find your comment very interesting because i do mockp-ups to document reporting requirements like any other requirement. How mock-up helps? It fulfils the purpose of presentation (user experience) requirements. It saves my time because i do not need to create document capturing presentation requirement by writing sentences like "Admitted Premium will be displayed right aligned and upto 2 decimal precision....". In addition, both IT and business stakeholders get a concrete sample of how the report will look like. So, mock-ups are really useful part of the requirement.
As regards to reporting requirement, i treat and manage reporting requirements as any other system process:
Primary actors: user roles who will run (in case of parameterized report) and view the report
Supporting actors: what other systems need to be accessed
System process: generate placement report (for example)
Data requirements: what specific busienss data they want to see in the report. Data mapping..
Business constraints: any specific business rules. Ex: preconditions that must fulfil before the report can execute, etc. Any post-condition....
Presentation requirements: mock-up:). Also, where on the system the report will be available
mock-up madness?
I find your comment very interesting because i do mockp-ups to document reporting requirements like any other requirement. How mock-up helps? It fulfils the purpose of presentation (user experience) requirements. It saves my time because i do not need to create document capturing presentation requirement by writing sentences like "Admitted Premium will be displayed right aligned and upto 2 decimal precision....". In addition, both IT and business stakeholders get a concrete sample of how the report will look like. So, mock-ups are really useful part of the requirement.
As regards to reporting requirement, i treat and manage reporting requirements as any other system process:
Primary actors: user roles who will run (in case of parameterized report) and view the report
Supporting actors: what other systems need to be accessed
System process: generate placement report (for example)
Data requirements: what specific busienss data they want to see in the report. Data mapping..
Business constraints: any specific business rules. Ex: preconditions that must fulfil before the report can execute, etc. Any post-condition....
Presentation requirements: mock-up:). Also, where on the system the report will be available