Construction Worker Management System

SESSION (2019-21)

Submitted By

Name: Muhammad Shoaib ID: F2019346063

Supervised By

Mr. Gulfraz Naqvi

SCHOOL OF COMMERCE AND ACCOUNTANCY

UNIVERSITY OF MANAGEMENT & TECHNOLOGY, LAHORE
 Construction Worker Management System

A Report Submitted to the School of Commerce & Accountancy

In
Partial Fulfillment of the Requirements for the Associate Degree
In
Computer Science
By
Name: Muhammad Shoaib
ID: F2019346063

Internal Examiner

(Supervisor)

Gulfraz Naqvi ---------------------------------------

External Examiner

---------------------------------------

Director

Mr. Muhammad AzeemNaz

School of Commerce & Accountancy

University of Management & Technology
(UMT), Lahore ----------------------------------------

I
DEDICATION

DEDICATED TO MY RESPECTED PARENTS AND FAMILY WHOSE UTMOST LOVE , CARE AND

STRUGGLE AGAINST ALL ODDS BROUGHT ME TO THIS HEIGHT OF KNOWLEDGE AND ENCOURAGED

ME TO COMPLETE THIS DEGREE AND WERE MAJOR DRIVING FORCE BEHIND MY ALL EFFORTS

WITH THE BLESSINGS OF ALMIGHTY ALLAH

II
ACKNOWLEDGEMENT

I am thankful to ALMIGHTY ALLAH who gave me courage and passion and prayers of my
parents and teachers to achieve the goal that was necessary for the degree. Although it was not an
easy task, with the useful direction, kind supervision and co-operation of Mr. Gulfraz Naqvi, it
became easy for me to complete the research work. I am really grateful to my Project Supervisor
because of his profound interest and encouragement throughout the project work.

I would like to acknowledge Mr. Muhammad AzeemNaz Director, School of Commerce

Accountancy, UMT Lahore, for encouraging and providing me all the facilities throughout the
project.

Last but not least, I extend my sincere appreciativeness and thankfulness to my Family for their
incredible encouragement. Their love and support means a lot to me.

III
UNDERTAKING

Construction Worker Management System

SESSION (2019-21)
This project is submitted to the School of Commerce Accountancy, University of Management &
Technology Lahore, for the partial fulfillment of the requirement for Master Degree in
Information Technology.

Approved on: _________________

Submitted By: Muhammad Shoaib

Name: F2019346063

Gulfraz Naqvi

S.C.A
UMT, Lahore
Project Supervisor

SCHOOL OF COMMERCE AND ACCOUNTANCY

UNIVERSITY OF MANAGEMENT & TECHNOLOGY, LAHORE

IV
CONTENTS

DEDICATION..........................................................................................................................................II
ACKNOWLEDGEMENT......................................................................................................................III
UNDERTAKING....................................................................................................................................IV
1. INTRODUCTION.............................................................................................................................2
1.1 PROJECT OVERVIEW......................................................................................................................................2
1.1.1 Goals and Objectives............................................................................................................................2
1.1.2 Definitions and Acronyms....................................................................................................................2
2. SYSTEM REQUIREMENT SPECIFICATION.............................................................................4
2.1 FUNCTIONAL REQUIREMENTS........................................................................................................................4
2.1.1 ADMIN PANEL:..................................................................................................................................4
2.1.2 USER PANEL:.....................................................................................................................................4
2.2 NON-FUNCTIONAL REQUIREMENT.................................................................................................................5
2.2.1 PERFORMANCE.................................................................................................................................5
2.2.2 Safety/Security:....................................................................................................................................5
2.2.3 Software Quality Attributes:.................................................................................................................5
2.2.4 Usability:..............................................................................................................................................5
2.3 USE CASE MODELS........................................................................................................................................5
2.3.1 List of Actors........................................................................................................................................5
2.3.2 List of Use Cases..................................................................................................................................5
2.3.3 Use Case Diagram..............................................................................................................................11
3. SYSTEM DESIGN..........................................................................................................................13
3.1 SYSTEM ARCHITECTURE..............................................................................................................................13
3.2 CLASS DIAGRAM..........................................................................................................................................14
3.3 SEQUENCE DIAGRAM...................................................................................................................................14
3.3.1 Login/Register....................................................................................................................................15
3.3.2 Construction Actions..........................................................................................................................16
3.3.3 Logout.................................................................................................................................................17
3.4 ENTITY RELATIONSHIP DIAGRAM................................................................................................................18
4. IMPLEMENTATION.....................................................................................................................20
4.1 TOOLS........................................................................................................................................................20
4.1.1 Web Application.................................................................................................................................20
4.1.2 Database.............................................................................................................................................20
4.2 LANGUAGES............................................................................................................................................20
4.3 SNAPSHOTS OF FROND END.........................................................................................................................21
5. TESTING.........................................................................................................................................26
5.1 TEST CASES.................................................................................................................................................26
6. RESULTS/OUTPUT/STATISTICS...............................................................................................29
6.1 90% COMPLETION.......................................................................................................................................29
6.2 90% ACCURACY..........................................................................................................................................29
6.3 90% CORRECTNESS.....................................................................................................................................29
7. CONCLUSION AND SUMMARY.................................................................................................31
7.1 CONCLUSION AND SUMMARY............................................................................................................31
8. FUTURE WORK.............................................................................................................................33

9. REFERENCES................................................................................................................................35
 1
INTRODUCTION
1. INTRODUCTION

1.1 Project Overview

In this project, we will build a web-based application named as “Online Building Construction Services”.
In this project a user can view the availability of the technical employees such as Masson, Electrician, and
Carpenter etc.
On the availability of the person, the user can book that resource for his/her construction work. In the
booking process, the user will provide all the details about the working he/she is going to plan.
The main purpose of this project is to facilitate the end users to online book a technical person for his/her
construction work according to the end user convenience.

1.1.1 Goals and Objectives

The main purpose of this project is to facilitate the end users to online book a technical person for his/her
construction work according to the end user convenience.

1.1.2 Definitions and Acronyms

1.1.2.1 ERD (Entity relationship Diagram)

Graphical representations of entities and their relationships among each other
1.1.2.2 Sequence Diagram
An interaction diagram helpful while checking requirements and design. It is also called event
diagram
1.1.2.3 Architecture Design Document
Describes the layered architectural model for the system. It contains three layers data link layer,
application layer and business layer.
1.1.2.4 Class Diagram
Describes the whole system by showing classes, their attributes and relationship among objects.
The classes in a class diagram represent both the main objects and interactions in the applications
and the objects to be programmed.
1.1.2.5 Database Diagram
Describes a way to logically group the objects. It is used to show the detail of operation or
methods and relationships of data.
1.1.2.6 Interface Design
Shows the important features of the system. It is a GUI view of main software. It shows how our
program will seem to be.

1.1.2.7 Test Cases

Test cases are provided in detail. A test case is a set of conditions or variables under which a
tester will determine whether an application is functioning properly or not.
 2
SYSTEM REQUIREMENT SPECIFICATION
2. SYSTEM REQUIREMENT SPECIFICATION

2.1 Functional Requirements

2.1.1 ADMIN PANEL:
 Login:
There will be login portal through admin can login with id and password.
 View:
The admin can view all information about their services.
 Add:
The admin can add different information about their services and create profile for their
employees such as Masson, Electrician, carpenter etc.
The admin can also add all the information about their employees such as information
about the available dates, their per day cost /service charges etc.
 Delete:
The admin can delete all information about their services
 Edit:
The admin can all information about their services
 Assign Task:
The admin can see the booking information and assign that work to a particular
employee(s) of different services.
 Generate Receipt:
The admin can generate a voucher/expense report for the user. The admin can also
generate different reports like total completed projects, total cost of a project etc.
 Manage Expense:
The admin can manage the expenses.

2.1.2 USER PANEL:

 Login:
The user first visits the “Online Building Construction Services”.
 Search:
The user can search for a different services likes Masson, Electrician, carpenter etc.
 Registration:
The user must register himself/herself before booking any service. In the registration
process, the user must provide all the details like name, address, cell no, etc.
 Expense Report:
The user can see the appropriate expense report after booking the
appropriate service.
 Pay amount:
The user can download the service dues voucher. Pay the dues in the
specific bank.
 Upload paid voucher:
The user must upload the paid voucher on his/her account
 Logout:
The user can logout.
 2.2 Non-Functional Requirement
2.2.1 PERFORMANCE
The App will be interactive, and the delays involved must be less. So, in every action-response of
the system, App will be fast enough to provide information timely.
2.2.2 Safety/Security:
App will be fully secured, and Security of database and system is followed.
2.2.3 Software Quality Attributes:
To be meaningful, quality attribute requirements should be followed about how an application
should achieve a given need.
2.2.4 Usability:
The App will be easy to use and learn. Interface will be highly user friendly.

2.3 Use Case Models.

2.3.1 List of Actors
Admin: The owner or manager with access to dashboard.
User: Simply the clients who are going to avail the services.
Employee: One with profiles in services section. Simply the labour.

2.3.2 List of Use Cases

2.3.1.1 ADMIN PANEL:

Use Case Name Login

Use Case No. 1
Action 1, User will provide id and password.
2. Click or Login
Description With Login in the application, one can be able
to use the application.
Alternative Path N/A
Pre-Condition Unregistered user
Post Condition Login successfully
Exception Incorrect information / Broken link
Use Case Name View
Use Case No. 2
Action View Services details

Description Provide information of different services

Alternative Path N/A

Pre-Condition Registered user
Post Condition Services viewed successfully
Exception View unavailable

Use Case Name Add

Use Case No. 3
Action The admin can add services details

Description Provide information to be added

Alternative Path N/A

Pre-Condition Registered user
Post Condition Services information added successfully
Exception Services details add unsuccessful

Use Case Name Delete

Use Case No. 4
Action The admin can delete services details

Description Provide information to be deleted

Alternative Path N/A

Pre-Condition Registered user
Post Condition services information deleted successfully
Exception Delete unsuccessful
Use Case Name Edit
Use Case No. 5
Action The admin can edit services details

Description Provide information to be edited

Alternative Path N/A

Pre-Condition Registered user
Post Condition Edit successful
Exception Edit unsuccessful

Use Case Name Assign Task

Use Case No. 6
Action Assigned task of different services

Description The admin can see the booking information

and assign that work to a particular
employee(s) of different services
Alternative Path N/A
Pre-Condition View booking information
Post Condition Service assign successfully
Exception Service not assign

Use Case Name Generate Receipt

Use Case No. 7
Action The admin can generate a voucher/expense
report for the user.
Description The admin can also generate different reports
like total completed projects, total cost of a
project etc.

Alternative Path N/A

Pre-Condition Edited details
Post Condition Receipt generated successfully
Exception Receipt not generated

Use Case Name Generate Report

Use Case No. 8
Action The admin can generate different reports of
book services

Description Reports are generated for complete details

Alternative Path N/A

Pre-Condition Services is booked
Post Condition Reports generated successfully
Exception Reports not generated

Use Case Name Manage Expense

Use Case No. 9
Action The admin can manage the expenses.

Description Services expenses are managed by admin.

Alternative Path N/A

Pre-Condition Verified amount receipt
Post Condition Expenses managed successfully
Exception Expenses not managed

2.3.1.2 USER PANEL:

Use Case Name Login
Use Case No. 1
Action The user first visits the “Online Building
Construction Services Application”.

Description User logins the website

Alternative Path N/A

Pre-Condition Unregistered user
Post Condition Login successful
Exception Login unsuccessful

Use Case Name Search

Use Case No. 2
Action The user can search for a different services
likes Masson, Electrician, carpenter etc.

Description Listed and available services can be searched.

Alternative Path N/A

Pre-Condition User has logged in
Post Condition Search successful
Exception Search unsuccessful

Use Case Name Registration

Use Case No. 3
Action The user must register himself/herself before
booking any service. In the registration
process, the user must provide all the details
like name, address, cell no, etc.

Description The user registers himself in order to book any

service
Alternative Path N/A
Pre-Condition Login successful
Post Condition Registration successful
Exception Registration not done

Use Case Name Pay amount

Use Case No. 4
Action The user must download the voucher from his
account and pay the amount in specific bank,

Description The user pays service charges in bank through

payment voucher
Alternative Path N/A
Pre-Condition Registered user
Post Condition Amount paid successfully
Exception Amount not paid

Use Case Name Upload paid voucher

Use Case No. 5
Action The user must upload the paid voucher on
his/her account

Description After amount payment, voucher is uploaded on

the account.
Alternative Path N/A
Pre-Condition Payment made successfully
Post Condition Voucher uploaded
Exception Voucher not uploaded

Use Case Name Logout

Use Case No. 6
Action The user can logout

Description The user logs out after completion of all

processes
Alternative Path N/A
Pre-Condition View book service
Post Condition Logout successful
Exception The user doesn’t log out.

2.3.2 Use Case Diagram

SYSTEM DESIGN
School of Commerce and Accountancy (SCA) <Project Name>

3. SYSTEM DESIGN

3.1 System Architecture

13 | P a g e
School of Commerce and Accountancy (SCA) <Project Name>

3.2 Class Diagram

3.3 Sequence Diagram

An interaction diagram helpful while checking requirements and design. It is also called event
diagra

14 | P a g e
School of Commerce and Accountancy (SCA) <Project Name>

3.3.1 Login/Register

15 | P a g e
School of Commerce and Accountancy (SCA) <Project Name>

3.3.2 Construction Actions

16 | P a g e
School of Commerce and Accountancy (SCA) <Project Name>

3.3.3 Logout

17 | P a g e
School of Commerce and Accountancy (SCA) <Project Name>

3.4 Entity Relationship Diagram

18 | P a g e
 4
IMPLEMENTATION
School of Commerce and Accountancy(SCA) <Project Name>

4. IMPLEMENTATION

4.1 TOOLS
4.1.1 Web Application
 VISUAL STUDIO

Visual studio is vast tool and most of work is done on visual studio. I choose this tool
because it is full of functions and library. We can easily manage our project folders. All files
can easily be managed at same place.
4.1.2 Database
 SQL SERVER MANAGEMENT STUDIO 2014

We have used SQL server management studio for the implementation of our database. We
have selected this software because we have used it before. Another reason for its selection is
because it is very easy to use and understand, therefore any problems we face in our database
can easily be overcome.
.

4.2 LANGUAGES
 SQL

SQL stands for Structured Query Language. It is a domain-specific language used in programming and

designed for managing data held in a relational database management system (RDBMS), or for stream
processing in a relational data stream management system (RDSMS). We have used SQL
programming language in our database.
 HTML

HTML stands for Hypertext Markup Language. It is the set of markup symbols or codes inserted in a
file intended for display on a World Wide Web browser page. The markup tells the Web browser how
to display a Web page's words and images for the user. We have used HTML in our web application.
 CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a
document written in a markup language. We have used CSS in our web application.
 PHP

PHP is a server-side scripting language designed primarily for web development but also used as a
general-purpose programming language. We have used PHP for the connectivity of our web and
android application with our database.

20 | P a g e
School of Commerce and Accountancy(SCA) <Project Name>

4.3 Snapshots of Frond End

Form Title: Index page
Interface Id: UI –01
Description: This is the index page and main page of the website.
Snapshot:

Form Title: Signin Page

Interface Id: UI –02
Description: This is the sigin page of website where users and admin can signin to their
account.
Snapshot:

21 | P a g e
School of Commerce and Accountancy(SCA) <Project Name>

Form Title: Signup Page

Interface Id: UI –03
Description: This is the signup page where user can create their account and after the
admin verification the will be able to login.
Snapshot:

22 | P a g e
School of Commerce and Accountancy(SCA) <Project Name>

Form Title: Dashboard

Interface Id: UI –04
Description: This is the dashboard of web application and only admin access to this.
Admin can approve user and create services and profiles here.
Snapshot:

23 | P a g e
School of Commerce and Accountancy(SCA) <Project Name>

24 | P a g e
 5
TESTING
School of Commerce and Accountancy(SCA) <Project Name>

5. TESTING

5.1 Test Cases

Test Case ID 1
Description Admin Login

Steps/Actions
1. Open the “system”.
2. Click on Login
3. Enter valid Username and password against the Role
Expected Results “Activate the Dashboard”
Actual Results “activate the Dashboard”
Status Pass

Test Case ID 2
Description Signup

Steps/Actions
1. Open the “system”.
2. Click on Signup
3. Enter valid Username and password against the Role
Expected Results “User created”
Actual Results “User Created”
Status Pass

Test Case ID 3
Description Activating User

Steps/Actions
1. Open the “system”.
2. Click on Login and login as admin
3. Go to dashboard and activate the user by verifying it.
Expected Results “User Activated”
Actual Results “User Activated”
Status Pass
Test Case ID 4

26 | P a g e
School of Commerce and Accountancy(SCA) <Project Name>

Description Add services and laborers

Steps/Actions
1. Open the “system”.
2. Click on login and login as admin and go to dashboard.
3. Create services and add different laborers profile in
these services
Expected Results “Services added and profiles created”
Actual Results “Services added and profiles created”
Status Pass

Test Case ID 5
Description Book a services

Steps/Actions
1. Open the “system”.
2. Click on Login and login as user
3. Chooses the service and confirm the service.
Expected Results “Service booked”
Actual Results “Service Booked”
Status Pass

27 | P a g e
 6
RESULTS/OUTPUT/STATISTICS
School of Commerce and Accountancy(SCA) <Project Name>

6. RESULTS/OUTPUT/STATISTICS

6.1 90% Completion

All the tests have been performed and project is fully working and we can say that project has
been completed about 90 percent. We can add furthered things but I have mentioned that in the
future work section that will be implemented on them.

6.2 90% Accuracy

Total Number of Test Cases Passed Test Cases Failed Defects Found
Test Cases
5 5 0 0

6.3 90% Correctness

As we can see in the tests and the results of the tests. All the results are correct and according to
our assumptions. So we can say that project is totally correct with precision of 10 percent. That
will also be eliminated in the futer work as mentioned in future work section.

29 | P a g e
 7
CONCLUSION &SUMMARY
School of Commerce and Accountancy (SCA) <Project Name>

7. CONCLUSION AND SUMMARY

7.1 CONCLUSION AND SUMMARY

The project is built for purpose to register the profiles of the workers especially who works on
daily wages on the website so they can get the wage. It is very easy for the person to find a
worker to his work within seconds. The project is basically a online construction market for
construction workers and on the availability of the person, the user can book that resource for
his/her construction work. In the booking process, the user will provide all the details about the
working he/she is going to plan.
The main purpose of this project is to facilitate the end users to online book a technical person for
his/her construction work according to the end user convenience.

31 | P a g e
 8
FUTURE WORK
8. FUTURE WORK

As we can see in the accuracy and completion section the project is complete and almost
fulfills all the requirements. But nothing is complete and further work can be done on it.
In future at different dimensions some changes can be made and also some other
functionality can be added.
In future, we can register construction companies and also provide complete house
projects. We can also add the functionality to accept the payment online for those who
feel easy to pay online.
 9
REFERENCES
School of Commerce and Accountancy(SCA) <Project Name>

9. REFERENCES

1. https://www.w3schools.com/

2. https://www.youtube.com/watch?v=U7n0AlCsFoE

3. https://www.upgrad.com/blog/computer-science-project-ideas-topics-beginners/

35 | P a g e