Project Tracking System

1.0 Problem statement

PROJECT TRACKING SYSTEM gives the management clear picture of usage of time by
projects. By analyzing the results provided by the software they might rectify the defects in
utilizing time and take remedial actions.

PROJECT TRACKING SYSTEM takes timesheet reports as input.

PROJECT TRACKING SYSTEM gives the individual report of the project, which
contains time used for various tasks. In this tool CLIENT gives requirements to the BDO and
makes an agreement with him. The new project information is entered by the BDO, based on
the project information the PROJECT MANAGER will take resources from the HR and assign
activities to DEVELOPERS who are working under him. Employees fill the time sheet and
complete the task assigned to them. These completed tasks are tested and finally the project is
submitted to the client.

Scope of the System

This project should have five modules – Client, Bussiness development officer (BDO),
Developer, Human Resource Manager (HR), Project manager (PM).

Client deals with checking the status of the project by the client. Only the authenticated client
login to the web page and checks in which phase the project is.

BDO deals with collecting the requirements from the client and add the client details and project
details into the database and also views and updates the respective details.

Developer deals with filling the timesheets, updating and viewing the timesheets and also
checking the project status.

HR deals with providing resources to the project manager by checking the employee details like
skill and designation. HR can also view the status of the project.

PM deals with planning the project i.e. dividing the project into different tasks and assigning
those tasks to the developers. PM also checks the timesheets of developers, fills his timesheet,
updates and views the timesheet. PM can also check the status of the project.

The data dictionary is useful in case of development.

1
CLIENT

NAME DATA TYPE CONSTRAINTS DESCRIPTION

CID VARCHAR2 Primary Key
(20)
CNAME VARCHAR2
(40)
PNO NUMBER (30)
EMAIL VARCHAR2
(50)
POSITION VARCHAR2
(50)
OFFADD VARCHAR2
(80)
HOMEADD VARCHAR2
(80)
TYPEOFIND VARCHAR2
(50)
SCALE VARCHAR2
(20)
PERIOD NUMBER (20)

EMPLOYEE

NAME DATA TYPE CONSTRAI DESCRIPTI

NTS ON
EID VARCHAR2 PRIMARYK
(50) EY
ENAME VARCHAR2
(50)
SKILLSET VARCHAR2
(50)
DESIGNATION VARCHAR2(
50)
EXPERIENCE VARCHAR2(
50)
CTC NUMBER(20
)

2
PHNO VARCHAR2(
50)
EMAIL VARCHAR2(
50)

HR REQUIREMENTS

NAME DATA CONSTRAIN DESCRIPTIO

TYPE TS N
PID VARCHA
R2 (30)
SKILL VARCHA
R2 (30)
NOP_REQ NUMBER
(3)
SDATE VARCHA
R2 (30)
EDATE VARCHA
R2 (30)
REQ_ID VARCHA
R2 (30)

MODULE

NAME DATA TYPE CONSTRAINTS DESCRIPTION

MID VARCHAR2
(30)
MNAME VARCHAR2
(30)
NOP NUMBER (3)
NOTASKS NUMBER (3)
PID VARCHAR2
(50)
MDETAILS VARCHAR2
(80)

MODULE STATUS

3
NAME DATA CONSTRAIN DESCRIPTIO
TYPE TS N
DATE1 VARCHA
R2 (20)
TIME VARCHA
R2 (20)
MID VARCHA
R2 (30)
STATUS VARCHA
R2 (500)

PROJECT

NAME DATA TYPE CONSTRAI DESCRIPTI

NTS ON
PID VARCHAR2 Primary key
(50)
NOP NUMBER (5)

PTITLE VARCHAR2
(50)
CID VARCHAR2
(50)
SDATE VARCHAR2
(50)
EDATE VARCHAR2
(50)
COST NUMBER
(20)
ESYSTEM VARCHAR2
(50)
PSYSTEM VARCHAR2
(50)
ABSTRACT VARCHAR2(
50)
LOC VARCHAR2(
50)
TYPEOF_OS VARCHAR2(

4
 50)
TYPEOF_APPL VARCHAR2(
50)
PLATFORM VARCHAR2(
50)
SW_MODEL VARCHAR2(
50)
PM VARCHAR2(
50)

PROJECT ASSIGN

NAME DATA TYPE CONSTRAI DESCRIPTI

NTS ON
EID VARCHAR2(
30)
PID VARCHAR2
(30)
REPORT_DATE VARCHAR2
(30)
REPORT_MGR VARCHAR2(
30)
NAME DATA TYPE CONSTRAI DESCRIPTI
NTS ON
DATE1 VARCHAR2(
30)
TIME VARCHAR2(
30)
PID VARCHAR2(
30)
STATUS VARCHAR2(
500)

TASK

NAME DATA TYPE CONSTRAI DESCRIPTI

NTS ON
TID VARCHAR2

5
 (30)
TNAME VARCHAR2
(30)
MID VARCHAR2
(30)
NOP NUMBER
(3)
SDATE VARCHAR2
(30)
EDATE VARCHAR2
(30)
T_PARTICULARS VARCHAR2
(80)
DEPENDABILITY VARCHAR2
(50)
STIME VARCHAR2
(30)

TIME SHEET

NAME DATA CONSTRAIN DESCRIPTI

TYPE TS ON
TID VARCHA
R2 (30)
STATUS VARCHA
R2 (500)
S_TIME VARCHA
R2 (30)
E_TIME VARCHA
R 2(30)
S_DATE VARCHA
R2 (30)
E_DATE VARCHA
R 2(30)
CURR_DATE VARCHA
R2 (30)

6
TASK ASSIGN

NAME DATA TYPE CONSTRAINTS DESCRIPTION

TID VARCHAR2
(50)
EID VARCHAR2
(50)

TASK STATUS

NAME DATA CONSTRAINT DESCRIPTIO

TYPE S N
TID VARCHAR
2 (50)
DATE VARCHAR
2 (50)
TIME VARCHAR
2 (50)
STATUS VARCHAR
2 (50)

USER PASSWORD

NAME DATA TYPE CONSTRAINTS DESCRIPTION

UNAME VARCHAR2
(10)
PASSWORD VARCHAR2
(50)

2.0 Project Development Guidelines

The project to be developed based on the below design considerations

7
Backend  Use Rest APIs (Springboot Core WebAPI to develop the
Development services
 Use Java latest features
 Use ORM with database
 Use JWT for authentication in SpringBoot/WebApi. A Token
must be generated using JWT. Tokens must expire after a
definite time interval, and authorization must be handled
accordingly based on token expiry
 Implement security to allow/disallow CRUD operations
 Message input/output format should be in JSON (Read the
values from the property/input files, wherever applicable).
Input/output format can be designed as per the discretion of
the participant.
 Any error message or exception should be logged and
should be user-readable (not technical)
 Database connections and web service URLs should be
configurable
 Implement Unit Test Project for testing the API
 Follow Coding Standards
Frontend  Use Angular to develop the UI
Development  Implement Forms, databinding, validations
 Implement Routing and navigations
 Use JavaScript to enhance functionalities
 Implement External and Custom JavaScript files
 Implement Typescript for Functions, Operators.
 Any error message or exception should be logged and
should be user-readable (and not technical)
 Follow coding standards
 Follow Standard project structure