Scribd
Upload
90 views3 pages

Fs - Blank Format

This document provides information for developing a dealer wise SO status program including the program title and type, required functionality, security requirements, input and output details, and test scenarios. It specifies the donor/target system details if an interface program, data volume and frequency. The document also lists the program logic, tables/files used, and additional notes.

Uploaded by

Subhash Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
90 views3 pages

Fs - Blank Format

This document provides information for developing a dealer wise SO status program including the program title and type, required functionality, security requirements, input and output details, and test scenarios. It specifies the donor/target system details if an interface program, data volume and frequency. The document also lists the program logic, tables/files used, and additional notes.

Uploaded by

Subhash Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Title: dealer wise SO

Status
Development ID
Number:
Type:
Module : PP
Sub-module
Criticality
Frequency of
:execution
Data Volume
Process Team Owner:
Technical Team
Owner:
Issue Date:
Status:

Document Control
Change
No.

Rev. No. inc.


change

Originator
of change

Date of
change

Description of change

Tested and Approved by:

Name of Business
Process Owner

Turanya Functional Specification

Sign of

Core Team Member

1 of 3

Sign of

22-Dec-15

Program Information

1.
1.1.

Description: Predefined requirements

(If any)
Program Title:
Program Name:
Transaction
Code:
Message Class:
Program Type:
Authorization
Group:
Menu Path
Layout Name
Font / Layout
type / etc.
1.2.

Input / Dependencies (If Any)

1.3.
1.4.
1.5.

Required Functionality
Donor / Target System details / requirements (Interface only)
Donor / Target System data volume / frequency. (Interface only)

1.6.
Security / Authorization requirements.
1.7.
Execution parameters.
1.8.
Detailed Requirements Program LogicAdditional Comments /
Requirements / Notes

1.9.

Table / File data used / produced.

Turanya Functional Specification

2 of 3

22-Dec-15

4. Input

5. Output
Output

1.

Test Scenarios

2.

Technical Specifications

Turanya Functional Specification

3 of 3

22-Dec-15

You might also like