Functional/Technical Specifications

[Former Member]

Hi Exp.

Could anybody please explain me difference between "Functional & Technical Specifications" and PLEASE, send me any prepared Fun/Tech Spec. from any of your project.

e-mail ID: amitbali243@gmail.com

It will be great help, point shall definatly be awarded.

Regards

AB

[Former Member · Accepted solution]

hi,

to start with a functional spec is prepared by a functional consultant based on a business requirement which is told by the enduser/client. After a clear cut analysis on what is require( which is not possible through config alone) is document in a technical way so that an abaper also can understand how to build the logic for the given requirement.

<b>these are few contents of a functional spec :</b>

It consists of the following:

1. Project name

2. Author name

3.Version

4.Function module of the project

5.Server name

6. Fields required

7. The naming conventions etc.

8. Tables necessary

After this the ABAPer understands the requirement and prepares a technical spec. This contains a very technical detail which is implemented at a programmers level. Now the required code is generated and tested back against the laid functional spec objective.

Tech. spec template :

Sample Template

Technical Spec for a Project.

Section 1.

Document Control

Change Log

Modification No. Change Date Description By

1.0 05.02.2003 First Version <Author>

Section 2

Table Of Contents

Section 3

Overview of the requirement.

Section 4

Process Flow

Section 5 - Detail Changes to be carried out.

<ABAP Name> - <ABAP Title>

Overview

Change Request

Selection Screen/Parameters

Reference to Tables

Include/Submits ABAPs

High Level Processing Logic

Output Format

Test Procedure

Other Impact

Thanks

sadhu kishore

[Former Member]

Thanx

[Former Member]

hi..

Both the documents are prepared mostly by the Business Analyst..

Functional Specifications are prepared in order to explain the functional processes of the business in a detailed way with the help of gud understandable language and with the help of pictures where ever possible for detailed explanation of the business process..

Technical Specificationas are those documents where in the technical terms are mostly mentioned and expalined.. say in a product based company.. a technical document palys a vitial role for the developers to develop the product.. this is the document where all the technical specifications related to the product, ie, say screen flow, attributes used and to be used, functions, methods to be called, say for an sap technical spec, u might more c the technical terms related to t.codes, rfms, bapis used and to be used, screen updations, fields to be mandatory or display etc.... and so on

c both these documents play more or less the same kind of role in a project life cycle.. the only difference is that technical docs are those which show up the technical requirements and functional specs are those which show up the functionality of the business process...

Refer to the links below for some more info

Functional Specs Template…

http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm

http://www.epri.com/eprisoftware/processguide/funcspec.html

Reward if Useful

Thanx & Regards

Naren..

[Former Member]

Functional specs are prepared by the functional consultants to make the ABAPers understand what the program is all about. Here we speak tables and important T codes those are being hit for a particular program. Based on the functional specs, ABAPers will prepare the Tech Specs to understand how the program should be and what are the important coding have to be done. It is more of technical only with ABAP knowledge, one can understand the Tech specs. These are required, in case, any functional or tech consultant is out of the project, and other consultant is substituted, he will read the program status only based on the specs available. And predominantly specs help in understanding the scope of a particular program.

Thanks,

Sanjay

[Former Member]

HI Amet,

I have a sample FS and I am forwarding the same to you. Hope this will be helpful.

FS is tha basis fr TS, It contains all the things available in FS, in addition you will have the program logic fr fetching the data.

Reward points if it helps

Regards

Srini

[Former Member]

Hi

Mail Sent

[Former Member]

hi

first you receive a design spec based on which you will write FUNCTIONAL SPECIFICATION

if any technical changes required you send this functional spec to ABAPer then ABAPer will write a TECHNICAL SPECIFICATION and CODE REVIEW.

Functional specifications (functional specs), in the end, are the blueprint for how you want a particular report and transaction to look and work. It details what the report will do, how a user will interact with it, and what it will look like. By creating a blueprint of the report or transaction first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect.

A key benefit of writing up a Functional Spec is in streamlining the development process. The developer working from the spec has, ideally, all of their questions answered about the report or transaction and can start building it. And since this is a spec that was approved by the client, they are building nothing less than what the client is expecting. There should be nothing left to guess or interpret when the spec is completed.

Functional Specification

A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.

For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:

also check u r mail

regards

prashanth