|
Managing
IT Projects
|
|
|
Statement of User Requirements
|
Click
for Sample |
|
|
A Specification of User Requirements ("SOUR") is an essential
document in the process of introducing new IT facilities. The SOUR helps
you by: |
|
|
|
|
|
| 1 |
Forcing users to sort out what
functions they need |
| 2 |
Identifying which other systems might
be affected |
| 3 |
Forcing suppliers to provide a price
against a fixed set of needs |
| 4 |
Allowing you to make fair comparisons
of different tenders against a common set of benchmarks |
| 5 |
Defining systems performance criteria |
| 6 |
Defining the probable data volumes of
the new systems |
|
|
|
A typical SOUR should contain the following information:
|
|
| 1 |
Background Information |
|
In this section, you should describe the background to the organisation, the
reasons for wanting to introduction a new system and the general business model
operated by the organisation. |
|
|
| 2 |
Evaluation Criteria |
|
You should explain the ways in which each tender is to be measured.
Usually, these will include - |
|
 |
cost |
|
degree of functionality and closeness of fit to SOUR |
|
ease of use |
|
location of supplier |
|
capability to support customer |
|
approach to training |
|
support and suitability of any special facilities required |
|
methodology for developing customised features |
|
|
|
| 3 |
Technical Background Information |
|
The SOUR should describe the IT environment within which the new facilities
must operate such as - |
|
|
existing hardware |
|
existing network and operating systems |
|
required protocols support - networking, email, etc |
|
existing remote data capture technology |
|
existing data storage facilities |
|
network diagrams showing the existing locations of servers, printers, PCs,
VDUs and other devices |
|
network diagrams showing the anticipated locations of existing and new
equipment |
|
|
|
| 4 |
Business Background Information |
|
Before describing each of the key functional parts of the new system, you
should explain how the business operates each day. The description should
explain both how the business processes operate today and how they are required
to operate in the future. By describing any planned changes, users are
made to think well ahead of the new IT facilities. Wherever possible, it
is helpful if you include diagrams, flowcharts and decision trees to amplify
your description. |
|
|
| 5 |
Module Descriptions |
|
For each of the principle functional modules, you should describe the
features you require. The specification should cover - |
|
|
brief overview of the functions required |
|
the objective of the module |
|
the key functions required distinguishing between those essential and
desired |
|
the essential reports |
|
the enquiry facilities, including ranges, filters and sorting criteria |
|
linkages to other modules or other applications |
|
the essential data required |
|
|
|
| 6 |
Data Volumes |
|
You should set out a table showing the anticipated data volumes to be process
by the new system. |
|
|
|
|
|
|
|
|
|
4-consulting
15 Palmerston Road,
Edinburgh, EH9 1TL
Tel 0131 668 2112
Copyright © 2002 4consulting |
|
