[Project Management System] Requirements Specification

Page 1 o f 8
 [Project Management System] Requirements Specification

Index
Project Overview 2

Purpose and Scope 2

 Product Scope 3
 Project Scope 3

Product/Service Description 4
 User Characteristics 4
 Assumptions 4
 Constraints 4
 Dependencies 4

Requirements 5
 Functional Requirements/Non functional Requirements 5
 Usability 5
 Performance 5
 Capacity 5
 Availability 5
 Latency 5
 Manageability/Maintainability 6
1. Monitoring 6

System Interface/Integration 6
 Software Requirements 7
 Hardware Requirements 7
 Security 7
1. Protection 7

Page 2 o f 8
 [Project Management System] Requirements Specification
Executive Summary

1.1 Project Overview

Managing a project involves many different aspects and many things that have to be tracked and
followed up on. Here we determined project tasks, create a schedule, assign resources, and identify and
track issues and risks. That's just the tip of the iceberg; as a project manager is responsible for the overall
success of a project. How one can successfully track all those different aspects of a project.
A “PROJECT MANAGEMENT SYSTEM” is a means of managing a project by planning,
organizing, and managing its different required aspects. Depending on the sophistication of the project
management system.

1.2 Purpose and Scope

1.2.1 The purpose of project management is to foresee or predict as many dangers and problems as
possible; and to plan, organise and control activities so that the project is completed as successfully as
possible in spite of all the risks.

The ever-present element of risk and uncertainty means that events and tasks leading to completion can
never be foretold with absolute accuracy. For some complex or advanced projects, even the possibility
of successful completion might be of serious doubt.

Project management can involve the following activities: planning - deciding what is to be done;
organising - making arrangements; staffing - selecting the right people for the job; directing - giving
instructions; monitoring - checking on progress; controlling - taking action to remedy hold ups;
innovation - coming up with new solutions; representing - liaising with users.

1.2.2 In project management, there are actually two types of scope:

 Product Scope
 Project Scope

1.2.2.1 Product Scope:

 Estimation activities
 Scheduling
 Resource allocation
 Quality management
 Risk management
 Change control
 Decision-making managing

Page 3 o f 8
 [Project Management System] Requirements Specification

1.2.2.2 Project Scope:

 Gathering Information
 Project acceptance criteria
 Project Execution procedure
 Work Break Down Structure
 Controlling various process
 Validation of various process

2. Product/Service Description
The product will deliver services for a Project Manager to manage all the undergoing projects, assigning
projects, tracking the progress of a project through a proper systematic manner.

2.1 User Characteristics

General customer profiles for each type of user who will be using the product
 Student/faculty/staff
 Project Mangers

2.2 Assumptions
 The product will be used by small organization as well as freelancers for tracking their ongoing
project work progress.
 It is web based application and should be used in computer system.
 The website will be free of cost with a donation button and few ads.

2.3 Constraints
Describe any items that will constrain the design options, including
 Web based application that needs an active internet connection.
 Technology components have security vulnerabilities.
 Indirect negative customer satisfaction.
 Significant employee productivity degradation.
 System resource constraints, web browser should support HTML5.

2.4 Dependencies
 Registered account for Project Management System service.
 Proper classification of sub-ordinates and co- workers.
 Allocation of project to registered mentor.

Page 4 o f 8
 [Project Management System] Requirements Specification

3. Requirements
 System requirement having 2GB RAM, 320 GB, intel dual core processor, OS (Windows, Mac, Linux), Web
browser.
 The data which is feed should be up to date.
 Details of the project should be described and the project life cycle should be mentioned.
 Submission of project reports weekly/monthly.
 Project reports will be verified by the respective mentors and the project progress will be updated by him/her.

3.1 Functional Requirements:

Sl no REQUIREMENT COMMENTS PRIORITY

1 Registration Project Managers, High

Mentors and project
leaders will have a
registration number.
2 Log in capabilities The system will provide High
the owners/users with log
in capabilities
3 Modify profile information All users can modify their Low
profile information
4 Alerts The system can alert the High
users or owners.
5 Web Pannel Support on web perform High
by admin and for
maintaining data
6 HOS, Mentors, Project leader The will have different High
interfaces and will be
performing different
activities
7 Security Data will be stored online
with custom encryption
8 Security settings Process old password if High
matches then proceed for
new password
9 Notification, message HOS, mentors can send Low
notifications

3.2 Usability
 Student can interact with mentors and head online, they can also send message through email.
 Attendance tab will help the mentor and head to check the presence of the students.
 Users find very easy to understand the working of project management system

3.3 Performance
 Accessing of data from any place is very easy.
 Simultaneously head, mentor and group members can input data.
 Users chat and other activities are handled at a time.

3.3.1 Capacity
 The project web server can handle more than thirty thousand users at a time.

Page 5 o f 8
 [Project Management System] Requirements Specification
 The System will allow access to all the project reports and project data to Project Manager directly.
 System will handle all the manual work.
 Easy interface will allow users to perform tasks quickly and easily.

3.3.2 Availability
 The website application will be available for 24*7.
 All the report data will show graphically.
 In the case of website crashing all the data can be recover throw backup server.
 The website will handle the entire manual work load.

3.3.3 Latency

The website related issues will solve within the time limit in case any delay it will be solved in 2-3 days.

3.4 Maintenance:
Maintenance is inevitable for almost any kind of product. Most products need maintenance due to wear
and tear caused by use. Software products do not need maintenance on this count. Many people think
only bad software products need maintenance. The opposite is true bad products are thrown away, good
products are maintained and used for a long time.
Most computer programs are difficult and expensive to maintain. Software changes are poorly designed
and implemented. The repair and enhancement of software often injects new bugs that must later be
repaired.
The maintenance of existing software can account for over 60 percent of all effort expended by a
development organization, and the percentage continues to rise as more software is produced. Much of
the software we depend on today is on average 10 to 15 years old.
Eve
 Passwords of the user shall be encrypted in DBMS for security purposes.
 When the system crashes, it will return back at most one hour in maintainability purposes.

3.4.1 Monitoring
 The project will ensure about any failure facts like Error free, if any bug found will be solved as
soon as possible.
 The data will be encrypted form to make sure no data will be lost due to any cyber-attack.
 All the data related to the projects will be secure and cannot be access by server admin.
 All the user password would be encrypted with custom encryption.

3.5 System Interface/Integration

Page 6 o f 8
 [Project Management System] Requirements Specification

Fig- Log in screen

3.5.1 Software requirements

 Wamp server
 Php editor
 Mysql
 Visual Studio Code
3.5.2 Hardware requirements
 2GB RAM
 320 GB Hard Disk
 Dual Core processor

Page 7 o f 8
 [Project Management System] Requirements Specification

3.6 Security
3.6.1 Protection

 Password encryption.
 Activity logging, historical data sets.
 Restrictions on inter module communications.
 Data integrity checks.

Page 8 o f 8