Can We Sell SAP By Writing GOOD Functional Specification?

Introduction

Can We Sell SAP By Writing GOOD Functional Specification?
The answer is a big YES.

What is Functional specification ?
Functional specification is a clear document of end user requirement and will be the reference document for the developer to develop the objects.

Why we need a Functional specification ?
Functional specification is required to document end user requirement and in future it will be reference document for the end user to enhance the requirement. Technical specification will be created on the basis of the functional specification documents.

Below I am trying to explain the details about the functional specification creation. It contains Cover page,
Document Control page and Content Page. Also mentioned about Do's and Don'ts of functional specification.


Cover page:

• Keep it SIMPLE

• Company name and logo

• Name of the functional specification

Document Control page

• Document Information

• Document History

• Document Approvals

Document Information :

• Document ID

• Project Name

• Document owner

• Issue date

• File name

Document History:
• Name

• Version

• Reason

• Date

Document Approvals

• Name

• Role

• Author - Functional consultant

• Business user

• Project manager of Author

• Project manager of Business user

• Signature

• Date




Content Page

• Introduction

• Scope

• Definitions

• References

• Function Specification Requirement

• Dependencies

• Assumptions

• User access requirements

• Testing requirements



FS Requirements

• Business description

• Business Logic

• Layouts

• Input Selection Screen

• Output Layout

• Flow diagrams

• Error handling





Do’s

• Keep it Simple and Clear

• Use Layman terminology

• Use pretty pictures

• Use flow diagrams

• User friendly comfortable format and fonts

• Maintain Headings and sub headings

• Use numbering and bullets

• Read the specification 2 to 3 times once it is completed

• Formal sign off




Don'ts

• Do not make it complicated

• Do not use too much of technical word

• Do not use odd fonts and colors

• Do not make spelling and grammatical mistakes

• Do not confuse the customer with long specification

• Do not leave any headings or subheadings open

• Do not repeat the same description again and again with different subheadings


By writing good functional specification, we can help the customer to get the rough picture of end product which will be used by them and also will be helpful for the developer to develop the object which will be required by the customer. These functional specifications will be stored in the customer system as a reference document for the future enhancement of the same object and also behave as user-guide. The quality of the document will increase the repetitive business to the company.