SRS document on library database

Software Requirements Specification

Project name:

Application name:

Customer:

Version:0.0

Date:........

Status: Draft/final

Revision History:

Table of Contents

Contents 1 Project overview 4 1.1 Definitions & Acronyms 4 1.2 Referenced Documents or Notes 4 1.3 Project name 5 1.4 System Overview 5 1.5 System Objectives 5 1.6 Support 5 1.7 Stakeholders 5 1.8 System Context 5 1.9 Acceptance Criteria 5 1.10 Evaluating Success 5 2 General Description 5 2.1 Product Functions 5 2.2 User Characteristics 5 2.3 Assumptions and Dependencies 6 2.4.1 User Interfacing 6 2.4.2 System Constraints 6 2.4.3 Operations 6 2.4.4 Adaptation / Compatibility Requirements 6 2.5 User Base 6 2.6 General Design Constraints 6 2.7 Project Feasibility 6 3 Requirements 7 3.1 Functional Requirements 7 3.2 Non-functional Requirements 7 3.3 Automatically generated value Rules 7 3.4 Interface Requirements 7 3.4.1 User Interfaces 7 3.4.2 User Story Boards 7 3.4.3 Hardware Interfaces 7 3.4.4 Software Interfaces 7 3.4.5 Communications Protocols 7 3.4.6 Site Map 7 3.5 Hardware Requirements 7 3.5.1 Client-side 7 3.5.2 Server-side 7 3.6 Software Requirements 7 3.6.1 Client-side 7 3.6.2 Server-side 7 3.7 Database Requirements 7 3.7.1 Entity-Relationship Diagram 7 3.7.2 Entity-Relationship Diagram Notes & Assumptions 8 3.7.3 Database Schema 8 3.8 Extra Quality Requirements 8 3.9 Training Requirements 8 4 Appendixes 9 4.1 Appendix A - Context diagram 9 4.2 Appendix B – DFD (Level 0) 9 4.3 Appendix C - Deployment Diagram 9 4.4 Appendix D - Use case model 9 4.5 Appendix E - Activity diagrams 9 4.6 Appendix F – Testing TOM Survey’s 9 4.7 Appendix G – Auto Generated Emails 9 4.8 Appendix H – Level Progress Diagram 9 5 Sign-off 10 5.1 Client Sign-off 10 5.2 Team Sign Off 10

This section is designed to give an overview of the project.

The following definitions and acronyms are used throughout this Document (Software Project Management Plan) they may refer to terms used by the client or by the development team.

Users:

Administrators:

Super Administrator:

Development team:

Display tests

Record data

Surveys

Administration area

Download Data

2.4.1.1 Use Cases

Use Case 1 – Super Administrator Login

Actors:

Procedure:

Exceptions:

Database requirements:

Use Case 2 – Manage Administrator Users

Actors:

Procedure:

Exceptions:

Database requirements:

Use Case 3 – ........

.

.

2.4.1.2 Activity Diagrams

Economic

Operational

Technical

Legal / Political

Ethical

3.7.2.1 Notes

3.7.2.2 Database Assumptions

Name: Date: / /

Name: Date: / /

Name: Date: / /

Name: Date: / /

Copyright © TBBC 2007 Page: 1 of 41

Copyright © TBBC 2007 Page: 1 of 41

Page: 4 of 11