An

Intrnship Report On
ZOHO Devloper Internship
At
Infobyd Software Soluction Pvt.Ltd

Submitted
In the Partial Fulfillment of
Bachelor of Technology
Department of Computer Science & Engineering

Mandsaur University, Mandsaur (M.P.)

(Technical University of Madhya Pradesh)
2019-2024

Submitted to: Submitted by:

Prof. Priyanka Khabiya Satya prakash
20ENG3CSE1045
 MANDSAUR UNIVERSITY, MANDSAUR
Rewas Dewda Road, SH - 31, Mandsaur, Madhya Pradesh- 458001

(SESSION 2019-2024)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

INTERNSHIP REPORT
Submitted in Partial Fulfillment of requirements for the Award of Degree of
Bachelor of Technology in Computer Science & Engineering

Mandsaur University, Mandsaur (M.P.)

Head of Dept.: Submitted By:

Mr. Prabhat Kumar Singh Satya prakash
 ACKNOWLEDGEMENT

Every training is the result of the toil of the craftsman and the sacrifice and forbearance of those
they were forced to neglect. Rubies are beneath their worth. We acknowledge our debt to those
who have contributed significantly to this Training. It is a pleasure to extend deep gratitude to
our department, for their valuable guidance and support and for providing us a good working
environment.
We thank to our Internship Coordinator Miss. Priyanka Khabiya for the helpful solutions and
comments enriched by his experience and also for pointing out mistakes and shortcomings from
time to time, which went a long way in completing the Training.

We are also thankful to Dr.Arunava Das, Dean of Academic Affairs and HOD Mr Prabhat
Kumar Singh and all the members of the staff for their support and motivation provided for this
Training. The Training would not have been a success without the encouragement and facilities
provided by help and guidance provided by colleagues, who helped us the way long.

Student Name-Satya prakash

Roll No.- 20ENG3CSE1045
CERTIFICATE TO BE
ATTACHED HERE
 MANDSAUR UNIVERSITY, MANDSAUR
Rewas Dewda Road, SH - 31, Mandsaur, Madhya Pradesh- 458001

Department of Computer Science & Engineering

APPROVAL CERTIFICATE
The Industrial Training entitled “ZOHO Devloper Intern” submitted by SATYA
PRAKASH Students of Bachelor of Engineering final year in the session 2019-24, for the
partial fulfillment of degree of Bachelor of Technology to Mandsaur University, Mandsaur is
approved for the award of degree of Bachelor of Technolohy in Computer Science and
Engineering.

Internal Examiner External Examiner

Date: Date:

Academic Coordinator: HOD Signature:

Dr.Harish Patidar Mr. Prabhat Kumar Singh

Table of Contents
Title Page i
Acknowledgement iii
Certificate iv
Approval Certificate v
Table of Contents vi

1. Company Profile INFOBYD SOFTWARE SOLUCTION PVT.LTD 1

2. Technology HTML,CSS,JS,DELUGE,CRM,CREATOR 2
2.1 Intoduction to Technologies…………………………………………………………………………. 2-4
2.1.1 Background About Technologies .
 2.1.2 …………
2.1.3 ………… version
2.1.4 …………….Application
2.2 Introduction of Language used ………………….……………………………………………………………… 4-10
2.2.1…………………...
2.2.2 ……………………………..
2.2.3 Application Framework
2.3 ….…………………………………………………………………………………………………… 10-16
2.3.1 ……………………
2.3.2 …………………………
2.4 Introduction to the Development tools…………………………………………………………………… 17
2.5 Design……………………………………………………………………………………………………………. 18-21
2.5.1 Introducing Layout
2.6 DataBase………………………………………………………………………………………………………………… 21-24
2.6.1 ……………………..
2.6.2 ………………………
2.6.3 ………………………….
2.6.4 …………………………………………
2.7 Software Requriment Specification………………………………………………………………………… 24-26
2.7.1 Existing System
2.7.2 Proposed System
2.7.3 Modules
2.7.4 HARDWARE AND SOFTWARE REQURIMENTS
2.8 CONCLUSION……………………………………………………………………………………………………………… 26
2.9 REFERENCES……………………………………………………………………………………………………………… 27
Presented by –
Satya Prakash
InfobydPvt.LtdIndore(MP)
Table of Contents
1. Introduction................................................................................................................................
1.1 Purpose…..........................................................................................................................................
1.2 Intended Audience….........................................................................................................................
1.3 Project Scope….................................................................................................................................
1.4 References….....................................................................................................................................
2. Overall Description.....................................................................................................................
2.1 Product Perspective...........................................................................................................................
2.2 Project Plan.......................................................................................................................................
2.3 Product Features...............................................................................................................................
2.4 User Classes and Characteristics......................................................................................................
2.5 Operating Environment....................................................................................................................
2.6 Data Model Design and....................................................................................................................
3. Functional Requirements............................................................................................................
3.1 Employee Details Form...................................................................................................................
3.2 Employee Details Report...............................................................................................................
3.3 Enter Time Attendance....................................................................................................................
3.4Enter Time Attendance Report................................................................................................ ......
3.5 Lunch Out Time.............................................................................................................................
3.6 Lunch In Time..............................................................................................................................
3.7Tea Out Time...............................................................................................................................
3.8Tea In Time..................................................................................................................................
3.9Employee Attendance Details Exit Time.......................................................................................
3.10Monthly Attendance Form...........................................................................................................
3.11Receipt Generation.......................................................................................................................
4.Non-Functional Requirements ...................................................................................................
4.1Usability........................................................................................................................................
4.2Security...........................................................................................................................................
4.2Performance....................................................................................................................................
5.System Requirement ....................................................................................................................
5.1Hardware........................................................................................................................................
5.2Software...........................................................................................................................................
6.Use case ..........................................................................................................................................
7.Constraints ....................................................................................................................................
8.Assumprions ..................................................................................................................................
9.Conclusion ......................................................................................................................................

1
1.Introduction
Purpose
The main purpose of this specification is to help people who will work on this
system to maintain the objectives and get started working in this project. This
specification will direct people who will work on this project step by step through
the process until they finish it successfully. This statement will describe specific
details into every step of this project that workers will immediately locate the
needs of this system to understand the purpose of doing any of the following
steps into the system.

Intended Audience
The audience of this system will be:
1. Intern
2. Employee
3.HR

This project will be managed by HR, created and developed by the IT staff
and other specialized people in the technology, such as programming,
design and others.

Project Scope
The scope of the system is to have a high-tech environment in the Office
community. That means by using the automatic attendance system, the
community will transfer to the technical environment.

That will help the community use the technology in effective ways:
1. Make the attendee process easier and effective.
2. Help Office community in the attendance process every time.
3. Mange and organize the attendance page through Canvas.

2
Overall Description

Product Perspective
 Product overview: The office employee attendance management
system is a software application that allows employees to clock in
and out of work, view their attendance records, and submit leave
requests. The system also provides managers with the ability to
track employee attendance, generate reports, and send notifications
to employees.
 Context & scope: The system will be used by employees and
managers in a corporate office setting. It will be accessible via a
web browser and will be hosted on a cloud server.
 Stakeholders & stakeholder analysis: The primary stakeholders for
the system are employees and managers. Employees will use the
system to clock in and out of work, view their attendance records,
and submit leave requests. Managers will use the system to track
employee attendance, generate reports, and send notifications to
employees.
 Business processes & usage processes: The system will support
the following business processes:
o Clocking in and out of work
o Viewing attendance records
o Submitting leave requests
o Tracking employee attendance
o Generating reports
o Sending notifications to employees
 Product requirements (including use cases): The following are the
product requirements for the system:

3
 o The system must be able to track employee attendance.
o The system must be able to generate reports on employee
attendance.
o The system must be able to send notifications to employees.
o The system must be hosted on a cloud server.This is just a brief
overview of the product perspective for an SRS document for an office
employee attendance management system. The specific requirements
for the system will vary depending on the needs of the organization.

Project Plan

This project has six phases to be completed within the time line. They are
initiating, project plan, components, process model, testing, and feedback.
The expected time for the project will take around five Days.
The project plan is in a PDF document.

2.3 Product Features

 Clocking in and out: Employees can clock in and out of work using a
web browser or mobile app. The system will automatically record the
time that the employee clocked in and out.
 Viewing attendance records: Employees can view their attendance
records at any time. The system will display the dates and times that
the employee clocked in and out, as well as any leave requests that
the employee has submitted.
 Submitting leave requests: Employees can submit leave requests
through the system. The system will send a notification to the
employee's HR once the leave request has been submitted.
 Tracking employee attendance: HR can track employee attendance
through the system. The system will display a dashboard that shows
the attendance data for all employees. HR can also generate
reports on employee attendance.
4
  Generating reports: The system can generate reports on employee
attendance. These reports can be used to track trends in employee
attendance, identify areas where attendance is low, and make
decisions about staffing levels.
 Sending notifications: The system can send notifications to
employees. These notifications can be used to remind employees to
clock in or out of work, or to notify employees of upcoming leave
requests.

These are just some of the product features that could be included in an
SRS document for an office employee attendance management system
created in Zoho Creator. The specific features included in the document
will vary depending on the needs of the organization.

Use case diagram:

5
2.4 User Classes and Characteristics

There are three types of user classes in this community:

1) Employee
2) HR
3)Office Community

2.5 Operating Environment

The office employee attendance management system will be hosted on a

cloud server. The system will be accessible via a web browser. The
following are the minimum system requirements for the system:

 Operating system: Windows7,8,10, macOS 10.15, or Linux

 Web browser: Google Chrome, Mozilla Firefox, or Safari
 Internet connection: A broadband internet connection is required to
access the system.

The system will be developed using Zoho Creator, a cloud-based

development platform. Zoho Creator is a low-code platform that allows
developers to create custom applications without writing any code.

This is just a brief overview of an operating environment section for an

SRS document for an office employee attendance management system
created in Zoho Creator. The specific system requirements will vary
depending on the needs of the organization.

Here are some additional considerations for the operating environment

section of the SRS document:

 Hardware requirements: The hardware requirements for the system

will depend on the number of users and the amount of data that will
be stored in the system.
6
  Software requirements: The software requirements for the system
will include the web browser and any other software that is required
to run the system.
 Security requirements: The system must be secure to protect the
privacy of user data.
 Performance requirements: The system must be able to handle the
expected load of users and transactions.

2.6 Data Model Design

The following are the data entities that will be used in the office employee
attendance management system:

 Employee: This entity represents an employee in the system. It

includes the employee's ID, name, email address, and department.
 Attendance record: This entity represents an attendance record for
an employee. It includes the date, time, and location of the
employee's clock in and clock out events.
 Leave request: This entity represents a leave request from an
employee. It includes the start and end dates of the leave, as well
as the reason for the leave.
 Notification: This entity represents a notification that has been sent
to an employee. It includes the message of the notification, the date
and time it was sent, and the employee who received it.

The following are the relationships between the data entities:

 Employee: An employee can have many attendance records.

 Attendance record: An attendance record is associated with a single
employee.
 Leave request: A leave request is associated with a single
employee.
 Notification: A notification is sent to a single employee.
7
This is just a brief overview of a data model section for an SRS document
for an office employee attendance management system created in Zoho
Creator. The specific data entities and relationships will vary depending
on the needs of the organization.

3.Functional Requirement
3.1 Employee Details Form:

 The form should include fields for employee details such as name,
email, date (automatically filled with the current date), phone
number, and role (with a dropdown list of options: HR, Developer,
Graphic Design, Management, Intern).

 The employee ID field should be automatically calculated using the

first 5 digits of the phone number, followed by the current 4-digit
year, and then the first 3 letters of the company name (totaling 12
characters).

3.2 Employee Details Report:

 The system should generate a report that displays all the employee
records captured in the Employee Details Form.

3.3 Attendance Entry Form:

 The form should have fields for employee ID (lookup from the
Employee Details), email (fetched from the Employee Details), enter
8
 time (automatically filled with the current time when the user
provides input).

3.4 Attendance Entry Report:

 The system should generate a report that shows all the attendance
records entered by the users, including the employee ID, email, and
enter time.

3.5 Lunch Out Time Form:

 The form should include fields for employee ID (lookup from the
Employee Details), email (fetched from the Employee Details), date
(fetched from the Employee Details), out time (automatically filled
with the current time when other fields are filled).

 Total break time should be calculated as the difference between the

lunch IN time and the lunch OUT time.

3.6 Lunch In Time Form:

 The form should include fields for employee ID (lookup from the
Employee Details), email (fetched from the Employee Details), date
(fetched from the Employee Details), IN time (the time when lunch
break ends).

3.7.8 Tea Out and Tea In Time Forms:

 Similar to Lunch Out and Lunch In forms, these forms should

include fields for employee ID, email, date (fetched from the
Employee Details), and respective in/out times.

 Total time taken for tea should be calculated.

 Lunch and Tea Time Exceed Email Notifications:

9
  If the total lunch time exceeds 45 minutes, an email notification
should be sent to the user's Gmail address provided in the
Employee Details form.

 Similarly, if the total tea time exceeds 25 minutes, an email

notification should be sent to the user's Gmail address.

3.9 Employee Attendance Detail Exit Time Form:

 The form should include fields for employee ID (lookup from the
Employee Details), email (fetched from the Employee Details), date
(automatically filled with the current date), and exit time
(automatically generated as the current time).

3.10Monthly Attendance Form:

 The form should include fields for employee ID (lookup from the
Employee Details), number, email, role (automatically fetched from
the Employee Details when filling the form), and leave (number of
leave days taken).

 Monthly present should be automatically calculated based on the

fixed number of working days (26 days) minus the leave taken.

 Salary calculation should be performed in the backend based on the

employee's role and leave taken.

3.11Receipt and Monthly Attendance Form:

10
  After submitting the Monthly Attendance Form, a receipt should be
automatically sent to the user's email address, containing all the
monthly filled details.

 The system should generate a monthly attendance report that

analyzes the records and provides insights.

4.Non-Functional Requirement

4.1:Usability

 The system should have a clean and intuitive user interface to

facilitate easy navigation and data entry.

 Error messages and notifications should be clear and concise to

assist users in understanding any issues or actions required.

4.2 Security

 User authentication and authorization should be implemented to

ensure that only authorized individuals can access and modify
employee attendance data.

 Data transmission should be encrypted to protect sensitive

information, such as employee details and attendance records.

11
4.3 Performance:

 The system should provide fast response times, ensuring that

actions such as data entry and report generation are completed
without significant delays.

 The application should be able to handle multiple concurrent

users efficiently

5. System Requirement
5.1 Hardware Requirements:

5.1.1 Sufficient processing power and memory to support concurrent user

access and database operations.

5.1.2 Stable internet connectivity to ensure uninterrupted access to the

system.

5.2 Software Requirements:

5.2.1 Zoho Creator account for system administration and application

development.

5.2.2 Google Chrome browser (latest version) for optimal compatibility

and performance.

5.2.2 Database management system compatible with Zoho Creator.

5.2.4 Proper firewall and antivirus protection to safeguard the system from
security threats.

12
6. Use Case
1.Use Case Name: Register Employee
Actors: Administrator
Description: The administrator registers a new employee in the
attendance system by providing their name, email, phone number,
role, and automatically generating the employee ID based on the
phone number and current year.

2.Use Case Name: View Employee Details Report

Actors: Administrator
Description: The administrator retrieves and views a report
containing all the employee details, including name, email, phone
number, role, and employee ID.

3.Use Case Name: Enter Attendance Time

Actors: Employee
Description: The employee enters their attendance time by selecting
their employee ID, which is retrieved through a lookup from their
employee details. The employee's email, phone number, and the
current time are automatically populated. The entered attendance
time is recorded in the system.

4.Use Case Name: Record Lunch Out Time

Actors: Employee
Description: The employee records their lunch out time by selecting
their employee ID, which is retrieved from their employee details.
The employee's email, date, and current time are automatically
populated. The lunch out time is recorded in the system.

5.Use Case Name: Record Lunch In Time

Actors: Employee
Description: The employee records their lunch in time by selecting
their employee ID, which is retrieved from their employee details.
The employee's email, date, and the current time are automatically
populated. The lunch in time is recorded in the system, and the total
break duration is calculated.

13
6.Use Case Name: Generate Lunch Time Exceeded Email
Actors: System
Description: If the total lunch break duration exceeds 45 minutes,
the system automatically sends an email to the employee's Gmail
address, notifying them about the lunch break time exceeding the
allowed limit.

7.Use Case Name: Record Tea Out Time

Actors: Employee
Description: The employee records their tea out time by selecting
their employee ID, which is retrieved from their employee details.
The employee's email, date, and current time are automatically
populated. The tea out time is recorded in the system.

8.Case Name: Record Tea In Time

Actors: Employee
Description: The employee records their tea in time by selecting
their employee ID, which is retrieved from their employee details.
The employee's email, date, and the current time are automatically
populated. The tea in time is recorded in the system, and the total
tea time taken is calculated.

9.Use Case Name: Generate Tea Time Exceeded Email

Actors: System
Description: If the total tea time taken exceeds 25 minutes, the
system automatically sends an email to the employee's Gmail
address, notifying them about the tea break time exceeding the
allowed limit.

10.Use Case Name: Record Exit Time

Actors: Employee
Description: The employee records their exit time by selecting their
employee ID, which is retrieved from their employee details. The
employee's email, date, and the current time are automatically
populated. The exit time is recorded in the system, and the total
office duration is calculated.

14
11.Use Case Name: Fill Monthly Attendance Form
Actors: Administrator
Description: The administrator fills the monthly attendance form by
selecting the employee ID from employee details, and the number,
email, role are automatically fetched. The administrator enters the
number of leaves taken by the employee, and the monthly present
is calculated automatically based on the total office days (26) minus
leaves. The salary is also calculated based on the employee's role
and leave data in the backend. After submitting the form, a receipt is
automatically sent to the employee's email address.

12.Use Case Name: Analyze Reports and Fill Monthly Attendance

Form
Actors: Administrator
Description: The administrator analyzes various reports generated
from the attendance system, such as employee attendance records,
lunch and tea break durations, and office durations. Based on these
reports, the administrator fills the monthly attendance form
accurately.

Use Case Diagram-

15
7. Constraints-
Internet Connectivity: The system is dependent on a stable internet
connection for users to access and use the application effectively.

Compatibility: The system is designed to be used specifically with

the Google Chrome browser. Users must have access to devices
that support Chrome for optimal functionality.

Zoho Creator Account: Users, including administrators and

employees, must have valid Zoho Creator accounts to access and
utilize the attendance system.

Data Accuracy: The accuracy of employee details, such as phone

numbers and names, is crucial for generating correct employee IDs
and calculating attendance durations. It is important to ensure the
accuracy of data entry during the initial setup and ongoing
maintenance of the system.

Lunch Time Limit: The system incorporates a constraint for lunch

duration. If the total lunch break exceeds 45 minutes, an email
notification is sent to the user's provided Gmail ID. The lunch time

16
limit is predefined and cannot be modified through the system
interface.

Tea Time Limit: Similar to lunch, the system also includes a

constraint for tea breaks. If the total tea break duration exceeds 25
minutes, a notification is triggered. The tea time limit is predefined
and not configurable through the system interface.

Monthly Attendance Calculation: The calculation of monthly present

days and salary is based on a fixed assumption of 26 working days
in a month. The system automatically deducts leave days from the
total working days to calculate present days. This assumption
remains fixed and cannot be modified through the system interface.

Role-Based Salary Calculation: Salary calculation is dependent on

the roles assigned to employees. The system must have accurate
and up-to-date role assignments to calculate salaries correctly.

Email Receipts: The system automatically generates and sends

email receipts to users upon form submission. It is crucial to ensure
the accuracy of email addresses provided by users for receipt
delivery.

8.Assumptions-
User Familiarity:
 Users of the system are assumed to have basic computer
literacy skills and familiarity with web-based applications.
 Employees and administrators will receive proper training and
guidance on using the system effectively.

Reliable Internet Connection:

 It is assumed that users will have a reliable internet
connection to access the Attendance System through the
Google Chrome browser.

17
  The system's availability and performance are dependent on a
stable internet connection.

Employee Information Accuracy:

 It is assumed that the employee details provided during
registration, such as name, email, phone number, and role,
will be accurate and up-to-date.

 The accuracy of employee information is crucial for generating

employee IDs, attendance records, and other relevant reports.

Timezone Consistency:

 The system assumes that all users, including employees

and administrators, operate within the same timezone.
 Time calculations, such as current date and time,
attendance timings, and office duration, will be based on
this common timezone.

Proper Hardware and Software:

 Users are assumed to have access to desktop or laptop
computers with compatible hardware and a supported
version of the Google Chrome browser.The system's
performance and functionality are optimized for these
standard hardware and software configurations.

Compliance with Data Privacy Regulations:

 It is assumed that the organization using the Attendance
System will comply with applicable data privacy
regulations, ensuring the security and confidentiality of
employee data.
 Adequate measures will be implemented to protect
sensitive information and ensure compliance with relevant
laws and regulations.

System Maintenance and Upgrades:

18
  The system assumes that regular maintenance activities,
including bug fixes, security updates, and system upgrades,
will be performed as required.
 System administrators will be responsible for maintaining the
system's stability and ensuring its continuous availability.

Email Delivery and Receipt:

 It is assumed that the provided user email addresses are valid
and capable of receiving emails.
 The email delivery process relies on the proper functioning of
the email server and the user's email provider's policies and
settings.

Calculation Accuracy:
 Calculations for employee IDs, attendance duration, monthly
attendance, and salary calculations are assumed to be
accurate based on the given formulae and business rules.
 The system's calculations will be thoroughly tested and
validated to ensure accuracy.

User Acceptance and Feedback:

 The success of the Attendance System relies on user
acceptance and feedback.
 Users are encouraged to provide feedback on usability,
functionality, and any issues encountered during system
usage to facilitate continuous improvement.

9.Conclusion:
In conclusion, the Attendance System created using Zoho Creator
through the Google Chrome browser offers a comprehensive
solution for efficient employee attendance management. The
system incorporates various forms, such as Employee Details,
Attendance Enter Time, Lunch Out Time, Lunch In Time, Tea Out,
Tea In, Employee Attendance Detail Exit Time, and Monthly

19
 Attendance. These forms facilitate data entry, record-keeping, and
reporting.
By leveraging the system's capabilities, organizations can easily
capture and maintain employee details, track attendance times,
monitor lunch and tea breaks, calculate office durations, and
generate monthly attendance reports. The system ensures
accuracy, automation, and timely notifications, such as email alerts
for lunch and tea break durations exceeding specified limits.
With its user-friendly interface and intuitive workflows, the
Attendance System simplifies the attendance management process,
enhancing productivity and eliminating manual errors. Furthermore,
the system supports scalability, security measures, and compatibility
with the latest technology standards.
By implementing this Attendance System, organizations can
effectively streamline attendance tracking, simplify leave
management, generate accurate monthly attendance reports, and
calculate salaries based on employee roles and leave days. The
system optimizes efficiency, ensures data integrity, and improves
overall workforce management.
In summary, the Attendance System offers a reliable, user-friendly,
and efficient solution for organizations to manage employee
attendance, ultimately contributing to better workforce productivity
and streamlined administrative processes.

******************************************

20