George Mason University

High Level Requirements Title

Last updated:

1/20/2012 1/20/2012

DRAFT

author
author'stitle
UniversityComputingandInformationSystems
GeorgeMasonUniversity
4400UniversityDrive
Fairfax,VA22030

High Level Requirements Title

Control Page
Title:

name of project

Author: original author of high level requirements document

File:

path and file name of document

Project Sponsor:

person sponsoring this project

Customers:

end-users of project when completed

Estimated Start Date: date project should begin

Estimated End Date:

date project should end

Approved By:

names, titles, project roles, signatures, dates of all who need to approve the project project sponsor, project manager I, IT Business Council
Name

Last updated: 1/20/2012 23:24 A1/P1

Title

Project Role

Signature

Date

High Level Requirements Title

Revision History
This document has been through the following changes:
Date

Author

Change

Mm/dd/yyyy

Author's name

Example: first draft

Last updated: 1/20/2012 23:24 A1/P1

Document and location

High Level Requirements Title

Table Of Contents
1 PROJECT OBJECTIVES/GOALS.........................................................................................................................5
2 IMPACT/BENEFITS................................................................................................................................................5
3 SCOPE........................................................................................................................................................................5
4 CURRENT BUSINESS PROCESS..........................................................................................................................5
5 PROPOSED BUSINESS PROCESS........................................................................................................................5
6 KEY FUNCTIONALITY..........................................................................................................................................5
7 REQUIREMENTS.....................................................................................................................................................5
8 RESOURCES.............................................................................................................................................................6
8.1 DESCRIBE THE TEAM IN DETAIL AND NAME THE TEAM MEMBERS. ................................................................................6
8.2 DESCRIBE THE HARDWARE, SOFTWARE IN DETAIL....................................................................................................6
9 TECHNICAL ASSUMPTIONS, CONSTRAINTS AND RISKS..........................................................................6
10 BUSINESS ASSUMPTIONS, CONSTRAINTS AND RISKS...........................................................................6
11 HIGH LEVEL SCHEDULE/MILESTONES......................................................................................................6

Last updated: 1/20/2012 23:24 A1/P1

High Level Requirements Title

1 Project Objectives/Goals
Define the requests objectives and goals, including problems to be solved.

2 Impact/Benefits
State anticipated general impact of this application on university functions. State
anticipated general benefits.

3 Scope
Define the requests scope including functions and processes to be examined, and
anticipated functional units which may be affected. State which systems will be affected by
this application (e.g., BR, FAM, SR, FRS, HRS) any functions within the system that may
be affected (e.g. Accounts payable, Payroll, Grading, Academic Action, etc.). Include the
intended audience of this application. Include the number of anticipated users.

4 Current Business Process

Describe manual or automated process(es) as it currently exists. This could include
flowcharts.

5 Proposed Business Process

Describe proposed processes as you perceive the new function changing or replacing the
existing process. This could include flowcharts.

6 Key functionality
State all required features of the proposed application. Examples of these features include:
a) Federal/State mandated rules, deadlines, etc.
b) University policies that must be implemented.
c) Specific input and outputs needed.
d) Describe all business rules to be implemented.

7 Requirements
Provide descriptions of the proposed functions and expected results, for example, report
descriptions. Describe design of user interfaces or anything that will alter the look of the
application.

Last updated: 1/20/2012 23:24 A1/P1

High Level Requirements Title

8 Resources
Describe each type of resource required and the expected role of each resource on the
project. Number each resource. The resources could be described in greater detail than in
the Project Charter and specific individuals could be named as team members.
8.1

Describe the team in detail and name the team members.

8.2

Describe the hardware, software in detail.

9 Technical Assumptions, Constraints and Risks

Describe technical assumptions, constraints and risks involving operating systems,
environments, and platforms. Note particular technical concerns involving security,
languages, new technologies, etc.

10 Business Assumptions, Constraints and Risks

Describe any critical business assumptions and/or criteria for project success like funding,
training requirements, milestones, staffing, and the like. Describe any assumed roles and
responsibilities that may impact short and long-term project success.

11 High Level Schedule/Milestones

Describe the meeting schedule during the project. Describe each milestone and the expected
date it will be accomplished. Number the milestones. The schedule and milestones would
be described in greater detail than in the Project Charter.

Last updated: 1/20/2012 23:24 A1/P1