G63 Report

Geeksforgeeks.
org Web Automator
A Project Report
on
Renewed Product Management
Submitted in partial fulfillment of the requirements

for the award of the degree of
Bachelor of Technology
in
Computer Science & Engineering
Submitted By
Mudit Arora (2818053)
Rajdeep (2818056)
Shubham Yadav (2818030)
Under the Supervision of

MS. Alankrita Aggarwal
Asit. Prof. (PIET)
Panipat Institute of Engineering & Technology, Samalkha, Panipat

Affiliated to
Kurukshetra University Kurukshetra, India

(2018-2022)
G-63 Panipat Institute Of Engineering And Technology Page-1

Geeksforgeeks.org Web Automator
CANDIDATE’S DECLARATION:
We hereby declare that the work presented in this training report entitled
“GEEKSFORGEEKS WEB AUTOMATOR”, submitted in partial fulfillment of the
requirement for the award of the degree of Bachelor of Technology in COMPUTER
SCIENCE ENGINEERING, submitted to Panipat Institute of Engineering &
Technology, Kurukshetra University, Kurukshetra, India is an authentic record of my
own work carried out during the period from 10/AUG/2021 to 10/JAN/2022 under the
guidance of Ms. Alankrita Aggarwal.
The work reported in this project report has not been submitted by me for the award of any other
degree or diploma.
Date: 10.01.2022
Mudit Arora 2818053
Rajdeep 2818056
Shubham Yadav 2818030
Place: PIET, Samalkha

Acknowledgement
It is my pleasure to be indebted to various people, who directly or indirectly contributed in

the development of this work and who influenced my thinking, behavior, and acts during
the course of study.
I offer our special thanks to our Project guide Ms. Alankrita Aggarwal, Assistant Professor,
P.I.E.T, without his help and support throughout this project would not have been this
success. I am thankful for his support, cooperation, and motivation provided to me during
the training for constant inspiration, presence and blessings.
We also extend our sincere appreciation to Mr. Gaurav Gambhir who provided his valuable
suggesstions and precious time in accomplishment of the project report. Lastly I would like
to thank the almighty and our parents for the moral support and my friends with whom I
shared my day to day experience and received a lot of suggestions that improved my
quality of work.
Name: Mudit Arora

Roll No. 2818053
Name: Rajdeep
Roll No. 2818056
Name: Shubham Yadav

Roll No. 2818030

ABSTRACT:
This project is aimed at Automating Web Process as well as Fetching the high end data from
the most worldwide used programing website named Geeksforgeeks.org. Automation is
Focused at Node.js module puppeteer which provides high level API to Control Chromium.
It is a Node.js based like script which enables web automation to entitle at a good pace, and
maintaining and analyzing various HTML Tags in the developer tools sections of the
website. Main focus of this system is all the educational organizations as well as students
which are preparing for the Interviews For Software Related Companies which require easier
navigation of Questions on day to day basis. This system comes equipped with capabilities
of high end storage across folders, based on Specific companies, such as Amazon, Adobe,
Microsoft, The most frequently asked Questions to the latest by date are stored in a Company
specific pdf files. This makes an ease to use interface that reduces the time spent on
managing all day to day Questions, as compared to traditional pen and paper method and
can increase the productivity of Students.

Table Of Contents
1)DECLARATION ......................................................................................................................... ii
2) CERTIFICATE ........................................................................................................................ iii

3) ACKNOWLEDGEMENTS ........................................................................................................ iv
4) ABSTRACT............................................................................................................................. v
5) TABLEOFCONTENTS ............................................................................................................. vi
LISTOFTABLES ............................................................................................................................... xi
LISTOF FIGURES .......................................................................................................................... xiii
CHAPTER1: INTRODUCTION ........................................................................................................... 1
1.1 Topic of the System .................................................................................................... 1

1.2 Project Abstract .......................................................................................................... 1
1.3 Purpose of the System ................................................................................................ 1
1.4 Target User ................................................................................................................. 2
1.5 Topic Background ....................................................................................................... 2
1.6 Problem Context ......................................................................................................... 3
1.7 Rationale behind the System: Why do we need this System? ...................................... 3
1.8 Objectives of the System............................................................................................. 5
1.8.1 Project Objectives ............................................................................................... 5
1.8.2 Learning Objectives ............................................................................................. 6
1.9 Scope of the System.................................................................................................... 7
1.10 Limitation of the System ............................................................................................. 7
1.11 Assumptions Made ..................................................................................................... 7
1.12 Success Criteria ........................................................................................................... 8
1.13 Functionalities of the System ...................................................................................... 8
1.13.1 Core Features...................................................................................................... 8
1.13.2 Enhanced Features .............................................................................................. 9
1.13.3 Special Features ................................................................................................ 10
1.14 Conclusion ................................................................................................................ 11
CHAPTER 2: PROBLEM DESCRIPTION ............................................................................................ 12

2.1 Current Problem Description .................................................................................... 12

2.1.1 Description of Problem Area ............................................................................. 12
2.2 Problem Importance and Justification ....................................................................... 12
2.3 Proposed Solution..................................................................................................... 13
2.4 Nature of Challenge .................................................................................................. 14
2.4.1 Domain Challenge ............................................................................................. 14
Technical Challenge........................................................................................... 14
2.5 Feasibility Study ........................................................................................................ 15
2.5.1 Technical Feasibility .......................................................................................... 16
2.5.2 Economic Feasibility .......................................................................................... 17
2.5.3 Schedule Feasibility ........................................................................................... 17
2.6 Conclusion ................................................................................................................ 18
CHAPTER 3: LITERATURE REVIEW ................................................................................................. 20
3.1 Introduction to Literature Review ............................................................................. 20

3.2 Advanced Preliminary Research ................................................................................ 20
3.3 Academic Research ................................................................................................... 21
3.3.1 Visualized Report Making Technology ............................................................... 21
3.3.2 Microsoft Power Platform Concepts .................................................................. 21
3.3.3 Human Computer Interaction Principles ............................................................ 22
3.4 Domain Research ...................................................................................................... 23
3.4.1 Power Apps and Power Bi ................................................................................. 24
3.4.2 Power Apps and Power Bi Architecture ............................................................. 25
3.4.3 Security and Permissions ................................................................................... 27
3.5 Market Review.......................................................................................................... 27
3.6 Product Analysis ....................................................................................................... 31
3.6.1 Qualitative Analysis ........................................................................................... 31
3.6.2 Quantitative Analysis ........................................................................................ 32
3.7 Critical Evaluation of Literature Review ..................................................................... 32
3.8 Critical Evaluation of Market Review ......................................................................... 34
3.9 Critical Success Factor ............................................................................................... 34
3.10 Conclusion ................................................................................................................ 34

CHAPTER 4: RESEARCH METHODS ................................................................................................ 35
4.1.1 Primary Research .................................................................................................. 35

4.1.2 Questionnaire ....................................................................................................... 35
4.1.3 Interview........................................................................................................... 43
4.2 Secondary Research .................................................................................................. 45
4.2.1 Technical Research ............................................................................................ 45
4.2.2 Development Methodology............................................................................... 52
4.2.3 Development Plan............................................................................................. 55
4.3 Conclusion ................................................................................................................ 57
CHAPTER5: ANALYSIS ................................................................................................................... 58
5.1 Analysis of Questionnaire ......................................................................................... 58

5.1.1 Overall Conclusion of Questionnaire ................................................................. 58
5.2 Overall Conclusion of Interview .............................................................................. 58
CHAPTER 6: SYSTEM DESIGN ........................................................................................................ 59
6.1 Introduction.............................................................................................................. 59
6.2 Designing of Power Apps .......................................................................................... 60
6.3 Designing of Database (Google Sheets) ..................................................................... 67
6.4 Designing of Power BI………………………………………………………………..63
CHAPTER7: IMPLEMENTATION ..................................................................................................... 73
7.1 Introduction.............................................................................................................. 73
7.2 Tools used for Implementation ................................................................................. 73
7.3 Implementation Plan…………………………………………………………………..73
7.3.1 Implementation Approach ................................................................................ 73
7.3.2 Implementation Approach Steps ....................................................................... 74
7.4 Implementation of Complex Modules ....................................................................... 75
7.5 Technical Quality and Other Features ....................................................................... 85
CHAPTER8: TESTING ..................................................................................................................... 99
8.1 Introduction.............................................................................................................. 99
8.2 Need of Testing......................................................................................................... 99
8.3 Test Plan ................................................................................................................... 99
8.3.1 Type of Testing.................................................................................................... 100

8.3.2 Pass/Fail Criteria ................................................................................................. 101

8.4 Point of Contact of Troubleshooting Purpose .......................................................... 102
8.5 Testing Duration ..................................................................................................... 102
8.6 Criteria of Test Cases .............................................................................................. 102
8.7 Technical requirements for Testing ......................................................................... 103
8.8 Users Involved in Testing ........................................................................................ 103
8.9 Unit Testing ............................................................................................................ 103
8.9.1 Justification for unit testing ............................................................................. 103
8.9.2 Black box testing (Functional Testing) .............................................................. 104
8.9.3 White Box Testing (Conceptual Testing) .......................................................... 112
8.10 Integration Testing.................................................................................................. 124
8.10.1 Technique used for Integration Testing ........................................................... 124
8.10.2 Justification for Integration Testing ................................................................. 124
8.11 System Testing ........................................................................................................ 127
8.11.1 Justification for System Testing ....................................................................... 127
8.11.2 System Testing for User Module ...................................................................... 127
8.12 Compatibility Testing .............................................................................................. 129
8.12.1 Justification for Compatibility Testing .............................................................. 129
8.13 GUI Testing ............................................................................................................. 131
8.14 Usability Testing and its Justification ....................................................................... 132
8.14.1 User Acceptance Testing (UAT) ........................................................................... 134
8.14.2 Justification for User Acceptance Testing ........................................................ 134
8.15 Test Schedule ...................................................................................................... 134
8.16 Documentation testing ........................................................................................... 136
8.17 Conclusion .............................................................................................................. 137
CHAPTER 9: CRITICAL EVALUATION ............................................................................................ 139
9.1Critical Evaluation.......................................................................................................... 139
9.2. Factors of Benefit (Usefulness of System to Target Audience) ...................................... 139
9.3 Comparison with Other Systems ............................................................................. 140

9.3.1 Success Assessment ....................................................................................... 140
9.3.2 Degree of Success ........................................................................................... 141
9.3.3 Critical Appraisal ............................................................................................. 141

CHAPTER 10: CONCLUSION ........................................................................................................ 143
10.1 Success Criteria ................................................................................................ 143

10.2 Limitations and Errors in the Developed System: .............................................. 143
10.3 Future Enhancement ........................................................................................ 143
10.4 What would have been done if given time to redo the project? ........................ 143
10.5 Computational Challenges ................................................................................ 144
10.6 Learning Experience Gathered .......................................................................... 144
10.7 Conclusion........................................................................................................ 145
CHAPTER11: REFERENCES .......................................................................................................... 147
11.1 Websites ........................................................................................................................ 147
11.2 References ..................................................................................................................... 147
List of Tables
Table 1: Tangible Benefits………………………………………………………………………4
Table 2: Intangible Benefits……………………………………………………………………. 5
Table 3: Core Feature……………………………………………………………………………9
Table 4: Enhanced Features………….………………………………………………………….9
Table 5: Special Features………………………………………………………………………10
Table 6: Core Features…………………………………………………………………………10
Table 7: Enhanced Features……………………………………………………………………11
Table 8: Special Features……………...……………………………………………………….11
Table 9: Hardware Resources………………………………………………………………… 16

Table 10: Software Resources…………………………………………………………………17
Table 11: Resources for Execution…….………………………………………………………17
Table12: Books References for Academic Research…………………….…………………….23
Table 13: Journals References for Academic Research……………………………………….23
Table 14: Market Review for Users…………………………………………...………………29
Table 15: Market Review for User…………………………………………………………….31
Table 16: Qualitative Analysis for User.………………………………………………………31
Table 17: Quantitative Analysis for Users…………………………………………………….32

Table 18: Questionnaire for Customer………………………………………………………...38

Table 19: Questionnaire for Developer…...……………………………………………………41
Table 20: Interview Question for Developer……...………………………………………… . 44
Table 21: Comparison between Power Apps and Traditional App Development……...… …. 48
Table 22: Phases of V-Model Methodology……………………………………………………49
Table 22: Development Plan.………………………………………………………….57
Table32: Testing Description………………………………………………………………….100
Table33: Point of contact for troubleshooting purpose………………………….…………….101
Table34: Testing duration…………………………………………………………...………...101
Table35: Technical requirements for testing………………….………………………………102
Table36: Registration check…………………………………………………………………..104
Table37: Blackbox testing of landing screen…………………………………………………...104
Table38: Blackbox testing of personal detail modules…………………………………………105
Table39: Blackbox testing of attendance system……………………………………………….107
Table40: Blackbox testing of sessional module………………………………………………. 108
Table41: Blackbox testing of assignment module…………………………………………… 108
Table42: Blackbox testing of Library module………………………………………………….110
Table43: Blackbox testing of Power Bi………………………………………………………...111
Table44: Whitebox testing of attendance system………………………………………………117
Table45: Whitebox testing of Library system………………………………………………….122
Table46: integration test-personal detail and attendance system………………………………124
Table47: integration test-personal detail and Sessional module………………………………. 124
Table48: integration test-personal detail and assignment module……………………………..125
Table49: integration test- Power apps and Power-Bi…………………………………………. 125
Table50: System testing………………………………………………………………………...128
Table51: Compatibility testing……………………………………………………………… 130
Table52: GUI test………………………………………………………………………………131
Table53: Questionnaire for usability testing………………………………………………… 132
Table54: Rating criteria for usability testing………………………………………………….. 132
Table55: Usability Test……………………………………………………………………… 133

Table56: Test schedule for UAT……………………………………………………………….133
Table57: user acceptance test…………………………………………………………………. 135
Table58: Documentation Testing………………………………………………………………135
Table59: Factors of Benefits………………………………………………………………… 139
Table60: Comparison with another system…………………………………………………….139
Table61: Success assessment……..…………………………………………………………….140

2.6.1

CHAPTER 1: INTRODUCTION:
Title: - “Geeksforgeeks Web Automator.”
Project Abstract :
The project “GEEKSFORGEEKS.ORG WEB AUTOMATOR.” Is a Automation based

Software in which User can have a Rich Collection Of Preparation Resources, stored on the
Local Computer System in the most User readable form. on Running a Single command on
the Integrated Terminal and can have Segregated Questions set, magnificently stored in pdf
files, with clickable links, to hover the particular, question selected by the user. Utilizing
which one can study thoroughly with compactness.(for managing the useful set of resources.
Specifically set of DSA Questions most frequent asked in a coding interview by any of the
one Company). Moreover, It is focused on less user tension making them free to prepare for
a specific company they want to prepare for them and Also to have a checklist for the same,
so that they can track what they are prepared with. This makes high level Api Calls to enable
Chromium to work and carry on with automation.
Purpose of the System:

This system will reduce our effort to great extent, as in this time of technologies where
everything is on our fingertips the student will not be manually searching for each company’s
resources to be prepared with to crack the coding Interview. but everything would be done
through the website only. All the necessary data will be stored on to the local system and the
folder name initialized by the user. The purpose of the system is to provide easiness to the
People preparing for the upcoming coding interview, Thereby maintain the order records.
There are lot of websites which claims to provide such type of features. But this software
fetches data with most ease, the users. In the existing situation the users have manually be
in finding of useful set of question s with solutions, But this all the process come to a single
place.

The proposed system provides the features to maintain and study Differently with different
logical Stuff. within one place with the help of laptops in the database..
Target User:
Whenever planning is done to make a software, we always conduct a research on the users
who are going to use the website. So, we decided to make a Web Automation And Web
scraping based software or say script. – Geeksforgeeks.org web Automator. This system is
for all the students and working professionals and the users of the colleagues well as
teachers, 1. Students who are preparing for the upcoming coding tests and interviews,
Working Technical Professionals who want a switch from their current company require
same preparation resources to excel in the Interview The college teachers or the core
placement team of a particular college to make their students inclined towards a particular
company. In a more efficient manner by providing them with company specific, Questions,
and other stuff.
Topic Background:
As we realize that the web is a significant part in each individual's life and everything in this
world is advancing according to the innovations happening every day. At the beginning of
present-day time frame, Computers are assumed as a significant part and as the innovation
extends everything has changed and the PCs became workstation PCs, super PCs, etc. Later
built up the portable innovation and now mobile got the opportunity to be everything.
Everything made straightforward utilizing portability.
From last few decades, the usage of mobile devices has increased a lot, due to which day to
day task can be performed very easily. In addition, with the advancement of wireless
technologies, wireless networks have taken over the entire world. Nowadays, viewing and
maintaining of data on the internet has become very easy and secured. Using the Internet,
that data can be seen anywhere in the world on any device with internet facility.
Since people have started to use mobile phones more than the web browser, there arise the
new opportunities to build this type of software.

Problem Context:
Every user maybe a student or working professional or be it any person who is preparing for
coding tests and upcoming coding interviews, And Lets say one wants to prepare for a
company named “MAQ Software” then user have to hover to the Google chrome browser or
any web browser and manually search for the content to want to reduce their effort of
hovering throughout the web.. All of us require some types of services, which reduces our
efforts to do our tasks. Devices can help to solve these problems of the canteen owner to
maintain the questions details at one place. There are not many websites which provide these
types of functionalities. We are in 21 st century where everyone likes to perform daily tasks
on Devices. The development and implementation of website which are more effective and
simpler than the current system. We feel hard to take the orders manually and for the users
to go to the different websites. be used easily anytime anywhere to view update the details.
Also, the system is provided with a feature to store specific, Company specific pdf files.
With Clickable links which hover to the Exact question clicked by the user
Rationale behind the System: Why do we need this System?

The problems that got discovered at the time of survey needs to be resolved so the conductor
of the research has decided to build such a system that would focus on providing solutions
for the above-mentioned problems.
Benefits of the System: What are the potential benefits derived?
Upon implemented, the system could bring about significant tangible and intangible
Benefits:

S. No. Tangible Benefits Description
Users will not have to pay any fees for using this
platform on any device. Everything in this system is

1. No investment
provided for free user can use any interface with
Without any restriction in the system.
This system can be used anywhere.

Accessibility of
2. System
3. Data Validation Validation of data is done to stop false entry.
4. User can view website view carrying out automation and

User View scrapping process as well as files on computer.
5. Who Can The Students, Working Professionals, And Teachers.
6. Accessibility User has the flexibility of using their devices to order
from the college canteen which saves their time.
7. Automatically stores When data is entered in website the data gets saved in
in Database
Proper formats in the Local Machine.
Intangible Benefits:
S. No. Intangible Benefits Description

It reduces our effort to great extent. For example if the

user has to prepare for “Amazon” Then he/she has a
specific company wise Allotted data in a pdf format
which contains most recently as well as frequently
1.
asked Questions by the respective company. Maybe it’s
Reduces Effort
amazon or any other.
This system ensures that user gets value of their time

and
2. Time Saving
don't have to rely upon any other website for this
purpose.
The script that is developed is very easily adaptable by

3. User Friendly the person who has some knowledge of using the
Interface
devices.
4. Customer GUI will be user-friendly and easy to use which will

Satisfaction
Result in improved satisfaction of the users.
5. Transparency This system will provide transparency as all the menu
changes will be done by the owner.
Maintenance of this is painless for its user. The
website will need no version updates and hence require

6. Maintainability
no maintenance until the user transforms the settings
accordingly.
7. Ease of learning and Keeping in mind the target audience, the software will be
Usability. designed accordingly for them.

Objectives of the System:
In order to achieve our goals of the system, it is necessary to achieve the objectives of the
system. The prime objective is to build such a platform for users which will resolve the
problem of maintain questions at single place with the help of the device. There are very few
chances of fake entry as data entered is validated. The other objectives are summarized
below:
 Users will not have to pay any fees for using this platform on any device. Everything
in this system is provided for free user can use any interface with without any
restriction in the system.
 It reduces our effort to great extent. For example if the user has to prepare for
“Amazon” Then he/she has a specific company wise Allotted data in a pdf format
which contains most recently as well as frequently asked Questions by the respective
company. Maybe it’s amazon or any other.
 This system ensures that user gets value of their time and don't have to rely upon any
other website for this purpose.
 User can view website view carrying out automation and scrapping process as well
as files on computer.
 This system will provide transparency as all the menu changes will be done by the
user.

 Maintenance of this is painless for its user. The website will need no version updates
and hence require no maintenance until the user transforms the settings accordingly.
Scope of the System:
The proposed system will be beneficial to colleges in many ways. The “Geeksforgeeks.com
web Automator” is actually made to change the traditional way of users giving orders in the
college canteen and the canteen owners taking the orders manually. So, its scope is not only
limited to colleges and universities. It can also be used in the canteen of the organizations.
The “Geeksforgeeks.com web Automator” will save a lot of time
Main focus of this system is to maintain security and services to the layman so that they can
fetch their details whenever they require it is one of the main mottos of this system.
Limitation of the System:
Limitations are always a part of every project. The project scope is limited to a confined
boundary as listed below:
Theuserwillneedaninternetconnectionforrunningtheplatformandperforming of tasks on it.
The website requires professional E-mails to work.
The website after sometimes requires paid plans to work.
Asumptions Made:

This website is although made user friendly but even then, there are some assumptions that
need to be made before the development of the website:
Users need to have basic knowledge of using the devices.
Great information on English, as well as nuts and bolts of Internet is required, for
example client should be a PC proficient.
The device users have not yet found such a website and encountered any secure
solution to protect the data from being stolen or mishandled by anyone.
The user of the system, is expected to have any device with a good Internet
Connection.
Success Criteria:
Success Factors depends upon how deeply the developer understands and use the experience
gained from the surveys done and websites viewed for the review and how proficiently the
engineer splits the issues looked in the system that led to advancement of such a system.
Website works find and is compatible with mentioned devices. Website will be of no
use if it is unable to run properly on the devices.There should not be any errors when it
is working on physical devices.
Framework meets all prerequisites of the proposed arrangement. In the event that the
website gives wanted results and produces expected yield for example in the event that
it is meeting users’ prerequisites, passing of above-mentioned functionalities. Website
must satisfy the center just as improved framework necessities referenced previously.
Project will be treated as constructive if the user gives approval. The developer will be
able to provide successful implementation of the system in terms of interactivity,
effectiveness and efficiency.
Functionalities of the System:
The proposed system having some core, enhanced and some special functionality. So, let’s
know them one by one and use of this functionality in this system.
Functionality Description
Geeksforgeeks.org – Web Automator
Details of the User The user must login in Geeksforgeeks.
It opens in Chromium which takes less Space saves time is

Web Browser more compatible then other web browsers.
Downloading the Allows the user to download the all the Questions and there
Question Sheet practice links for various companies mentioned in
Geeksforgeeks.org .
Conclusion:
The Chapter 1 incorporates the foundation concrete for the framework. Examining the
framework has gathered the motivation behind the objectives/destinations of the framework.
After the reason for the framework is recognized, the engineer at that point concocted the
advantages of the framework to its expected end-client and how the framework can profit its
clients. The designer at that point developed the attractive highlights to be executed in the
proposed framework to determine the issues that were recognized in the difficult setting
segment. The section has additionally incorporated the expectations the framework will
create after it is finished. The impediments for the framework have additionally been
recognized that restricts the extent of the proposed project.

Chapter 2: Problem Description
Current Problem Description:
After the analysis of the system to be made, the developer (researcher) has identified some
of the problem of the website which are depicted underneath:
Description of Problem Area:

Downloading Questions Manually: Event this time when technology has grown so
much the download of the question .
Users searching: In colleges the students has to go to a particular site and find the
suitable material for preparation
Having : A lot of users take their resource from online site.
Mess of Resources : Due to the chaos in the web, a student gets distracted by a hell lot
of resources.
Reliability: There is no such system developed which offers to give offline questions
accessibility to the user.
Problem Importance and Justification:
The solution for the current system is to develop a platform which will figure out all the
above issues. The proposed framework will work upon the current issues and will defeat the
issue that it has at this moment:
Taking Orders Manually : Currently the orders in the college canteen by the canteen
owner is taken manually which takes a lot of time.

Proposed Solution
Nature of Challenge
To develop this website, the developer would need to go through some significant
difficulties during the development stage like:
Implementation: To implement the concepts practically on to the Python

Language.
Synchronization: The primary challenge in developing this website would be to
communicate with the database in order to sync with the Python Language to provide
the relevant data from the source.
Interaction Principles: To understand the interaction principles between the human a

and the technology to develop the website keeping in mind the implementation of all
those principles which will justify the successful implementation of the min platform.
Sharing services: To understand how to share the application on the Database

environment with all the required permissions.
Technical Challenge
The challenges that would come on the way of the researcher while working on the
technology area are as follows:
JavaScript Language: This is an easy one, but surprisingly common. A lot of times
this can be blamed on poor documentation. Maybe the endpoints do not explicitly say what
methods are supported between GET/POST/PUT etc., or they have the wrong verb.
Tools can also play tricks on you if you're not careful. For example, let's say you want to
make a GET request with a request-body (not a great practice, but it happens). If you make
a curl request using the -d option, and don't use the `-XGET` flag, it will automatically
default to POST and include the `Content-Type: application/x-www-form-urlencoded`
header.

Platform and I am totally unknown about this platform, off-course I have started learning it
but still I need to learn many concepts of the tools and technology for successful
development of this project.
To sync data: It is its self challenging task to sync the data to the Chromium web
browser. And then sync that data to the code.
Transforming of data: It’s a challenging task to transform the data in

codeeditorasthedatawhentakenfromdatabaseisnotproperandrequiresometransformations
to be done like removal of inappropriate rows columns and values. it requires
calculations and changing of data types of the values.
Visualization of data : It will be quite challenging to visualize the data as I am new

to UI and doesn't know much about the charts use to visualize the data. As it requires
proper visualization of the data so every user can understand it.
To provide view: To provide view in the Python language in such a large organization
it is difficult to maintain the granularity to provide the correct view to everyone.
Feasibility Study
Feasibility study is ordering system of a proposed task to decide whether it is achievable
specialized, financially, convenient and operationally. Feasibility study for the task is
directed to examine whether the proposed project is conceivable/achievable to be created
inside planned time, accessible assets, inside assessed spending plan. After practicality study
is done, it is assessed if to continue with the task. The Feasibility study can be sorted into
following four sections:
Technical Feasibility:
Technical feasibility is directed to confirm whether the project is practical to be created

inside the accessible assets or not. The technical feasibility considers the specialized
prerequisites for the task, the specialized resources needed by the project for its effective and

productive finishing. The particular specialized assets to be accessible for finishing the
project effectively are given underneath:
Hardware Resources
S. No. Hardware Resources

1. Processor- Core i3 and later version
2. RAM (Memory) - 2 GB and more
3. Monitor – Any standard monitor
4. Mouse, Printer, Keyboard
5. System Type- 64-bit OS
6. Accessories – Internet connection.
Software Resources
S. No. Software Resources
1. Operating System (PC) - Windows 8.1 or later
2. Web Service – Google Chrome
3. For Database Technology – SQLite
4. Case Tools – Visual Studio Code
5. Documentation and Presentation tool - Microsoft Office 2010
Resources of Execution
S. No. Resources for Execution

1. Operating system - Android 4.0 and later
2. CPU: 600 MHZ

3. RAM: 100 MB (estimated)
4. Disk space: 50 MB (estimated)
5. A good data/internet connection for customers
2.1.1 Economic Feasibility

The primary reason for directing monetary feasibility is to distinguish the money related
advantages and expenses related with the project development. With respect to any
framework if the assessed benefits equivalent or outperforms the normal costs that is
determined for the framework then the project would be monetarily attainable. Since the
proposed system programming climate depends on PC which is an open-source stage, so
there is less of interest in the advancement parcel. What's more, any product or program that
is delivered should be tried which should be possible very less investment. Just required
speculations would be Python language licenses and physical devices to test the system.
2.1.2 Schedule Feasibility

Schedule feasibility for a project is done to check whether the project can be finished
inside planned time or not as chosen by the Gantt chart. Dates are fixed for each stage all
through the undertaking and it is to be guaranteed that the project can finish inside the
predefined dates and the timetable. In the event that the task can be finished inside the
timetable, the planned possibility is high. Gantt chart is an undertaking the executive’s
device that can be utilized to quantify the planned possibility of the project. The proposed
course of events for the website would burn-through roughly 38 weeks and time the
executives for each assignment is brought out appropriately through Gantt chart.
Operational Feasibility
Operational feasibility measures to which degree the proposed project settle the issues
distinguished in the beginning period of the task; how the project plans to satisfy the

prerequisites recognized during extension definition and how the project utilizes the open
doors distinguished during degree definition. The project will be operationally achievable
without a doubt as the primary rationale is to take care of the issues of the individuals who
face issues in nowadays environment which are looked by masses.
2.1.4 Conclusion of Feasibility Study
The task is in technically feasible since the equipment, programming and the assets required
for executing the project are prepared. Subsequent to assessing the expense and advantages
acquired on and got from the project, it is inferred that the project is economically practical.
The task will be finished on schedule and cutoff times will be followed as planned in the
Gantt chart. The system will be socially satisfactory and will fulfill the necessities of clients.
Operational feasibility measures to which degree the proposed system settle the issues
recognized in the beginning period of the task; how the project expects to satisfy the
prerequisites distinguished during extension definition and how the project utilizes the open
doors distinguished during degree definition. The project will be operationally practical
without a doubt as the principle thought process is to tackle the issues of the individuals who
face issues in nowadays environment which are looked by masses.
2.2 Conclusion
Chapter 2 is about the issues recognized in the current territory of study for example the
issues in college canteen record maintenance and ordering system . The developer has
distinguished all the issues which is commonly looked by the instructors and understudies.
The issues have been reported alongside the support for every issue. After all the issues are
recognized, the developers next errand was to give suitable answers for resolving the issues.
For a similar reason, the arrangement relating to every issue has been archived alongside the
justification. A feasibility study is then led for the project to guarantee that the proposed
project is actually, operationally, financially achievable and can be finished inside a
predefined time span. The plausibility study is effective, making a further way for the
developer to push forward with the project.
CHAPTER 3: RESEARCH METHODS

Primary Research
Primary research is defined as collecting data or the information about the domain of the
study from the real world directly, for the very first time about a given subject directly from
the real world. It is done to remove the confusion and ambiguity that came in the mind of
the developer after performing secondary research by actually asking such questions directly
to the forum users and considering their suggestions. The developer can use this research to
move further in the development of the project. The primary research methods used by the
developer are questionnaire and interview which are described below:
Questionnaire
A Questionnaire consists of a number of questions printed in a piece of paper in a definite
order to elicit necessary information from the target users within a short duration. The
Questionnaire is provided to the respondents who are expected to read and understand the
questions and write down the reply in the space provided. Since, user is the types of users
for the proposed system; the developer will distribute the questionnaire among them.
Justification for Conducting Questionnaire

The reason for choosing questionnaire as a primary data gathering method is described
below:
1. Since the target users of the system are quite large in number, and it is impossible
to reach out to each of them individually to collect their requirements and
suggestions.
2. With questionnaire, it is possible to reach to masses simultaneously irrespective of
their geological location which is less time consuming
3. Since, the statistical techniques can be applied to it the analysis of questionnaire is
efficient which is done in the terms of graphs and charts which are more accurate.
4. Users are free to answer questions anonymously, so there are more chances of
obtaining exact requirements.
CHAPTER 4: ANALYSIS
4.1Overall Conclusion of Questionnaire
The questionnaires were distributed among the students and fauclty of different colleges and
the output which was very gud as they said they will get a full package of mamangaing all
records.Also because of attendance management students were happy that their attendance
wont be missed and in case of fees payment the response was good also the day pass facility
was of great use .All said to add more and more sections in the application as it is of great

use because here we are able to schedule assignments and submit simultaneously in the same
application only.
4.2Overall Conclusion of Interview

The research was conducted to gather the opinions of the developer about the proposed
application to be developed. The type of research helped the developer a lot in identifying
the problems faced by the users while managing their college attendance , assignments and
fess and what can be the convenient solutions for the problems mentioned. The developer of
the proposed system acquired knowledge about the required functionalities, pros and cons
of each module only by the actual end-users who are going to implement the system. Thus,
the developer targeted the colleges and institutes and took their responses and now the
developer is trying to implement more modules for future as overall response of EPICOR
was quite well.
This app would be beneficial to colleges and Institutes as it runs on android phones and its
so easy to use for everyone.
CHAPTER 5: SYSTEM DESIGN

5.1 Introduction
The design phase starts when the developer is done with the research and analysis phase.
The design phase includes the transformation of user’s specifications and software
components into the software interface to build a platform for establishing the system. It
covers the building of blue prints of the system that include physical modelling using
software engineering tools and methods.
In the design phase for the proposed system, the design is taking the requirements as the
input and will produce a guideline for the implementation as output. Three to four design
elements are to be produced for each and every module after completing the research and
analysis part which will be fed as input to the design.
5.2 UML Diagram

Use Cases: Use case will be required by the developer so that the flow of the functionalities
mentioned in the proposed system could be reviewed to validate the architecture and
evaluation of the complexity level of individual modules could be assessed easily. Therefore,
it would be helpful in testing the system through forward and reverse engineering. (Booch,
Rumbaugh & Jacobson, 2008)

Activity Diagrams: Activity Diagrams will be used by the developer to show the flow of
control of program modules from activity to activity. This would help us to show the
concurrency as well as branches of control in the proposed system. (Booch, Rumbaugh &
Jacobson, 2008)
Sequence Diagrams: Sequence Diagrams would help the developer to show the series of
interactions prevailing between users and system/modules. (Booch, Rumbaugh & Jacobson,
2008)
Class Diagrams: UML class diagrams will be required to provide an independent

description of the objects that would be used in the system and which would be helpful in
the implementation phase. The design can be used as a reference to implement on any
platform using any development environment. (Booch, Rumbaugh & Jacobson, 2008)
Entity-Relationship Diagram (ERD): ER diagrams will be required by the developer to

identify the entities and relationship between them is beneficial in storing the data which
would be then converted into tables in the normalization phase. (Booch, Rumbaugh &
Jacobson, 2008)
Chapter 6: Implementation:
Introduction :
The project “GEEKSFORGEEKS.ORG WEB AUTOMATOR.” Is a Automation based
Software in which User can have a Rich Collection Of Preparation Resources, stored on
the Local Computer System in the most User readable form. on Running a Single
command on the Integrated Terminal and can have Segregated Questions set,
magnificently stored in pdf files, with clickable links, to hover the particular, question
selected by the user. Utilizing which one can study thoroughly with compactness.(for
managing the useful set of resources. Specifically set of DSA Questions most frequent
asked in a coding interview by any of the one Company). Moreover, It is focused on less
user tension making them free to prepare for a specific company they want to prepare for
them and Also to have a checklist for the same, so that they can track what they are
prepared with. This makes high level Api Calls to enable Chromium to work and carry on
with automation.

6.1 Introduction
After the completion of the design phase, the developer analyzed that it was necessary that
the requirements quoted down must meet the proposed system development schema.
Implementation phase is one of the most essential stages of any project as the developer
would work to implement the system design into a real system. Implementation phase
involves the vivid usage of tools to convert the design modules into a real working system.
For working on the real system, the prerequisite for the developer would be a programming
language and a programming tool. The developer chooses to work Android SDK and the
development language chosen would be JAVA. The developer had to undergo through a
series of errors which was obstructing the implementation tenure. This chapter further throws
light on how the design has been implemented and what were the shortcomings during the
making of the system. Furthermore, list of problems are mentioned and what were the
probable solutions that were provided.
6.2 Tools used for Implementation

The developer has mentioned all the tools that has been used in the development of the
system.
Tools Purpose
Windows 10 Used as an operating system to run the all the below
mentioned tools for the development of the system.
Microsoft Visio 2010 Used to draw all the UML diagrams.
Microsoft Word 2010 Used to document the project.
Microsoft Project 2010 Used to prepare the Gantt Chart.
Microsoft PowerPoint 2010 Used to prepare the presentation slide.
Android Studio 2.2.3 It is used to design the pages of the application.
JavaScript The spine of the project
NodeJs Used as a backend support for the project.
Table 103:Tools used for Implementation
Technologies Used For Making This Project:
 HTML: The HyperText Markup Language, or HTML is the standard markup

language for documents designed to be displayed in a web browser. It can be
assisted by technologies such as Cascading Style Sheets (CSS) and scripting
languages such as JavaScript.Web browsers receive HTML documents from a web
server or from local storage and render the documents into multimedia web
pages. HTML describes the structure of a web page semantically and originally

included cues for the appearance of the document.HTML elements are the
building blocks of HTML pages. With HTML constructs, images and other objects
such as interactive forms may be embedded into the rendered page. HTML
provides a means to create structured documents by denoting structural
semantics for text such as headings, paragraphs, lists, links, quotes and other
items. HTML elements are delineated by tags, written using angle brackets. Tags
such as <img /> and <input /> directly introduce content into the page. Other
tags such as <p> surround and provide information about document text and may
include other tags as sub-elements. Browsers do not display the HTML tags, but
use them to interpret the content of the page.
 CSS: Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language such as HTML. CSS
is a cornerstone technology of the World Wide Web, alongside HTML and
JavaScript.CSS is designed to enable the separation of presentation and content,
including layout, colors, and fonts. This separation can improve content
accessibility; provide more flexibility and control in the specification of
presentation characteristics; enable multiple web pages to share formatting by
specifying the relevant CSS in a separate .css file, which reduces complexity and
repetition in the structural content; and enable the .css file to be cached to
improve the page load speed between the pages that share the file and its
formatting.
Separation of formatting and content also makes it feasible to present the same
markup page in different styles for different rendering methods, such as on-screen, in
print, by voice (via speech-based browser or screen reader), and on Braille-

based tactile devices. CSS also has rules for alternate formatting if the content is
accessed on a mobile device.
 JavaScript: JavaScript often abbreviated JS, is a programming language that is

one of the core technologies of the World Wide Web, alongside HTML and CSS.
Over 97% of websites use JavaScript on the client side for web page behavior,
often incorporating third-party libraries. All major web browsers have a dedicated
JavaScript engine to execute the code on users' devices.JavaScript is a high-level,
often just-in-time compiled language that conforms to the ECMAScript
standard.[14] It has dynamic typing, prototype-based object-orientation, and first-
class functions. It is multi-paradigm, supporting event-driven, functional, and
imperative programming styles. It has application programming interfaces (APIs)
for working with text, dates, regular expressions, standard data structures, and
the Document Object Model (DOM).The ECMAScript standard does not include
any input/output (I/O), such as networking, storage, or graphics facilities. In
practice, the web browser or other runtime system provides JavaScript APIs for
I/O. JavaScript engines were originally used only in web browsers, but are now
core components of some servers and a variety of applications. The most popular
runtime system for this usage is Node.js. Although Java and JavaScript are similar
in name, syntax, and respective standard libraries, the two languages are distinct
and differ greatly in design.

 NodeJS: Node.js is an open-source, cross-platform, back-end JavaScript runtime

environment that runs on the V8 engine and executes JavaScript code outside a
web browser. Node.js lets developers use JavaScript to write command line tools
and for server-side scripting—running scripts server-side to produce dynamic web
page content before the page is sent to the user's web browser. Consequently,
Node.js represents a "JavaScript everywhere" paradigm, unifying web-application
development around a single programming language, rather than different
languages for server-side and client-side scripts.
Though .js is the standard filename extension for JavaScript code, the name
"Node.js" does not refer to a particular file in this context and is merely the name of the
product. Node.js has an event-driven architecture capable of
asynchronous I/O. These design choices aim to optimize throughput and
scalability in web applications with many input/output operations, as well as for real-
time Web applications (e.g., real-time communication programs and browser
[7]
games).
The Node.js distributed development project was previously governed by the
Node.js Foundation, and has now merged with the JS Foundation to form the
OpenJS Foundation, which is facilitated by the Linux Foundation's Collaborative Projects
program.

Implementation Approach Steps:
1. Since the system have only one app which consists of Faculty and Student Login.
Student login can only work if there is a Faculty like if there is lecture or time table
scheduled then only student can attend the particular lecture and then only they
would be able to mark themselves as present or absent..
2. Then in Faculty login we implemented registration module taking their unique id as
input without which they cant register as the id is unique identity which is given to
them by the concerned college department so if they have that id then only they
can register filling details of them in Name ,Phone number, Email, Password
,Select Branch where they would be choosing the branch which will allow them to
get aligned to particular department.
3. Then Time Table session is created in Faculty section where faculty can schedule
lecture with the lecture duration and with some particular date but the lecture of
same day would be shown to faculty on same day.
4. After that as Student Login is created wherein students can easily see the schedule
of their department and section and mark their attendance easily.
5. After that testing was done to see that the lecture which is getting scheduled is
reaching ro students or not.
6. Then Faculty info section was added where the students can get their necessary
facukty information which would be directly fetched from the database because of
which students can easily know the teacher of their department and what subject
they teach.
7. Then Time Table session is created in Faculty section where faculty can schedule
lecture with the lecture duration and with some particular date but the lecture of
same day would be shown to faculty on same day.

8. After that as Student Login is created wherein students can easily see the schedule
of their department and section and mark their attendance easily.
9. After that testing was done to see that the lecture which is getting scheduled is
reaching ro students or not.
10. Then Faculty info section was added where the students can get their necessary
facukty information which would be directly fetched from the database because
of which students can easily know the teacher of their department and wht
subject they teach.
11. Then Schedule Assignment Section was added in the Faculty module wherein the
Faculty can easily upload the assignment and give the deadline to students that
when to submit the assignments similarly viewing assignment option was also
made so that faculty can easily download and view the assignments of particular
student.
12. Then Assignment Section was made in Student Login where students can easily
see the scheduled assignments by the teacher of their department and also they
are having option there only to download the assignment and upload the
assignment when they are done.
13. Then logo was assigned to assignment where there was scheduled time in up and
submission time in bottom.
14. Then the schedule notice session was made so tht teacher can easily schedule the
notice and upload it from their device , which in turn will allow students to easily
see them.
15. Then the Notice section was made in Student Login where students can see what
notice is scheduled for them and it is scheduled by which Faculty,
16. Then the Day Gate Pass Section was added in the Student module where Students
can easily apply for” request day pass” wherein mentioning the date of gate pass
and reason for the day pass request so that teacher can easily approve or reject
the gate pass.
17. Then the Day Pass request section was made so that Faculty can easily see the day
gate pass requests of the user and can easily see the reason which will help faculty
to easily approve or reject the request.
CODE for the main File:













Result After Implementation :

We can see various companies named pdfs which contain frequently asked questions
asked by companies as per data provided by Geeksforgeeks.org

CHAPTER 8: TESTING
“... we have as many testers as we have developers. And testers spend all their time
testing, and developers spend half their time testing. We're more of a testing, a
quality software organization than we're a software organization.” – Bill Gates
8.1 Introduction
Testing is the process of exercising software with the intent of finding and correcting
errors. The objective of the testing is to uncover different classes of errors and to
do so with a minimum amount of time and effort. In order to provide highly
acceptable and error free system, the system should have to face the testing
procedure and evaluation of each and every module and functionality.

8.2 Need of Testing

The significance of the testing phase is done to verify and validate the completed
system. So that it will execute and presented the way it was expected and all the
functionalities function as were defined in the project specification form. The
testing does not require that the developer has to test each and every section of
code to verify the bugs and recover from the errors and bugs that are present in it
but its objective is to uncover the situations that could impact the system or the
project or can lead in making the project unsuccessful. Thus, testing is done to
enhance the quality of the system produced so that it is acceptable by the intended
user with satisfaction. The highlights of this chapter include:
 The different types of testing done.
 The duration taken to test.
 The person(s)involved.
 The reported errors.
 The measures taken.

8.3 Test Plan

Website development processes typically focus on avoiding errors, detecting and
correcting the website faults that do occur and predicting reliability after development.
The test process, techniques and tools are significant contributors to effective and
efficient testing and quality assurance. Various testing techniques to be implemented
for proposed system are given in the next section.
8.3.1Type of Testing
Unit Testing (Black Box & White Box

Testing)
Integration
Testing
System Testing
Testin
g User Acceptance
Testing
Usability
Testing
GUI Testing
Documentation
Testing
Figure 43: Type of Testing

Testing
S. No Requirement
Technique
Testing of individual website component or modules of the
system. This type of testing is performed by the developers
1.
Unit Testing only because it requires detailed knowledge of the internal
program design and code. It includes performing black box and
white box testing.
Testing of integration modules to verify combined
Integration functionality after integration. Various modules are integrated
2. Testing together and then tested by the developer of the system to
check whether the modules work properly after integration.
Entire system is tested by the developer as per the requirements.
3. System Testing All the modules of the system are combined and check whether
they work perfectly after being integrated into one system as a

whole.
4. Compatibility Compatibility testing is used to determine if the system
causes any
Testing issues related to how it functions in concern with the operating

system and different type of system hardware and software.
The developer performs this type of testing on various
hardware/ software platform to test the compatibility of the
system one ach platform.
The testing is to be done to verify the design of the system
5. GUI Testing whether it satisfies the six predefined HCIU design principle
and whether the system is user friendly.

The purpose of doing a usability test is to determine whether

a product or document works with its intended users or
readers. This is to be done by evaluating a product through
6.
observing the real people actually working on or using it so
Usability Testing as to improve or enhance the system. The end- users execute
the system to test it.
User Acceptance Testing tests that the system satisfies all the
essential user requirements and is performing to the

7. User
acceptable level as expected by the customer. This is done by
Acceptance
Testing defining a set of acceptance criteria which the system must
satisfy before the customer will accept it.
Documentation Testing is to be done to verify the system

8. Documentation
documentation whether it is meaningful and user friendly or
Testing
not.
Table 44: Testing Description
8.3.2 Pass/Fail Criteria
 The produced system meets all the specifications mentioned in the

project specification form and all the requirements of the user gathered
during the research phase.
 All the modules/ functionalities are implemented in a way that the

desired system produced runs without any bugs and quickly.
 System is to be verified for the usability that depends upon proven

Human-Computer Interaction (HCI) principles and aims to achieve in the
application ease of use, Navigation, time for completion and errors
removal

8.3.4 Point of Contact of Troubleshooting Purpose
Name: Harsh, Shubham Jaiswal, Harshit Jain

Designation: Renewed Product Management Website
Contact No.: +91-856989607, +91-9711694180 and +91-7206621181
Email ID: goyal.harsh739@gmail.com,
shjuly152000@gmail.com and
harshitj1312@gmail.com
Table 45: Point of Contact for Troubleshooting Purpose
8.4 Testing Duration
S. No. Testing Technique Start Date End Date
1. Unit Testing 1st December 2021 19th December 2021
2. Integration Testing 2nd December 2021 20th December 2021
3. System testing 4th December 2021 9th December 2021
4. Compatibility Testing 8th December 2021 10th December 2021
5. GUI Testing 11th December 2021 11th December 2021
6. Usability Testing 12th December 2021 12th December 2021
7. User Acceptance Testing 13th December 2021 17th December 2021
8. Documentation Testing 18th December 2021 18th December 2021

Table 46: Testing Duration
8.5 Criteria of Test Cases

The system must comply with the success criteria mentioned in the specification.
Some of the requirements are:
 All modules should work efficiently.

 User Register System should work efficiently.
 Synchronization must work efficiently
 Menu Based features should work efficiently.
 Order should be Placed Easily.
 System should satisfy all user requirements.
 UI should have a consistent layout and must follow the HCIU principle
 The Website should be easy to use.
8.6 Technical requirements for Testing
S. No. Technical Requirements

1. CPU: 600 MHZ
2. RAM: 500MB (estimated)
3. Disk space: 500 MB (estimated)
4. A good data/internet connection for customers
5. Laptop with internet connection.
Table 47: Technical requirements for Testing
8.7 Users Involved in Testing

The developer will play the role of tester.
8.8 Unit Testing

In order to test each small part of the developed system individual test cases were
developed. Unit testing was very helpful as it helped the developer to test individual
units of code. This is performed before any other testing because it is easy to find out
errors at lower level that is at module level than to find them at integration or system
level. It is performed at two levels; black box test cases are made and then white box
testing is done. Two levels of unit testing were basically conducted, namely black box
(also called functional testing) and white box (also called logical testing).
8.9.1 Justification for unit testing

For the system produced named Renewed Product Management each module is tested
and its corresponding test case is produced. Therefore, individual test cases are

produced for all the modules. Unit testing is performed at the primary level for the
system.

8.9.2 Black box testing (Functional Testing)
Figure 44: Black Box
Black Box Testing, also known as Functional Testing, is a software testing technique that
exposes only the functionalities and the design of the system; hiding the internal
implementation/ structure of the system. The internal code or the structure is not known
to the user who is going to use the system.
 Justification for Black Box Testing
The testing is to be performed by the developer of the system but testing the
functionalities of the system and not going into the code of the system.
 Registration check
Project Name Renewed Product Management

Test Case ID TC – 01 Testing Case Name User registration

Testing Priority High Tester Developer

Testing Date Dec 3rd, 2021 Testing Duration 15 Minutes
Description This module deals with user registration.
Pre-Condition User details.
S. No. Test Step Test Data Expected Result Actual Result Status
1. User registered Users should User should have All users are Pass
to the admin have credentials for registered.
panel and gets registered accessing the
credentials. with help of website.
developer
Table 48: Registration Check
 Landing Screen

Test Case ID TC – 02 Testing Case Name User Login
Testing Date Dec 3rd, 2021 Testing Duration 15 Minutes
Description This module deals with user login.
Pre-Condition User details must be in the database and developer must have
assigned the rights to him.
S. No Test Step Test Data Expected Result Actual Result Status
User name User() Must show user Email is shown. Pass
1. function
check at top. email
check on the
landing page.

Only The website should

Check the Required Pass
2. Required display only those
right Buttons Buttons are
Information class buttons which
displayed to shown
is shown to the user has access
the users. the users. too.
Post-Condition The user is on the correct landing screen
Table 49: Black Box Testing of Landing Screen
 Personal Details Checking.
Test Case ID TC – 03 Testing Case Name Personal details

check
Testing Date Dec 4, 2021 Testing Duration 45 Minutes

Description This module deals with checking of the student details.
Pre-Condition User must provide all details.
1. Personal Verify All details should All details are Pass
Details check personal Be correct. correct.
details
2. Edit details User should His details should They are getting Pass.
functionality be able to update in database updated
update his
details

3. Add user User Should New user should be New user is Pass
details. be able to added. added
add new successfully.
user details
Post-Condition A user has been registered.

Table 50: Black Box Testing of Personal details Modul
 User Ordering Module

Test Case ID TC – 04 Testing Case Name User Ordering Module
Testing Priority High Teste Tester Teste Developer
Testing Date Dec 10, 2021Testing Duration 1 Hour
Description Checking Ordering System
Pre-Condition null.
S. No Test Step
Test Data Expected Result Actual Result Status
Products Products Products should be Visibility
1. Pass
Visible to are visible visible properly.
the user. correct.
2. Ordering of Ordering Items must be Order was Placed Pass

the items Items. ordered properly properly

3. Total of the proper output Correct no. It was all Pass

no. of items should appear of items and correct
amount total
displayed amount
Table 52: User Ordering Module
 Receiving Order module

Test Case ID TC – 05 Testing Case Name Receiving Order
Testing Date Dec 14, 2021Testing Duration 2 Hours
Description Checking the Order is received

Pre-Condition Nill.
Order
1. Received to Checking Order should be Order was Pass
the Admin Order received the
Panel. received correct user correct.
should be
correct
2. Correct Checking Order details should As per the Fail and
details of
the order be correct. Expected result message is
order
details. displayed
user.
3. Accept and Buttons Accept and Reject Buttons were Pass
Reject Buttons should be buttons should be Present
present present.
Table 53: Receiving Order module

 MongoDB Report
Test Case ID TC – 06 Testing Case Name Checking Analysis and

Visualization
Testing Date Dec 18, 2021 Testing Duration 2 Hours
Description Checking of all the MONGO-DB Databases

Pre-Condition Must have MONGO-DB installed and knowledge of analysis
1. Database MONGODB Database should Only a Pass

negligible
Loading speed Database load In minimum
time. amount of delay

was observed.
2. Database Refresh Database New data must load There was an Fail
Should on refreshing the error.
refresh with dataset
new data.
3. Checking on All All visualizations As per the Pass
all the
Visualization must visualize expected result
visualizations.
On the correct data. was visualizing
database
correct result.

4. Launching the MONGODB All the data should It was storing the Pass
database through
Databases be stored in correct correct data.
MONGO-DB.
database
Table 54: SQLite Report
8.9.3 White Box Testing (Conceptual Testing)

White Box Testing also known Code-Based Testing or Logical Testing is a software testing
technique that exposes the internal implementation or the internal structure of the
system or the code. The testing is to be performed by someone who is skilled in Frontend
and Backend. It is something ahead of the user interface as it has nothing to do with the
external structure or the interface but is concerned about the internal design/ structure
or the implementation. The testing is employed to thus test the internal workings of the
proposed system or the website.
 User Register

Test Case ID WB-01
Testing Module User Registering Tester Developer
Testing Date Dec 19,2021 Testing Duration 5 Hours
Description To test whether the following code update attendance to the local
database or not.
Objective To check the working of code in user register.
Pre-Condition User must have his/her personal details in the database.

[Type here] [Type here] [Type here]
Post Description User Register will be done in the database.

Test Input Enter all the necessary details and click enter.
User is Registered.
Expected Result
Actual Result Identical to the expected result
Code
G-63 Panipat Institute Of Engineering And Technology p-1

CHAPTER 7: TESTING

“... we have as many testers as we have developers. And testers spend all their time testing, and
developers spend half their time testing. We're more of a testing, a quality software organization
than we're a software organization.” – Bill Gates
(Information Week 2002)
7.1 Introduction
Testing is the process of exercising software with the intent of finding and correcting errors. The
objective of the testing is to uncover different classes of errors and to do so with a minimum
amount of time and effort. In order to provide highly acceptable and error free system, the system
should have to face the testing procedure and evaluation of each and every module and
functionality. (Mustafa & Khan, 2007)
7.2 Need of Testing

The significance of the testing phase is done to verify and validate the completed system. So that
it will executed and presented the way it was expected and all the functionalities function as were
defined in the project specification form. The testing does not require that the developer has to test
each and every section of code to verify the bugs and recover from the errors and bugs that are
present in it but its objective is to uncover the situations that could impact the system or the project
or can lead in making the project unsuccessful. Thus, testing is done to enhance the quality of the
system produced so that it is acceptable by the intended user with satisfaction.The highlights of
this chapter include:
 The different types of testing done.

 The duration taken to test.
 The person(s) involved.
 The reported errors.
 The measures taken.
7.3 Test Plan

Software development processes typically focus on avoiding errors, detecting and correcting the
software faults that do occur and predicting reliability after development. The test process,
techniques and tools are significant contributors to effective and efficient testing and quality
assurance. (Mustafa & Khan, 2007).Various testing techniques to be implemented for proposed
system are given in the next section.

7.3.1 Type of Testing
CHAPTER 8: CRITICAL EVALUATION

8.1 Critical Evaluation
After completion of the project from the developer side, it’s time for critically evaluating the
project by mapping the project and its requirements with the specifications given in the project
specification form. Since the developer has made an extensive research on the system’s
functionalities, made a broad analysis of the same. After research and analysis, developer has
designed the system to set the goals which were further implemented and then tested to recover
any errors if were present in the system so as to produce a bug free system. Now time has come to
critically evaluate the system that includes the complete assessment of the system. The critical
evaluation is not done module by module but whole system is evaluated to determine the quality,
significance and worth of the system.
8.2. Factors of Benefit (Usefulness of System to Target Audience)

The developed system renders much usefulness to the target users because the system is able to
solve the problems mentioned in the problem description section of CHAPTER 2. The usefulness

of the system was discussed in the tangible and intangible benefits of section 1.7. Some of the
usefulness and benefits are recapitulated below:
Cost Efficient Benefits

Since, the app targets to remove the limitations of a dedicated scanner or QR Code reader
and clunky PC. Thus, it will save ample amount of retailer’s money.
The developer launched this app to be used free of cost and can be accessed from anywhere
and is readily available to its user. But this app would require little bit Internet accessibility
which would require little costing.
Mobility
The entire POS has been molded to a mobile phone, thus users will get a great advantage of
mobility.
The whole application will work on mobile for a user so user has a great advantage of mobility
while using application.
Increased Productivity
The more number of user’swill book use this app, thus it will increase the productivity in the
college itself.
By making the fee payment section students can easily pay their fees from their homes only
without paying an extra amount in the name of fine.
Table:Factors of Benefits.
8.3 Comparison with Other Systems
S. No. Features Epicor Other System
1. Faculty and Student  
Login
2. Mark Attendence  
3. Schedule Time Table  
4. Assigning Gate Pass  
5. Verifying Mobile × 
Number
6. Maintaing Attendence × ×
7. Paasword Protection  
8. Notice  

9. Assigning  
Assignments
10. Refusing  
Assingnments
11. Sending Fee due × 
Notification.
12. No Duplicate Logins  
Table:Comparison with Another System
8.3.1 Success Assessment
The success assessment consists of analyzing whether the output received matches to what was
proposed. It consists of comparing the project outcomes to the results expected. The present project
meets all the requirements mentioned in PSF. It fulfils the scope and boundary of the project. The
following results prove it:
Criteria Result Success Degree (out of 10)

User interaction YES 9
Project management YES 9
Project requirements YES 10
Secured app YES 8
Testing YES 9
Quality YES 9
Graphical interface YES 9
Academic goals achieved YES 10
Project objective achieved YES 9
Feedback YES 9
9+9+10+8+9+9+9+10+9+9 = 91/100
Overall Success Rating of the system
Success Rate: 91%
Table:Success Assessment

8.3.2 Degree of Success

The rate of success of any project is determined on the mapping of the requirements documented
for the proposed system in the project specification form. The system should satisfy the quality
standards for project development and implementation should be feasible.
8.3.3 Critical Appraisal

The developer has tried to impose all the proposed functionalities into the developed app. The
proposed requirements have successfully been mapped into real world system. Now, after the end
of implementation and testing phase, a security efficient app is ready to be deployed. There were
many setbacks during the development of system. The developer had to undergo many operability
issues of Fee Payment. Rooting can hamper android phone’s regular functioning and harm the
processor and memory. There were server issues as developer cannot work on heavy server as it
would involve money and were very expensive and also didn’t fit in for the level of project. The
developer tried all his labor to complete this module as proposed but due to some technical and
software issues (refer chapter 7) developer was not able to complete that. Developer has included
the part of the implementation he has done in the implementation phase and is now working on
the same subject as his research work. Apart from this, the functional requirements, non-functional
requirements like quality, usability, and user interface, etc. is well achieved by the developer.
Beside these, the project is tested with various real time test cases to achieve a genuine result,

evaluation, and feedback. The System developed is working fine as proposed and is ready to
access.
“EPICOR -PIET ERP” is one of its kind app which has been developed by the developer no such
app is available in market with such functionalities in a single app with such a versatility and user
friendly system with a high level of smart ERP management..
CHAPTER 9:REFERENCES
9.1 Books
1. JavaScript Programming by Ethem Mining
2. Python For Everybody by Charles Severance
3. HTML&CSS Design and Build Website by Jon Duckett
4. HTML and CSS by Elizabeth Castro and Bruce Hyslop
5. JavaScript &Jquery by Jon Ducket
6. JavaScript The Definitive Guide by David Flanagan
7. SQL: The Complete Reference by James R. Groff
8. Effective SQL by John L. Viecas
9.2Journals
1. Accelerate transformation with the new modern project accelerat or and one plan.
2. Newadaptivemicrosoftppmwithmicrosoftproject,azuredevoopsandjirausingPython.
3. Getting Started with the New Python Activity Log API .
4.
9.3Websites
1. Nodejs.org
2. w3schools.com
3. Mozilla Developers
4. Javascript.info
9.4 References
1. Udemy
2. Coursera

3. Edx
CHAPTER 10: CONCLUSION
10.1 Success Criteria

The proposed system named “College Canteen – Snack Zillas” has proved to be significantly
useful for the end-user as it meets all the requirement of the user as well as fulfils the entire
criterion that judge the quality and success of the system. The success for the proposed system is
achieved as it has met the success criteria and established what it was supposed to. The system
has resolved the issues that were discussed in the chapter 2 regarding the problems raised and the
solutions provided. The proposed system after evaluation has been found to successfully
guarantee the booking and checking at the real-time environment to the end- user and hence has
solved the problem what was expected.
10.2 Limitations and Errors in the Developed System
1. The project requires some paid licenses.

2. For some of the features the mobile should have internet.
10.3 Future Enhancement

1. The web application can be improved in future by implementing Qr online payment
feature to the web application.
2. The app can be implemented with location features.
3. Log in and logout facility.
4. The web application can be made more secure.
5. The Report can have more visualization.
10.4 What would have been done if given time to redo the project?
If the developer is provided a second chance to make this project then he would certainly
make this project a better one.
6. Improved ordering system: If the developer gets a chance then developer will improve
the ordering system and make totally an automatic process.
7. Would make SQL report have more visualization: Will make the report system have
more visualization.

10.5 Computational Challenges

Using connectors, services and auto updating of data in a single activity was the main
computational challenge in the system as the developer had to do several things in single activity
like:
1. Connecting all the tools together with the help of connectors and syncing data was really
tough for the developer.
2. Controlling the flow of such large amount of data was quite a challenge for the developer.
10.6 Learning Experience Gathered

1. Learnt a lot from research work: In the preliminary stage of the project, the developer
was quite confused about what features to be included in the system. So, the developer
carried out secondary research by studying the research works of various authors and
pointing out what all mistakes they have done. It helped in gathering intense knowledge
about the subject domain and critically analysing similar systems in terms of their
features and drawbacks. Finally, the developer conducted primary research to gather real
time user requirements.
2. Learned to manage stress and time: While working through the different phases of
SDLC, the developer played various roles as follows: analyser, researcher, database and
mobile app developer and tester. This gave the developer the skill to manage both stress
and time efficiently. The developer was able to complete the project within the scheduled
time period overcoming all stresses and time constraints that came during the
development phase.
3. Gained technical expertise: The implementation of the system required not only to
apply learning outcomes achieved during academics but also a clear understanding of
various technologies. It required studying various books and articles to grab the concepts
Python and various services, My SQL database concepts etc. It ultimately helped in
widening the technical knowledge and to gain a mastery over different languages.
4. Had an experience of project management: The project gave a wonderful experience
and feeling of working as if in some corporate world. The developer also played a vital
role of a project manager by getting the completed-on time, delivering a quality system,
fulfilling user requirements, using fact finding techniques to collect requirements. Divide

and conquer approach was used to divide the entire project into small tasks and
completing them according to the schedule prepared in the Gantt chart.
5. How to resolve errors and learn from them: While implementing the system, the
developer encountered many errors and exceptions which were corrected after applying
various methods. This gave an understanding how to debug and rectify errors using top
down approach. Also, the developer came to know how to find errors and fix them
which is very unique skill needed to deliver an error free system.
6. Gained lot of confidence: Before implementing the system, the developer was in a
dilemma how to implement the complex modules of the system. But gradually things
became easier after doing research work in each phase of the development which itself
paved a pathway to plan the logic and flow of the entire system. Although it required
consistent and sincere effort,but the developer became assure of one thing that ‘where
there is a will, there is a way’. This learning has motivated the developer to accept
greater challenges by strongly believing that to every problem there is a solution. Last
but not the least, this final year project gave a great learning and pleasant experience of
working on real time projects and created a deep interest in the Python development field
which will help in reaping benefits for having a bright career in future.
10.7 Conclusion
1. The documentation presents the proposed system’s report, how the system went through
various phases during its development. The developer started with the background study
of the system where he has inferred out the problems faced by a user in today’s
environment in context of being a teacher. The background study phase is followed by
the literature review which is a kind of research to gather knowledge in the current area
of study to develop a successful system.
2. The developer has conducted both primary and secondary research. It is concluded that to
gather the desired information about the proposed system, the developer had to go
through various steps. Questionnaire and Interviews are the data gathering techniques that
have been used to identify the need of the target people, the employees within an
organization. Questionnaires have got filled by the staffs/ employees while interviews
have been conducted by the administrators and the highly-authorized persons.

3. The analysis of the questionnaire and interviews and focus groups have helped the
developer to have a complete knowledge and understanding of the security measures of
an organization as the users were taken from different industrial sectors. Also, the
technical knowledge has been gained by taking the interview from the software
developers and software designers. Their opinions have been evaluated to get an in-depth
knowledge of the technologies and the databases on the basis of which the developer has
decided to use Power apps technology and google sheets as databases. In this way, the
research part for the proposed project has been completed.
4. The developer then continues with the system design part in which the system design is
prepared that includes the logical and physical designs of the system that further
categorizes to UML diagrams, Physical designs of the system, entity relationship diagram
etc.
5. Then comes the implementation phase that covers the implementation approach to be
followed by the developer to implement various modules of the system starting with a
module that has lower priority and moving towards the higher priority modules. Other
than that, a user manualas well as technical manual is provided that guides the user about
the flow of the system and how to use the system and installation instruction respectively.
Then various types of testing have been conducted to test the system and its various
modules by conducting unit test, integration test, system test and many more.
At last the final project is critically evaluated to come to a conclusion, how the system
can benefit its end-users and how much the project is successful from the user’s point of
view.

Chapter 11. References

11.1 Websites
 https://dashboard.heroku.com/apps
 https://jwt.io/
 https://nodejs.org/en/
11.2 Reference
 https://udemy.com
 https://github.com/
 https://www.youtube.com/
 https://devcenter.heroku.com/articles/getting-started-with-nodejs/
 https://www.section.io/engineering-education/how-to-build-authentication-api-with-jwt-
token-in-nodejs/
 https://github.com/heroku/heroku-buildpack-nodejs

G63 Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

G63 Report

Uploaded by

Copyright:

Available Formats

Geeksforgeeks.

org Web Automator

Submitted in partial fulfillment of the requirements

Under the Supervision of

Panipat Institute of Engineering & Technology, Samalkha, Panipat

Kurukshetra University Kurukshetra, India

G-63 Panipat Institute Of Engineering And Technology Page-1

G-63 Panipat Institute Of Engineering And Technology Page-1

It is my pleasure to be indebted to various people, who directly or indirectly contributed in

Name: Mudit Arora

Name: Shubham Yadav

G-63 Panipat Institute Of Engineering And Technology Page-1

G-63 Panipat Institute Of Engineering And Technology Page-1

2) CERTIFICATE ........................................................................................................................ iii

LISTOF FIGURES .......................................................................................................................... xiii

CHAPTER1: INTRODUCTION ........................................................................................................... 1

1.1 Topic of the System .................................................................................................... 1

G-63 Panipat Institute Of Engineering And Technology Page-1

2.1 Current Problem Description .................................................................................... 12

3.1 Introduction to Literature Review ............................................................................. 20

G-63 Panipat Institute Of Engineering And Technology Page-1

CHAPTER 4: RESEARCH METHODS ................................................................................................ 35

4.1.1 Primary Research .................................................................................................. 35

5.1 Analysis of Questionnaire ......................................................................................... 58

G-63 Panipat Institute Of Engineering And Technology Page-1

8.3.2 Pass/Fail Criteria ................................................................................................. 101

9.1Critical Evaluation.......................................................................................................... 139

9.2. Factors of Benefit (Usefulness of System to Target Audience) ...................................... 139

9.3 Comparison with Other Systems ............................................................................. 140

G-63 Panipat Institute Of Engineering And Technology Page-1

CHAPTER 10: CONCLUSION ........................................................................................................ 143

10.1 Success Criteria ................................................................................................ 143

11.1 Websites ........................................................................................................................ 147

11.2 References ..................................................................................................................... 147

Table 7: Enhanced Features……………………………………………………………………11

Table 8: Special Features……………...……………………………………………………….11

Table 9: Hardware Resources………………………………………………………………… 16

G-63 Panipat Institute Of Engineering And Technology Page-1

Table 18: Questionnaire for Customer………………………………………………………...38

Table33: Point of contact for troubleshooting purpose………………………….…………….101

Table34: Testing duration…………………………………………………………...………...101

Table35: Technical requirements for testing………………….………………………………102

Table36: Registration check…………………………………………………………………..104

Table37: Blackbox testing of landing screen…………………………………………………...104

Table38: Blackbox testing of personal detail modules…………………………………………105

Table39: Blackbox testing of attendance system……………………………………………….107

Table40: Blackbox testing of sessional module………………………………………………. 108

Table41: Blackbox testing of assignment module…………………………………………… 108

Table42: Blackbox testing of Library module………………………………………………….110

Table43: Blackbox testing of Power Bi………………………………………………………...111

Table44: Whitebox testing of attendance system………………………………………………117

Table45: Whitebox testing of Library system………………………………………………….122

Table46: integration test-personal detail and attendance system………………………………124

Table47: integration test-personal detail and Sessional module………………………………. 124

Table48: integration test-personal detail and assignment module……………………………..125

Table49: integration test- Power apps and Power-Bi…………………………………………. 125

Table50: System testing………………………………………………………………………...128

Table51: Compatibility testing……………………………………………………………… 130

Table52: GUI test………………………………………………………………………………131

Table53: Questionnaire for usability testing………………………………………………… 132

Table54: Rating criteria for usability testing………………………………………………….. 132

Table55: Usability Test……………………………………………………………………… 133

G-63 Panipat Institute Of Engineering And Technology Page-1