Report Functional and Technical Specification Document

[system]

Hello All,

Please find the functional and technical Specification document for the report development.

Appreciate your feedback…
Report Functional and Technical Specification Template.doc (241.0 KB)

---

sid786 (BOB member since 2008-10-06)

[system]

Moderator Note:
Approved and moved to BOB’s Downloads

---

Marek Chladny (BOB member since 2003-11-27)

[system]

Thats great

Thank you so much for sharing this document.

I do come across some other documents with names report design specification ,reports requierment deliverable template documents.

I am bit confused about which is the first docuement we do after conducting workshops and meeting with users and stckholders in the inertial phase of gathering requierments.

IS that functional specification?

IS the Reports requirement deliverable template same as functional specification document?

IS Reprot design specifcation document same as Report Techincal document?

Do we take sing off from stackgolders or sponsors after documenting both founctional specification and techincal documents?

Do we have to write function specifcation and techincal specifcation for each indivudual report we identifed and gathered from users or Just a one functional specifcation documenst to define the overall reports scope of the prjoect?

Could you please clear those very basic questions?

Thanks

---

shine (BOB member since 2010-11-13)

[system]

Hi, you probably have some good questions about functional and technical specs in here somewhere, but I think you need to drop down a couple of levels before you try to understand the documents. First things first: You need to understand the language in which the documents are written.

@shine

I am bit confused about which is the first docuement we do after conducting workshops and meeting with users and stckholders in the inertial phase of gathering requierments.

I’m guessing your confusion could be a symptom of your limited command of the english language. First of all, they aren’t stckholders or even stockholders, but stakeholders. Also, I think you mean ‘initial’ phase, not ‘inertial’ phase… unless you are using some fancy new terminology with which I am unfamiliar.

@shine

IS that functional specification?

IS the Reports requirement deliverable template same as functional specification document?

IS Reprot design specifcation document same as Report Techincal document?

What is this IS you are talking about? Does that stand for Information Systems? If so, I can’t make any sense of what you’re saying. If you’re just attempting to use the english word “is”, then don’t capitalize both letters.

@shine

Do we take sing off from stackgolders or sponsors after documenting both founctional specification and techincal documents?

There is no sing off from stackgolders. That’s an alternate universe you’re thinking of. In this universe we get sign off from stakeholders.

@shine

Do we have to write function specifcation and techincal specifcation for each indivudual report we identifed and gathered from users or Just a one functional specifcation documenst to define the overall reports scope of the prjoect?

This question seems a little more coherent. The answer is it depends on the reports.

---

pabrams (BOB member since 2011-07-05)

[system]

Thank you so much for takeing time to answer all questions one by one.

You are 100 % right.I should agree ,I have limited command on English Language. typed some words wrong.

You have answered all my questions.

---

shine (BOB member since 2010-11-13)

[system]

I have been asked to submit a detailed design Document. I did review the High level document but it just seems so ambiguous . could not get anything out of it.

Is a detailed design document similar to report specifications?
Can someone please tell me how to go about creating a detail design document?

---

karna (BOB member since 2010-03-07)

[system]

@pabrams

Hi, you probably have some good questions about functional and technical specs in here somewhere, but I think you need to drop down a couple of levels before you try to understand the documents. First things first: You need to understand the language in which the documents are written.

@shine

I am bit confused about which is the first docuement we do after conducting workshops and meeting with users and stckholders in the inertial phase of gathering requierments.

I’m guessing your confusion could be a symptom of your limited command of the english language. First of all, they aren’t stckholders or even stockholders, but stakeholders. Also, I think you mean ‘initial’ phase, not ‘inertial’ phase… unless you are using some fancy new terminology with which I am unfamiliar.

@shine

IS that functional specification?

IS the Reports requirement deliverable template same as functional specification document?

IS Reprot design specifcation document same as Report Techincal document?

What is this IS you are talking about? Does that stand for Information Systems? If so, I can’t make any sense of what you’re saying. If you’re just attempting to use the english word “is”, then don’t capitalize both letters.

@shine

Do we take sing off from stackgolders or sponsors after documenting both founctional specification and techincal documents?

There is no sing off from stackgolders. That’s an alternate universe you’re thinking of. In this universe we get sign off from stakeholders.

@shine

Do we have to write function specifcation and techincal specifcation for each indivudual report we identifed and gathered from users or Just a one functional specifcation documenst to define the overall reports scope of the prjoect?

This question seems a little more coherent. The answer is it depends on the reports.

Such rudeness for post number one. It is a shame to see this here.

---

BOXI Balboa (BOB member since 2007-01-24)