Functional Requirements Document Template

brokenroomNetworking and Communications

Nov 21, 2013 (3 years and 11 months ago)

133 views

Functional Analysis Tempalte.docx



1

Last Update: 9
/
10
/08



Functional Analysis



Project Name:



Department:


Project Manager
/Developer
:


Date
:




Approval


Name


Date


Signature

Technical Review Team

(approve technical design)




Database Administration

(approve database/software
configuration)




Developer

(approve programming technology)




Director, SNT

(approve server

security
, application

security
, network security and data
transport security)




CSA

(approve data elements
collected &
transferred; approve hosted vendor
security, if applicable)




Project Manager

(approve
scope and feasibility)




Key User

(approve functionality)




Departmental VP

(approve project and funding)




Functional Analysis Tempalte.docx



2

Last Update: 6/9/08



1

INTRODUCTION

1.1

Purpos
e

Provide an overall
description of the

system/project
,
what is the purpose of this
system/project
. Reference the system name and identifying information abou
t the system
to be implemented.

1.2

Scope

Discuss t
he scope of the
system/project
and how it
accomplishes

its purpose
/objectives

along with any additional information to place the system/project in context
.


1.3

Backgroun
d

Describe the current department’s systems/processes. This history will support why the
enhancement/development is needed. This section should provide enou
gh detail for the
audience to understand why the department’s need is valid.


1.4

Benefits

Describe the benefits that this new system/process will provide.


1.5

Return on Investment

ROI is the ratio of
money

gained or lost on an
investment

relat
ive
to the amount of money
invested. Please use the following table, when
applicable, to calculate ROI:


I. Cost of Ownership

Year 1

Year 2

Year 3

a. Software/Hosted Fees







b. Hardware







c. Maintenance/Support







d. Other Costs







TOTAL















II. Benefits

Year 1

Year 2

Year 3

a Staff Time Savings







b. Vacancy savings







c. Other







TOTAL















III. Savings

Year 1

Year 2

Year 3

a) Annual







Functional Analysis Tempalte.docx



3

Last Update: 6/9/08


b) Cumulative










1.6

Long/Short Term Costs


List all of the costs associated with the system/project. Costs may include
development,
purchases, maintenance, support, hardware, etc
.


FUNCTIONAL REQUIREMENTS

2.1

User Requirements

Provide requirements of the system, user or business, taking into account all major
classes/categories of users.


TECHNICAL REQUIREMENTS

3.1

Interface
Requirements

Describe the user interfaces that are to be implemented by the system

as documented in
the context diagram.

If there will be database interfaces, please specify the type below.




Database Link



ODBC Connection



JDBC Connection



Other


3.2

Data Encryp
tion

Is d
ata
e
ncryption
r
equired?
If so, please note the type
of encryption

below.



FGAC (fine grain access control)



Oracle TDE (transparent data encryption)



Other


3.3

Sign
-
on attributes
.

Please specify the authentication method below.



AD authentication
(ldap/ldaps)



Database user authentication



Application login

3.4

Data Conversion Requirements

Describe the requirements needed for conversion
of legacy data into the system.

Functional Analysis Tempalte.docx



4

Last Update: 6/9/08


3.5

Hardware/Software Requirements

Provide a description of the hardware and software platf
orm
s needed to support the
system.

3.6

Network Requirements

Please document what types of users will uses this system (students, staff, faculty and/or
non
-
Bentley employees, where they will access it from (inside or outside of Bentley) and
approximate number o
f users that will
use

this system.

Also note if the application will
be accessed outside of Bentley.

3.7

Security

and Privacy

List specific data elements that
will be stored in this system

and if they
are considered
confidential or

institutional
.


3.8

System
Availability

State the
period
during which the application
must be
available to users.




Functional Analysis Tempalte.docx



1

Last Update: 9
/
10
/08

Appendix A

-

Network Diagram