cancel
Showing results for 
Search instead for 
Did you mean: 

How to review Functional specification Document (FSD)

Former Member
0 Kudos

Hi all,

My current requirement is to review Functional spec document and then create a TS out of it.

What are the basic Questions or clarifications that needs to be kept in mind before reviewing FS..so that I can clarify them before I create a TS.

Do we have any blog or any links which explains about the key points to be clarified to review a FS.

It would be a great help.

Cheers,

Karthick

Accepted Solutions (1)

Accepted Solutions (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi ,

Functional Specification document will give more idea about your bussiness reuirement,suppose you have onction spec it explain about what are the system invloving ,and about data formats and criticallity.its about flow in bussines point fo view.

-


>When you are goin to review the document you shoukd understand the high level flow of interface

-


>what are the bussiness systems fort Interface

-


>Data formats you are going to exchnage.

-


>you should clear about the scernario/requirement,

then only you can prepare technical specification document according to PI/XI.

How you are going to achieve your requirement using PI,you ned maintain technical details and PI interface flow in PI.

Regards,

Raj

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi ,

For review every comany have own formate of checklist.

Functional specific document will be exact bussines requirment. It includs all the details regarding particular object. for exmple how amny systes invalved, wt is the output they required ect..

1.If your review the document you shoul know business flow of that application

2. you should understand requirement.

3. you should know the project specific requirement

then you can easily prepare TS.

Thanks

Sivaram

Former Member
0 Kudos

You can consider below mentioned points while reviewing FS.

1. Is Process and scope of XI clearly mentioned?

2. Is requirement technically feasible?

3. Is the requirement criticality mentioned?

4. Is the requirement clearly mentioned along with AS IS & TO BE Process?

5. Is the source and target system details clearly mentioned?

6. Are Design Assumptions clearly mentioned?

7. Is detailed process flow diagram explaining requirement present?

8. Is source and target structures specified clearly in the FS?

9. Is detailed mapping provided in FS?

10. Is the processing details specified clearly?

11. In case of File, is archiving strategy mentioned clearly?

12. In case of File, is file naming conventions specifies clearly?

13. Is the source and target system connection details specified correctly?

14. Are the dependencies and Design Constraints specified correctly?

15. Is the error handling approach specified correctly?

16. Is test data or sample data given which is required for development?

17. Is volume details given?

18. Is frequency details given?

Based on adapter used for source & target, few more questions can come.

Warm Regards,

Gouri