Requirements Specification Project Client Organisation: Contact: System Name <> Date of Design Document <> Document Status Draft / Approved <> Document Reference <> Version Number Version 1<> Prepared by <> 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 <> 4. Requirements Analysis 4.1. Business Goals of the Project <> To be considered successful, the proposed project must achieve the following goals for the client: BUSINESS GOAL EVIDENCE OF GOAL ACHIEVED 1. 2. 3. 4. 5. 4.2. Site Requirements <> 4.3. User Requirements <> 4.4. Application Requirements <> 4.5. Technical Goals <> 4.5. Scalability 4.5. Availability 4.5. Network Performance 4.5. Security 4.5. Manageability 4.5. Usability 4.5. Adaptability 4.5. Affordability 5. The Existing Environment <> 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 <>