Report

(IDP) PROJECT REPORT
HRMS
By
Hemangi Pathak
Under the guidance of

Prof. Renish padariya
ASSISTANT PROFESSOR
Project Manager - Hardik Sonchhabda
A project report submitted to

Gujarat Technological University in
Partial Fulfillment of Requirements for the
Degree of Bachelor of Engineering in
Department of CSE/IT
March 2019
CERTIFICATE
This is to certify that research work embodied in this report entitled

“HRMS” was carried out by HEMANGI PATHAK(160043107530)at
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGYfor
partial fulfillment of Bachelor of Engineering degree to be awarded by
Gujarat Technological University. This research work has been carried
out under my supervision and is to my satisfaction.
Date:15/03/2019
Place: Rajkot
External guide H.O.D.

Mr.Hardik Sonchhabda
Internal guide
Prof. Renish padariya Prof. Hemal Rajyaguru
SIGN:
SIGN:
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page I of VII

CANDIDATE DECLARATION
I declare that the dissertation report presented here for Bachelor of

Engineering. (CSE/IT) entitled “HRMS” is my own work conducted under
the guidance of Prof. Renish padariya
I further declare that to the best of my knowledge, this dissertation report

does not contain any part of work, which has been submitted for the award
of any degree either in this university or in other university/ deemed
university without proper citation.
Signature of Student:
Name of Student: Hemangi Pathak
Enrollment No: 160043107530
Name of Guide: Prof. Renish padariya
Signature of Guide:
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page II of VII

Department of CSE/ITEngineering
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page III of VII

ACKNOWLEDGEMENT
During the development of this work, the constant association with the team
members of this project has been most pleasurable. With teamwork, the completion
of this work would have been not more difficult. We are thankful to our family for
their warm and calm support to us.
We are highly indebted to our project guide Prof. Renish padariya and Mr. Hardik
Sonchhabda for his continuous support, supervision, motivation and guidance
throughout the work of our project in spite of his hectic schedule who truly
remained driving spirit in our project and his experience gave us the light in
handling project and helped us in clarifying the abstruse concepts, requiring
knowledge and perception and understanding the objective of ourwork.
DATE:15/03/2019 NAME & SIGN OF STUDENT

Hemangi pathak
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page IV of VII

ABSTRACT
Our project is about HRMS system. It is an easy way to find System is to capture
employee’s check in, break in, break out and check out entries within an organization.
The backend of the system works on processing user’s recording and train it perfectly
to recognize user.
The system provides several features related to it and also allows Super Admin user to
check employee’s reports of any single day in a month.
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page V of VII

TABLE OF CONTENTS
CERTIFICATE .............................................................................................................. i
CANDIDATE DECLARATION ................................................................................. .ii
ACKNOWLEDGEMENT ........................................................................................... iii
LIST OF FIGURE........................................................................................................ iv
LIST OF TABLE ...........................................................................................................v
ABSTRACT ................................................................................................................. vi
CHAPTER 1 INTRODUCTION ............................................................................... 5
CHAPTER-2 LITERATURE REVIEW .................................................................. 6
CHAPTER-3REQUIREMENT ANALYSIS ............................................................ 7
3.1 Functional Requirement .................................................................... 7
3.2 Non-Functional Requirement ……………………………………...7
3.3 HardwareRequirement ...................................................................... 8
3.4SoftwareRequirement ......................................................................... 8
3.5Feasibility study ................................................................................... 8
3.6Testing strategies ............................................................................... 10
3.7testing tools and technologies............................................................ 12
CHAPTER-4 DATA DICTIONARY ...................................................................... 13
CHAPTER-5 UML DIAGRAMS ............................................................................ 15
5.1 Use case Diagram .............................................................................. 15
5.2Activity Diagram................................................................................ 16
B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 1 of 3

5.3Sequence Diagram(Module 1) .......................................................... 17
5.4Sequence Diagram(Module 2) .......................................................... 18
5.5Class Diagram .................................................................................... 19
5.6ER Diagram........................................................................................ 20
CHAPTER-6 FORM DESIGN ................................................................................ 21
CHAPTER-7CONCLUSION & FUTUREWORK................................................ 24
7.1 CONCLUSION ................................................................................. 24

7.2FUTURE WORK/SCOPE
……………………………………………………..24
CHAPTER-8REFERENCES ................................................................................... 25
APPENDIX-A LIST OF ABBREVIATIONS ........................................................ 26
APPENDIX-B ORIGINALITY REPORT ............................................................ 27
APPENDIX-C REVIEW CARD ............................................................................ 28
APPENDIX-D CANVAS ACTIVITY .................................................................... 31

LIST OF FIGURE
Figure 1.1 Use case Diagram ……………………..…………………………………………1
Figure 3.2 Activity Diagame……………………………..……………………………..…….2
Figure 3.3 Sequence Diagram(Module 1)………………..…………………………………5
Figure 4.1Sequence Diagram(Module 2)…….…………………………………………….8
Figure 4.2Class Diagram ………………………..………………………………….………..9
Figure 5.1 ER Diagram ……………………………..…………………………………...….11

LIST OF TABLE
Table 1.1 Login .............................................................................................................. 2

Table 1.2Registration................................................................................................... 14
Table 1.3 Time-table .................................................................................................... 15
Table 1.4 Documents ................................................................................................... 16

CHAPTER-1 INTRODUCTION
Our project is about HRMS system. The main purpose of the HRMS System is to
capture employee’s check in, break in, break out and check out entries within an
organization.
The backend of the system works on processing user’s recording and train it perfectly
to recognize user.
The system provides several features related to it and also allows Super Admin user to
check employee’s reports of any single day in a month.
There are basically 2 types of users in the system.
1) Super Admin and 2) Employees.
Super Admin have the access of all the modules in the system and Employees
have only access to his profile and can see the daily logs.
The most important part of the application is under the Video Recorder tab in
edit profile section.
Where user need to upload a video of 15 seconds with normal spects and without
spects.
This video will be trained by our backend system to recognize the user when he is
scanned by the camera in the organization premises.

CHAPTER-2
LITERATURE REVIEW
Our project is about HRMS system. The main purpose of the HRMS System is to
capture employee’s check in, break in, break out and check out entries within an
organization. The backend of the system works on processing user’s recording and
train it perfectly to recognize user. The system provides several features related to it
and also allows Super Admin user to check employee’s reports of any single day in a
month.
2.1 Organization :
Super Admin can see his company Details. It shows Company name, Company
URL, Company address, Company phone no. It also displays Contact person
details which can be edited.
This is one of the most important module. Let me explain you this with example.
Suppose you want to set a work shift of 8 hours that starts at 10AM in the
morning, having 1 hour of break and ends on 7PM in the evening, you can set
these parameters in this module. The break added here will be a compulsory
break time for an employee. If he doesn’t take a break then also he will have to
stay up to 7PM to complete his staffings. When employee comes in the morning,
he will be checked in. When he goes out of the office by facing exit camera, he
will be break out, once he come back and face in camera, he is break out and if
he leaves the office after 7 PM, he is check out. He can come back inside n
number of times, the last exit time for him in the day will be termed as checkout
time.
2.2 HRMS
Super Admin can see his own daily logs here. It shows Entry Time, Exit Time,
Staffing, Actual Staffing, Break, Actual Break and Comments made by user for the
day.
Here Admin can see all the active users of the system. Admin can search the user
and click on any of the user. That will take Admin to a screen, where he can
modify or add the entries for the user. You also get additional features like
filtering to display any month’s data for the user or any specific date range you
can choose to get data.
This is pretty similar to above module but here instead of 1 user’s all days of the
month entries, we are showing all the user’s current day staffing. So it provides a

facility to see all user’s current status from this screen. Choose any date from the
calendar and it will show you all the entries for that day.
This module displays all employee’s current month’s Attendance sheet, which is
quite useful for Super admin to take a whole look of all employees in a single
page. Nothing functional here except the filter.

CHAPTER-3 REQUIREMENT ANALYSIS
3.1 Functional Requirement

Any requirement which specifies what the system should do.
Typical functional requirements include:
 This HRMS system is to capture employee’s check in, break in, break out and
check out entries within an organization. The backend of the system works
on processing user’s recording and train it perfectly to recognize user. The
system provides several features related to it and also allows Super Admin
user to check employee’s reports of any single day in a month.
3.2 Non-Functional Requirement

Any requirement which specifies how the system performs a certain
function. In other words, a non-functional requirement will describe
how a system should behave and what limits there are on its
functionality.
This application will not affect any other applications installed
on the user’s desktop and its internal components. An additional
security key or passwords is required.
The application can be accessed only by the students or
faculties who have registered in it. A reminder will show if user get
any notification.
 Scalability:
It is the ability ofa computer application or product
(hardware or software) to continue to function well as
it (or its context) is changed in size or volume in order
to meet a user need.
 Reliability:
The system must function reliably. The system must
give stable and reproducible results.
 Security:
The Home Security also provide more facility, The
User firsttime to also registered to Application. Then it
will use application’s functionality. Otherwise it
would be not be able to use it.

 Designrequirements:
The system must be designed and documented with the
expectation that its operational lifetime will be many
years.
 Performance:
The system will be designed so that background tasks
can continue while the user performs foreground tasks.
 Resource constraints:
Processor speed, memory, disk space, network bandwidth, etc.
3.3 Hardware Requirement

Laptop
computer
pen drive
3.4 Software Requirement
Notepad++
Wampp server
operating System.
3.5 Feasibility study
The main aim of the feasibility study is to determine whether developing the
project is financial and technically feasible.
Financial Analysis:
This is the heart of the feasibility study report. Here you
will do all the financial analysis and report the various
performance indicators. The information of this section should
be organized under following heads:
 Supply, Demand and Projected Absorption

 Pricing Strategy
 Estimated required (development cost, financing cost etc.)
 Various Financial Performance Indicators
 Scenario Analysis
 Sensitivity Analysis

Market analysis:
 Total market vs. Market segment
 The analysis of the total market takes on an aggregate
perspective. You should evaluate the space supply, the
development of the space demand as well as vacancies
and top rents of the market.
 The analysis of the market segment is focused on a
disaggregated market perspective. Take into
consideration that you should consider geographic and
typological market segments. A differentiated
assessment of supply and demand, space, vacancies
and the rents of the object-specific rents should be
implemented.
 The market analysis can be done in a quantitative or qualitative way, or

a combination of both. So, for example, report the supply and demand
of square feet (qualitative) versus draw conclusion from the
quantitative supply- and demand analyses with qualitative criteria.
Competition analysis:
 Identify relevant competitive smart classroom in your market
 Prepare a checklist of important criteria
 Estimate the degree of completion of the
various goals and results respectively
 Well criteria
 Calculate of an attractiveness index for the
objects of analysis and competitive objects
 Determine competitive positions of the investigated object
Economical Feasibility:
Economic justification is generally the “Bottom Line” consideration for most
systems. Economic justification includes a broad range of concerns that
includes cost benefit analysis. In this we weight the cost and the benefits
associated with the candidate system and if it suits the basic purpose of the
organization i.e. profit making, the project is making to the analysis and design
phase.
The financial and the economic questions during the preliminary investigation
are verified to estimate the following:
 The cost to conduct a full system investigation.

 The cost of hardware and software for the class
of application being considered.
 The benefits in the form of reduced cost.
 The proposed system will give the minute
information, as a result the performance is
improved which in turn may be expected to
provide increased profits.
3.6 Testing Strategies

Software testing is the process of executing a program with intension of
finding errors in the code. It is a process of evolution of system or its parts by
manual or automatic means to verify that it is satisfying specified or requirements
or not.
Generally, no system is perfect due to communication problems between user
and developer, time constraints, or conceptual mistakes by developer. To purpose
of system testing is to check and find out these errors or faults as early as possible
so losses due to it can be saved.
Objectives of Software Testing:

The software testing is usually performed for the following objectives:
SOFTWARE QUALITY IMPROVEMENT: The computer and the software are
mainly used for complex and critical applications and a bug or fault in software
causes severe losses. So a great consideration is required for checking for quality
of software.
Verification and validation:
Verification means to test that we are building the product in right way .i.e. are
we using the correct procedure for the development of software so that it can
meet the user requirements. Validation means to check whether we are building
the right product or not.
Software Reliability Estimation:
The objective is to discover the residual designing errors before delivery to the
customer. The failure data during process are taken down in order to estimate the
software reliability.

Principles of Software Testing:
 It is impossible to test everything

 Testing time and resources should be limited i.e. avoid redundant testing.
 Use effective resources to test
 Test should be planned long before testing begins i.e. after requirement phase
 Test for invalid and unexpected input conditions as well as valid conditions
 Testing should begin in “in the small” and progress towards testing “in the large”
 For the most effective testing should be conducted by an independent party
 Keep software static (without change meanwhile) during test
 Document test cases and test results
 Examining what the software not doing which it expected to do and also checking
 what it is doing that was not expected to do.
Testing Methods:
1. Black Box Testing
Black box testing focuses on the functional requirements of the software. This is
black box testing enables the software engineering to derive a set of input
conditions that will fully exercise all functional requirements for a program.
Black box testing is not an alternative to white box testing rather it is
complementary approach that is likely to uncover a different class of errors that
white box methods like..
1) Interface errors
2) Performance in data structure
3) Performance errors
4) Initializing and termination errors

2. White Box Testing
White box sometimes called “Glass box testing” is a test case design uses the
control structure of the procedural design to drive test case. Using white box
testing methods, the following tests were made on the system
a) All independent paths within a module have been exercised once. In our
system, ensuring that case was selected and executed checked all case structures.
The bugs that were prevailing in some part of the code where fixed
b) All logical decisions were checked for the truth and falsity of the values.
3.7 Testing Tools&Technologies
MySQL Server:-
MySQL server provides the features to store entire database of
our Application and also provide better user interaction.it is also stored
to all database.
CHAPTER-4 DATA DICTIONARY
1) Entity Name: Login

2) Entity Name: Registration
Table 1.2 Registration Data Dictionary
3) Entity Name: Time-table
Table 1.3 Time-table Data Dictionary Admin

4) Entity Name: Donation

CHAPTER-5 UML DIAGRAMS
5.1 Use case Diagram:

5.2 Activity Diagram:

5.3 Sequence Diagram(Module 1):
Admin:-

5.4 Sequence Diagram(Module 2):
Employe :-

5.5 Class Diagram:

5.6 ER Diagram:-

CHAPTER-6 FORM DESIGN
1) Dashbord
=> Here Super Admin can see the calendar in the left side of the page and can
also see his own entry and exit time in the right hand side of the page. In
calendar we are displaying the holidays, birthdays and anniversary date of the
employees if they have added it in their profile.
Link: https://browser.test4you.in/
2) Profile
=> Super Admin can see the his profile and can see details like Position in
company, Bank Detail, Qualification, Work Experience, Current Contact,
Permanent Contact, Emergency Contact, Attachment.
Link: https://browser.test4you.in/user_profiles/index

Organization > Company Details
=> Super Admin can see his company Details. It shows Company name, Company
URL, Company address, Company phone no. It also displays Contact person details
which can be edited.
Link: https://browser.test4you.in/company_details/index-view
Organization > Workshifts

=> This is one of the most important module. Let me explain you this with example.
Suppose you want to set a work shift of 8 hours that starts at 10AM in the morning,
having 1 hour of break and ends on 7PM in the evening, you can set these parameters
in this module. The break added here will be a compulsory break time for an
employee. If he doesn’t take a break then also he will have to stay up to 7PM to
complete his staffings. When employee comes in the morning, he will be checked in.
When he goes out of the office by facing exit camera, he will be break out, once he
come back and face in camera, he is break out and if he leaves the office after 7 PM,
he is check out. He can come back inside n number of times, the last exit time for him
in the day will be termed as checkout time.
Link: https://browser.test4you.in/work_shifts/index-view
Organization > Roles management

=> Super Admin, if wants to add multiple roles within the organization, he can do it
here. And then assign them permission in the available modules using the next
module.
Link: https://browser.test4you.in/roles/index

Organization > Role wise Permission management
=> Here there will be a list of all the available roles in the left side of the screen,
selection one will list the access of the modules in the right hand side. With the help
of checkbox you can select and unselect items. This will reflect to all the users having
that particular role when user refreshes the page.
Link: https://browser.test4you.in/permissions/index
HRMS > Time Tracker > Timesheet

=> Super Admin can see his own daily logs here. It shows Entry Time, Exit Time,
Staffing, Actual Staffing, Break, Actual Break and Comments made by user for the
day.
Link: https://browser.test4you.in/time_sheet/user-wise-report-view/self

HRMS > Time Tracker > User wise Time-sheet
=> Here Admin can see all the active users of the system. Admin can search the user
and click on any of the user. That will take Admin to a screen, where he can modify
or add the entries for the user. You also get additional features like filtering to display
any month’s data for the user or any specific date range you can choose to get data.
Link: https://browser.test4you.in/user_wise_time_sheet/user-wise-view
HRMS > Time Tracker > Date wise Timesheet

=> This is pretty similar to above module but here instead of 1 user’s all days of the
month entries, we are showing all the user’s current day staffing. So it provides a
facility to see all user’s current status from this screen. Choose any date from the
calendar and it will show you all the entries for that day.
Link: https://browser.test4you.in/date_wise_time_sheet/date-wise-view

HRMS > Time Tracker > Attendance Chart
=> This module displays all employee’s current month’s Attendance sheet, which is
quite useful for Super admin to take a whole look of all employees in a single page.
Nothing functional here except the filter.
Link: https://browser.test4you.in/attendance_chart/attendance-chart-view
HRMS > Employee Management > View User

=> This page provides the listing of all active users along with their departments as
filter. Change the department and you will only see users belong to that department.
You can view profile of employee, edit it or delete it as well from here. Add user is
also available here, which will allow super admin to add a new employee here.
Link: https://browser.test4you.in/users/list

HRMS > Employee Management > Add User
=> This page provides the facility to add new employee which will send email to the
new employee on successful account creation. Employee will then be able to login to
his account using his credentials.
Link: https://browser.test4you.in/users/add
HRMS > Employee Management > Approve User

=> If any external employee has registered, he can not login to the system until super
admin approves his request. Once approved, employee will get an email with the
password set by Super Admin and then he can login.
Link: https://browser.test4you.in/users/approve
HRMS > Qualification > Skills

=> This module allows Super Admin to add list of skills to be used in user profile
section. Skill can be edited and deleted as well.

Link: https://browser.test4you.in/skills/index
HRMS > Qualification > Education

=> This module allows Super Admin to add list of Education Qualification types to be
used in user profile section. Education Qualification can be edited and deleted as well.
Link: https://browser.test4you.in/educational_qualifications/index
HRMS > Qualification > Language

=> This module allows Super Admin to add list of languages to be used in user profile
section. Language can be edited and deleted as well.
Link: https://browser.test4you.in/languages/index

HRMS > Designation Management
=> This module allows Super Admin to add list of different Designation to be used in
user profile section. Designation can be edited and deleted as well.
Link: https://browser.test4you.in/designations/index
HRMS > Holiday Management

=> On the dashboard we can see a calendar displaying different type of leaves, which
can be added from this screen. Festival and General type of holidays can be added
right now which will reflect on the dashboard calendar.
Link: https://browser.test4you.in/holidays/index-view

HRMS > Department management
=> This module allows Super Admin to add list of different Departments to be used in
user profile section. Department can be edited and deleted as well.
Link: https://browser.test4you.in/departments/index

CHAPTER-7 CONCLUSION AND FURTHERWORK
7.1 Summary of the results
This is our first attempt in developing an website for blind which gave us a basic
understanding of development and challenges of getting correct information for
an website. The main aim of the project is to provide a user.
Advantages of your work
We are createing a site which can help to find System is to capture employee’s
check in, break in, break out and check out entries within an organization.
7.2 Future work
We are planning to expand the more functionality for user to donation the money.
We are also planning to host our web-site and launch on the internet.
Unique Features of your Project
There are basically 2 types of users in the system. 1) Super Admin and 2) Employees.
Super Admin have the access of all the modules in the system and Employees have
only access to his profile and can see the daily logs.
The most important part of the application is under the Video Recorder tab in edit
profile section. Where user need to upload a video of 15 seconds with normal specks
and without specks. This video will be trained by our backend system to recognize the
user when he is scanned by the camera in the organization premises.

CHAPTER-8 REFERENCES
https://www.hrpayrollsystems.net/hrms/
https://www.betterbuys.com/hrms/

APPENDIX A LIST OF ABBREVIATIONS
DFD- Data Flow Diagram
CFD- Control Flow Diagram
UML Diagram- Unified Modelling Language Diagram
ER Diagram- Entity Relationship Diagram
PPR- Periodic Progress Report
PMMS- Project Monitoring and Mentoring System
PSAR- Patent Search and Analysis Report
GTU- Gujarat Technological University

APPENDIX BORIGINALITY REPORT
Plagiarism Report

APPENDIX CREVIEW CARD
Review Card 1:

Review Card 2:

Review Card 3:

APPENDIX DCANVAS ACTIVITY
AEIOU canvas:

Empathy Mapping Canvas:

Ideation Canvas:

Product development Canvas:

Report

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Report

Caricato da

Copyright:

Formati disponibili

(IDP) PROJECT REPORT

Under the guidance of

Project Manager - Hardik Sonchhabda

A project report submitted to

This is to certify that research work embodied in this report entitled

External guide H.O.D.

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page I of VII

I declare that the dissertation report presented here for Bachelor of

I further declare that to the best of my knowledge, this dissertation report

Name of Student: Hemangi Pathak

Enrollment No: 160043107530

Name of Guide: Prof. Renish padariya

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page II of VII

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page III of VII

DATE:15/03/2019 NAME & SIGN OF STUDENT

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page IV of VII

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page V of VII

CANDIDATE DECLARATION ................................................................................. .ii

ACKNOWLEDGEMENT ........................................................................................... iii

LIST OF TABLE ...........................................................................................................v

CHAPTER 1 INTRODUCTION ............................................................................... 5

CHAPTER-2 LITERATURE REVIEW .................................................................. 6

CHAPTER-3REQUIREMENT ANALYSIS ............................................................ 7

3.1 Functional Requirement .................................................................... 7

3.2 Non-Functional Requirement ……………………………………...7

3.3 HardwareRequirement ...................................................................... 8

3.5Feasibility study ................................................................................... 8

3.6Testing strategies ............................................................................... 10

3.7testing tools and technologies............................................................ 12

CHAPTER-4 DATA DICTIONARY ...................................................................... 13

CHAPTER-5 UML DIAGRAMS ............................................................................ 15

5.1 Use case Diagram .............................................................................. 15

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 1 of 3

5.4Sequence Diagram(Module 2) .......................................................... 18

5.5Class Diagram .................................................................................... 19

CHAPTER-6 FORM DESIGN ................................................................................ 21

CHAPTER-7CONCLUSION & FUTUREWORK................................................ 24

7.1 CONCLUSION ................................................................................. 24

APPENDIX-A LIST OF ABBREVIATIONS ........................................................ 26

APPENDIX-B ORIGINALITY REPORT ............................................................ 27

APPENDIX-C REVIEW CARD ............................................................................ 28

APPENDIX-D CANVAS ACTIVITY .................................................................... 31

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 2 of 3

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 3 of 3

Table 1.1 Login .............................................................................................................. 2

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 4 of 3

There are basically 2 types of users in the system.

1) Super Admin and 2) Employees.

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 5 of 3

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 6 of 3

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 7 of 3

3.1 Functional Requirement

Typical functional requirements include:

3.2 Non-Functional Requirement

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 8 of 3

3.3 Hardware Requirement

 Supply, Demand and Projected Absorption

B.H.GARDI COLLEGE OF ENGINEERING & TECHNOLOGY Page 9 of 3

 The market analysis can be done in a quantitative or qualitative way, or

 The cost to conduct a full system investigation.

3.6 Testing Strategies

Objectives of Software Testing: