DETAILED REQUIREMENTS

SPECIFICATION

Project MONITORING
AND
CONTROL

Table of Contents

1. INTRODUCTION
1.1 Document purpose
1.2 Document conventions
1.3 Operating environment
1.4 Assumptions and Dependencies

2. FUNCTIONAL REQUIREMENTS
2.1 Administrator
2.2 Manager
2.3 Leader
2.4 Developer
2.5 Client
2.6 Quality Assurance team
3. OTHER SYSTEM FEATURES

1. INTRODUCTION
1.1 Document Purpose

PROJECT MONITORING AND CONTROL (PMC) describes software that lets an

enterprise manage user access to its network resources efficiently . PMC also describes
software that manages and monitors all of a company's assets and resources. The success or
the failure of the project depends heavily on the project management abilities of the project
manager. There are various factors that need to be taken into consideration while managing a
project and some of the crucial factors include scheduling, resource allocation, cost control,
quality control, risk management, etc. Besides that, larger projects will involve multiple
teams. Keeping track of each one's progress and performance will not be an easy task if it
has to be handled manually. Project monitoring and controlling software will help us
synchronize various aspects of the project in a matter of few clicks. The efforts required by
the project manager to coordinate various aspects of the project will be reduced considerably
when you use effective project monitoring software tools.

1.2 Document Convention

All requirements specified in this document are given following attributes:

ID: Used to uniquely identify the requirement and its category

Description: Describe the requirement itself.

Risk: Describes the risk or difficulty associated with the requirement as

follows:
High . This requirement will be difficult to implement for technical or other
reasons or is subject to change.
Medium . This requirement is stable and will be of average difficulty to
implement
Low. This requirement is stable and will be of low difficulty to implement.

Priority: Describes the priority weighting for the requirement as follows:

High Priority. All high priority requirements must be implemented an verified
as part of this project.
Medium Priority. Medium priority requirements should be included,
implemented and verified, or at the very least design of the system must take
these into account.
Low Priority. Low priority requirements are optional depending on resource
and time availability.

1.3 Operating Environment

Hardware Interface
Processor : 32 bit
Ram

: minimum 1 GB

Hard disk : minimum 40 GB.

Software Interface
FRONT END

: ASP .NET, C#

Operating system

: windows 98/XP

BACK END

: Microsoft sql.

1.4 Assumptions and Dependencies

Assumptions
1. This system is a web based project
2. User has an internet connection

Dependencies
We must have an internet connection

2. FUNCTIONAL REQUIREMENTS
2.1 Administrator
ID
Description
ADM_001 Log in to the system. If the user name and password is correct
administrator can log in to the system (the password and the login
name is stored in the database).
ADM_002 Administrator has possibility to change the password.
ADM_005 Administrator add the manager , leader , developer details
ADM_007 Administrator can edit, remove and update project managers,
leaders and developers details.
ADM_005 Administrator can add project

2.2 Manager

Priority Risk
1
2

ID
Description
MNG_001 Log in to the system. If the user name and password is correct
manager can log in to the system.
MNG_002 Manager has possibility to change the password.
MNG_003 Manager can view their project details .
Manager can build a team for their project
MNG_
MNG_004 Project managers can view all details about leaders and developers
MNG_005 Project managers divide the project into different modules. Each
module has an id
MNG_006 Project manager assigns these project modules to different project
leaders based on whether his/her is available or not.
MNG_007 Managers provide the time limit to complete the module to project
leaders. Project cannot complete at that time manager ask
explanation from project leaders
MNG_009 Manager can view the status about the project way of graphical
representation(project day to day developments)
MNG_012 Manager verify the modules day by day

Priority Risk
2
2
3
1

2
2

2.3. Leader
ID
Description
LDR_001 Log in to the system. If the user name and password is correct leader
can log in to the system.
LDR_002 Leader has possibility to change the password.
LDR_003 Leaders can view all (sent module, module details) the requests from
the manager.
LDR_004 Project leader can view all details about developers
LDR_005 Leaders divide the module into different sub-modules. Each sub
module has an id.
LDR_006 Leader assigns these sub-modules to different developers based on
whether he/she is available or not.
LDR_007 Leader provides the time limit to complete the module. Project
cannot complete at that time leader ask explanation from developer
LDR_008 If leader wants to change the time(module completion) he gets the
approval from the manager and do accordingly

Priority Risk
2
2
3
1

2
2

2
2

2
2

2.4 Developer
ID
Description
Priority Risk
DLR_001 Log in to the system. If the user name and password is correct leader 2
2
can log in to the system.
DLR_002 Leader has possibility to change the password.
3
2
DLR_003 Developers can view all (sent task, task details) the requests from the 1
leader.
DLR_004 In all modules have an completion time ,In case he/she cannot
1
complete the modules in that time they give explanation to the
project leaders
DLRDLR_005 Developers send the completed modules to QA
1

2.5 Client
ID
Description
CLT_001 Log in to the system. If the user name and password is correct client
can log in to the system.
CLT_002 Client has possibility to change the password.
CLT_003 The client gives the project (project name, date of completion,
description about the project) to administrator
CLT_004 Client can see the details about the company
CLT_005 The client can view status of the project.
CLT_007 The client can send feedback to the ADM about the project

2
2

Priority Risk
1
2
3
1

2
2

2
1
1

2
2
2

2.6 QA
ID

Description
Log in to the system. If the user name and password is correct
QA_001 QA can log in to the system.
QA_002 QA has possibility to change the password.

Priority Risk
1
2
3

QA_003

QA has receive the completed task from the developer

QA_004

QA update the task to leader after testing

QA_005

QA has receive the completed module from the leader

QA_006

QA update the module to leader after testing

QA_007

QA has receive the completed project from the manager

QA_008

QA update the project to manager after testing

Table Design

1.login
Attribute name
Login-id
username
Password
Type

Data type
Varchar(10)
Varchar(15)
Varchar(15)
Varchar(15)

Remarks
Store the login id of the user
Stores the name of the user.
Stores the password of the user.
Stores the type of the user.

2. Client_details

Attribute name

Data type

Remarks

Clnt_Name
Clnt _id
Clnt _Password
Clnt_login id

Varchar(10)
Varchar(5)
Varchar(10)
Varchar(10)

Store the name new member

Store the id of new member
Store the password of new member
Store the login id of the new member

Primary
contct_name
Secondary
contct_name

Varchar(10)

Store the primary contact name of the client

Varchar(10)

Store the secondary contact name of the client

Clnt _Date of join

Clnt _Email
Clnt _phone
Clnt _fax
Clnt_company
Clnt_status

Date
Varchar(10)
Integer(10)
Varchar(10)
Varchar(10)
Varchar(10)

Store the join date of new member

Store the Email address of new member
Store the phone of new member
Store the fax of new member
Store the compony name of the client
Store the approbation of the client

3.Employee_Details
Attribute name
Data type
Login_id
varchar(15)
User_id
varchar(15)
User _name
varchar(15)

Remarks
Stores the log in id of the Employee.
Stores the id of the Employee.
Stores the name of the Employee

Qualification
Address
Age
Email
Phone

Varchar(15)
varchar(50)
Integer
varchar(15)
integer

Stores the qualification of the Employee.

Stores the address of the Employee.
Stores the age of the Employee.
Stores the email id of the Employee.
Stores the phone number of the Employee.

User _status
User_role

varchar(15)
Varchar(10)

Stores the Employee present or not

Store the role of the employee

4.pro_details
Attribute name

Data type

Remarks

pro_name

varchar(15)

Stores the name of the project

pro_id

varchar(15)

Stores the id of the project

Client_id

varchar(15)

Stores the id of the Client

Pro_budget

Integer(10)

Store the project budget details

Employee_id

varchar(15)

Duration

varchar(15)

Stores the id of the employee who handles the

project
Stores the duration of the project

Date_of_started

Date/Time

Store the date of starting a project

Date_of_submission Date

Stores the date for the completion of the project

Description

varchar(50)

Stores the description of the project

Pro_status

Varchar(5)

Store the status of the project

Pro_ownership

Varchar(10)

Store the details of who is held on the project

Pro_size

Varchar(10)

Store the size of the project

Pro_scope

Varchar(10)

Store the description of the project

Pro_effort

int

Store the details about the effort of the project

Pro_QA

Varchar(10)

Store QA part about the project

Pro_reference

Varchar(10)

Store the reference details of documentation of the

project

5.Team Table

Data type

Attribute name
Team_Id
pro_id

varchar(15)
varchar(15)
varchar(15)
varchar(15)
varchar(15)
varchar(15)
varchar(15)

Manager Name
Developer
leader
Tester
Emp_id

Data type
Stores the id of the project
Stores Manager Name

Stores the value of employee.

6.Module
Attribute name
module_id
module_name
pro_id
manager
leader
Stating Date
Ending Date
Module_status
Module_assign
Completed_effort
Estimated_effort
Module_QA
Module_reference

Data type
varchar(15)
varchar(15)
varchar(15)
varchar(15)
varchar(15)
datetime
datetime

Varchar(15)
Varchar(15)
int
int
Varchar(10)
Varchar(10)

Reject_Description Varchar(10)

7. Task_details

Data type
Stores the id of the module.
Stores the name of the module.
Stores the id of the project.
Stores the id of the manager who handles the project.
Stores the id of the leader who handles the project.
Stores the starting date of the module completed.
Stores the ending of the module completed.
Store the status of the module.
Store who held on the module.
Store the size of the module.
Store the details about the effort of the module
Store QA part about the module
Store the reference details of documentation of the
Module.
Stores reason of rejection of task.

Attribute name
module_id
Task_id
Task_name
pro_id
leader
developer
Starting date
Ending Date
User_role
Phase
Task_status
Hour
Days
Priority
Estimated_Task_effort
CompletedTask__effort
Task_QA
Task_reference

Data type
varchar(15)
varchar(15)
varchar(15)
varchar(15)
varchar(15)
varchar(15)

Reject_Description

Varchar(10)

datetime
datetime

Varchar(15)
Varchar(15)
Varchar(15)
Varchar(10)
Varchar(10)
Varchar(10)
Varchar(10)
Varchar(10)
Varchar(10)
Varchar(10)

Remarks
Stores the id of the module
Stores the id of the task
Stores the name of the module
Stores the id of the project
Stores the id of the leader
Stores the id of the developer
Stores the starting date of the task completed
Stores the ending date of the task completed
Store which task assign to employee
Store which phase do a employee
Store the progress of the task
Store the hour of completed in a task
Store the days of completed in a task
Store the priority of a task
Store the details about the effort of the task
Store the size of the task
Store QA part about the task
Store the reference details of documentation of
the task
Stores reason of rejection of task.

8. Company_details(our company profile)

Attribute name

Data type

Remarks

Cmp_Name

Varchar(10)

Store the name of compony

Cmp_web

Varchar(10)

Store the web address of the company

Cmp_email

Varchar(10)

Store the email address of the company

Cmp_ph

Integer(10)

Store the phone number of the company

Cmp_details

Varchar(10)

Store the compony details (history) of the

compony

Num_pro

Integer(5)

Store the quantity of project

9.Cost_details
Attribute name

Data type

Remarks

Pro_id
Pro_Total amount
Pro_payed amount
Pro_balance amount
Status
Date

Varchar(10)
Integer(10)
Integer(10)
Integer(10)
Varchar(10)
Date

Store the id of project

Store the amount of the project
Store the payed amount of the project
Store the balance amount of the project
Store the amount fully paid or not
Store the date of the amount payed