cancel
Showing results for 
Search instead for 
Did you mean: 

Functional Spec

Former Member
0 Kudos

Hi,

can any one help me in finding answer for these questions.

1. What is Functional Spec

2. What are all the activities involved in Post Go-live support to the users

Regards,

Kannan M

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Kannan

Functional Spec is nothing But BUSINESS FLOW/PROCESS requirement, it will be preapared by Functional consultant/s and it will have some functional test cases also.

What Is A Functional Specification?

Functional specifications (functional specs), in the end, are the blueprint for how you want a particular web project or application to look and work. It details what the finished product will do, how a user will interact with it, and what it will look like. By creating a blueprint of the product 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.

Why write a Functional Spec?

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 application 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...and this, in a nut, explains my love affair with the Functional Spec.

Who writes a Functional Spec?

The functional spec should be written by someone who is not involved in any other aspect of the project. You will want somebody who is very familiar with user-interface issues and web design, familiar enough with technology to know its limitations and capabilities, and someone who is a very skilled and detailed writer. While writing a spec, you will spend much of your time imagining how a user might use a certain feature and how they may navigate their way through the information. Not only do you need to map this world out visually, but you also have to write out in great detail what this world does; all the while, balancing everything within the current technological limitations and business demands. The functional spec writer's sole concern is marrying the user-experience with the various departmental, business, and technical requirements of the project.

The link below will help u

http://www.mojofat.com/tutorial/index.html

Reward if useful to u

Lakshmipathi
Active Contributor
0 Kudos

Hi Kannan

To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.

The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.

The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.

The functional specification translates the Software Requirements template into a technical description which

a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.

b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.

At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.

Let me throw some light on documentation which is prepared before and in a project:

1) Templates

2) Heat Analysis -

3) Fit Gap or Gap Analysis

4) Business Process Design

5) Business Process Model

6) Business Change & Impact

7) Configuration Design, which is just 5 % of Total SAP- have different names -

😎 Future Impact & Change Assessement

9) Functional Design (Module Wise)

10) Risk Assessement

11) Process Metrics and Many More-- Which has impact on Business and its work flow

Note * -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP.

<b>Post Go-Live Support</b>

The main activity is that you need to assist your client whenever there is on line issues which is nothing but live issues which would arise on day to-day basis.

Besides this as and when some new requirements will be raised by the client by way of tickets. You have to study their new process / requirement and decide whether it is feasible to address in SAP and can be addressed through standard SAP itself or need zee program. Once you decide on this, you need to give some target date to complete the new requirement.

Thanks

G. Lakshmipathi

Former Member
0 Kudos

<b>Functional Specification:</b>

To speak at macro level that is at project manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functionality. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.

The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.

The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.

The functional specification translates the Software Requirements template into a technical description which

a) Ensures that the product feature requirements are correctly understood before moving into the next step that is technical development process.

b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.

At the consultant level the functional specs are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.

Let me throw some light on documentation which is prepared before and in a project:

1) Templates

2) Heat Analysis -

3) Fit Gap or Gap Analysis

4) Business Process Design

5) Business Process Model

6) Business Change & Impact

7) Configuration Design, which is just 5 % of Total SAP- have different names -

😎 Future Impact & Change Assessment

9) Functional Design (Module Wise)

10) Risk Assessment

11) Process Metrics and Many More-- Which has impact on Business and its work flow.

<b>Format for Functional Specs:</b>

Document Control

Change History

Issue No

Date

Name

Change

Initial Draft

Authorizations

Role

Name

Signed

Date

Business Process Lead (customer)

Functional Analyst (specification author)

Technical Lead

Developer (if known)

Select program type below and then use menu option tools > unprotect to

open other fields for input

Type

Table of Contents

Document Control 1

Overview. 3

1.1 Short Description. 3

1.2 Business Process. 3

1.3 Terminology. 3

1.4 New Custom Objects Required. 3

1.5 Impacted SAP Transactions/Tables. 4

Process Decomposition. 5

2.1 Process Flow. 5

2.2 New Tables/Structures Required. 5

2.3 Sub-Process Description. 5

2.4 Error Handling. 5

2.5 Security Considerations. 5

2.6 Database Considerations. 5

2.7 Conversion Implications. 5

2.8 Batch Processing. 6

2.9 Functional Test Requirements. 6

Overview

1.1 Short Description

1.2 Business Process

1.3 Terminology

1.4 New Custom Objects Required

Include all new tables, key new fields/domains, new lock objects, new

match-codes, new transaction codes, new authorization objects, new

function groups, reports and module pools (transaction programs). Don't

specify all includes, function modules, routines etc. here.

Type (table, transaction etc.)

Description

Naming convention

1.5 Impacted SAP Transactions/Tables

List SAP objects updated/impacted by this specification (do not include

read only impacts)

Object(s)

Type (table, transaction etc.)

Description of Impact

Process Decomposition

2.1 Process Flow

2.2 New Tables/Structures Required

Specify new tables and structures required. If appropriate, you may

defer detailed field list/specification to the technical specification

(e.g. for secondary tables and structures).

Table id

Description

Type

Master, transaction, customizing, staging

Expected size

Maint. dialog

None, SM30, custom

Fields

Key

Domain/data element names

Domain format (if new)

Description

2.3 Sub-Process Description

2.4 Error Handling

Specify what to do if a condition passes AND fails (e.g. - what happens

if a customer record is found, or is not found). Specify messages and

type.

Specify any special error logging or table storage, including use of

standard application log where appropriate.

Field

Validation

Message type/no.

Message text

2.5 Security Considerations

2.6 Database Considerations

2.7 Conversion Implications

2.8 Batch Processing

2.9 Functional Test Requirements

Consider all the conditions that need testing for this enhancement and

document below. For each logic branch in theory both (or more)

conditions of the branch should be tested. For each scenario that could

impact program execution, all situations must be tested.

No.

Test condition

Expected result

Data set-up reqt.

Dependencies

Functional specification: The Functional Specification is a comprehensive document created after the Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functinality. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.

You will specify the the selection screen, authorizations, and logic needed to fetch the data.

The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.

It also contains the data regarding change history, if any.

Functional Spec is mainly prepared for the purpose of developing the new reports (this happens only when SAP standard report not achieve the client purpose) using the ABAP Program. for ABAPers you need to give the details of the Tables , Fields and the logic how to pick the value and get the report.

e.g. (this is just an example it can be possible in standard SAP report) I need one new report like in the output i need only company code, Vendor number and recon.account assigned. like as below:

Company Code Vendor Recon account

1000 90000001 156001

1000 90000002 156001

2000 90000001 156002

for the above requirement with the input selection criteria like as below

Company Code ( ) ( )

Vendor ( ) ( )

if you give input selection as above as required you will get the output as given above

Logic should be as below:

for input selection

Company Code - BUKRS is the ABAP field for the company code

Vendor - LIFNR

for the output

Company Code - LFB1-BUKRS

Vendor - LFB1-LIFNR

Recon account - LFB1-HKONT

You will get the recon account details in the LFB1 table , if you give the logic as above , ABAP er will write the program for the same.

<b>

Visit the following links:</b>

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

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

regards,

Arun prasad

null