Recently, I was assigned to a project with another 2 BAs and I was responsible to the Reporting part of it. It’s a national project, and I would like to do it as properly as I could.

I am new to requirement analysis for reporting. Does anyone have a template or suggestions that how I could address the requirement in a professional way?

So far, I have decided to do the data flow diagram, Entity relationship diagram.

 How about starting with what the project stakeholder's need from the reports.

Typical things include

• Showing how we are doing on our KPIs (Are we doing okay?)
• Monitoring staff production against incoming work (Do we need to hire more)
• What's coming into our system (eg call patterns for call centres, sales queries by type for sales & marketing people, faults by type for help desks)
• Average handle times and elapse times  on transactions for the continuous improvement folk

And so on.

If you don't know what business decisions are important you are diving into a painful process.  

After that you can consider the data.

"Start with the end in mind."

Tartar,

I reckon Craig and Tony are both spot on. Craig’s focus is on working what is relevant; and Tony's focus is analyse these relevant domains only so that your DFDs and Entity Relationships information are focused and goal directed.

warm regards,

K