Design Documentation

Discussion created by paritosh.hebbal on Jun 13, 2013
Latest reply on Jun 17, 2013 by Chris_Hackett

So we're suggesting the client a few Clarity-BO reports which they don't have already, which might add value to their organisation.

We've obtained the Requirements Documents from the Process Management team for a few reports that could be made for them.

Our part of the work, is just to produce Design Documentation for these requirements and pas them on to their Development team who will develop these reports. I am a little inexperienced when it comes to making documentations.

Could anyone please tell me the best practices when it comes to building a Design Documentation for Reports? For e.g, what fields need to be present mandatorily, which ones can be omitted etc?

I know all this depends on the client's guidelines, but I'm asking for the ideal (Most basic) Design Document.

If anyone has a template I could follow, i'd be ever-grateful to them if they attached it here!

Thank you