Complete Project Management System
Software Requirement Specifications
Version 1.0
Table of Contents
1. Introduction 3
1.1 Purpose of this document 3
1.2 Scope of this Document 3
1.3 Overview 3
1.4 Workflow of the Application
2. General Description 5
2.1 Product Functions 5
2.2 Similar System Information 6
2.3 User Characteristics 6
2.4 User Problem Statement 7
2.5 User Objectives 7
3. Functional Requirements 8
3.1 User Authentication
.*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦
*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*
ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ
²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²
*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦..8
3.2 Creation and Termination of Projects
*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*
ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ
²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²
*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦…8
3.3 Addition and Deletion of Members
*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*
ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ
²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²
*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦….9
3.4 Communication Channel
*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*
ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ
²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²
*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*
ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦*ƒ²*ƒ”€š*ƒ‚¦9
4. Interface Requirements 10
4.1 User Interfaces 10
4.2 Hardware Interfaces 12
4.3 Communications Interfaces 12
5. Performance Requirements 12
6. Other non-functional attributes 12
7. Operational Scenarios 12
8. Preliminary Schedule 13
1. Introduction
1.1 Purpose of this document
This document includes the specifications of the software required in developing the
Complete Project Management System. Project Management System provides enterprise
program and project planning, estimating, budgeting, resource allocation, collaboration,
and time capture to help companies deliver project portfolios efficiently.
1.2 Scope of this Document
*ƒ¿*…¡*ƒ‚§ A powerful user interface that is easy to understand for both business and
technical users.
*ƒ¿*…¡*ƒ‚§ Tracks the growth, functioning and the progress, of each of the company
current assignments, i.e. their projects.
*ƒ¿*…¡*ƒ‚§ CPMS provides full overview of the current projects in the company that are
exclusive and are sharable.
*ƒ¿*…¡*ƒ‚§ The dashboard provided is customizable, and user-friendly.
*ƒ¿*…¡*ƒ‚§ Enterprise permissioning and security serves as a major aspect in developing
the Complete Project Management System.
*ƒ¿*…¡*ƒ‚§ Easily extended to and can aslo be integrated with other systems (including
email, Access, XML and source control).
*ƒ¿*…¡*ƒ‚§ Highly configurable notification options
*ƒ¿*…¡*ƒ‚§ CPMS runs on almost any hardware, OS and database platform
*ƒ¿*…¡*ƒ‚§ Web service needs to be enabled in CPMS.
1.3 Overview
Provides a brief overview of the product defined as a result of the requirements elicitation
process.
Project Monitoring, Costing, Billing and Invoicing
It should provide all the tools needed to help manage your projects. Once your project is
under way, the user should be able to monitor progress against plan by reviewing the
“traffic lights” shown at all levels from the individual tasks, through the products and
stages (activities and phases) right up to the whole project.
Time and cost collection (project tasks and non-project activities) via timesheets
The integrated Timesheet Application should be able to analyze the actual time spent on
projects – and also on non-project activities.
Functional
The project should be web based application. Admin rights will be restricted.
Risks and issues logging
It enables the user to enter the issues and risks as they occur, and monitor progress on
resolving or mitigating them.
The logs can include:
*ƒ¿*…¡*ƒ‚§ Status descriptions
*ƒ¿*…¡*ƒ‚§ Severity measurements and scores
