Insert logo and School Name/Address

Project Documentation Plan Template

[SRS-Based]

< The Project Documentation Plan provides the detailed project work plan,
timescale and resourcing requirements to effectively monitor and control IS Project
progress. While a working system is not required, the Project Documentation Plan also
provides the business justification for the project, which is reviewed as the project
progresses. Accordingly, this guide should be removed from the front of the document
once completed. >

o Items that are intended to stay in as part of your document are in bold;
o Explanatory comments for each section/subsection are in italic text (blue).
This is where you might insert wordings about your project.
 <<PROJECT FULL TITLE here…>>

Version 1.0

<Company Logo>

GROUP #_

<TEAM MEMBERS>
 <<PROJECT FULL TITLE here…>>

TABLE OF CONTENTS

1. Introduction.....................................................................Error: Reference source not found

1.1 Purpose............................................................................Error: Reference source not found

1.2 Scope...............................................................................Error: Reference source not found
1.3 Definitions, Acronyms and Abbreviations......................Error: Reference source not found
1.4 References.......................................................................Error: Reference source not found
1.5 Overview.........................................................................Error: Reference source not found

2. General Description........................................................Error: Reference source not found

2.1 Product Perspective.........................................................Error: Reference source not found

2.2 Product Functions............................................................Error: Reference source not found
2.3 User Classes and Characteristics.....................................Error: Reference source not found
2.4 Design and Implementation Constraints.........................Error: Reference source not found

3. Specific Requirements....................................................Error: Reference source not found

3.1 User Interfaces.................................................................Error: Reference source not found

3.2 Hardware Interfaces........................................................Error: Reference source not found
3.3 Software Interfaces..........................................................Error: Reference source not found
3.4 Communications Interfaces.............................................Error: Reference source not found

4. System Requirements Planning

4.1 Scope Planning................................................................Error: Reference source not found

4.2 Financial Planning...........................................................Error: Reference source not found
4.3 Quality and Acceptance Planning...................................Error: Reference source not found
4.4 Communication Planning................................................Error: Reference source not found
4.5 Procurement Planning.....................................................Error: Reference source not found

<Please edit page numbers and include the contents of Deliverable #2. >
 <<PROJECT FULL TITLE here…>>

1 Introduction
<This section of the Project Documentation Plan defines the introduction of the
plan.>

1.1 Purpose

<This subsection of the Project Documentation Plan describes the

purpose of the plan and identifies the system to be implemented.>

1.2 Scope

<This subsection of the Project Documentation Plan discusses the scope

of the project and its delimitations.>

1.3 Definitions, Acronyms and Abbreviations

<This section should define all terms, acronyms and abbreviations used in
this document. Particular care should be taken to define terms that are specific to
the application.>

1.4 References
o Specify the sources from which the references can be obtained.
o List any other documents or Web addresses to which this document refers.

1.5 Overview

1.5.1 System Overview

<Provides a description of the system to be implemented and its organization.>

2 General Description
<This section of the document describes all general factors of the product and its
requirements.>
 <<PROJECT FULL TITLE here…>>

2.1 Product Perspective

<Describe the context and origin of the product being specified in this SRS.

2.2 Product Functions

<Summarize the major functions the product must perform or must let the user
perform. Details will be provided in Section 3, so only a high-level summary (such as a
bullet list) is needed here. Organize the functions to make them understandable to any
reader of this document.>

2.3 User Classes and Characteristics

<Identify the various user classes that you anticipate will use this product. User
classes may be differentiated based on frequency of use, subset of product functions used,
technical expertise, security or privilege levels, educational level, or experience.
Describe the pertinent characteristics of each user class. Certain requirements may
pertain only to certain user classes. Distinguish the most important user classes for this
product from those who are less important to satisfy.>

2.4 Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the
developers. These might include: corporate or regulatory policies; hardware limitations
(timing requirements, memory requirements); interfaces to other applications; specific
technologies, tools, and databases to be used; parallel operations; language
requirements; communications protocols; security considerations; design conventions or
programming standards (for example, if the customer’s organization will be responsible
for maintaining the delivered software).>

3 Specific Requirements

3.1 User Interfaces

<Describe the logical characteristics of each interface between the software product and
the users. Define the software components for which a user interface is needed.>

3.2 Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the
software product and the hardware components of the system. This may include the
supported device types, the nature of the data and control interactions between the
software and the hardware, and communication protocols to be used.>
 <<PROJECT FULL TITLE here…>>

3.3 Software Interfaces

<Describe the connections between this product and other specific software
components (name and version), including databases, operating systems, tools, libraries,
and integrated commercial components. Identify the data items or messages coming into
the system and going out and describe the purpose of each. Describe the services needed
and the nature of communications.

3.4 Communications Interfaces

<Describe the requirements associated with any communications functions required

by this product, including e-mail, web browser, network server communications
protocols, electronic forms, and so on. Define any pertinent message formatting. Identify
any communication standards that will be used, such as FTP or HTTP. Specify any
communication security or encryption issues, data transfer rates, and synchronization
mechanisms.>

4 System Requirements Planning

● Section 1: Scope Planning

○ Determined most or all specific activities/tasks required to complete the

project
○ Developed a comprehensive schedule of project activities/tasks with realistic
due dates for the project

● Section 2: Financial Planning

○ Identified all resources needed and realistically quantified them for the project
○ Realistically forecast all expenses for the project

● Section 3: Quality and Acceptance Planning

○ Clearly defined all quality targets and processes for assurance, control and
management of quality that are applicable in the project
Correctly identified complete acceptance criteria, acceptance schedule and a
logical acceptance management process that are applicable in the project.

● Section 4: Communication Planning

 <<PROJECT FULL TITLE here…>>

○ Correctly identified complete delivery channels, communications schedule,

communications events and communication matrix that are applicable in the
project

● Section 5: Procurement Planning

○ Correctly identified complete procurement requirements, list of available

offerings, procurement schedule and procurement process that are applicable
in the project.
 <<PROJECT FULL TITLE here…>>

5. System Features

<This section illustrates organizing the functional requirements for the product by system
features, the major services provided by the product.

5.1 Functional Requirements

<Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the services provided by
the feature, or to execute the use case. Include how the product should respond to anticipated error
conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable,
and necessary.
<Each requirement should be uniquely identified with a sequence number or a meaningful tag
of some kind.>

REQ-1:
REQ-2:

6. Nonfunctional Requirements

6. 1 Performance

6.2 Reliability

6.3 Availability

6.4 Security

6.5 Maintainability

6.6 Portability

7. System Design

7.0 Other Requirements

 <<PROJECT FULL TITLE here…>>

<Include any pertinent analysis models, such as context data flow diagram, use cases,
database schema or entity-relationship diagrams or data dictionary, activity diagram and class
diagrams. Add any new sections that are pertinent to the project.>

2.1 Overview Architecture of the Proposed System

<......>

2.2 Context Diagram

<......>

2.3 Use Case Diagram

<......>

2.4 Database Schema

<......>

2.5 Data Dictionary

<......>

2.6 Activity Diagram (Swimlane)

<......>

2.7 Class Diagram (Swimlane)

<......>
 <<PROJECT FULL TITLE here…>>

2. 8 Other important/applicable diagrams to your proposed system

<......>

2. 9 Sample UI Design for each module.