QR Student Attendance App

Semester- VIII

A PROJECT REPORT

Submitted by

Neil Javiya – 170200107044

Happy Manvar – 170200107066

Kwiza Kaneria – 170200107051

In partial fulfillment of the award of the degree of

BACHELOR OF ENGINEERING
in

COMPUTER ENGINEERING

Government Engineering College, Rajkot

Head of Department: Internal Guide:

Prof. Chirag S Thaker Prof. Prashant Mehta

GEC, Rajkot

Gujarat Technological University

Academic Year 2020-21
 Government Engineering College, Rajkot
Computer Department
CERTIFICATE

Date:20/04/2021

This is to certify that the project entitled QR Student Attendance App has been
carried out by NEIL JAVIYA (170200107044) under my guidance in partial
fulfillment of the degree of Bachelor of Engineering in Computer (8th
Semester) of Gujarat Technological University, Ahmadabad during the
academic year 2020-21.

Internal Guide Head of Department

Prof. Prashant Mehta Prof. (Dr.) Chirag S Thaker

Assistant Professor Professor and Head

GEC Rajkot GEC Rajkot

2
Government Engineering College, Rajkot
Computer Department
CERTIFICATE

Date:20/04/2021

This is to certify that the project entitled QR Student Attendance App has been
carried out by HAPPY MANVAR (170200107066) under my guidance in
partial fulfillment of the degree of Bachelor of Engineering in Computer (8th
Semester) of Gujarat Technological University, Ahmadabad during the
academic year 2020-21.

Internal Guide Head of Department

Prof. Prashant Mehta Prof. (Dr.) Chirag S Thaker

Assistant Professor Professor and Head

GEC Rajkot GEC Rajkot

3
 Government Engineering College, Rajkot
Computer Department
CERTIFICATE

Date:20/04/2021

This is to certify that the project entitled QR Student Attendance App has been
carried out by KWIZA KANERIA (170200107051) under my guidance in
partial fulfillment of the degree of Bachelor of Engineering in Computer (8th
Semester) of Gujarat Technological University, Ahmadabad during the
academic year 2020-21.

Internal Guide Head of Department

Prof. Prashant Mehta Prof. (Dr.) Chirag S Thaker

Assistant Professor Professor and Head

GEC Rajkot GEC Rajkot

4
 ACKNOWLEDGEMENT

We have taken many efforts in this project. However, it would not have been possible
without the kind support and help of many individuals and organizations. We would like
to extend my sincere thanks to all of them.

We are highly indebted to “Prof. Prashant Maheta” Sir for their guidance and constant
supervision as well as for providing necessary information regarding the Project Titled
“QR Student Attendance App”. We would like to express my gratitude towards staff
members of Computer Engineering Department, Government Engineering College, Rajkot
for their kind co- operation and encouragement which helped us in completion of this
project.

We even thank and appreciate to our colleague in developing the project and people
who have willingly helped us out with their abilities

Neil Javiya
Happy Manvar
Kwiza Kaneria

5
 Index
Title Page No
Acknowledgement 5

Chapter-1 INTRODUCTION 8

1.1 Current System 8

1.2 Limitations of current system 8
1.3 Goals and Objectives of our proposed system 8
1.4 Scope of system 8
1.5 Technology 8
1.6 Literature Review 9

Chapter-2 PROJECT MANAGEMENT 10

2.1 Project Planning and Scheduling 10

2.1.1 Project Development Approach and Justification 10
2.1.2 Project Plan 10
2.1.2.1 Milestones 10
2.1.2.2 Deliverables 10
2.1.2.3 Roles 10
2.1.2.4 Responsibilities 10
2.1.2.5 Resources 11
2.1.2.6 Dependencies 11
2.1.3 Schedule Representation 11
2.2 Risk Management 11
2.3 Estimation 12
2.3.1 Effort Estimation 12
2.3.2 Cost Analysis 12

Chapter-3 SYSTEM REQUIREMENT STUDY 13

3.1 User Characteristic 13

3.2 Hardware and Software Requirements 13
3.3 Constraints 13

Chapter-4 SYSTEM ANALYSIS 14

4.1 Prototype 14
4.1.1 Feature Extraction 14
4.1.2 Classification 14
4.1.3 Results 14
4.1.4 Conclusion 14
4.2 Current System 14
4.3 Problems and Weakness of Current System 14
4.4 Requirements of New System 14
4.4.1 Functional Requirements 14
4.4.2 Nonfunctional Requirements 15
4.5 Feasibility Study 15
4.5.1 Technical Feasibility 15
4.5.2 Economical Feasibility 15

6
 4.5.3 Operational Feasibility 16
4.5.4 Management Feasibility 16
4.5.5 Social Feasibility 16
4.6 Requirements Validation 16
4.7 Data Modeling 16
4.7.1 Architecture 16
4.7.2 Data Flow Diagram 17
4.7.3 Use Case Diagram 18
4.7.4 Activity Diagram 19

Chapter-5 DESIGN CANVASES 20

5.1 Empathy Canvas 20

5.2 AEIOU Canvas 20
5.3 Ideation Canvas 21
5.4 Product Development Canvas 21

Chapter-6 PROJECT PROOF OF CONCEPT (SCREENSHOTS) 22

6.1 General 22
6.2 Some Important plots for visualization 22
6.2.1 Feature Comparison 22
6.2.2 Metadata of an sample audio file in librosa library 22

Chapter-7 CONCLUSION AND FUTURE SCOPE 23

7.1 Future Scope 23

7.2 Conclusion 23

REFERENCES 24
APPENDIX 25

7
 Chapter-1 Introduction

1.1 Current System

• Following are current system available on the internet

1. Time Labs (https://www.timelabs.in/Student-Attendance-Management)
2. Finclock (https://finclock.com/attendance-system/)
3. Pocket (https://www.pockethrms.com/attendance-management-system/)
4. Greythr (https://www.greythr.com/attendance-management-software/)

1.2 Limitations

• It is not up-to-date.
• It is providing paid API call, if anyone wants to use it in any other project.
• Any software developer cannot contribute in that project because it is not open-
source project.
• It is not providing any extension to run it in background of any web browser.
• More time consuming.

1.3 Goals & Objective

1.3.1 Goals

• To provide faster and secure way to take attendance.

• To provide software as service without any financial benefits.
• To save the paper being used in conventional method.
1.3.2 Objective

• To make attendance process less time consuming and more efficient.

• To implement our programming skills to solve real world problems.

1.4 Scope

• Students/employees having internet can use this service, so its scope is internet.
• If any college or school wants to implement an online and reliable attendance
system for their students, they can use this project.

1.5 Technology

• We will develop our web application using PHP/HTML/CSS/JS.

• We will store data in relational database management system.

8
1.6 Literature

• We’ve used Google, Stack overflow, GitHub to solve our doubts.

• We’ve also referred the documentations of such open-source systems available
online.

9
 Chapter-2 Project Management

2.1 Project Planning and Scheduling

2.1.1 Project Development Approach and Justification

1. Initially, we’ve searched on internet about our project topic to get broader idea.
2. After that we have built some UML diagrams to understand how our project will
work and what features to include.
3. After that we have started implementing this project in Android Studio with Java as
programming language and PHP for web part.
4. We will deploy our web application on internet to get user feedback and
appropriate improvement will be done.

2.1.2 Project Plan

2.1.2.1 Milestone

Milestone Status
Project Title Completed
Finding Reference Completed
Planning Phase Completed
Implementation Completed
Deployment Completed
Analysis Completed
Customer Feedback Completed
Improvement Pending

2.1.2.2 Deliverables:

• We will use GitHub as our deliverables.

• We will submit our work on GitHub our branch.

2.1.2.3 Roles & Responsibilities:

1. Basic Management

• Work Distribution, content Collection

2. Transformative Conversation

• Changes in report, canvas, program etc.

3. Problem Solving Attitude

• If any problem occurs then each help each other.

10
2.1.2.5 Resources

• Computer with good internet availability

• One web server to and IDE to develop host our web application.
• To develop our web app we need integrated development environment.
• Any relational database management system to store data.

2.1.2.6 Dependencies

• During the lecture smart phone is required for attendance marking.

• Android 5.0 or Higher.

2.2 Risk Management

2.2.1 Risk Identification

• There is chance that a student mark someone else’s attendance.

• It is possible that application might not work on older devices.
• Sometimes, server might not respond resulting unable to generate QR.

2.2.2 Risk Analysis

2.2.2.1 Risk Assessment

• If application or web portal do not work as expected, users may face some
serious issues.

2.2.2.2 Risk Management

• We have evaluated all factors which causes the app or portal to misbehave
and we’ve also solved dependencies of almost all of those factors.

2.2.2.3 Risk Communication

• We provide contact us section, so clients can directly contact us.

• We are also going to push our project on GitHub, so if any user find any
bugs in app, he/she can directly pull request on GitHub.

2.2.3 Risk Planning

2.2.3.1 Risk Avoidance

• We will regularly update our application as well as web portal.

• If any user finds any security holes, we will try to manage that issue.

2.2.3.2 Risk Reduction

11
 • We will use security algorithm that monitors incoming data cannot degrade
or harm our web application.

2.2.3.3 Risk Retention

• We will store log file on server and back up the data monthly to come out
from risk retention.

2.2.3.4 Risk Transfer

• We will use auto-scaling, Http-Load balancer which will save our web
application to perform well if the number of requests is so high.

2.3 Estimation

2.3.1 Effort Estimation & Cost Analysis

• We will require 4-5 months to develop and deploy android app and web app.
• Nowadays, many web hosting sites provide free hosting for educational purpose
we have applied for that, so our cost for deployment is very minimum.

12
 Chapter-3 System Requirement Study

3.1 User Characteristic

• Any organization which require their employees or students to record their
attendance on daily basis can use our project.

3.2 Hardware & Software Requirement

• For User
• Computer & Mobile with standard configuration.
• Good Internet Availability.
• For Developers
• Hardware
• Computer or Laptop.
• Cloud Platform to deploy web application.
• Software
• Android studio for application development.
• Scripting language (HTML, CSS, JS) to improve frontend.
• RDBMS to store application data.
• Local Server for testing security of web application.

3.3 Constraint
• Low Internet Speed.
• High Rate of Incoming HTTP Request.

13
 Chapter-4 System Analysis
4.1 Prototype

4.2 Study of Current System

Following are current system available in internet

1. Time Labs (https://www.timelabs.in/Student-Attendance-Management)
2. Finclock (https://finclock.com/attendance-system/)
3. Pocket (https://www.pockethrms.com/attendance-management-system/)
4. Greythr (https://www.greythr.com/attendance-management-software/)

4.3 Problem with Current System

• It is not up-to-date.
• It is providing paid API call, if anyone wants to use it in any other project.
• Any software developer cannot contribute in that project because it is not open-
source project.
• It is not providing any extension to run it in background of any web browser.
• More time consuming.

4.4 Requirement of New System

4.4.1 Functional Requirement

• Interoperability:
• Requirement implies whether a system is interoperable across
different systems.
• Our web portal can be accessed from different OS platform, whereas
application is only available for android users.

• Security:
• Android provides in-built security feature.

14
 • Accuracy:
• It defines if a data entered into the system is correctly
calculated and used by the system and that the output is correct.
• Our QR generator algorithm which is used in our web portal will
give correct result in almost all the cases.

• Compliance:
• Such requirements validate that the developed system is compliant to
current industrial standards.
• Our web portal and android application can also be useful to Industry
and almost all government organization.

4.4.2 Non-Functional Requirement

• Performance: We will check how system responds in normal load/stress

conditions.
• Usability: It will define how many users can use this web
applications.
• Maintainability: Maintainability is often measured at code level using
Cyclomatic complexity. Cyclomatic complexity says that the lesser complex
the code is, the less hard it is to maintain the software.
• Portability: It means the ability of a system to work in different
environment if the core dependent framework stays the same.

4.5 Feasibility Study

4.5.1 Technical Feasibility

• Android studio used in our project is freely available and the technical
skills required are manageable.
• Initially the website will be hosted in free web hosting space, but later
implementations it will be hosted in paid web hosting space with sufficient
bandwidth.
• Bandwidth required in this application is very low, since it does not
incorporate any multimedia aspect.

4.5.2 Economical Feasibility

• Our economic feasibility is very less because we only need hosting space
on internet.
• For educational purpose we can also get free hosting space.
• For real time use we need cloud platform to serve our user in better way.

4.5.3 Operational Feasibility

• This application is easy to use and user-friendly.

15
 • This application can work on low bandwidth because it is not using
multimedia.
• Developers can add more features to this app because this is open-source
project.
• Engineers can report the bug and also send possible fix to that bug through
GitHub.

4. 6 Requirement Validation
• We will add valid feature suggested by user.
• We will also fix any error and security holes later detected by us or user.

4.7 Data Modeling

4.7.1 Architecture

16
4.7.2 Data Flow Diagram

-Level 0

-Level 1

-Level 2

17
 4.7.2 Use Case Diagram

18
4.7.4 Activity Diagram

19
 Chapter-5 System Design
5.1 Empathy Canvas

5.2 AEIOU Canvas

20
5.3 Ideation Canvas

5.4 Product Development Canvas

21
 Chapter-6 Project Proof Of Concept (Screenshots)
6.1 General

6.2 Some Important Plots For Visualization

6.2.1 Feature Comparison

22
 Chapter-7 Conclusion and future scope
7.1 Future Scope

• We are planning to implement GPS based System along with QR Scanning.

7.2 Conclusion

• To conclude, it is very clear that using online QR based attendance system would
be an effective solution to the conventional pen-paper based method of attendance
marking.
• Also, usage of paper will be reduced by using such methods making it more
environment friendly.
• Detailed reports and Transparency are other advantages.

23
 References
PHP - https://www.php.net/docs.php

Android - https://developer.android.com/docs

Help related to some topics of app - https://stackoverflow.com/

Video lectures -
https://www.youtube.com/watch?v=at19OmH2Bg4&list=PLu0W_9lII9aikXkRE0WxDt1
vozo3hnmtR

https://www.youtube.com/watch?v=InigFUSiPl8&list=PLu0W_9lII9aiL0kysYlfSOUgY5r
NlOhUd

24
 Appendix
Periodic Progress Report – 1

25
 Periodic Progress Report – 2

26
Periodic Progress Report – 3

27
 Periodic Progress Report – 4

28
BMC Sheet

29
 Business Model Canvas Report:

• KEY PARTNERS

➢ Finance Partners

Who provide financial support for investment, purchasing row materials and maintenance cost
etc.

Here,
• Individual Company

➢ Decision committee

It is Main Staff of Company Who Takes Major decisions about company.

Here,
• CEO
• Project Manager

➢ Training partners

Who provide work force and proper guidance.

Here,
• Developers
• App development training

• KEY ACTIVITIES

➢ Analytical Unit

It does the analysis of complete problem.

Here,
• Which functionalities should be added?
• Which are the problems are solved?

➢ Coding Unit

It performs coding of the software.

30
 Here,
• System maintenance
• Bug bounty

➢ Testing Unit

It is unit in which testing of product is done. It is helpful to maintain quality of working of

attendance system.

Here,

• Testing is done by checking various features of the app.

• KEY RESOURCES

➢ Software and Technologies:

Our main resources to develop the attendance system are included here.

Here,
• Android
• Java
• Sqlite
• Database handling

➢ Financial Capital:

Our financial resources to develop the attendance system are included here.

Here,
• Developers
• DBA.

• VALUE PROPOSITIONS

In this section we include the features which make our project more attractive.

Here,
• Automation

31
 • Prevention of proxy attendance
• Interactive UI

• CUSTOMER RELATIONSHIPS

It is all about how company maintains relationship with their customers by giving them
facilities and services.

➢ Feedback& Service

It takes complains of customers and solve their problems.

Here,
• contact info in about us page.

It is a facility provided by company to recover the error in product in minimum time period.

Here,

• Testing

• CHANNELS

In this section it includes the devices through which our attendance system can be accessible.

Here,
• Smart phones
• Tablets

• CUSTOMER SEGMENTS

In this section it includes the customers of our product.

Here,

• Colleges/University
• Schools
• Individual tutors

32
• COST STRUCTURE

It includes cost that company has to setup product.

Here,
• Software
• Maintenance

• REVENUE STREAMS
Revenue generated by product selling to consumers.

Here,
• Consumer.

33
 Patent Drafting Exercise

34
35
36
37
 Page 1

PLAGIARISM SCAN REPORT

Words 851 Date April 26,2021

Characters 6340 Excluded URL

0% 100% 0 44
Plagiarized
Plagiarism Unique Unique Sentences
Sentences

Content Checked For Plagiarism

1.1 Current System
ꞏ Following are current system available on the internet
1. Time Labs (https://www.timelabs.in/Student­Attendance­Management)
2. Finclock (https://finclock.com/attendance­system/)
3. Pocket (https://www.pockethrms.com/attendance­management­system/)
4. Greythr (https://www.greythr.com/attendance­management­software/)
1.2 Limitations
ꞏ It is not up­to­date.
ꞏ It is providing paid API call, if anyone wants to use it in any other project.
ꞏ Any software developer cannot contribute in that project because it is not open­source project.
ꞏ It is not providing any extension to run it in background of any web browser.
ꞏ More time consuming.
1.3 Goals & Objective
1.3.1 Goals
ꞏ To provide faster and secure way to take attendance.
ꞏ To provide software as service without any financial benefits.
ꞏ To save the paper being used in conventional method.
1.3.2 Objective
ꞏ To make attendance process less time consuming and more efficient.
ꞏ To implement our programming skills to solve real world problems.
1.4 Scope
ꞏ Students/employees having internet can use this service, so its scope is internet.
ꞏ If any college or school wants to implement an online and reliable attendance system for their students, they can use
this project.
1.5 Technology
ꞏ We will develop our web application using PHP/HTML/CSS/JS.
ꞏ We will store data in relational database management system.
1.6 Literature
ꞏ We’ve used Google, Stack overflow, GitHub to solve our doubts.
ꞏ We’ve also referred the documentations of such open­source systems available online.
Chapter­2 Project Management
2.1 Project Planning and Scheduling
2.1.1 Project Development Approach and Justification
1. Initially, we’ve searched on internet about our project topic to get broader idea.
2. After that we have built some UML diagrams to understand how our project will
work and what features to include.
3. After that we have started implementing this project in Android Studio with Java as programming language and PHP
for web part.
4. We will deploy our web application on internet to get user feedback and
 Page 2
appropriate improvement will be done.
2.1.2 Project Plan
2.1.2.1 Milestone
Milestone 
Status
Project Title 
Completed
Finding Reference 
Completed
Planning Phase 
Completed
Implementation 
Completed
Deployment 
Completed
Analysis 
Completed
Customer Feedback 
Completed
Improvement 
Pending
2.1.2.2 Deliverables:
ꞏ We will use GitHub as our deliverables.
ꞏ We will submit our work on GitHub our branch.
2.1.2.3 Roles & Responsibilities:
1. Basic Management
ꞏ Work Distribution, content Collection
2. Transformative Conversation
ꞏ Changes in report, canvas, program etc.
3. Problem Solving Attitude
ꞏ If any problem occurs then each help each other.
2.1.2.5 Resources
ꞏ Computer with good internet availability
ꞏ One web server to and IDE to develop host our web application.
ꞏ To develop our web app we need integrated development environment.
ꞏ Any relational database management system to store data.
2.1.2.6 Dependencies
ꞏ During the lecture smart phone is required for attendance marking.
ꞏ Android 5.0 or Higher.
2.2 Risk Management
2.2.1 Risk Identification
ꞏ There is chance that a student mark someone else’s attendance.
ꞏ It is possible that application might not work on older devices.
ꞏ Sometimes, server might not respond resulting unable to generate QR.
2.2.2 Risk Analysis
2.2.2.1 Risk Assessment
ꞏ If application or web portal do not work as expected, users may face some serious issues.
2.2.2.2 Risk Management
ꞏ We have evaluated all factors which causes the app or portal to misbehave and we’ve also solved dependencies of
almost all of those factors.
2.2.2.3 Risk Communication
ꞏ We provide contact us section, so clients can directly contact us.
ꞏ We are also going to push our project on GitHub, so if any user find any bugs in app, he/she can directly pull request
on GitHub.
2.2.3 Risk Planning
2.2.3.1 Risk Avoidance
ꞏ We will regularly update our application as well as web portal.
ꞏ If any user finds any security holes, we will try to manage that issue.
2.2.3.2 Risk Reduction
ꞏ We will use security algorithm that monitors incoming data cannot degrade or harm our web application.
2.2.3.3 Risk Retention
ꞏ We will store log file on server and back up the data monthly to come out
from risk retention.
2.2.3.4 Risk Transfer
ꞏ We will use auto­scaling, Http­Load balancer which will save our web
 Page 3
application to perform well if the number of requests is so high.
2.3 Estimation
2.3.1 Effort Estimation & Cost Analysis
ꞏ We will require 4­5 months to develop and deploy android app and web app.
ꞏ Nowadays, many web hosting sites provide free hosting for educational purpose
we have applied for that, so our cost for deployment is very minimum. 
Chapter­3 System Requirement Study
3.1 User Characteristic
ꞏ Any organization which require their employees or students to record their attendance on daily basis can use our
project.
3.2 Hardware & Software Requirement
ꞏ For User
ꞏ Computer & Mobile with standard configuration.
ꞏ Good Internet Availability.
ꞏ For Developers
ꞏ Hardware
ꞏ Computer or Laptop.
ꞏ Cloud Platform to deploy web application.
ꞏ Software
ꞏ Android studio for application development.
ꞏ Scripting language (HTML, CSS, JS) to improve frontend.
ꞏ RDBMS to store application data.
ꞏ Local Server for testing security of web application.
3.3 Constraint
ꞏ Low Internet Speed.
ꞏ High Rate of Incoming HTTP Request.

Sources Similarity
 Page 1

PLAGIARISM SCAN REPORT

Words 625 Date April 26,2021

Characters 5138 Excluded URL

0% 100% 0 29
Plagiarized
Plagiarism Unique Unique Sentences
Sentences

Content Checked For Plagiarism

Chapter­4 System Analysis
4.1 Prototype
4.2 Study of Current System
Following are current system available in internet
1. Time Labs (https://www.timelabs.in/Student­Attendance­Management)
2. Finclock (https://finclock.com/attendance­system/)
3. Pocket (https://www.pockethrms.com/attendance­management­system/)
4. Greythr (https://www.greythr.com/attendance­management­software/)
4.3 Problem with Current System
• It is not up­to­date.
• It is providing paid API call, if anyone wants to use it in any other project.
• Any software developer cannot contribute in that project because it is not open­source project.
• It is not providing any extension to run it in background of any web browser.
• More time consuming.
4.4 Requirement of New System
4.4.1 Functional Requirement
•Interoperability:
•Requirement implies whether a system is interoperable across different systems.
•Our web portal can be accessed from different OS platform, whereas application is only available for android users.
•Security:
•Android provides in­built security feature.
•Accuracy:
•It defines if a data entered into the system is correctly calculated and used by the system and that the output is correct.
•Our QR generator algorithm which is used in our web portal will give correct result in almost all the cases.
•Compliance:
•Such requirements validate that the developed system is compliant to the current Industrial standards.
•Our web portal and android application can also be useful to Industry and almost all government organization.
4.4.2 Non­Functional Requirement
•Performance: We will check how system responds in normal load/stress
conditions.
•Usability: It will define how many users can use this web applications.
•Maintainability: Maintainability is often measured at code level using
Cyclomatic complexity. Cyclomatic complexity says that the lesser complex
the code is, the less hard it is to maintain the software.
•Portability: It means the ability of a system to work in different environment if the core dependent framework stays the
same.
4.5 Feasibility Study
4.5.1 Technical Feasibility
•Android studio used in our project is freely available and the technical skills required are manageable.
 Page 2
•Initially the website will be hosted in free web hosting space, but later
implementations it will be hosted in paid web hosting space with sufficient
bandwidth.
•Bandwidth required in this application is very low, since it does not
incorporate any multimedia aspect.
4.5.2 Economical Feasibility
•Our economic feasibility is very less because we only need hosting space on internet.
•For educational purpose we can also get free hosting space.
•For real time use we need cloud platform to serve our user in better way.
4.5.3 Operational Feasibility
•This application is easy to use and user­friendly.
•This application can work on low bandwidth because it is not using
multimedia.
•Developers can add more features to this app because this is open­source
project.
•Engineers can report the bug and also send possible fix to that bug through
GitHub. 
4. 6 Requirement Validation
•We will add valid feature suggested by user.
•We will also fix any error and security holes later detected by us or user.
4.7 Data Modeling
4.7.1 Architecture
4.7.2 Data Flow Diagram
­Level 0
­Level 1
­Level 2
4.7.2 Use Case Diagram

4.7.4 Activity Diagram

Chapter­5 System Design
5.1 Empathy Canvas 
5.2 AEIOU Canvas
5.3 Ideation Canvas
5.4 Product Development Canvas
Chapter­6 Project Proof Of Concept (Screenshots)
6.1 General
6.2 Some Important Plots For Visualization
6.2.1 Feature Comparison

Chapter­7 Conclusion and future scope
7.1 Future Scope
• We are planning to implement GPS based System along with QR Scanning.
7.2 Conclusion
• To conclude, it is very clear that using online QR based attendance system would be an effective solution to the
conventional pen­paper based method of attendance marking.
• Also, usage of paper will be reduced by using such methods making it more environment friendly.
• Detailed reports and Transparency are other advantages.

References
PHP ­ https://www.php.net/docs.php
Android ­ https://developer.android.com/docs
Help related to some topics of app ­ https://stackoverflow.com/
Video lectures ­ https://www.youtube.com/watch?v=at19OmH2Bg4&list=PLu0W_9lII9aikXkRE0WxDt1vozo3hnmtR
https://www.youtube.com/watch?v=InigFUSiPl8&list=PLu0W_9lII9aiL0kysYlfSOUgY5rNlOhUd

Sources Similarity