Functional Requirements Specification

<Project>
Information Technology Services

<Date>
<Version>
<Author>

THINKING AT THE EDGE

Document Control

Change Record

Date Author Version Change Reference

Reviewers

Sign Off Reviewer Position Sign Off

Date

Distribution

Copy Name
Number

UC Santa Cruz Functional Requirements Specification ii

Table of Contents

DOCUMENT CONTROL..................................................................................................................... II
Change Record ...............................................................................................................................................................ii
Reviewers ii
Distribution ....................................................................................................................................................................ii

TABLE OF CONTENTS .................................................................................................................... III

1. INTRODUCTION ........................................................................................................... 4
1.1 Overview .................................................................................................................................................................. 4
1.2 Objectives ................................................................................................................................................................ 4
1.3 Scope. ................................................................................................................................................................... 4
1.4 Terms and Acronyms .............................................................................................................................................. 4

2. SYSTEM USAGE .......................................................................................................... 5

2.1 System Users ........................................................................................................................................................... 5
2.1.1 Primary Users .................................................................................................................................... 5
2.1.2 Secondary Users ................................................................................................................................ 5
2.1.3 User Characteristics ......................................................................................................................... 5
2.2 Use Cases ................................................................................................................................................................. 6
2.2.1 <Use Case 1> .................................................................................................................................... 6

3. OPERATING REQUIREMENTS ..................................................................................... 7

3.1 Performance Requirements ..................................................................................................................................... 7
3.2 Presentation Requirements ..................................................................................................................................... 7
3.3 Administration Requirements ................................................................................................................................. 7
3.3.1. Data Security .................................................................................................................................... 7
3.3.2. Maintainability and Upgradability ................................................................................................. 7
3.3.3. Portability ......................................................................................................................................... 7
3.3.4. Transaction Volumes and Future Growth ...................................................................................... 7
3.4 Communications Interface Requirements .............................................................................................................. 7

4. DIAGRAMS.................................................................................................................................... 8

5. NOTES AND DISCUSSIONS.......................................................................................................... 9

6. REFERENCES ............................................................................................................................. 10

UC Santa Cruz Functional Requirements Specification iii

 1. Introduction

1.1 Overview
<Purpose of the software or project high level>

1.2 Objectives
<Bullet-point list of specific goals to be met>

1.3 Scope
< Define what is in/out of scope>

1.4 Terms and Acronyms

Short Name Long Name Description

FRS Functional Requirements This document

Specification

ITS Information Technology The information technology division. at UCSC

Services

UC Santa Cruz Functional Requirements Specification 4

 2. System Usage

2.1 System Users

2.1.1 Primary Users
<Describe primary user base who are they?>

2.1.2 Secondary Users

<Describe secondary user base who are they?>

2.1.3 User Characteristics

User Characteristics User Type
<General usage traits> Primary
<General usage traits> Secondary

UC Santa Cruz Functional Requirements Specification 5

2.2 Use Cases
<Supply list of use cases>

2.2.1 <Use Case 1>

Business Event <Describe real-world business operation taking place>
Actor(s) <Describe who is involved>
Overview/Description <Surrounding/precipitating events, if applicable>
Flow of events 1. <Step 1>
2. <Step 2>

Preconditions <Describe what needs to be true before processing>

Business rules <Describe rules that apply to this use case>

Input summary <Describe required user input>

Output summary (post- <Describe successful outcome>
conditions)
Possible causes for <Describe what can go wrong>
failure
Assumptions <List any assumptions made>

Security <List security requirements specific to this use case>

Notes <Any additional comments>

2.2.1.1 <Scenario A for Use Case 1>

<Use to describe scenarios, e.g. actions based upon error states for use case>

UC Santa Cruz Functional Requirements Specification 6

 3. Operating Requirements

3.1 Performance Requirements

<Describe performance expectations>

3.2 Presentation Requirements

<Describe UI requirements>

3.3 Administration Requirements

<Describe software administration requirements>

3.3.1. Data Security

<Describe system security requirements>

3.3.2. Maintainability and Upgradability

<Describe requirements to maintain/upgrade software>

3.3.3. Portability
<Describe portability requirements / need to operate in heterogeneous environment>

3.3.4. Transaction Volumes and Future Growth

<Describe initial and anticipated usage rates>

3.4 Communications Interface Requirements

<Describe any need for communication with other systems>

UC Santa Cruz Functional Requirements Specification 7

 4. Diagrams

<Include any diagrams pertinent to the analysis phase>

UC Santa Cruz Functional Requirements Specification 8

 5. Notes and Discussions

<Use this section for recording anything deemed important that doesnt fit in other areas>

UC Santa Cruz Functional Requirements Specification 9

 6. References

Item Reference

APM
Information Technology Services
University of California, Santa Cruz
2300 Delaware Ave.
Santa Cruz, CA 95060

UC Santa Cruz Functional Requirements Specification 10