Requirements Specification

Project Client	Organisation:
	Contact:

System Name	<<To be created by team and client>>

Date of Design Document	<<Date of this version>>

Document Status	Draft / Approved <<delete one>>

Document Reference	<<FileName.doc>>

Version Number	Version 1<<update as necessary, in whole numbers>>

Prepared by	<<Technical Writer>>

Team Members	<< Names of other team members>>

1.Change History

All changes to the Design Document must be recorded in the Change History.

Date	Description of Change	Reason for Change	Author of Change	Version No.

dd/mm/yyyy	Initial draft	N/A		Version 1

2.Table of Contents

1. Change History 2

2. Table of Contents 3

3. Purpose of the Project 4

4. Requirements Analysis 4

4.1. Business Goals of the Project 4

4.2. Site Requirements 4

4.3. User Requirements 4

4.4. Application Requirements 5

4.5. Technical Goals 5

4.5. Scalability 5

4.5. Availability 5

4.5. Network Performance 5

4.5. Security 5

4.5. Manageability 5

4.5. Usability 5

4.5. Adaptability 5

4.5. Affordability 5

5. The Existing Environment 5

5.1. Overview of the Existing Environment 5

5.2. Technical Details of the Existing Environment 5

5.3. Existing Applications 5

5.4. Existing Logical Layout 5

5.5. Existing Physical Layout 6

6. References 6

3.Purpose of the Project

<<What will the client be able to do after the project has been completed, that cannot be done now? This section should be similar to the same section in the project charter.>>

4.Requirements Analysis

4.1.Business Goals of the Project

<<This section should contain a more detailed description and discussion of the business objectives initially identified in the project charter. The business goals should be refined as more about the project is discovered with clear, identifiable and measurable evidence discussed.>>

To be considered successful, the proposed project must achieve the following goals for the client:

	BUSINESS GOAL	EVIDENCE OF GOAL ACHIEVED

4.2.Site Requirements

<<This section should identify and document layer 1 and layer 2 requirements of the project. It is important to remember that this document is detailing what is required by the client. Questions you should ask include:

are there layer 1 cabling requirements of the project?
what are the LAN requirements for the project?
what are the WAN requirements for the project?
is wireless access a requirement for the project?
what buildings, offices and geographical locations are included in the requirements?

This section should contain unambiguous concise specifications and may include diagrams to assist in clearly identifying this part of the requirements specification.>>

4.3.User Requirements

<<This section should identify and document user requirements of the project. Which users or user groups exist, what are the requirements of each user group. It should contain specific details such as the number and category of users for each location and details of the users data storage and network usage requirements.>>

4.4.Application Requirements

<<This section should identify and document network applications and their requirements. It should identify the topology of network applications, the location of application components (such as interface, data storage, data processing), the data flow requirements for applications as well as any specific application requirements such as quality of service, latency, redundancy or throughput requirements.>>

4.5.Technical Goals

<<This section should identify and document the technical goals for the project. Each category should identify the particular requirement and identify the tradeoffs that will need to be considered when designing the proposed solution. See Reading 5 for more detail on each of the following sections..>>

5.1.Scalability

5.2.Availability

5.3.Network Performance

5.4.Security

5.5.Manageability

5.6.Usability

5.7.Adaptability

5.8.Affordability

5.The Existing Environment

<<If applicable, this section should describe in as much detail as possible the clients existing environment. It should include written descriptions, concise technical details and diagrams to describe the existing network, applications and site details.>>

5.1.Overview of the Existing Environment

5.2.Technical Details of the Existing Environment

5.3.Existing Applications

5.4.Existing Logical Layout

5.5.Existing Physical Layout

6.References

<<You must acknowledge all official publications that you use during the life of the project. However templates and other materials provided by lecturers do not need to be acknowledged.>>