topic Re: FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION in Application Development and Automation Discussions

FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION

Former Member — Fri, 04 Jan 2008 07:17:41 GMT

hi Experts,

how does a functional specification looks and a technical specification looks.

can i have these requirements with samples..

or any helpful link wher i can get in template form.

thanks i advance

Re: FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION

Former Member — Mon, 07 Jan 2008 05:22:55 GMT

Hi I am giving a sample of FRS and its TS.

This will help u.

FRS :

Functional Requirement Specification – Form

Object : FR007f

Object Description : Life Cycle Definition

CONTENTS

1 Revision History 3

2 Functional specifications – Forms 3

2.1 Justification 3

2.2 Form Selection Criteria 4

3 Form Layout Criteria 4

3.1 Form Layout 4

3.1.1 Header 4

3.1.2 Item 4

3.1.3 Footer 5

3.2 Desired Form layout 6

3.3 Printing Attributes 9

4 Processing Logic 9

5 Performance Criteria 10

6 Usage Frequency 10

7 Security information 10

8 Additional information 10

1 Revision History

Version No Date Change By Brief Description of change

1 26-Nov-07 Anil Sinha Document creation

2 Functional specifications – Forms

2.1 Justification

Area

(SAP System components) N/A

Date:

07/01/2008

Requested by: Anil Sinha Tel no:

Title: Life Cycle Definition

Short description: Definition of Life Cycle

Priority: 0 High/mandatory 1 Medium/recommended 0 Low/optional

If you answered “High,” briefly explain why you set this priority:

Complexity: 0 High/mandatory 1 Medium/recommended 0 Low/optional

If you answered “High,” briefly explain why you set this priority:

Approx. duration of development work: TBD

Date available from: Before start of UT

Is there an alternative in the standard system? 0 Yes 1 No

Description of alternative: NA

ReaLife Cyclens why alternative is not acceptable: NA

Date of project

management

approval:

Date of steering committee approval:

2.2 Form Selection Criteria

Defined in Processing Logic

3 Form Layout Criteria

3.1 Form Layout

3.1.1 Header

Sr.

No. Field Text on Layout Field Name Remarks

1 Log On UserName Log on Name

2 Last Login LastLogin Last Accessed Login Date and Time

3.1.2 Item

Form A: Life Cycle Menu

Sr. No Field Text on layout Field Name Remark

1 Add Add Button On Pressing Add button, Form for creating a new

Life Cycle will be displayed

2 Edit Edit Button On Pressing Edit button, Form for editing a

already existing Life Cycle will be displayed

3 Delete Delete Button On Pressing delete button, Form for deleting a

already existing Life Cycle will be displayed

Form B: Life Cycle Definition – Addition of New Life Cycle

Sr.

No. Field Text on Layout Field Name Remarks

1 Life Cycle Code LifeCycleCode System Generated Code. Should start with LIFE CYCLE

2 Life Cycle Description LifeCycleDesc Short Description of LIFE CYCLE entered by User

3. Lifecycle Level LifeCycleLevel Level Number

Form C: Life Cycle Definition – Editing a Life Cycle

Sr.

No. Field Text on Layout Field Name Remarks

1 Life Cycle Code LifeCycleCode List Box displaying the defined LIFE CYCLE Code

2 Life Cycle Description LifeCycleDesc Short Description of LIFE CYCLE entered by User. User should be able to edit this field

3. Lifecycle Level LifeCycleLevel Level Number

Form 😧 Life Cycle Definition – Deleting a Life Cycle

Sr.

No. Field Text on Layout Field Name Remarks

1 Life Cycle Code LifeCycleCode List Box displaying the defined LIFE CYCLE Code

2 Life Cycle Description LifeCycleDesc Display the LIFE CYCLE Desc for selected LIFE CYCLE. Display only field

3. Lifecycle Level LifeCycleLevel Level Number

3.1.3 Footer

Sr. No Field Text on layout Field Name Remark

1 Date SysDate System Date

2 Time SysTime System Time

3 Submit Submit Button On Pressing the button, data will be stored in

LIFE CYCLE Table. In case of delete operation, a Flag

Will be set as deleted. No hard delete allowed

3.2 Desired Form layout

Form A: Life Cycle Menu

Form B: Life Cycle Definition – Addition of New Life Cycle

Form C: Life Cycle Definition – Editing a Life Cycle

Form 😧 Life Cycle Definition – Deleting a Life Cycle

3.3 Printing Attributes

N/A

4 Processing Logic

Step 1: User should be able to select a mode of operation from Life Cycle Menu – Add, Edit and Delete

Step 2: In Add Mode, LIFE CYCLE Code will be generated by system with prefix LIFE CYCLE. Only Admin should be able to create a LIFE CYCLE

Step 3: In Edit Mode, only Description can be edited. Only Admin should be allowed to edit a LIFE CYCLE. In LIFE CYCLE List box, only active(Not deleted) LIFE CYCLE will be displayed

Step 4: In Delete Mode, Description can not be edited. LIFE CYCLE Delete Flag will be set to indicate it is a deleted LIFE CYCLE. In LIFE CYCLE List box, only active(Not deleted) LIFE CYCLE will be displayed. Validation should be performed before marking a LIFE CYCLE delete for Parent Child relationship. The proposed LIFE CYCLE should be used in any of the project.

Make sure that 2 Lifecycle codes are not at same level number.

5 Performance Criteria

-NA-

6 Usage Frequency

High (For each delivery)

7 Security information

-NA-

8 Additional information

-NA-

End of the Specification *

TS:

SCSL

Technical Specification

TS007f_Life Cycle_PMCOE Masters

Version 1.0

1 Revision History

Version No Date Change By Brief Description of change

1.0 12/12/2007 Nutan Champia Initial Document

2 Technical Specifications – Portal

2.1 Justification

Module:

Project Administration Date:

07/01/2008

TS Author: Nutan Champia Tel no: 7548

Title: Life Cycle Definition

Short description: Definition of Life Cycle can used in a project

Priority: 0 High/mandatory 1 Medium/recommended 0 Low/optional

Complexity: 0 High/mandatory 1 Medium/recommended 0 Low/optional

Approx. duration of development work: 2days

Business Owner: KK/Praveen Tel no:

FRS Id: FRS007f Version: 1.0

FRS description: Definition of Life Cycle

Functional Consultant: Anil Sinha Tel no:

Date of TS

approval:

Date of FRS approval:

3 Functional Overview

This Functionality provides users with respective maintenance screens for Life Cycle Definition.

4 Technical Overview

4.1 Solution Architecture

The solution involves creation of Visual Composer Application and SAP tables accessed through Web Service.

4.2 Assumptions

1. User logged in and authenticated by Portal.

4.3 Known Issues & workarounds

Issue Since Owner Resolved?

Y/N Workaround

Available Y/N Workaround Description

4.4 Prerequisites

1. CGN SAP29 server with Visual Composer and ECC 6.0 component.

4.5 Dependencies

5 Technical Details

5.1.1 Configuration

Configuration file: NA

Config parameter Possible values Description Effect

e.g. LOGGING Y

5.1.2 Object Hierarchy

5.1.3 Model

Name: PMCOE

5.1.4 Package

Name: com.satyam

5.1.5 Pages

Name: Life Cycle

Description: New, Edit, Delete Screens for Life Cycle Definition

5.1.6 IViews

Iview Maintenance

Component UI element UI Element Type Validation Source Remarks

Life Cycle Details Enter Life Cycle Description Input Field NA User Short Description of Life Cycle entered by User

Search Button NA On clicking it details related to the entered Life Cycle Name will be displayed.

Life Cycle NEW Button NA NA On Pressing Add button, Form for creating a new Life Cycle will be displayed

EDIT Button NA NA On Pressing Edit button, Form for editing a already existing Life Cycle will be displayed

DELETE Button NA NA On Pressing delete button, Form for deleting a already existing Life Cycle will be displayed

Select Check Box

NA NA Selection of a particular Life Cycle can be done.

LifeCycle Code Text Edit NA BAPI System Generated Code. Should start with LIFE CYCLE

LifeCycle Description Text Edit NA BAPI Short Description of LifeCycle entered by User

LifeCycle Level Text Edit NA BAPI Short Description of level

New LifeCycle Life Cycle Code Input Field NA User System Generated Code. Should start with LIFE CYCLE

Description Input NA User Short Description of Life Cycle entered by User

LifeCycle Level Text Edit NA User Short Description of level

Submit Button NA NA On Pressing the button, data will be stored in

Life Cycle Table.

Back Button NA NA On pressing back it moves to the LifeCycle Details screen.

Edit LifeCycle LifeCycle Code Input Field NA BAPI System Generated Code. Should start with U

Description Input Field NA BAPI Short Description of LifeCycle entered by User

LifeCycle Level Text Edit NA BAPI Short Description of level

Submit Button NA NA On Pressing the button, data will be stored in

LifeCycle Table

Back Button NA NA On pressing back it moves to the LifeCycle Details screen.

Delete Lifecycle Lifecycle Code Input Field NA BAPI System Generated Code. Should start with User

Description Input Field NA BAPI Short Description of LifeCycle entered by User

LifeCycle Level Text Edit NA BAPI Short Description of level

Submit Button NA NA On Pressing the button, data will be stored in

LifeCycle Table

Back Button NA NA On pressing back it moves to the LifeCycle Details screen.

5.1.7 Resources (MIME)

Resource Unique ID Name Type Location

5.1.8 Data Interfaces

Name

BAPI_LIFE CYCLE_GET_LIST

Type BAPI 0

RFC 0

Web service 1

Short Description To list all the details from Development Life Cycle table when ever we enter in to this form.

Repository location CGNSAP29

INPUT PARMETERS OUTPUT PARAMTERS

Name Type Length Name Type Length

DLCode CHAR 10

DLDesc CHAR 20

DLLevel CHAR 2

GET LIST BAPI Flow Logic This BAPI fetches Output parameters DLCode, DLDesc, DLLevel , using the SELECT statement, from the Development Life Cycle( ZSE_DEVLIFECYCLE) table. If the table is empty an error message is displayed.

Name

BAPI_LIFECYCLE_SEARCH

Type BAPI 0

RFC 0

Web service 1

Short Description Based upon the search keyword it should filter the data from Service Offering table. The input parameter may contain partial data.

Repository location CGNSAP29

INPUT PARMETERS OUTPUT PARAMTERS

Name Type Length Name Type Length

DLCode CHAR 10 DLCode CHAR 10

DLDesc CHAR 20

DLLevel CHAR 2

SEARCH BAPI Flow Logic This BAPI fetches Output Parameters DLCode, DLDesc, DLLevel fields available from the Development Life Cycle( ZSE_DEVLIFECYCLE) table based on the Input parameter DLCode using the SELECT statement. If the Development Life Cycle( ZSE_DEVLIFECYCLE) table is empty an error message is displayed

Name

BAPI_LIFE CYCLE_CREATE

Type BAPI 0

RFC 0

Web service 1

Short Description It should insert the data into Development Life Cycle table.

Repository location CGNSAP29

INPUT PARMETERS OUTPUT PARAMTERS

Name Type Length Name Type Length

DLCode CHAR 10

DLDesc CHAR 20

DLLevel CHAR 2

CREATE BAPI Flow Logic Using this BAPI the Input Parameters DLCode, DLDesc, DLLevel are inserted into the Development Life Cycle( ZSE_DEVLIFECYCLE) table using the MODIFY Statement.

Name

BAPI_LIFE CYCLE_MODIFY

Type BAPI 0

RFC 0

Web service 1

Short Description It should Update the data into Development Life Cycle table.

Repository location CGNSAP29

INPUT PARMETERS OUTPUT PARAMTERS

Name Type Length Name Type Length

DLCode CHAR 10

DLDesc CHAR 20

DLLevel CHAR 2

MODIFY BAPI Flow Logic Using this BAPI Input Parameters DLCode, DLDesc, DLLevel are Updated into the Development Life Cycle( ZSE_DEVLIFECYCLE) table using the MODIFY statement.

Name

BAPI_LIFE CYCLE_DELETE

Type BAPI 0

RFC 0

Web service 1

Short Description It should Delete the data from the Development Life Cycle table.

Repository location CGNSAP29

INPUT PARMETERS OUTPUT PARAMTERS

Name Type Length Name Type Length

DLCode CHAR 10

DLDesc CHAR 20

DLLevel CHAR 2

DELETE BAPI Flow Logic Using this BAPI the records are deleted from the Development Life Cycle( ZSE_DEVLIFECYCLE) table using the DELETE statement with DLCODE, DLDesc, DLLevel as Input Parameters

Name

BAPI_LIFE CYCLE_CODEGENERATION

Type BAPI 0

RFC 0

Web service 1

Short Description Once the NEW button is clicked it should search the back end system and generate the code automatically.

Repository location CGNSAP29

INPUT PARMETERS OUTPUT PARAMTERS

Name Type Length Name Type Length

DLCode CHAR 10

CODEGENERATION BAPI Flow Logic Using this BAPI the auto generated fields in the Development Life Cycle( ZSE_DEVLIFECYCLE) table are generated by counting the number of available records in the table and the new DLCode is generated following the sequence of the table.

5.1.9 Guided Procedures

5.1.10 DDIC elements

Table Name Field Data Type Length Description

ZSE_DEVLIFECYCLE

(COMMON SCREEN) Mandt(Pk) CHAR 3 Client

DLCode(Pk) CHAR 10 Development Life Cycle Code

DLDesc CHAR 30 Development Life Cycle Description

DlLevel CHAR 2 Development Life Cycle Level.

Loekz CHAR 1 Deletion Indicator

5.1.11 Table Maintenance

5.1.12 UI Flow logic

Step 1: User should be able to select a mode of operation from Life Cycle Menu – Add, Edit and Delete

Step 2: In Add Mode, LIFE CYCLE Code will be generated by system with prefix LIFE CYCLE. Only Admin should be able to create a LIFE CYCLE

Step 3: In Edit Mode, only Description can be edited. Only Admin should be allowed to edit a LIFE CYCLE. In LIFE CYCLE List box, only active (Not deleted) LIFE CYCLE will be displayed

5.2 Error Handling

S.No. Scenario Error Display Information

Control Return

1. If the Description entered is already in database Data redundancy Description already exist New Description

5.3 Common Functionalities

Search is the common functionality used across all the iviews in the application.

5.4 Enhancements

6 Performance Criteria

7 Usage frequency

High (For each delivery)

8 Security Information

9 Miscellaneous

with regards,

Hema.

pls give points if helpful.

Re: FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION

Former Member — Mon, 07 Jan 2008 07:31:44 GMT

Hi Jagmohan soni,

Functional Specification represents the Bussiness Language........which is written by the functional consultants......for the respective modules.......in which u have to get understood of the requirement and proceed for the further process like.....preparing of the Technical Specification and Coding and etc.....

Technical Specification represents the Flow of the Coding, the type of the object, priority of the object(as like in the FS), and use of the requirement......

I think u have got the information......of which u required...

U should be keep NOTE that no one will be provided u Template.......coz this is against the Company Confidnetiality.....Hope u can understand this....

Regards,

Brahma....

Re: FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION

Former Member — Mon, 07 Jan 2008 09:18:57 GMT

Function spec

1 Functional Specification 4

1.1 Terminology 4

1.2 Business functionality 4

1.3 Language management i.

1.4 Screen Description 5

• Selection screen 6

• Data selection and file generation rules 8

• Layout 9

1.5 Authorisation Control 10

1.6 Data selection 10

• Extraction principles 10

• Selection parameters 11

1.7 Report design 11

• Model 11

• Download File Location 11

• Sorts 11

• Breaks and page-breaks 11

• Header 11

• Footer 11

1.8 Selected fields 11

1.9 Management rules 11

• Rule 1 11

• Exceptions 12

• Translations 12

2 Tests 13

2.1 Units Tests 13

3 Pending Issues 14

4 Legende 15

5 Reference Documents 16

6 Versions, Validation and Diffusion follow up 17

Technical spec.

1 REPORT OVERVIEW 3

1.1 General presentation 3

1.2 Terminology 3

1.3 Report description 4

2 Technical Specification 5

2.1 Description 5

2.2 Objects created for the report: 7

2.3 Detailed specifications 7

2.4 Additional Information 8

3 Tests 11

3.1 Unit tests 11

4 Continuation of incident 12

4.1 Risks bound to the exchange 12

4.2 Incident Impacts 12

4.3 Resumption constraints 12

4.4 Check points and operator orders 13

5 Pending Issues 14

5.1 Pending Issues 14

6 Legende 15

7 Reference Documents 16

8 Versions, Validation and Diffusion follow up 17

9 Object / Transport Request Listing. 18

The function spec and technial spec design dependends on the project and clint

Regards point if help ful