[

Functional Specification Enhancement

Prepared By:
Prepared For:
Date Created:
Last Updated:
(R)esponsible
(A)uthority
(S)upport:
(C)onsult:
(I)nform:

Document Overview
Authors Name
Department Name
Month Day, Year
August 13, 2008
RASCI Alignment

FUNCTIONAL SPECIFICATION

PROJECT NAME

Revision Log
Revision

Date

1.0

MM/DD/YY

Initials

Description of Revision

Initial Draft

Table of Contents
1) FUNCTIONAL HEADER........................................................................ERROR! NO BOOKMARK NAME GIVEN.
2) ENHANCEMENT DEFINITION...........................................................ERROR! NO BOOKMARK NAME GIVEN.
3) FUNCTIONAL SPECIFICATIONS.......................................................ERROR! NO BOOKMARK NAME GIVEN.
4) CUSTOM TABLES..................................................................................ERROR! NO BOOKMARK NAME GIVEN.
5) SELECTION SCREEN............................................................................ERROR! NO BOOKMARK NAME GIVEN.
6) TRANSACTION SCREENS...................................................................ERROR! NO BOOKMARK NAME GIVEN.
6.1) SCREEN FLOW LOGIC ....................................................................................ERROR! NO BOOKMARK NAME GIVEN.
6.2) SCREEN LAYOUT............................................................................................ERROR! NO BOOKMARK NAME GIVEN.
6.3) HEADER.........................................................................................................ERROR! NO BOOKMARK NAME GIVEN.
6.1) LINE ITEM......................................................................................................ERROR! NO BOOKMARK NAME GIVEN.
7) ADDITIONAL TOPICS...........................................................................ERROR! NO BOOKMARK NAME GIVEN.
8) DOCUMENT SIGN OFF.........................................................................ERROR! NO BOOKMARK NAME GIVEN.

File Name: 334185944.doc

Last Saved: 10/30/2012 04:45:00 PM

Page 2 of 7

FUNCTIONAL SPECIFICATION

PROJECT NAME

1) Functional Header
Note: An Enhancement is an approved modification to an existing application, which will modify or extend
code. This may often include the introduction of new screens, new database tables, new functionality, etc.
Enhancements may also include workflows which is a semi-automated process designed to complete a
series of tasks in a specified order. Upon completion of a step or task, the workflow notifies the next
resources that their tasks can be performed.
Dev. ID
Functional

(ID)

Team

(functional owner)

(phone #)

Dev. Team

High/Medium/Low

Release /
Priority

2) Enhancement Definition

Basic Information
Program type
(i.e. Custom program, Dialogue,
User Exit, etc)

Triggered

Manually / Scheduled job

Run Frequency

On-demand | Hourly | Daily | Weekly | Monthly | Quarterly | Yearly | Other Specify

High/Medium/Low

Usage Volume

File Name: 334185944.doc

Last Saved: 10/30/2012 04:45:00 PM

Page 3 of 7

FUNCTIONAL SPECIFICATION

PROJECT NAME

3) Functional Specifications

Functional Requirements
Purpose
Summarize the purpose of the enhancement as defined in the Requirements
document or DDS
Current functionality
Describe the current functionality, system or manual
Desired functionality
Describe the future functionality after the enhancement
Assumptions / Issues
Document any known assumptions and issues

Narrative Flow
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 9

4) Custom Tables
(If applicable)

Basic Information
Table name
Field

Key
(Y/N)

Data format

File Name: 334185944.doc

Last Saved: 10/30/2012 04:45:00 PM

Comment

Page 4 of 7

FUNCTIONAL SPECIFICATION

PROJECT NAME

5) Selection Screen
Select options

M/O

Default

(Mandatory/ Optional)

6) Transaction Screens
6.1) Screen Flow Logic

Screen Flow Logic

#

Screen Logic Description

6.2) Screen Layout

6.3) Header
Field

M/O

Comment

(Mandatory/
Optional)

File Name: 334185944.doc

Last Saved: 10/30/2012 04:45:00 PM

Page 5 of 7

Comment

FUNCTIONAL SPECIFICATION

PROJECT NAME

6.1) Line Item

Field

M/O

Comment

(Mandatory/
Optional)

7) Additional Topics

Additional topics
Unit Test
Suggestions
Security/
Authorizations
Error Handling

Suggested unit test scenarios from a business perspective should be listed here

Dependencies

Configuration, master data or any other prerequisites. Include predecessor and

successor processes.

References

Insert name and location of references relevant to this requirement that are not listed
elsewhere in this document

Out of scope
requirements

Requirements that you have not planned for within the current implementation. If
applicable requirements here may become candidates for the next set of changes

Specify security requirements

Describe error handling requirements

8) Document Sign Off

Phase: Design
The (Deliverable Name) document has been reviewed and found to be consistent with the specifications
and/or documented project requirements. The signature below documents acceptance of this document
and/or work product by the signing authority
Organization: University of Chicago________________

File Name: 334185944.doc

Last Saved: 10/30/2012 04:45:00 PM

Page 6 of 7

Contractor________________

FUNCTIONAL SPECIFICATION

PROJECT NAME

Approved by:
Signature: ___________________________________________________________________
Name: ______________________________________________________________________
Title:
Date:
Organization: University of Chicago________________

Contractor________________

Approved by:
Signature: ___________________________________________________________________
Name: ______________________________________________________________________
Title:
Date:
Organization: University of Chicago________________

Contractor________________

Approved by:
Signature: ___________________________________________________________________
Name: ______________________________________________________________________
Title:
Date:

File Name: 334185944.doc

Last Saved: 10/30/2012 04:45:00 PM

Page 7 of 7