Development of Web-Based

Field and Workshop Job Process

Management System
By

D.M. SHIRLEY PRIYANTHA

Registration Number: CODL/23DSE077

(July 2023 - November 2024)

This report is submitted in partial fulfilment of the requirement for the

Diploma in Software Engineering
Center for Open and Distance Learning
Sabaragamuwa University of Sri Lanka

Name of Lectures:
Dr. R.V.S.P.K Ranathunga
Mr. Sathuta Sellapperuma
Mr. Hasanka Wijesinghe
Mr. S.Nimishan
 Web Base Job Management System

Abstract
In today's world fast and dynamic work environments, managing jobs and tasks efficiently
is crucial for both field and workshop-based industries. The Web-Based Field and Workshop
Job Process Management System aims to streamline the job management process, ensuring
that tasks are assigned, tracked, and completed efficiently. This system provides an intuitive
web interface where administrators can create, assign, and monitor jobs, while field and
workshop workers can view their assigned tasks, update job statuses, and report completion

Built using HTML, CSS, PHP, MySQL, and JavaScript, the system allows for real-time data
processing and job status updates, ensuring seamless communication between field and
workshop staff. The application includes user roles such as administrators, employees and
customers, each with specific privileges and access controls.

This project offers a scalable solution for field and workshop environments, improving overall
operational efficiency and job accountability.

ii
 Web Base Job Management System

Table of Content

Abstract ........................................................................................................................ii
Table of Content ......................................................................................................... vii
List of Figures ............................................................................................................ vii
Acknowledgements ................................................................................................... iiii
Chapter 1 – Introduction ............................................................................................... 1
1.1 Motivation for the project ................................................................................... 1
1.2 Objectives and scope of the project ..................................................................... 1
1.2.1 Objectives .................................................................................................... 1
1.2.2 Scope of the project ...................................................................................... 2
Chapter 2 – System Analysis .................................................................................... 4
2.1 Introduction......................................................................................................... 4
2.2 Existing system ................................................................................................... 4
2.3 Problems in the existing system .......................................................................... 4
2.4 Proposed Solutions ......................................................................................... 5
2.5 Requirments Gathering........................................................................................ 5
2.5.1 Stakeholder Identification ............................................................................ 6
2.5.2 Current System and Worklow Analysis ........................................................ 6
2.6 Functional requirements ....................................................................................... 6
2.6.1 User Authonitication ..................................................................................... 7
2.6.2 Job schedule and Job Update ........................................................................ 7
2.6.3 Job Tracking................................................................................................. 8
2.6.3.1 DFD Level-0 diagram for job tracking................................................... 8
2.6.4 Job History and Reporting ............................................................................ 8
2.6.5 Notification ................................................................................................... 8
2.7 Non-functional requirements.............................................................................. 9
2.7.1 Performance ................................................................................................. 9
2.7.2 Security and Safeguard ................................................................................. 9
2.7.3 Userbility ..................................................................................................... 9
2.7.4 Availability .................................................................................................. 9
2.7.5 Platform Independence ................................................................................. 9

iii
 Web Base Job Management System

2.8 System Feasibility ................................................................................................

2.4.1 Economic Feasibility ..................................................................................
2.4.2 Technical Feasibility ..................................................................................
2.4.3 Behavioral Feasibility.................................................................................
2.9 Selected Process Model ........................................................................................
2.9.1 Requirment Gathering and Planning ...........................................................
2.9.2 Requirment Analysis ..................................................................................
2.9.3 System Design ...........................................................................................
2.9.4 Developement ............................................................................................
2.9.5 Testing .......................................................................................................
2.9.6 Deployement & Mainternance ....................................................................
2.10 Logical Design Diagram.....................................................................................
Chapter 03 – Design ....................................................................................................
3.1 Introduction ........................................................................................................
3.2 Alternative solutions evaluation ..........................................................................
3.3 Selected Solutions ..............................................................................................
3.4 Selected Solutions ..............................................................................................
3.5 Prototype Design ................................................................................................
3.6 Relational Schema Design ..................................................................................
3.7 Database Structure..............................................................................................
3.8 Table Structure ...................................................................................................
3.9 Sample Data with table.......................................................................................
3.10 User Interface Design ................................................................................... 21
3.11 User Interface Standard ................................................................................ 23
Chapter 04- Implementation ................................................................................... 26
4.1.Development Enviroment ............................................................................... 26
4.2.Hardware and Software Requirment ............................................................... 26
4.3.Client / Server Enviroment ............................................................................. 27
4.4.Development Tools ........................................................................................ 28
4.4.1.VS Code/ Sublime Text ........................................................................... 28
4.4.2.Wamp Server ........................................................................................... 28
4.4.3.Draw.IO .................................................................................................. 28

iv
 Web Base Job Management System

4.5.Third party code ................................................................................................ 28

4.6.UI/UX design & implimentation ....................................................................... 29
Chapter 05 – Evaluation ............................................................................................. 31
5.1 Technique of Testing…………………………………………………………….31
5.2 Test Plan for proposed system……………………………………..…………….31
5.2.1.Function Testing ....................................................................................... 32
5.2.2.Non Function Testing ................................................................................ 32
5.3 .Test case .......................................................................................................... 33
5.4 .Add new Staff .................................................................................................. 34
5.5 User evaluation ................................................................................................. 34

Chapter 06 – Deployment ........................................................................................... 36

6.1 Key consideration ......................................................................................... 36
6.1.1 connectionpage ........................................................................................... 36
6.1.2 Domain register.......................................................................................... 37
6.1.3 Domain Hosting and File manager ............................................................. 38
Chapter 07 – Conclution ............................................................................................. 31
7.1 Encountered problems and lessons learnt ...................................................... 39
7.2 Future developments..................................................................................... 40

List of Figures
Figure 2.1: Use case for old manual system ................................................................... 6

Figure 2.6.1: Flow Chart of Login System...................................................................... 7

Figure 2.6.2: Job schedule context diagram.................................................................... 7

Figure 2.6.3: DFD Level-0 diagram for job tracking...................................................... 8

Figure 2.10.1: ER Diagram for entire system...............................................................12

v
 Web Base Job Management System

Figure 3.4.1: Use case diagram for entire system ..........................................................14

Figure 3.5.1: Prototype design of the customer login.....................................................15

Figure 3.5.2: Prototype design of the admin login.........................................................16

Figure 3.5.3: Prototype design of the technician login...................................................16

Figure 3.6.1: Relational Schema Diagram……..............................................................17

Figure 3.7.1: phpMyAdmin Database diagram...............................................................18

Figure 3.8.1: Database with Table structure and Screenshot..........................................18

Figure 3.8.2: Physical table screenshot for fieldjob........................................................19

Figure 3.9.1: Sample data with field job data.................................................................20

Figure 3.9.2: Sample data with user table ..................................................................... 21

Figure 3.10.1: Home page……………….. ................................................................... 22

Figure 3.10.2: Admin Homepage ………….................................................................. 23

Figure 3.11.1: Record adding page ………................................................................... 24

Figure 3.11.2: Data table………… ………................................................................... 24

Figure 3.11.3: User validation…… ………................................................................... 25

Figure 4.3.1: Server side minimum requirment.............................................................. 27

vi
 Web Base Job Management System

Acknowledgement
I would like to express my gratitude to our supervisors and lectures at the University of
Sabaragamuwa, for their guidance and provision of all the relevant technical knowledge.
Without their encouragement, support, advice, and guidance throughout the project, it would
have been extremely difficult to complete it successfully.

Furthermore, I extend my sincere appreciation to the coordinators and staff for the University
of Sabaragamuwa Center for Open and Distance Learning (CODL) for providing us with the
wonderful opportunity to pursue the Diploma in Software Engineering course. This program
has greatly aided in developing our careers and enhancing our experience in programming
development. Thank you for this invaluable opportunity.

Finally, I take this opportunity to express my gratitude to my family, friends, colleagues and
all the people those who help me directly and indirectly to successfully complete this project.

vii
 TechManagePro System.

Chapter 1 – Introduction

The aim of JPMS project is to develop a web-based system to enables field & workshop
ITC operations be more effective by simplifying job scheduling and streamlining
operations of Mylogic Technical Services. This system will address the challenges of
schedule daily field & workshop jobs, tracking job status, client portal for directly submit
their work request instead of manual call method. Maintaining good communication
between clients, management, field and workshop engineers. This is all-in-one platform
for job management, scheduling, planned maintenance, invoicing, quoting, automated
client communications, reporting and more. The proposed system will improve efficiency,
reduce errors, and enhance overall productivity.

1.1 Motivation for the project

In many field and workshop environments, job management is traditionally handled
through manual paper-based systems and phone calls, which come with significant
drawbacks. These methods are not only time-consuming but also prone to errors,
miscommunication, and delays. Paperwork can be easily misplaced or damaged, and
tracking the progress of multiple jobs simultaneously becomes challenging without a
centralized system.

1.2 Objectives and scope of the project

1.2.1 Objectives
• Create work orders with detailed information, assign technicians, and schedule
dates.
• Track job progress in real-time with updates from field technicians, including
location.
• Generate reports on job completion times, resource allocation, and identify areas
for
improvement.
• Facilitate communication between field and workshop, enables people to share
ideas, feedback.
• Securely store and share documents related to jobs, such as work instructions,
schematics and safety manuals.

1
 TechManagePro System.

• All day-to-day operations from the palm of your hand.

• customer satisfaction and engagement by providing self-service options for
accessing web base solution.

1.2.2 Scope of the project

This Web-Based Job Process Management System Include user role management
(Admin, Manager, Technician, Customer) with permissions for job creation and
tracking. Also Provide job management functionalities such as job creation, assignment,
and completion tracking. A responsive web interface optimized for use on mobile
devices.

 System perspective

o Administration level login

 System administrator or company administrative

user can manage user roles. accounts who are
member of this system.
 They can define access groups with the internal
stakeholders and also access rights can be manage
within the system.
 Admin who is maintain the company website can
be able to change website main banners and details
of the company like location, description of the
company, etc.

o Employee level login

 manager- role
 Access of main dashboard menu
 System allows to add, edit, delete, view users like,
• Technician.
• Client registration.
 System allows to add, edit, delete, jobs like,
• Field jobs.
• Workshop jobs.

2
 TechManagePro System.

 technician- role
 Access of sub dashboard menu
 System allows to view, update, delete, jobs like,
• Field jobs.
• Workshop jobs.
• Close completed job

 Website perspective
Customers level login
 System does not allow customers to register with
the system by their own.
 Customer can login to dashboard after registration
done by manager.
 Registered customers can manage only their user
accounts.
 System allows to add, view, jobs like,
• Field jobs.
• Workshop jobs.

3
 TechManagePro System.

Chapter 2 – System Analysis

2.1 Introduction
Requirements analysis, also called requirements engineering, is the process of
determining user expectations for a new or modified product. These features, called
requirements, must be quantifiable, relevant and detailed.

2.2 Existing system

MYLOGIC current job process management for field and workshop operations often
relies on manual methods such as paper forms, emails, and phone calls. This leads to
several challenges

2.3 Problems in the existing system

•
Difficulty tracking job status,
•
Delays in communication,
•
and manual data entry waste valuable time.
•
Limited visibility into the overall job progress both client and the management.
•
Manual data entry is prone to errors, impacting project planning and resource
allocation.
•
Communication gaps between field and workshop, lack of trust among team
members.
•
Also, many human mistakes can be happened on manual system.

4
 TechManagePro System.

Use case of the old system can be shown in the following Figure 2.1

Figure 2.1: Use case for old manual system

2.4 Propose Solutions

In order to overcome almost all the issues in the existing system ‘built on a secure cloud-
based platform has become the best solution. That can be accessed anywhere. So,
TechManagePro” solutions help keep job schedule and track, boost team’s productivity
and customer interaction, make smarter business decisions quicker.

2.5 Requirements Gathering:

As the goal of the application is ease of use and to provide an interactive interface,
extensive research has been done to gain an insight into the needs and behaviors of various
users

5
 TechManagePro System.

2.5.1. Stakeholder Identification

 Key Stakeholders: Identify everyone who has an interest in the system. This
includes:
o Users: The individuals or groups who will interact with the system (e.g.,
job coordinators, technicians, managers).
o Customers: The clients who request job services or follow up on job
progress.
o System Administrators: Those responsible for maintaining the system.
o Management: The decision-makers who will evaluate the system’s
performance.

2.5.2. Current System and Workflow Analysis

 Existing Processes: Gather information about how the current (manual) job
management process works. Focus on:

o Job Scheduling: How jobs are currently assigned and tracked.

o Communication: How stakeholders (technicians, customers, managers)
communicate about job statuses.
o Documentation: How job records are kept (manual paperwork,
spreadsheets, etc.).
o Job Completion: How the organization tracks progress and closes jobs.

 Pain Points: Identify the inefficiencies and challenges with the current system,
such as:
o Slow or inefficient job assignment.
o Delays in communication.
o Lack of real-time updates or status tracking.
o Issues with storing and retrieving job data (e.g., lost paper work).

2.6 Functional requirements

Functional requirements of a system explain the ‘what system must do’. It simply means
the functionalities and services of the system and its components.

6
 TechManagePro System.

2.6.1 User Authentication

• Verifying identity of users.
• The system must allow users (e.g., admin, manager, technician, customer)
to log in and log out securely.

Figure 2.6.1: Flowchart for login system

2.6.2 Fault reporting, Job schedule and Job update

• The system support fault reporting by customer login.

• The system should enable the creation of new job requests by the admin
or manager.

• Managers should be able to assign jobs to technicians

Figure 2.6.2: Context diagram for fault reporting, job schedule and update

7
 TechManagePro System.

2.6.3 Job Tracking

 The system should allow users to track the status of a job (e.g., pending,
in-progress, completed)

Figure 2.6.3: DFD Level-0 diagram for jobs tracking

2.6.4 Job History and Reporting

• The system must store job history, allowing users to search and filter
completed jobs.
2.6.5 Notification System

 The system should send notifications to technicians when a new job is

assigned.
 Admins and managers should be notified when jobs are completed or
delayed.

8
 TechManagePro System.

2.7 Non-functional requirements

Non-functional requirements of a system simply mean ‘what are the properties of the
system’ and how the system perform which explain the time constraints, security and
safe guard constraints.

2.7.1. Performance
Performance is mainly concern with the response time of the system after a
transaction or any user task which is perform within the system.

2.7.2 Security and safe guard

System consists of user personal data, transaction details and other financial
details. Therefore, the security and the safe guard of the system is really
important.

2.7.3. Usability
Usability can be concern with the ease of use and easy to learn the system.

2.7.4. Availability
System should be available for the use whenever the user wants to access the
system.

2.7.5 Platform independence

System should be work on any operating system while it can be access on the any
of web browser.

9
 TechManagePro System.

2.8 System Feasibility

The system feasibility can be divided into the following sections:

2.8.1 Economic Feasibility

Costs:

 Development costs: Includes hiring developers (if necessary), purchasing

software licenses, and any costs related to using cloud services (e.g., hosting,
databases, storage).
 Hardware costs: Costs for servers or cloud infrastructure, if applicable.
 Operational costs: Maintenance costs, future updates, and support.

2.8.2 Technical Feasibility

Technology Availability:

 Web technologies: The project requires tools like HTML, CSS, JavaScript, PHP,
MySQL, and web hosting services. These are well-established technologies,
making the system technically feasible.
 Infrastructure: A web-based system can be hosted on cloud platforms offering
flexibility and scalability. Hosting platform can handle the anticipated load and
data storage needs.

2.8.3 Behavioral Feasibility

User Adaptability:

 Ease of Use: The system has an intuitive user interface (UI) so that employees
can easily learn and adapt to the new system without significant resistance.

2.9 Selected process model

Process model is the development approach which split the whole system developments
process in to specific stages. As the requirement from the client is stable agile
methodology used as the process model. Scrum framework used to implement Agile
principles

10
 TechManagePro System.

2.9.1 Requirement gathering & Planning

Planning is the first phase of the agile software development lifecycle. During this
phase, the project team and stakeholders work together to define the project scope,
identify requirements, and prioritize features. Planning is critical as it sets the
foundation for the entire project, ensuring everyone is aligned and working towards
the same goals.

2.9.2 Requirement Analysis

The project team thoroughly analyzes the requirements and user stories during the
analysis phase. This phase is vital as it allows the team to identify potential roadblocks
and challenges that may arise during the development process. The team must also
work together to define the acceptance criteria and determine how the project will be
tracked and reported.

2.9.3 System Design

The design phase involves creating the project's architecture, interface, and database
design. The design phase is critical to the project's success, as it sets the foundation
for the development phase. During this phase, the team must ensure that the design
meets the project requirements, is scalable, and can be implemented within the project
timeline.

2.9.4 Development

The development phase involves the actual coding and implementation of the software.
The team must work together to develop and test the code, ensuring it meets the
acceptance criteria defined in the analysis phase. This phase requires continuous
collaboration between developers and the project team to ensure the project is
progressing according to plan.

11
 TechManagePro System.

2.9.5 Testing
During the testing phase, the project team tests the software to ensure it meets the
acceptance criteria and is bug-free. The testing phase involves unit testing, integration
testing, and system testing. The team must also work together to resolve bugs and
issues identified during testing.

2.9.6 Deployment & Maintenance

The deployment phase involves releasing the software to the end users. The team
must work to ensure the software is installed correctly and configured and provide
end-users training to ensure they can effectively use the software.

2.10 Logical Diagrams

After carefully analyzing the requirements and functionality of the web application,
I had two important diagrams by the end of the analysis phase. They are the ER
diagram and data flow diagram which were the basis for finding out entities and
relationships between them, the flow of information.

Figure 2.10.1: ER Diagram for entire system

12
 TechManagePro System.

Chapter 03 – Design
3.1 Introduction

Systems design is the process of defining the architecture, components, modules,

interfaces, and data for a system to satisfy specified requirements. There are multiple
approaches for system designing.

system design will follow an iterative, flexible approach while adhering to the structure
of Scrum. The key is that the system design evolves over multiple Sprints as the team
iterates on the product

3.2 Alternative solutions evaluation

Standalone system may be inconvenient for users as the system cannot be accessed at
any place as it has to be installed to the computer before it is being used. Clients mainly
requested for a web-based system as it will be very convenient for them as they can use
the system at any place even when they are at home or office or out of region.

3.3 Selected solution description and justification

The client is more concern about carrying out their own business processes rather than
adopting to a standalone system. Therefore, alternatives option has been discarded as
they do not fulfill client’s requirement. Client interest is with a web based software
solution, not a standalone applications.

In order to fulfill the client’s expectations, proposed web based software solution was
implemented and operational data stored in a central database where whole business
functionalities can be manage from a one system.

13
 TechManagePro System.

3.4 Use case diagrams

Use case diagrams symbolize the user interaction with the system while addressing the
functional requirements of the system. It is a representation of a user’s interaction with
the system that shows the relationship between the users. It contains use cases, actors,
their relationship, and system boundary. In the JobManagePro web System there are 3
main actors of the system named admin, technician and customer. The use case shows
function of the system, actor is a person or system that interact with the central system.
There are different type of relationship among use cases and actors such as association,
generalization, include and extend. The system boundary represents scope of the system
by rectangle around the use cases.

The Figure 3.4.1 shows use case diagrams of the system.

Figure 3.4.1: Use Case Diagram for the System

14
 TechManagePro System.

3.5 Prototype Design

Designing dynamic website involves several key elements to ensure a user-friendly and
visually appealing experience. It is an interaction diagram which shows how separate
objects operate with each other in what order is called Phototype diagram. In another
word it can be called as flow of object in order in the system. It shows the object
arrangement in a time sequence. Following Figure 3.2 show the phototype diagram of
the developed system between the objects customer, admin and technician.

Customer Login Dashboard

Figure 3.5.1: Prototype Design of the Customer Login system

15
 TechManagePro System.

Admin Login Dashboard

Figure 3.5.2: Prototype Design of the Admin Login system

Technician Login Dashboard

Figure 3.5.3: Prototype Design of the Technician Login system

16
 TechManagePro System.

3.6 Relational Schema Diagram

A relational schema is a blueprint for a relational database, detailing how data is
organized and related across tables. It is derived from the Entity-Relationship (ER)
diagram and outlines the structure of each table, including columns, data types, and
constraints, and shows how tables are related to each other through foreign keys.

Figure 3.6.1: Relational Schema Diagram for the System.

3.7 Database structure and screenshot

The database structure refers to the organization of data in a database, defining how
data is stored, accessed, and related within the database. A well-designed database
structure ensures data integrity, efficiency, and scalability, and includes the following
key elements:

17
 TechManagePro System.

Figure 3.7.1: phpMyAdmin Database Diagram for the System

3.8 Table structure and screenshot

The following Table 3.8.2, Table 3.8.3, Table 3.7.4 shows the table structure of the All
Tables and field_job, shows relevant physical table screenshot of the TechManagePro
database. All the other tables using in the system are same as follow structure.

Figure 3.8.1: phpMyAdmin Database with Tables Structure for the System

18
 TechManagePro System.

E – Entity R – Reference D - Derive

Attribute Description Data Type Length Key Type

FIELDJOB_ID FIELDJOB_ID INTEGER PK E

JOB_ID JOB_ID INTEGER FK R

REQUIRMENTS REQUIRMENTS VARCHAR 200 E

TECHNICIAN_ID TECHNICIAN_ID INTEGER FK R

START_DATE START_DATE DATE E

END_DATE END_DATE DATE E

Table 3.8.2: Table structure for field job table

Table 3.8.3: Physical table screenshot for field job table

19
 TechManagePro System.

3.9 Sample Data with Table

Data tables are a means of arranging data into an information format. Since data are often
viewed as the lowest level of abstraction from which information and then knowledge
are derived (ref. Wikipedia, Data), it is usually a collection of numbers, words, figures,
etc. that result from data collection activities. When data is processed and arranged in
such a way that satisfies certain queries, it is known as information. The basic Idea of
arranging data into information format is the field and record concept. A record
consisting of several fields gives information about a specific Item. Fields are attributes
of the subject item of the record. Data tables are collection of records arranged as rows
of the table while columns of the table represent the fields of these records.

The following Table 3.9.1, Table 3.9.2 shows the table structure of the field job and the
user tables. All the other tables using in the system are same as follow structure.

Table 3.9.1: Sample data with field job table

20
 TechManagePro System.

Table 3.9.2: Sample data with user table

3.10 User Interface Design

User interface is the front-end application view to which user interacts in order to use the
software. User can manipulate and control the software as well as hardware by means of
user interface. Today, user interface is found at almost every place where digital
technology exists, right from computers, mobile phones, cars, music players, airplanes,
ships etc. User interface is part of software and is designed such a way that it is expected
to provide the user insight of the software. UI provides fundamental platform for human
computer interaction. UI can be graphical, text-based, audio-video based, depending
upon the underlying hardware and software combination. UI can be hardware or software
or a combination of both.

User interface should be,

21
 TechManagePro System.

• Ease of use
• Attractive
• Ease of understanding
• Quick response time
• Easy to navigate

Home Page – Website

Online system mainly consists of 2 modules which is admin system and the website.
Following Figure 3.10.1 shows the home page of the website which can be access locally
by the URL http://localhost/jpms But after it is hosted it can access by the URL
http://techmanagepro.atwebpages.com Home page and the whole website is developed
with very simple UI and professional look and feel. User can easily navigate through the
website. That is shown in the following Figure 3.10.1

Table 3.10.1: home page

Home Page – System (Admin panel)

System home page can be accessed by the URL http://techmanagepro.atwebpages.com

only after login in to the admin panel. From the above URL it directs to the login page
and if the credentials are correct then the system (admin panel) is run in a separate popup
window. That can be find in the Figure 3.10.2.

22
 TechManagePro System.

Figure 3.10.2: Admin Home Page

system
3.11 User interface standard
Front end development or UI development was done by the HTML and CSS used as the
style sheet language. Bootstrap is used as a front end framework which has built with
HTML and CSS. Client side scripting language is java script that is implement in this
project.

Input Forms

Mainly input forms contains input fields and tool bar with buttons. Data entered to input
fields by text fields, drop downs, check box etc., Fields and buttons are disable or enable
with respect to the CRUD operations. Following are some example for input data forms.

1. Following Figure 3.11.1 shows the item add screen which provide the facility to
add images to the adding item and also other input fields for general details.

23
 TechManagePro System.

Figure 3.11.1: Record Adding Form

Page system

Data Tables
Data tables use to show the saved data in the database and also use to store data temporary
before submit into the database. PHP query is used to create tables which has several
features. Figure 3.11.4 shows the component of the data table.

Figure 3.11.2: Data table

24
 TechManagePro System.

Validation

Validation of a system is an important factor and TechManagePro Online System

validated 100% to ensure the authorization and authentication. In terms of input field
validation, following Figure 3.11.3 shows an example. Error is indicate top of the field
and the error is also display in red color. Any of data forms cannot be submit if those
errors message are shows in the screen.

Figure 3.11.3: Validation

25
 TechManagePro System.

Chapter 04 – Implementation
Transform the design into actual code. Implementation is the longest and most time
consuming phase in software development life cycle. Successful design phase prior to
implementation phase always make the way to success the development phase. All of
the works are divided into models. Each model transfer into system by using code, this
is the main task of the programmers.

This chapter is mainly focus on the implementation details of the developed system. In
addition to that, this section will describe the hardware/software environment,
development tools as well as model/code structure and reusable code.

4.1 Development environment

Hypertext Preprocessor 8.0 edition (PHP) is selected as the major programming language
to implement this Red Rooster Online Shopping System as it is a web-based project. PHP
is an open-source, server-side programming language that can be used to create websites,
applications, customer relationship management systems and more. This whole system
is run on a multi-tier architecture and following Figure 4.1 shows the overview diagram.

HTML, CSS and JavaScript are used for the presentation layer in the client's browser
used as the presentation layer. MySQL used as the database management system for the
Online System.

4.2 Hardware and software requirements

Selecting correct and compatible versions of software and hardware is really important
when developing a system.

Hardware requirements

• Personal computer or a laptop Dual Core CPU or above.

• Memory: minimum 4GB RAM or above.
• Internal hard disk: 500GB or above.
• The Internet connection can be established using ADSL, Fiber, or a dongle.
• Keyboard and mouse.

26
 TechManagePro System.

Software Requirement

• WAMP Server 3.3.2

• Code editing: Visual Studio Code & Sublime Text
• Database: MySQL server 8.0
• Graphical designing: Adobe Photoshop, Paint, Ice cream Photo editor
• Web browser: Any modern Web browser, Chrome or Firefox latest versions are
recommended

4.3 Client / server environment

Same as selecting the development system requirements, selecting the client and server
environment is important. Following tables at Table 4.3.1 and Table 4.3.2 are the
minimum hardware and software requirements needed.

Server-side Environment
Hardware Requirement Software Requirement

Multi-core Processors MYSQL

50GB hard disk space Apache Web Server

4GB RAM PHP

Personal computer with Dual Core CPU 64 bit Operating System

Table 4.3.1.: Server-side minimum requirements

Client-side Environment
Hardware Requirement Software Requirement

A modern multi-core processor Plugin or Runtime Environments: Adobe

Flash, Java, or specific browser
extensions may be required.
Storage 5-10 MB: for Cookies, Web Office productivity suites
Storage
2GB RAM or Above Latest Web browser (ex: Chrome,
Firefox)
Table 4.3.2: Client-side minimum requirement

27
 TechManagePro System.

4.4 Development tools

Development tools are used in the process of implementation of the system to accelerate
processes. Other than developing tools, additional third-party tools were used for several
purposes.

4.4.1 Visual Studio Code (VS Code)

• Language Support: Extensive support for various programming languages.
• Features: Lightweight, customizable, integrated terminal, debugging support,
extensions.

4.4.2 Wampserver
 Purpose: WampServer is a software stack used for local web development.
 Components:
 Apache: A web server that serves web pages.
 MySQL: A relational database management system.
 PHP: A server-side scripting language for web development.
 Features:
 Provides a local development environment for testing and building web
applications.
 Simplifies the setup of a web server, database server, and PHP on a local
machine.
 Ideal for developers working on PHP-based web applications and
websites.
4.4.3 Draw.IO
Diagrams.net (previously draw.io) is a cross-platform graph drawing software developed
in HTML5 and JavaScript. Its interface can be used to create diagrams such as
flowcharts, wireframes, UML diagrams, organizational charts, and network diagrams.
diagrams.net is available as an online web app, and as an offline desktop application for
Linux, macOS, and Windows.

4.5 Third party codes used in the system

Main target of a developing a software solution is to maximize the user friendliness file
achieving the functional requirements. To increase the performance and the user
friendliness, several existing codes were reused. Those third party libraries may be
JavaScript.

28
 TechManagePro System.

Bootstrap

This structure suggests a collapsible navigation menu with a main category ("user
Management") and sub-options ("Add jobs" and "View jobs") under that category. The
Bootstrap classes (data-bs-toggle, collapse, etc.) indicate the use of the Bootstrap
framework for styling and interactive features. Sample bootstrap class shown in the
Figure 4.1

Figure 4.4.3: Admin-menu using Boostarp Framework

4.6 The UI/UX Design & Implementation

In the context of software development and project management, the topics of User
Interface (UI) and User Experience (UX) are typically addressed during the design and
development phases of the Software Development Life Cycle (SDLC). These concepts
are integral to creating software that is user-friendly, visually appealing, and provides a
positive overall experience for users. The user interface of the application has been
designed using Figma.

 UI developers work on implementing the visual elements and interactions

according to the design specifications.
 Attention is given to ensuring that the user interface is responsive, works across
different devices, and aligns with the intended user experience.

29
 TechManagePro System.

View jobs

The user can see the list of jobs that assigned. Following Figure 4.4.3 shows an example.

Figure 4.4.4: View jobs Page

30
 TechManagePro System.

Chapter 05 – Evaluation
The main objective of this project is providing a useful software systems which helps
client to do their work easily and with much efficient.

Evaluation phase is the process in software development cycle as it ensures that the
product which is actually implemented matches with the requirements. Verification and
validation is done during this phase to assure that the system meets its initial objectives,
and testing should be planned at the very beginning of the project and carry out parallel
with the development process.

5.1 Techniques of testing

A proper system testing should be carried out for evaluating the system to see its
compatibility as a solution for the problem domain. Testing strategies may vary from
product to another as software can fail in different ways unlike a physical product. It will
lead the software to a poor quality state unless the testing is not done properly.
Following Figure 5.1 shows the overview abstract idea of the testing.

Figure 5.1: Functional and non-functional testing overview diagram. [7]

5.2 Test Plan for Proposed System

Testing plan of the system according to functional and non- functional testing are listed
in the following sections.

31
 TechManagePro System.

5.2.1 Functional Testing

Functional testing of a developed system can be categorized into 4 major types as shown
in the above Figure 5.1.

Unit Testing

Unit testing is very important as it can be used to find out errors within a module of a
software. Each individual unit of user interfaces, classes should be tested for assuring
their proper individual functionality.

Integration Testing

This testing is usually done with a combination of automated functional tests and manual
testing. During integration testing it will check that the units tested in isolation works
properly when they are put together.

System Testing

System as a whole should perform well concerning with all interdependencies. During
System Testing it checks whether system works correctly when real clients typically use
it. It will also checks how the system will perform if the system undergoes any extreme
condition.

Acceptance Testing

System is tested at the client site using real data and check whether it works properly as
expected.

5.2.2 Non-Functional Testing

Non-functional testing also very important same as functional testing. Non-functional
testing is done against the non-functional requirement of the system.

Performance Testing

Performance testing or it can be named as load testing also. Performance testing ensure
that the developed system is cable of handling load which are number of users and
amount of data. Meanwhile stress testing can be done to find the failure points in the
system when load testing is happening.

32
 TechManagePro System.

Security Testing

Security testing is a process intended to reveal flaws in the security mechanisms of an

information system that protect data and maintain functionality as intended. Due to the
logical limitations of security testing, passing security testing is not an indication that no
flaws exist or that the system adequately satisfies the security requirements. [8]

Security testing is consist of specific elements such as confidentiality, integrity,

authentication, authorization, availability and non-repudiation.

Usability Testing

Easy to use the system and easy to navigate through the system.

Compatibility Testing

System should be work without any problem in recommended environments.

5.3 Test Cases

The test Plan of the system describes the testing strategies and the approaches to testing.
By studying test cases of the system, it was discovered that the final system was satisfied
user requirements and compatible with design specifications. Table 5.1 shows the test
plan.

Module Name Function Name Test Priority

Login and User Login to the system (Admin) High

management
Login to the website (Customer) High

Customer registration High

Officer registration High

Update profile High

Deactivate officer High

Log out from the system High

Log out from the website user account High

Job management Define new job High

33
 TechManagePro System.

Update / delete jobs High

View Pending, Completed Jobs High

Update Jobs High

Table 4.1: High level test plan

5.4 Add New Staff

1. Navigate to 'Admin Account setup'.
2. Click 'Staff & Guest management'
3. Click '+ Add Staff'
4. Fill out name, address and email.
5. Create a password.
6. Select option box to assign user role.
7. Click submit.

5.5 User Evaluation

Getting user feedback is one of most important thing that should be done in the user
acceptance test phase. In this process, user feedback forms are given to the system users
and receive their feedback through the forms so that we can get a clear idea about the
developed system from the user aspect. Following user feedback form in the Figure 5.4
shows the different aspect of the system that user must consider about and gives the
rating from 1 to 5.

34
 TechManagePro System.

Figure 5.4: User feedback form

35
 TechManagePro System.

Chapter 06 – Deployment

The Deployment phase is when the hosting decision becomes critical. It involves the
release of the ecommerce website to a production environment, making it accessible to
the public. The hosting infrastructure, whether it's on-premises servers, cloud-based
services, or a hosting provider, is put into action during this phase.

6.1 Key Consideration

Key considerations during deployment include:

 Server Configuration:

Set up servers with the necessary software, databases, and

configurations.

 Domain Configuration:
Configure domain settings to point to the server's IP address or domain
name system (DNS).
 SSL Configuration:
Implement SSL certificates for secure transactions.

6.1.1 Connection Page

The connection page of an dynamic website typically refers to the part of the
website's backend where the application connects to the database. This
connection is crucial for retrieving and storing data related to products,
customers, orders, and other essential aspects of the ecommerce platform. Below
is a TechManagePro system PHP connection page for an ecommerce website
using MySQL as the database

36
 TechManagePro System.

Figure 5.5: Connection page diagram

6.1.2 Domain Register

Figure 5.6: Domain Register page diagram

37
 TechManagePro System.

6.1.3 Domain Hosting & File Manager

Figure 5.7: Award space Hosting & file manager diagram

38
 TechManagePro System.

Chapter 07 – Conclusion
The Internet has become a major resource in modern business, thus electronic shopping
has gained significance not only from the entrepreneur’s but also from the customer’s
point of view.

7.1 Encountered problems and lessons learnt

Facing problems in a software development is very common and rectify. Those problems
measure the success of the project. Several problems were encountered during this
project.

• Limited time period to do the development which was a main problem as there
were vast research area to investigate.
• Increasing the performance of the system and the website.
• Enhancement in the client requirements were affected to the time frame of the
project, which was again effected to the table structure of the system.

Main lesson learnt throughout this project is time management by delivering the product
within a time frame. This project gave significant practical experience in software
engineering disciplines. Most import part of software development life cycle is the
analysis and design phase as I came to know by the practical experience. Learn about
how to design a diagram using UML and develop the system using these diagrams. List
of things learnt are as follows;

• Time management was an important fact to finish this project successfully.

• Experience of working with the client; how to manage them and how to respond
to their requirements.
• Different business domain knowledge was gathered from this project in the
requirement gathering phase.
• New technologies in programming languages and experience of working with
new tools.

• Important of documentation and practical experience of making them was get to

known.
• Opportunity to open up the mind to study more details of cloud systems and
domain.

39
 TechManagePro System.

• Challenging and valuable project to enhance system development capability.

• A chance to strengthen the project management skills by providing deadlines to
meet up and thereby heighten the time management skills. At the same time it
enhanced the analyzing skills and given a unique opportunity to boost
interpersonal skills by interact with the clients and to develop understanding on
business philosophy.

7.2 Future developments

Some major client requests were arisen while the user acceptance testing. But those were
not be able to complete with in this scope and the time frame. Hence they were agreed
to continue few future developments as listed below.

• Online customer care service with a chatting module.

• Provide a total mobile application solution for the website of the system.
• Job tracking mechanism with a GPS facility which can be monitored the
technician and the job status.
• Email and SMS notification facility for customers and technicians

Thank you……

40
TechManagePro System.

41