0% found this document useful (0 votes)
314 views53 pages

Final Report of Summer Project

This document is a student declaration certifying that the student completed a summer project titled "Loan Management System" under the guidance of their supervisor. It states that the work is original and has not been submitted elsewhere. It is accompanied by a certificate from the supervisor confirming they guided the project work. An evaluation committee also approved the project as fulfilling degree requirements.

Uploaded by

Ganesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
314 views53 pages

Final Report of Summer Project

This document is a student declaration certifying that the student completed a summer project titled "Loan Management System" under the guidance of their supervisor. It states that the work is original and has not been submitted elsewhere. It is accompanied by a certificate from the supervisor confirming they guided the project work. An evaluation committee also approved the project as fulfilling degree requirements.

Uploaded by

Ganesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 53

STUDENT DECLARATION

This is to certify that I have completed the Summer Project entitled “


Loan Management System” under the guidance of “Mr. Chakra
Narayan Rawal” in partial fulfillment of the requirements for the
degree of Bachelor of Information Management at the Faculty of
Management, Tribhuvan University. This is my original work and I have
not submitted it earlier elsewhere.

Date:

__________
________

Signature
of Student

Name:Raksha Paudel
ASIAN SCHOOL

OF MANAGEMENT & TECHNOLOGY

Affiliated to Tribhuvan University

Gongabu-4, Kathmandu

CERTIFICATE FROM THE SUPERVISOR

This is to certify that the supper project entitled “Loan Management System”
is an academic work done by submitted in partial fulfillment of the
requirements for the degree of Bachelor of Information Management at
Faculty of Management, Tribhuvan University under my guidance and
supervision. To the best of my knowledge, the information presented by his/her
in the summer project report has not been submitted earlier.

……………….

Signature of the Supervisor

Mr. Chakra Narayan Rawal

Date:
ASIAN SCHOOL

OF MANAGEMENT & TECHNOLOGY

Affiliated to Tribhuvan University

Gongabu-4, Kathmandu

Date:

LETTER OF APPROVAL

We, the evaluation committee of the Summer Project report have approved that
Summer Project entitled “Loan Management System” submitted by “Raksha
Paudel” is fully adequate and satisfactory in scope and quality for the partial
fulfillment of Bachelor of Information (BIM), Faculty of Management.

Evaluation Committee

……………… ………………

Mr. Chakra Narayan Rawal Mr.Chakra Narayan Rawal

Supervisor Program Coordinator

……………… ………………

External Examiner Internal Examiner

………………..

Er. Anil Lal Amatya

Principal
ACKNOWLEDGEMENT

Seeing as conceptual knowledge is insufficient for successful practice in information


technology, real-world projects are required to gain additional knowledge and
experience. I'd like to thank Tribhuvan University and the Asian School of
Management and Technology for allowing us to create a real-world project based on
an organization operating in a real-world environment.

The satisfaction and success of completing this task would be insufficient if heartfelt
thanks were not extended to those whose constant guidance, support, and
encouragement made this work possible. I was fortunate to receive assistance,
support, and encouragement from many people while working on this undergraduate
project, and we would like to thank them for their assistance.

I would also like to extend my heartfelt thanks to Mr. Chakra Narayan Rawal and
Mr.Surya Bam for the guidance they have provided in the process of preparing this
project, without them this project never would have been completed.I would also like
to thank my colleagues who helped me during my project time by sharing their
knowledge, idea, feelings, and opinion.

Secondly, I would like to thank my friends who helped me to make my work more
organized and well-stacked till the end.

Thirdly, I would like to thank the Spyderslab team mentors and seniors who helped
me to make my work error-free.

Last but clearly not least, I would thank The Almighty for giving me the strength to
complete my report on time.

I
EXECUTIVE SUMMARY

The report herein includes all the activities done during the summer project on the
topic of "Employee Management System". The project is complete as a part of the
requirement of the Bachelor of Information Management course syllabus at Tribhuvan
University.

The ‘Employee Management System’ system is designed to replace the traditional


way of record-keeping in the business site with a new digitized and more efficient
way. Previously, at the project site, all the employee record keeping was done
traditionally, which resulted in low efficiency while searching for the data and loss of
time, and a time-consuming process to find the required data. This system developed
helps the user to store all the employee records of the organization in one digital
place. It helps to track all the employees records in one place securely. The process of
retrieving a needed record at the required time is also very easy with this system.
Organizations’ staff can quickly find a needed record using the search and advanced
search function provided by the system. Human resource managers of the
organization can easily add new employees, and employees can take leave, edit
profiles and attendance using this system

This system will help the user make the record-keeping system much more efficient
and accessible and make the information retrieval process quick and convenient. This
system is expected to save time and eliminate the need for redundant work for the
staff members of the Spyderslab, within the mind to implement the system without
using extra manpower.

II
Contents
ACKNOWLEDGEMENT...........................................................................................I

EXECUTIVE SUMMARY.........................................................................................II

LIST OF FIGURES....................................................................................................V

LIST OF TABLES.....................................................................................................VI

LIST OF ABBREVIATIONS..................................................................................VII

CHAPTER ONE...........................................................................................................8

INTRODUCTION........................................................................................................8

1.1Background of Study........................................................................................................................

1.2 Introduction to organization...........................................................................................................

1.2.1.1Service Provided.........................................................................................................................

1.2.1.2 Technology Adapted..................................................................................................................

1.2.1.3 Targeted Customers..................................................................................................................

1.3 Problem Statement..........................................................................................................................

1.4 Objective of the Project...................................................................................................................

1.5Methodology....................................................................................................................................

1.5.1 Project Framework.................................................................................................10

1.5.2 Data and information.............................................................................................11

1.5.3 Techniques of Project report analysis....................................................................12

CHAPTER TWO.......................................................................................................14

TASK AND ACTIVITIES PERFORMED..............................................................14

2.1 System Review................................................................................................................................

2.2 Analysis of tasks and activities......................................................................................................

2.3 Requirements Analysis..................................................................................................................

2.3.1 Functional Requirements.......................................................................................17

2.3.2 Non-Functional Requirements...............................................................................19

2.5 Feasibility Study............................................................................................................................

2.5.1 Technical Feasibility...............................................................................................20

III
2.5.2 Economical Feasibility............................................................................................20

2.5.3 Operational Feasibility...........................................................................................20

2.6 System Design................................................................................................................................

2.6.1 Schema Diagram and Class Diagram......................................................................21

2.6.2Activity Diagram......................................................................................................23

2.6.3 Sequence Diagram.................................................................................................25

2.7 System Implementation.................................................................................................................

2.7.1 Module Description...............................................................................................28

2.7.2 Tools used..............................................................................................................30

2.7.2.2 Backend Tools.....................................................................................................31

2.8 System Testing and validation......................................................................................................

2.8.1 System Testing.......................................................................................................33

2.8.2 Unit Testing............................................................................................................33

CHAPTER THREE...................................................................................................36

DISCUSSSION AND CONCLUSION.....................................................................36

3.1 Findings..........................................................................................................................................

3.2Discussion........................................................................................................................................

3.3Conclusion.......................................................................................................................................

3.4 Further Enhancement...............................................................................................37

REFERENCES....................................................................................................................................

APPENDICES......................................................................................................................................

Appendix A Screenshots.................................................................................................39

Appendix B Sample Code................................................................................................45

IV
LIST OF FIGURES

Figure 1: Use Case Diagram

Figure 2: Class Diagram

Figure 3: Admin Activity Diagram

Figure 4: User Activity Diagram

Figure 5: Admin Sequence Diagram

Figure 6: Employee leave Sequence Diagram

Figure 7: Admin Adding New Employee Sequence Diagram

V
LIST OF TABLES
Table 1:Unit Testing Table

VI
LIST OF ABBREVIATIONS

BIM Bachelor of Information Management

CSS Cascade Style Sheet

HTML Hypertext Markup Language

MySQL Structured Query Language

PHP Hypertext Pre-Processor

SP Summer Project

TU Tribhuvan University

XAMPP X (cross platform), Apache, MySQL, PHP, Perl

VII
CHAPTER ONE
INTRODUCTION

1.1Background of Study
Employe management System project deals with the development of web applications
for Spyderslab Pvt. Ltd. It is a web application designed to help organizations keep
records of their employees and save time and money by eliminating the manual
process of collecting information.

This web application is based on managing the information of employees in


organization. This application provides flexible and practical features that allow
employees to manage their profiles as they please. This application ensures a better
connection between your organization and your employees. This application contains
a general profile for each user, employee details, salary, vacation reports, and
attendance reports.

1.2 Introduction to organization


Spyderslab Pvt.Ltd is one of the rising inclusive digital marketing agency and computer
training institutes located at Sorakhutte, Kathmandu, Nepal. This company has been in
operation since February 2018. This institution has been delivering excellent education,
training, internship possibilities for new freshers, job placement opportunities, and a variety
of other professional IT training since its inception. The company has been employing experts
from the IT field to impart professional education.

1.2.1.1Service Provided
Company has been providing service for students who have desire to study IT
Professional course.Many SEE appeared students, +2 appeared students , and
Bachelor students come to learn and do intern in this institute.Similarly, company is
providing digital marketing, web development, designing, software development and
other IT service for other businesses.

1.2.1.2 Technology Adapted


Spyderslab is a pure IT based organization. Here, almost all work and system are
govern by using latest technology.Software system are mostly used as

8
technology.Moreover, Employee Management system is also designed for proper ,
systematic and scientific management of the employee record in organization.

1.2.1.3 Targeted Customers


The targeted Customers for this project are employee.Employee can get benefit from
this system,because a employee can request for leave with reason where admin have
authority to accept or reject.Attendance of the system is another important part. Salary
report is genereted where employee can see their salary information.

1.3 Problem Statement


As of now, no digital technology has been used to oversee all of the employee's
operations. Employee operations are managed manually using a paper-based
approach. Employees and company managers have lost time as a result of this.

Handling personnel information by hand has a variety of drawbacks. This can be seen
in systems like leave management, where an employee must fill out paperwork that
may take weeks or months to be authorized. When dealing with some of these issues,
paperwork is used. Processes may result in human error, papers may get into the
wrong hands, and don't forget about the security risks.

The fact that it takes a long time Employee self-service is lacking in a lot of current
systems. Employees are unable to access and manage their personal information
without the assistance of a supervisor.

Developing and deploying a web-based employee management system can address


the aforementioned issues. This solution will keep employee information in a database
by totally automating the process.

Through a password-protected system, we may keep track of the employee's


performance and accomplishments.

1.4 Objective of the Project


The aim of this research is to design an employee management for SpydersLab Pvt
Ltd.

9
The Human workforce has grown as a result of the abundance of job options. As a
result, a system that can handle the data of such a vast number of employees is
required. Because of its user-friendly design, this project will make the process of
keeping records easier.

The specific objective of this study is to create an employee management system with
employee leave, employee profiles, salaries, attendance, leave, and reports to assist.

 To provide convenient services to the employee through the system.


 To keep track of employee attendance and performance.
 To interact with the system, there will be a user-friendly front-end.
 To store employee information, there will be a well-designed database.

1.5Methodology
There are various methods for gathering the necessary data and information. For the
project, the following methods are used to extract the information needed for the
proposed system:

1.5.1 Project Framework


A project framework is a collection of processes, tasks, and tools that are used to
guide a project from start to finish. This chapter describes the project's proposed
implementation strategy. The importance of this systematic planning and
implementation in order to complete the system on time.

Project Initiation
This is the first phase of the system development cycle, in which a reasonable topic
capable of resolving the organization's problem is chosen. After defining the topic's
objectives and scope, work on it began. A written document, in the form of a project
proposal, was submitted to the relevant faculty, outlining the organization's issues,
recommendations, and requirements. The organization had to be visited in order to

10
collect all of these data. The next phase began after the project proposal was
approved.

Project Planning
During this phase, planning for how to manage the time frame within which the
project should be completed was completed. The time and work was divided into
different modules such as front end, back end, data collection, organization visit, and
so on.

Project Execution
During this phase, I prepared interview questions about the subject and presented
them to the organization's owner for his response. It was beneficial to learn about the
organization's working environment and activities. The specifics were meticulously
recorded. In this phase, system development begins. The project execution phase is
typically the longest in the project life cycle, consuming the most energy, time, and
resources.

Project Controlling
After gathering all of the organization's information and data. The organization had to
be adjusted.

Project Monitoring
The project was monitored by checking it on a regular basis.

Project Closure
The final stage of the project life cycle is project closure. During this phase, we
prepare project and activity reports. Project closure entails handing over the
deliverables and passing the documentation, which includes all activities from the
beginning to the end of the project, to the relevant External teachers and presenting
them visually using PowerPoint.

1.5.2 Data and information


The procedure of collecting, measuring, and analyzing accurate insights for research
using standard validated techniques is known as data collection. Essentially, there are
two major data sources.

11
Primary and secondary sources are used.

1.5.2.1 Primary Source


The primary source of data for this project is primarily observation of the entire
operating procedures on site, as well as interviews with relevant organization staff
members.

The observation provided critical data for the project's requirements. The observation,
combined with interviews of the staff members who perform the tasks, aided in
verifying the problems and providing insights for solutions.

 Interview

Some questions were asked to the CEO Mr.Sandesh Dawadi of company personally.
There were simple and research based questions.

 Direct Observation

The company was personally visited, and the organization's working environment was
observed.

1.5.2.2 Secondary Source


The secondary source of data is basically used from various websites(Spyderslab.com),report
and articles form the internet (researchgate.net) and other related organizations.

1.5.3 Techniques of Project report analysis


The majority of the project's data is gathered from primary sources. I prepared various
questions for gathering primary data, visited the organization, met with employees,
and so on. Another data collection procedure is gathering information via the internet
and manuals, which is saved as secondary data. The following methods were used to
collect critical data.

1. Interview: Data can be collected through interviews with workers in the


organization, which is one of the most important tools for data collection. To
support the dependability, some informal interviews were conducted with the
staff and managing director.

12
2. Questionaire: The questionnaire  was used to collect data. Different questions
was posed to the organization's employees.

3. Observation: Various situations and actions were observed directly by


visiting the organization on several occasions in order to gather reliable
information.

4. Data Processing and Techniques used: Data and information are represented
in various tables and diagrams, with or without descriptions.

5. Tools used: To understand the accuracy of problems and situations, secondary


data sources such as office records, websites, organizational reports, and
surveys were used. The structured questionnaire, interviews, and observations
were the primary data sources.

13
CHAPTER TWO

TASK AND ACTIVITIES PERFORMED

2.1 System Review

An HRMS refers to the systems and processes at the intersection between human
resource management (HRM) and information technology. It merges HRM as a
discipline and in particular,its basic HR activities and processes with the information
technology field whereas the programming of data processing systems evolved into
standardized routines and packages of enterprise resource planning (ERP) software.

An organization or company with a very large number of employees manages a


greater volume of data. This activity can be daunting without a more sophisticated
tool to store and retrieve data. The various levels of sophistication can be examined
by looking at the evolutionary aspects of HR technology. These aspects can be
characterized by four stages of development: Paper-based systems, early personal
computer (PC) technology, electronic databases, and Web-based technology.

According to the Tennessee Technology Centre at Hartsville, “attendance is among the


10 employee work ethics most valued by employers” (Work - Chron.com, 2015)
implying its importance where employee management is concerned. EMS (employee
management systems) time and attendance deliver data based on the collection of
employee timekeeping and their overall attendance. Admin can successfully monitor
their staff and can identify any suspicious patterns exhibited, e.g. employees with
continuous late streaks or a frequent amount of absences against their name can be
highlighted to the admin for them to take possible disciplinary action. Therefore, time
and attendance are one of the preliminary components included in the construction of
an employee.

Other existing systems were referred to for the purpose of this project and its required
features, in order to gain inspiration and observe what features general-purpose

14
software has and may require for this project. When looking for existing software that
could aid in the development of this project.k

According to the Sesame website, Employee Management System(EMS) allows you


to carry out all the previously mentioned functions of the HR department which are
explained below;

 Employee Database: All the information about former and current employees is
centralized and organised in a single place.
 Time Tracking: Employees can clock in and out themselves and check their
schedules, while managers have access to their team members’ time sheets.
 Task Planning: Managers can easily assign tasks to their employees and schedule
the work of their entire team.
 Shift Planning: Manging Shifts and avoiding time conflicts becomes much easier
when shift planning is automated.
 Documents: EMS reduces paperwork by providing place where employees can
consult all their documents such as payslips.
 Leave Management: Employees can request leave days directly through the
system and be notified when their request has been processed.
 Payroll: Automated payroll calculates and processes the pay that is due to each
employee.(Sesame, 2018)

OrangeHRM is a powerhouse human resources tool that any small or midsize


business can benefit from using. With OrangeHRM, you have options: You can
download and install the system on your own hardware, or you can purchase a hosted
solution. To get prices for the hosted solution, you have to contact them from their
Request a Quote page. OrangeHRM's features include: fully modular, addons (e.g.,
benefits, employee self-service, training, budget, job and salary history, etc.) for
purchase, all standard HR functions (employees, leave, benefits, performance, etc.),
and more. The installation is fairly straightforward. With a self-extracting Windows
installer or full-source installations for Windows, Mac, and Linux, you can get
OrangeHRM up and running on nearly every platform. If you don't have the hardware

15
or the skills to set up Orange onsite, you can request a quote for a hosted instance of
OrangeHRM. You can also purchase support plans and customizations.

2.2 Analysis of tasks and activities


The analysis is the process of gathering and interpreting facts, diagnosing problems,
and recommending system improvements. It is a problem-solving activity that
necessitates close collaboration between system users and system developers. System
analysis or study is a critical stage in the system development process. Many tasks
and activities had been completed, all of which contributed to the achievement of our
project's main goal. The primary goal of the project was to gather information about
the use of technology in one of the country's organizations. Some of the tasks that are
completed are listed below:

• Organization selection: Choosing a specific organization from among many was


difficult. Spyserslab Pvt Ltd was chosen after a search.

• Gathering facts about the organization: Following selection, the next step was to
gather the necessary information about the organization. It was accomplished through
an interview and observation of the work process.

• Reviewing the problem: After receiving the information, the organization's main
problem was thoroughly reviewed.

• Suggested solution: Following a review of the problem, a solution was proposed,


which was to create a system that digitized previously traditional work.

• Solution development: Following approval of the proposed solution, the next step
was to develop the system itself.

2.3 Requirements Analysis


The process of defining the expectations of users for an application that is to be built
or modified is known as requirements analysis. It includes all tasks performed to
identify the needs of various stakeholders. As a result, requirements analysis entails
analyzing, documenting, validating, and managing software or system requirements.

16
2.3.1 Functional Requirements
Functional requirement refers to the statement of services the system should provide,
how the system should react to particular inputs and how the system should behave in
particular situations. The functional requirements of my project are:

 Admin can update the database.


 Employees will have access to their profiles and will be able to edit their details,
and salary reports.
 Employee can apply for leave and Admin can reject/accept the leave.
 Admin will add an employee and a default password and employee id will be
generated
 The system should show the current available records.
 The user should be able to search for any particular record.
 The system should not allow the unregistered user to log in or update data.

 Admin can generate timely reports to monitor employees and this can be used
for performance appraisals.

17
Use case Diagram

Figure 1 use case diagram

18
2.3.2 Non-Functional Requirements

• Usability: The system must be simple to use and comprehend. The data must be
displayed in an intuitive and simple manner. The system's menus must be easily
navigable by users and simple to understand.

• Reliability: The system must successfully add, delete, or update any record provided
by the user, as well as generate the final report.

• Performance: The system must not lag because the user does not have the luxury of
waiting for it to complete an action. Every time the system is turned on, the user must
have access to all of the system's functions. The system's calculations must adhere to
the norms set by the user and should not vary unless explicitly changed by the user.

• Supportability: The system should be designed to work in any system and browser,
such as Firefox, Chrome, Microsoft Edge, and so on.

• Security and Privacy: The system must keep the recorded data private. Any
unauthorized person should not have access, as this could lead to data mishandling
and manipulation.

2.5 Feasibility Study


A feasibility study examines how successfully a project can be completed while
taking into account factors such as economic, technological, legal, and scheduling
considerations. It demonstrates how the system is linked to the business strategy.
Economic and technical feasibility must be discussed within the scope of the
feasibility study.

19
2.5.1 Technical Feasibility
The following technical issues are frequently raised during the feasibility stage of the
investigation:

The system is technically capable of storing the data required to use the system.
Inquiries from users will be responded to by the system. The system is in its initial
version and can be upgraded as needs change.The current system that has been
developed is technically feasible. It comes with a web-based user interface. It uses
user login and authentication to provide data security and ensure that data can only be
inserted and updated by those who are authorized to do so, in this case, the
organization's employee. Before being stored in the database, user passwords are
encrypted. The software requirements for this project's development are minimal, and
it is already available for free as open-source. Open-source programming languages
and databases include PHP and SQL. They are all open to the public.

2.5.2 Economical Feasibility


The system is economically feasible. It does not require any additional hardware or
software. Since the interface for this system is developed using the existing resources
and technologies available at the organization, there is nominal expenditure and
economic feasibility.

2.5.3 Operational Feasibility


Operational feasibility is the measure of how well a proposed system solves the
problems and takes advantage of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements analysis phase of
system development. Operational feasibility is the ability to utilize, support, and
perform the necessary tasks of a system or program. It includes everyone who creates,
operates, or uses the system. To be operationally feasible, the system must fulfill a
need required by the business.

20
2.6 System Design
Based on the user requirements and the detailed analysis of the problems and work
process of Spyderslab Pvt Ltd, the new system is designed. This is the phase of
system designing and is the most crucial phase in the development of a system. The
logical system design is arrived at as a result of system analysis and is converted into
physical system design.

2.6.1 Schema Diagram and Class Diagram

Figure 2 Schema Diagram

21
22
2.6.2Activity Diagram
An activity diagram is a behavioral diagram i.e., it depicts the behavior of a system.
An activity diagram portrays the control flow from a start point to a finish point
showing the various decision paths that exist while the activity is being executed.
They are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency

Figure 3 Admin Activity Diagram

23
Figure 4 User Activity Diagram

24
2.6.3 Sequence Diagram
Admin

Figure 5 Admin Sequence Diagram

25
Figure 6 Employee Leave Sequence Diagram

26
Figure 7 Admin Adding New Employee Sequence Diagram

27
2.7 System Implementation
In this phase, the actual functioning system is developed by converting the system
specification into a computer instruction and the defined procedures are transformed
into control specifications by the help of a computer language.

2.7.1 Module Description


2.7.1.1Login Module
When the user is confronted with a login screen, he/she has to enter a username and
password. If the data provided are valid the login will be successful.

28
2.7.1.2 Admin Dashboard
In admin dashboard, admin can perform function like add, delete,and employee,
generate salary, accept/reject leave, send notice to all employee, and change
password.

2.7.1.3 User Dashboard


In user dashboard, it contains profile of the employee, attendance, salary report,
employee can give feedback,and apply for leave

29
2.7.2 Tools used
The Frontend Tools and Backend Tools used for the developmentof the software are
explained as below:-

2.7.2.1 Frontend Tools used


Front end is a term used to characterize program interfaces and services relative to the
initial user of this interface and services. It usually refers to the client-side of an
application. A front-end application is one that users interact with directly. Turban et
al (2008, p45) define the front end as the portion of a reseller’s portal, electronic
catalogs, a shopping cart, a search engine, and a payment gateway.

HTML 5

HyperText Markup Language (HTML) is used which is a computer language devised


to allow website creation. These websites can then be viewed by anyone else
connected to the Internet. It is relatively easy to learn, with the basics being accessible
to most people in one sitting; and quite powerful in what it allows you to create.
Having a basic knowledge of HTML will help make or develop e-commerce websites
and will also prove to be handy, especially for editing and modifying web pages.
Furthermore, it has some low-cost benefits because of its many free online tutorials
and advice support which is vital for e-commerce development.

CSS

Cascading Style Sheets (CSS) is used for describing the presentation of a document
written in a markup language such as HTML.CSS is a cornerstone technology of the
World Wide Web, alongside HTML and JavaScript.

CSS is designed to enable the separation of presentation and content, including layout,
colors, and fonts. This separation can improve content accessibility, provide more
flexibility and control in the specification of presentation characteristics, and enable
multiple web pages to share formatting by specifying the relevant CSS in a
separate .css file which reduces complexity and repetition in the structural content as
well as enabling the .css file to be cached to improve the page load speed between the
pages that share the file and its formatting.

30
JavaScript

Alongside HTML and CSS, JavaScript is one of the core technologies of the World
Wide Web. JavaScript enables interactive web pages and is an essential part of web
applications. The vast majority of websites use it for client-side page behavior, and all
major web browsers have a dedicated JavaScript engine to execute it.

As a multi-paradigm language, JavaScript supports event-driven, functional, and


imperative programming styles. It has application programming interfaces (APIs) for
working with text, dates, regular expressions, standard data structures, and the
Document Object Model (DOM).

jQuery

jQuery is a fast, small, and feature-rich JavaScript library. It makes things like
HTML document traversal and manipulation, event handling, animation, and Ajax
much simpler with an easy-to-use API that works across a multitude of browsers.
With a combination of versatility and extensibility, jQuery has changed the way that
millions of people write JavaScript

2.7.2.2 Backend Tools


PHP

PHP, abbreviated to Hypertext Preprocessor is a server-side web programming


language that can be embedded into HTML. PHP is free software i.e. it is open source
code. It is used for creating dynamic web pages that interact with the user and can
include functionalities such as getting user input, manipulation of the input, and
storage of this data in a suitable DBMS. PHP is also easy to integrate with web pages.

31
MySQL

MySQL stands for My Structured Query Language. It is the world’s most popular
open-source relational DBMS. MySQL is available for free under the GNU General
Public License for open source benefits/reasons related to development. Initially,
MySQL was free and some versions of it are still free though if you desire to use
MySQL for commercial purposes you will need to purchase a license. It is non-
proprietary, easily extensible and platform-independent. Its downside is that it lacks a
graphical user interface; therefore you need to know how the database works to make
the most efficient use of it.

Laravel
Laravel is a php framework and uses a scripting language rather than being a strict
PHP programming language. While scripting languages and programming languages
are related, they have several noticeable differences, primarily in ease of use and
speed of execution.

Scripting languages are platform-specific, interpreted languages. In contrast,


programming languages are platform-agnostic, compiled languages. Being platform-
specific, scripting languages rely on the compiler of the application in which they are
working.

Applications built using scripting languages are compiled at runtime, meaning that
each instruction is interpreted individually at runtime, rendering the application
slower than a pre-compiled application. Runtime compilation also results in the
application stopping or shutting down if it encounters a runtime error; in contrast, pre-
compiled applications perform error checking during compilation, making them more
robust at runtime.

32
2.8 System Testing and validation

2.8.1 System Testing


This part will look at the testing of the system developed to ensure it has met its
requirements.As a fairly flexible methodology was adopted for the development , the
testing ogf the application started during its development with bugs being fixed as
they were discovered .After each section of the application was completedd it was
twted so that errror could be corrected.

2.8.2 Unit Testing


Unit Testing was undertaken during the actual implementation of the system.Each
time some code was wriiten it was run and monitiored for the bug .As bugs were
discovered they were corrected by adding additional code or modifying the existing
code.Severeal bugs were corrected by analyzing the error messages and correcting
them by changing the codes.After development of the system competed,testing was
also perfomed.Functionality testing and interface testing were combined to ensure the
system functionality as required.

33
Table 1: Unit Testing Table

Test Name Prerequisi Steps Test Data Excepted Actual Result


CaseI te Outcome Outcome
d
TC_0 Login The user • Type username Email:admin@gm User login User login pass
1 must be on • Enter the ail.com successfull successfull
the login password y y!
page. • Enter email Password:
• Hit the ‘Login’ ‘password'
button
Tc_0 Login The user • Type username Email:sujan@gma Unsuccessf Invalid pass
2 must be on • Enter the il.com ul email
the login password Password:123wer
page. • Enter email
•Hit the ‘Login’
button
Tc_0 Add The user  Click on Employee pass
3 employee should be add has been
on the add employe created
employee e succcesfull
page.  Enter the y
details
--------------
 Enter the
submit
button
Tc_0 Leave Type The user  Click on Leave type pass
4 must be on leave has been
Leave type successfull
Page.  Choose y added.
one leave
----------------------
 Enter
submit

Tc_0 Attendance The user  Click on Your total pass


5 must be on the working
the clock_ou ------------------ hrs is
attendance t button ……..
page.  Submit
Tc_0 Grievance The user  Write Description: Hello Successfull pass

34
6 must be on down the Spyderslab team
the feedback. members.
Feedback  Enter the
page. button
Tc_0 Grievance The user  Write Description: null unsuccesful Description pass
7 must be on down the can’t be
the notice feedback. null
page.  Enter the
submit
button.
Tc_0 Notice The user  Write Description: Successfull pass
8 must be on down the Tomorrow is
the Notice notice. holiday
page  Enter the
submit
button.
Tc_0 Notice The user  Write Description: null unsuccesful Notice pass
9 must be on down the can’t be
Notice notice. null
page  Enter the
submit
button.

35
CHAPTER THREE

DISCUSSSION AND CONCLUSION


3.1 Findings
Following the installation of the new system at the site, the overall record-keeping
process was discovered to be far more efficient than before. Because all of the records
were digitized, the chances of losing important information were greatly reduced. The
organization quickly adapted to the new system and was able to navigate the UI. The
traditional method of recording results has been replaced by a new digitized method.
Using the system's search and advanced search functions, I was able to quickly locate
a specifically required record and its details. Overall, the efficiency of the
organization's tasks has increased, with almost no cases of lost information.

3.2Discussion
This project was initiated with the aim to overcome the difficulties created by a paper
based recording system of employees.This was done by developing a web based
application of the Spyderslab Pvt Ltd that provide every records and access to the
employees.Similarly, it provides the facility to apply leave for online, salary report
display.Employee can send feeedback and check total working hrs.

Great effort and time were spent on completing the project as per the requirement
specified by the organization.Despite the challenges and problems, the project was
completed in specified duration. The system was tested by the developers and by
some other person indirectly involved in the project.

3.3Conclusion
This project is finally obtained as a system that can convert manual process of
recording into computerized system.This is user-friendly interface that gives
authenticate access to the authorized user, where he/she can view their details,apply
leave, view salaryof employees, give attendance.In this way this application will
effectively reduce the inconvienceof the company to record informations about

36
employees and enhance the connectivity of the Spyderslab Pvt Ltd with its
employees.

3.4 Further Enhancement


Although the project has been completed and the study's problem has been solved,
there are still many tasks in the system that need to be improved in the future for
better performance, such as:

 More secure login system with 2 factor authentications


 Storing data in a secured and encrypted way
 Making database strong so that no manipulation can be made from
unauthorized access
 Show the employee progress.

37
REFERENCES

 HR Press “The Largest Selection of Software for Human Resource Management,


Workplace Safety, and Employee Testing and Training.” URL:
http://www.hrpresssoftware.com/peopleman.html, (March 2004).
 IEEE 1074-1997, Standard for Developing Software Life Cycle Processes.
 Object Management Group, UML Resource Page. URL: http://www.omg.org/uml/,
(March 2004)
 Dean Leffingwell and Don Widrig, Managing Software Requirement: A Unified
Approach, Addison-Wesley, 2000
 Spyderslab (Professional IT Training Institute), About Resource
page.URL:https://spyderslab.com/about/, ( Feburary,2018)
 Seasame, URL: https://www.sesamehr.com/,(October, 2018)

38
APPENDICES
Appendix A Screenshots
Add Employee

Employee Report

39
Leave Type

Leave View

40
Change Password

Employee Report

41
User Dashboard

Take Leave

42
Edit Profile

Add Grievance

43
Notice View

Salary Report

44
Appendix B Sample Code

Admin Dashboard Code

@extends('admin.layouts.workspace')
@section('workspace-content')

    <div class="content-wrapper">
        <div class="content-header">
            <h1 class="m-0 text-dark"><i class="fa fa-user"></i> Employee </h1>
        </div>
        <div class="container-fluid">
            @include('admin.partials.message')

            <div class="card elevation-3">


                <div class="card-header">
                    <h3 class="card-title">
                        <a href="{{route('admin.employees.create')}}">
                            <button class="btn  btn-flat btn-primary">
                                <i class="fa fa-plus-circle"></i>
                                Add Employee
                            </button>
                        </a>
                    </h3>
                </div>

                <div class="card-body p-3 table-responsive">


                    <table class="table table-md table-striped">
                        <thead>
                        <tr>
                            <th>ID</th>
                            <th>Image</th>
                            <th>Name</th>
                            <th>Address</th>
                            <th>Phone</th>
                            <th>Position</th>
                            <th>Email</th>
                            <th>Status</th>

                        </tr>
                        </thead>
                        <tbody>
                        @foreach($users as $user)

45
                            <tr>
                                <td>{{++$loop->index}}</td>
                                <td>
                                    <img
                                        @if($user->image)
                                        src="{{$user->image->url}}"
                                        @else
                                        src="{{asset('default-image/default-U.jpg')}}"
                                        @endif
                                        class="upload"
                                        style="height: 70px;width: auto; object-fit: contain !important;"
                                        id='form_image'
                                        alt="Product Picture">
                                </td>
                                <td>{{$user->name}}</td>
                                <td>{{$user->address}}</td>
                                <td>{{$user->phone}}</td>
                                <td>{{$user->position}}</td>
                                <td>{{$user->email}}</td>
                                <td>
                                    active
                                </td>
                            </tr>
                        @endforeach
                        </tbody>
                    </table>
                </div>
                <div class="card-footer ">
                <span class="pull-right">
                </span>
                </div>
            </div>
        </div>
    </div>
@endsection

46
User Dashboard Code

@extends('user.layouts.workspace')
@section('workspace-content')
    <div class="content-wrapper">
        <!-- Content Header (Page header) -->
        <section class="content-header">
            <div class="container-fluid">
                <div class="row mb-2">
                    <div class="col-sm-6">
                        <div class="content-header">
                            <h1 class="m-0 text-dark"><i class="fas fa-dollar-sign"></i> Salary </h1>
                        </div>
                    </div>
                </div>
            </div><!-- /.container-fluid -->
        </section>

        <section class="content">
            <div class="container-fluid">
                <!-- Small boxes (Stat box) -->
                <div class="row">
                    <div class="col-12">
                        <div class="card">
                            <div class="card-header">
                                <p>This is the salary report of {{auth::user()->name}} ,{{auth::user()-
>position}} of
                                    this
                                    organization</p>
                                <p>Currently, his/her monthly salary is as following.</p>
                                @foreach($salaries as $salary)
                                    <div class="row col-md-12">
                                        <div class="col-md-8">
                                            <h5>Basic Pay</h5>
                                        </div>
                                        <div class="col-md-4">
                                            <h5>{{$salary->basic_pay}}</h5>
                                        </div>
                                    </div>
                                    <hr>
                                    <div class="row col-md-12">
                                        <div class="col-md-8">
                                            <h5>Transportation</h5>
                                        </div>

47
                                        <div class="col-md-4">
                                            <h5>{{$salary->transportation}}</h5>
                                        </div>
                                    </div>
                                    <hr>
                                    <div class="row col-md-12">
                                        <div class="col-md-8">
                                            <h5>Gross Salary</h5>
                                        </div>
                                        <div class="col-md-4">
                                            <h5>{{$salary->basic_pay + $salary->transportation}}</h5>
                                        </div>
                                    </div>
                                    <hr>
                                    <div class="row col-md-12">
                                        <div class="col-md-8">
                                            <h5>Income Tax</h5>
                                        </div>
                                        <div class="col-md-4">
                                            <h5 class="text-danger">{{$salary->income_tax}}</h5>
                                        </div>
                                    </div>
                                    <hr>
                                    <div class="row col-md-12">
                                        <div class="col-md-8">
                                            <h5>Total Payable Salary</h5>
                                        </div>
                                        <div class="col-md-4">
                                            <h5 class="text-success">{{($salary->basic_pay + $salary-
>transportation) - $salary->income_tax}}</h5>
                                        </div>
                                    </div>
                                @endforeach
                            </div>
                        </div>
                    </div>
                </div>

                <!-- /.row (main row) -->


            </div><!-- /.container-fluid -->
        </section>
    </div>

@endsection

48
49

You might also like