Techrevive Report - Merged
Techrevive Report - Merged
PROJECT REPORT
Submitted in partial fulfillment of the requirements for the award of the
degree of Master of Computer Applications of A P J Abdul Kalam
Technological University
Submitted by:
KERALA
NOVEMBER 2024
ST. JOSEPH’ S COLLEGE OF ENGINEERING
AND TECHNOLOGY, PALAI
(An ISO 9001: 2015 Certified College)
CHOONDACHERRY P.O, KOTTAYAM KERALA
CERTIFICATE
This is to certify that the project work entitled Techrevive submitted by Merin
Babu student of Third semester MCA at ST. JOSEPH’S COLLEGE OF
ENGINEERING AND TECHNOLOGY, PALAI in partial fulfillment for the
award of Master of Computer Applications is a bonafide record of the project
work carried out by her under our guidance and supervision. This report in any
form has not been submitted to any other university or institute for any purpose.
Examiner 1:
Examiner 2:
DECLARATION
I Merin Babu, do hereby declare that the project titled "Techrevive" is a record of
work carried out under the guidance Prof.Anish Augustine, Asst. Professor,
Department of Computer Applications, SJCET, Palai as per the requirement of the
curriculum of Master of Computer Applications Programme of A P J Abdul Kalam
Technological University, Thiruvananthapuram. Further, I also declare that this report
has not been submitted, full or part thereof, in any University / Institution for the award
of any Degree / Diploma.
Date: (SJC23MCA-2042)
ACKNOWLEDGEMENT
The success of any project depends largely on the encouragement and guidelines of many
others. I would like to take this opportunity to express my gratitude to those people who
have been instrumental in the successful completion of this project.
First and foremost, I give all glory, honor and praise to God Almighty who gave me
wisdom and enabled me to complete the project successfully.
I also express sincere thanks, from the bottom of my heart, to my parents for their
encouragement and support in all my endeavors and especially in this project.
Words are inadequate to express my deep sense of gratitude to Dr. V. P Devasia, Principal,
SJCET, Palai for allowing me to utilize all the facilities of our college and for his
encouragement.
I extend my sincere gratitude to Dr. Rahul Shajan, HOD, Department of Computer
Applications, SJCET, Palai who has been a constant source of inspiration and without
his tremendous help and support this project would not have been materialized.
I owe a particular debt of gratitude to my project guide, Prof. Anish Augustine ,
Asst.Professor, Department of Computer Applications, SJCET, Palai for all the
necessary help and support that he has extended to me. His valuable suggestions,
corrections, and the sincere efforts to accomplish my project even under a tight time
schedule were crucial in the successful completion of this project.
I extend my sincere thanks to all our teachers and non-teaching staff of SJCET, Palai for the
knowledge they have imparted to me over the last three years.
I would also like to express my appreciation to all my friends for their comments, help and
support.
DEPARTMENT OF COMPUTER APPLICATIONS
VISION
MISSION
❖ Provide quality education in Computer Applications and bridge the gap
between the academia and industry.
❖ Promoting innovation research and leadership in areas relevant to the
socio-economic progress of the country.
❖ Develop intellectual curiosity and a commitment to lifelong learning in
students, with societal and environmental concerns.
Co No CO Blooms Category
Level 4:
CO4 Analyse and design a software product / project
Analyse
Level 6:
CO6 Build and integrate different software modules
Create
Level 3:
CO7 Document and deploy the product / project
Apply
SYNOPSIS
The platform supports four distinct user roles: Admin, Technician, E-waste Collector, and
Customer, each playing a vital role in the system’s functionality. The Admin manages service
requests, registers technicians and collectors, and allocates tasks. Technicians can accept or
reject assigned repairs, while e-waste collectors handle collection requests and record disposal
locations. This user-based structure ensures efficient workflow and transparency in both repair
and recycling services. By providing easy-to-access repair options and promoting sustainable
e-waste management, TECHREVIVE makes gadget upkeep more manageable and eco-
friendly.
TABLE OF CONTENTS
1. Introduction_______________________________________________1
1.1 About the project………………………………... 2
1.2 Objective of the project…………………………..2
1.3 Scope of the project……………………………… 3
2. Initial investigation and Feasibility study_______________________4
2.1 Initial Investigation…………………………... .5
2.2 Feasibility study……………………………..….6
2.2.1 Economic Feasibility………………………....7
2.2.2 Technical feasibility…………………………..7
2.2.3 Behavioral feasibility………………………....7
2.2.4 Operational feasibility……………………......8
3. System Analysis_____________________________________________9
3.1 System Analysis………………………………...10
3.2 Existing system…………………………………10
3.3 Proposed System……………………………….11
3.4 Software Requirement Specification………….11
4. Modules__________________________________________________16
4.1 Modules…………………………………………17
4.1.1 Admin…………………….…………17
4.1.2 Technician…………………...………18
4.1.3 Ewaste Collector……………………18
4.1.4 Customer……………………………19
5. Flow Diagrams____________________________________________20
5.1 Data Flow Diagram……………………………..21
6. System Design_____________________________________________ 26
6.1 System Design…………………………………...27
6.2 Input Design……………………………………..27
6.3 Output Design…………………………………...28
6.4 Table Design…………………………………….28
7. Tools and Platforms________________________________________35
7.1 Front end…………………………………………….36
7.2 Back end……………………………………………..36
7.3 Framework…………………………………………..36
7.4 Platform……………………………………………...36
7.5 Database……………………………………………..37
8. Testing___________________________________________________38
8.1 Unit Testing …………………………………………39
8.2 Integration Testing………………………………….39
8.3 System Testing………………………………………39
8.3.1Acceptance Testing …………………………...40
8.3.2 Validation Testing…………………………….40
8.3.3 Black Box Testing…………………………….40
8.3.4 White Box Testing…………………………….40
8.4 Sample Test Cases…………………………………...41
9. System Implementation_____________________________________42
9.1 Implementation……………………………………...43
9.2 Problem Statement………………………………….43
9.3 Problem Definition………………………………….44
10. Conclusion_______________________________________________45
11. Appendices______________________________________________ 47
A. Sample Screens………………………………………48
B. Sample Code………………………………………….55
C. Hardware and Software Requirements…………….61
D. Bibliography………………………………………….61
MCA 2023-2025 1
INTRODUCTION
1. INTRODUCTION
Data entry screens are designed such that they are very user friendly and minimum typing is
required from the user,
The initial investigation for this project highlights the growing demand for accessible, reliable
gadget repair services and responsible e-waste disposal. With electronic devices becoming
indispensable in everyday life, users often face challenges when their gadgets malfunction.
Traditional repair services may be inconvenient, while doorstep repair offers added ease and
customer satisfaction. Additionally, the rise in e-waste poses environmental concerns, creating
a need for responsible collection and disposal solutions. This platform aims to address both
issues by providing users with a streamlined process to book repair services and request e-
waste pickups from their homes.
A market analysis reveals that while many repair services focus on in-store solutions, few
combine direct booking and e-waste collection in a single platform. By integrating both
services, this project fills a significant gap, catering to users who value convenience and
environmental responsibility. It aligns with global trends in sustainability, making it appealing
to tech-savvy and eco-conscious users. This unique approach also offers businesses a chance
to expand their service offerings, making the platform valuable to both customers and repair
stores alike.
The project’s technical requirements involve creating a robust system with four distinct user
roles: Admin, Technician, E-waste Collector, and Customer. Key functionalities include
booking management, real-time updates, and secure user profiles. Python, chosen for its
flexibility and support for web development, will ensure the platform is scalable, responsive,
and easy to maintain. With attention to usability, scalability, and data security, the project
aims to deliver a reliable platform that addresses customer needs, supports e-waste
management, and promotes sustainable practices.
System feasibility is a test or evaluation of the complete system plan. Such an evaluation is
necessary to define the application area along with the extend and capability to provide the
scope of computerization together with suggested output and input format and potential
benefits. Feasibility study is a proposal according to the work ability, impact on the
organization, ability to meet user’s needs and efficient use of resources. The feasibility study
is conducted to determine if the proposed system is feasible or not. Feasibility analysis
evaluates the candidate systems and determines the best system that needs performance
requirements. The purpose of feasibility study is to investigate the present system, evaluate
the possible application of computer-based methods, select a tentative system, evaluate the
cost and effectiveness of the proposed system, evaluate impact of the proposed system on
existing personnel and ascertain the need for new personnel. All projects are feasible when
given unlimited resources and infinite time. It is both necessary and prudent to evaluate the
feasibility of a project at the earliest possible time. A feasibility study is not warranted for
systems in which economic justification is obvious, technical risk is low, few legal problems
are expected and no reasonable alternative exists. An estimate is made of whether the
identified user needs may be satisfied using current software and hardware technologies. The
study will decide if the proposed system will be cost effective from the business point of view
and if it can be developed in the given existing budgetary constraints. The feasibility study
should be relatively cheap and quick. The result should inform the decision of whether to go
ahead with a more detailed analysis. Feasibility study may be documented as a separated
report to higher officials of the top-level management and can be included as an appendix to
the system specification. Feasibility and risk analysis are related in many ways. If there is
more project risk then the feasibility of producing the quality software is reduced.
TECHREVIVE is expected to achieve high user acceptance, as it aligns with the preferences
of modern customers who seek convenience in booking doorstep repair services. The user-
friendly interface caters to diverse user roles—customers, technicians, e-waste collectors, and
the admin—ensuring smooth onboarding and minimal training requirements. Technicians and
e-waste collectors will require only brief tutorials to manage their roles, while the admin, with
some training, can effectively oversee the system using an intuitive dashboard. Given the
efficient workflows and customer-centric features, user adaptation is anticipated to be smooth,
with a positive reception among all stakeholders.
SYSTEM ANALYSIS
Analysis is a structured method for identifying and solving problems. Analysis implies
breaking something into its parts so that the whole may be understood. The definition of
system analysis not only process analysis but also that of synthesis, which implies the process
of putting parts together to form a new whole. All the activities relating to the life cycle phase
must be performed managed and document. To design a system, we need requirements of the
system and the specification document are prepared in this phase. The purpose of this
document is to specify the functional requirement of the software that is to build. The
specifications are intended to guide the activities, relationships and all other objectives. The
main thing is to find what is to be done to solve the problems with the current system. In the
phase the problems or drawbacks of the current system is identified and the necessary actions
to solve these problems are recommended
The existing system for managing gadget repairs and e-waste disposal is fragmented and often
inconvenient for users. Typically, customers in need of repairs must rely on in-store service
centers or independent repair providers, which usually require them to either visit a physical
location or mail their devices for service. This process can be time-consuming and lacks the
flexibility needed in today’s busy lifestyle, as customers may face issues with transport, long
wait times, and limited access to reliable repair centers. Transparency is often lacking in terms
of service pricing and progress tracking, leaving users unsure of the status and quality of the
repair. Additionally, the process for e-waste disposal remains separate from repair services.
Users who wish to dispose of non-functional or outdated gadgets often must search
independently for recycling centers, municipal disposal programs, or specialized e-waste
management companies. This disconnection can lead to improper disposal practices, as users
may be unaware of or lack convenient access to disposal services, contributing to
environmental issues related to e-waste accumulation. In regions where recycling facilities are
scarce or inconveniently located, users may resort to storing old gadgets or discarding them
improperly, missing out on opportunities for responsible disposal and material recovery.
Overall, the existing system lacks a unified solution that could streamline both repair services
and e-waste collection, making it difficult for users to manage all their device-related needs
on a single platform. An integrated system that offers easy booking for gadget repairs along
with accessible e-waste disposal options would significantly enhance user convenience,
encourage eco-friendly practices, and better support customers in maintaining their devices
responsibly.
The proposed system is an integrated web platform designed to streamline gadget repair
services and e-waste management into a single, efficient solution. Customers will be able to
easily book doorstep repair services for various electronic devices, eliminating the need for
in-store visits. The platform will feature user registration and profile management, allowing
customers to track their repair requests, view service history, and receive real-time updates on
the status of their services, thereby enhancing transparency and trust.
In addition to repair services, the platform will incorporate an e-waste collection feature,
enabling users to request pickups for non-functional gadgets directly from their homes. E-
waste collectors will manage their collection assignments and log disposal sites, promoting
responsible recycling practices. The system will support four user roles—Admin, Technician,
E-waste Collector, and Customer—ensuring an efficient workflow and accountability. By
leveraging modern web technologies, the proposed system aims to enhance the customer
experience and contribute to environmental sustainability through responsible electronic
waste disposal.
A. Purpose
The purpose of this system is to provide a comprehensive web platform that allows users to
book gadget repair services and request e-waste collection from the comfort of their homes.
This system aims to enhance user convenience, promote responsible e-waste disposal, and
streamline the management of repair services.
B. Scope
The scope of the project includes the development of an online platform with the following
features:
• User registration and profile management
• Booking of repair services for various electronic gadgets
• E-waste collection request management
• Role-based access for Admin, Technician, E-waste Collector, and Customer
• Real-time status updates for repair requests and e-waste collections
• Administrative management of users and service requests
C. Overall Description
❖ Product Perspective
The "TECHREVIVE & E-WASTE" web application is a new, independent system designed
to streamline the management of electronic repair services and e-waste collection. It is a web-
based platform that leverages modern web development technologies such as HTML, CSS,
Bootstrap, Python, Django, jQuery, Ajax, and Javascript. The backend uses SQLite for
database management.
❖ Product Functions
• Admin Functions: User registration, service allocation, system management,
report generation, and user feedback management.
❖ User Characteristics
• Admin: Experienced in managing web applications, familiar with store
operations.
❖ Constraints
• The system must be compatible with Windows 11.
• The application should ensure data security and privacy for all users.
• The system must handle multiple user requests simultaneously without performance
degradation.
D. Functional Requirements
❖ User Registration and Authentication
• Users should be able to register with their basic details (name, email, password,
contact number).
• Users must be able to log in and log out securely.
❖ Profile Management
• Users can view and update their profile information.
• Users can view their repair request history and e-waste collection requests.
❖ Repair Service Booking
• Customers can browse available repair services and book a service by selecting a date
and time for the technician's visit.
• Customers will receive a confirmation of their booking and a unique request ID.
❖ E-Waste Collection Request
• Customers can request e-waste pickups, specifying the type and quantity of items.
• Customers will receive a confirmation of their e-waste collection request.
❖ System Design
The system architecture follows a client-server model, where the client interacts with the
application through a web browser, and the server processes requests using Python and
Django. The database layer is managed by SQLite.
• Front-end: HTML, CSS, Bootstrap, JavaScript, jQuery, Ajax.
• Database: SQLite.
❖ Data Flow
1. User Interaction: Users interact with the web application via a browser.
2. Request Handling: The Django server processes the requests, interacting with the
database.
3. Response Generation: The server sends back the processed data to the client for
display.
G. Conclusion
This SRS document outlines the key requirements for the Integrated Repair and E-Waste
Management System. The successful implementation of these requirements will ensure that
the system meets user needs, provides reliable services, and promotes environmentally
responsible practices.
MODULES
4.1 MODULES
In a software project, a module is a collection of source files and build settings that divides a
project into distinct units of functionality. Modules can be used to: Make software easier to
use, Define program boundaries, Implement separate modules for different areas of a program,
and Partition the system design or code.
Modules can be designed to be reusable and can be called by the program as needed. They
can also be imported from others, which may be called a library
Administrator is the person who manages the software. He/she is the person who focuses on
the data and reports of the software. He/she is the person who add brands, categories, districts,
places, products, yards. He/she also performs the allocation of service bookings and e-waste
collection requests.
The Technician module enables technicians to view and update their own information. In
addition, they can viewthe work assigned by the administration and can complete the work.
a) The system should have a provision to login the technician by
entering email id and password.
b) After logging in the technician have the permission to view and edit their profile.
c) The technician should have the permission to edit the password
that is already given by the admin.
d) The technician should have the permission to view the service
bookings allocated to do that are assigned by the admin.
e) Technician should have the provision to accept and reject the assigned service.
The E-Waste Collector module is designed for collectors to manage e-waste collection
requests and ensure responsible disposal.They can also view and update their own
information. In addition, they can view the work assigned by the administration and can
complete the work of collecting e-waste. Also have a provision to select the yard where the
collector dumped the e-waste.
a) The system should have a provision to login the e-waste collector by entering email
id and password.
b) After logging in the collector have the permission to view their profile details.
c) The collector should have the permission to edit the password that is already given
by the admin.
d) The collector should have the provision to view the allocated e-waste collection
requests.
e) Collector should have the provision to confirm and reject the collection request
allocated to them.
f) Collector should have the provision to select the yard where the e-waste is dumped
after collecting.
g) Collector should have the provision to view the confirmed collection requests.
h) System should have the provision to log out.
4.1.4 Customer
The Customer module allows users to easily access repair services and e-waste collection
through a straightforward interface.They are main users of this application. They can book
repair services for their electronic appliances at doorstep. Also can send an e-waste collection
request for collecting e-wastes. They can post complaints regarding the service done by
technician or send feedback about the web application.
a) The system should have a provision to register a new user by filling a registration
form.
b) The registered customers can log into the system by entering email id and password.
c) After logging in customer must have a provision to view their profile and edit profile.
d) Customers should have the permission to change password.
e) There should a provision for customers in order to book service by submitting a form.
f) Customer should have a provision to view their service request and its status.
g) Customer should have the permission to view bill details of the service and a provision
for payment.
h) Customer should have the provision to request e-waste collection.
i) Customer should have the provision to view their given e-waste collection requests and
its status.
j) Customer should have the provision to give complaints against technicians and view
reply.
k) Customer should have the provision to give feedback regarding the web application.
FLOW DIAGRAMS
DFD is the abbreviation for Data Flow Diagram. The flow of data of a system or a process is
represented by DFD. It also gives insight into the inputs and outputs of each entity and the
process itself. DFD does not have control flow and no loops or decision rules are present.
Specific operations depending on the type of data can be explained by a flowchart. Data Flow
Diagram can be represented in several ways. The DFD belongs to structured-analysis
modeling tools. Data Flow diagrams are very popular because they help us to visualize the
major steps and data involved in software-system processes.
External entity: An outside system that sends or receives data, communicating with the
system being diagrammed. They are the sources and destinations of information entering or
leaving the system. They might be an outside organization or person, a computer system or a
business system. They are also known as terminators, sources and sinks or actors. They are
typically drawn on the edges of the diagram.
Process: Input to output transformation in a system takes place because of process function.
The symbols of a process are rectangular with rounded corners, oval, rectangle or a circle.
The process is named a short sentence, in one word or a phrase to express its essence.
Data Flow: Data flow describes the information transferring between different parts of the
systems. The arrow symbol is the symbol of data flow. A relatable name should be given to
the flow to determine the information which is being moved. Data flow also represent
material along with information that is being moved. Material shifts are modeled in systems
that are not merely informative. A given flow should only transfer a single type of
information. The direction of flow is represented by the arrow which can also be bi-
directional.
Data Store: Also known as warehouse. The data is stored in the warehouse for later use. Two
horizontal lines represent the symbol of the store. The warehouse is simply not restricted to
being a data file rather it can be anything like a folder with documents, an optical disc, a filing
cabinet. The data warehouse can be viewed independent of its implementation. When the data
flow from the warehouse it is considered as data reading and when data flows to the
warehouse it is called data entry or data updation.
Levels of DFD
DFD uses hierarchy to maintain transparency thus multilevel DFD’s can be created. Levels of
DFD are as follows:
◼ 0-levelDFD
◼ 1-levelDFD
◼ 2-levelDFD
Rules for creating DFD
❖ The name of the entity should be easy and understandable without any extra assistance
❖ The processes should be numbered or put in ordered list to be referred easily.
❖ The DFD should maintain consistency across all the DFD levels.
❖ A single DFD can have maximum processes upto 9 and minimum 3 processes.
LEVEL 1-ADMIN
LEVEL 1-USER
LEVEL 1-TECHNICIAN
SYSTEM DESIGN
System designing is the process of defining the architecture, components, modules, interfaces
and data for a system to satisfy specified requirements. it is a solution to a “how to” approach
compared to system analysis which is a “what is” orientation. it translates the system
requirements into ways of making them operational. The design phase focuses on the detailed
implementation of the system recommended in the feasibility study. The system which is in
making is developed by working on two different modules and combining them to work as a
single unit. That single unit is the one which is known as the new software. We go through the
different design strategies to design the system we are talking about. In the input design we
decide which type of input screens are going to be used for the system in making. In the
output design we decide the output screens and the reports that will be used to give the output
and in the database design we decide what all tables will be required and what all fields will
be there in those tables. Each of them discussed briefly below.
Input design converts user-oriented inputs to computer-based formats, which requires careful
attention. The collection of input data is the most expensive part of the system in terms of the
equipment used and the number of people involved. In input design, data is accepted for
computer processing and input to the system is done through mapping via a map support or
links. Inaccurate input data is the most common cause of errors in data processing. The input
screens need to be designed more carefully and logically. A set of menus is provided which
help for better application navigation. While entering data in the input forms, proper
validation checks are done and messages will be generated by the system if incorrect data has
been entered. The objective of input design is to create an input layout that is easy to follow
and prevent operator errors. It covers all phases of input from creation of initial data into
actual entry of the data to the system for processing. The input design is the link that ties the
system into world of its users. The user interface design is very important for any application.
The interface design defines how the software communication within itself, to system that
interpreted with it and with human who use it. The input design requirements such as user
friendliness, consistent format and interaction dialogue for giving the right message and help
for the user at right time are also considered for the development of the project.
Outputs are the most important and useful information to the user and to the department.
Intelligent output designs will improve systems relationships with the user and help much in
decision-making. Outputs are also used to provide a permanent hard copy of the results for
later use. The forms used in the system are shown in the appendix. The outputs also vary in
terms of their contents, frequency, timing and format. The users of the output, its purpose and
sequence of details to be printed are all considered. The output forms a system in the
justification for its existence. If the outputs are inadequate in any way, the system itself is
inadequate. The basic requirements of output are that it should be accurate, timely and
appropriate, in terms of content, medium and layout for its intended purpose. Hence it is
necessary to design output so that the objectives of the system are met in the best possible
manner.
The efficiency of an application using SQLITE-3 Server is mainly dependent upon the
database tables, the fields in each table and joined using the fields contained in them to
retrieve the necessary information. A table is a set of data elements that is organized using a
model of vertical columns and horizontal rows. A table has a specified number of columns,
but can have any number of rows. Each row is identified by the values appearing in a
particular column subset which has been identified as a unique key index. The primary
objective of a database design is fast response time to inquiries, more information at low cost,
control of redundancy, clarity and ease of use, accuracy and integrity of the system fast
recovery and availability of powerful end-user language.
1. Admin
2. User
3. Ewastecollector
4. Technician
5. Brand
6. Category
7. District
8. Place
9. Gallery
10. Type
11. Yard
12. Collectedewaste
13. Servicebill
14. Complaint
15. Ewastebooking
16. Feedback
17. Servicebook
18. Assignewastebooking
19. Assignservicebook
20. Product
1.Table: Admin
Description: This table is used to store the details of admin.
Sl.n Field Name Data type Size Constraints
o
1 id IntegerField Primary key
2 admin_name CharField 100 Not Null
3 admin_email CharField 100 Not Null
4 admin_password CharField 50 Not Null
2. Table: Brand
Description: This table is used to store brand names.
3. Table: User
Description: This table is used to store the details of user.
Sl.no Field Name Data type Size Constraints
1 id IntegerField Primary key
2 user_name CharField 50 Not Null
3 user_gender CharField 50 Not Null
4 user_contact CharField 50 Not Null
5 user_email CharField 50 Not Null
6 user_photo FileField Not Null
7 user_proof FileField Not Null
8 user_password CharField 50 Not Null
9 user_address CharField 100 Not Null
10 place IntegerField ForeignKey
4. Table: Ewastecollector
Description: This table is used to store details of e-waste collector.
Sl.no Field Name Data type Size Constraints
1 id IntegerField Primary key
2 Ewastecollector_name CharField 50 Not Null
3 Ewastecollector_contact CharField 50 Not Null
4 Ewastecollector_email CharField 50 Not Null
5 Ewastecollector_photo FileField Not Null
6 Ewastecollector_proof FileField Not Null
7 Ewastecollector_password CharField 50 Not Null
8 Ewastecollector_vehicleno CharField 50 Not Null
9 Ewastecollector_vehiclemodel CharField 50 Not Null
10 Ewastecollector_vehicleimg FileField Not Null
5. Table: Technician
Description: This table is used to store details of technician.
6. Table: Category
Description: This table is used to store category names.
7. Table: District
Description: This table is used to store district names.
The front end of a website is what users directly interact with, built using HTML, CSS,
JavaScript, and Bootstrap. HTML provides the structure of web pages, laying out elements
like headings, paragraphs, and links. CSS styles these elements, adding colors, fonts, and
layouts to make the site visually appealing. JavaScript enables interactivity, allowing users to
engage with dynamic features like buttons and animations. Finally, Bootstrap offers us
various pre-designed components and styles for creating responsive and modern layouts
across various devices, making development faster and more consistent. Together, these tools
create a visually appealing and user-friendly web experience.
The back end of a Django application is developed using Python, a versatile and easy-to-read
programming language. In Django, Python handles all server-side logic, including managing
requests, processing data, and interacting with the database. Python's readability and extensive
libraries make it ideal for creating robust and scalable web applications, enabling Django to
provide a smooth, efficient back end experience.
7.3 FrameWork:Django
Django is a high-level web framework for building backend applications using Python. It
simplifies web development by providing built-in tools for handling database management,
URL routing, authentication, and more. Django follows the Model-View-Template (MVT)
architecture, which promotes organized and maintainable code, making it easy to build robust
and secure applications quickly.
Visual Studio Code (VS Code) is a lightweight and powerful code editor used as the primary
platform for developing and managing the project. With support for multiple programming
languages, extensions, and features like debugging, syntax highlighting, and Git integration,
VS Code makes coding, testing, and deploying applications convenient and efficient. It’s
especially helpful for Django development, as it provides tools to streamline coding in Python
and managing web files in one workspace.
7.5 Database:SQLite
SQLite is a lightweight, self-contained database engine that Django uses by default. It stores
data in a single file on disk, making it simple to set up and ideal for development and small
projects. SQLite requires minimal configuration and provides essential features for managing
data, like creating tables, querying data, and handling relationships. Although it's not typically
used for high-traffic applications, SQLite is highly effective for testing, prototyping, and
small-scale applications due to its simplicity and portability.
TESTING
8. TESTING
environment that closely resembles the production environment where the application will be
finally deployed. The perquisites for System Testing are: -
SYSTEM IMPLEMENTATION
9.SYSTEM IMPLEMENTATION
9.1 Implementation
Implementation includes placing the system into operation and providing the users and
operation personnel with the necessary documentation to use and maintain the new system.
Implementation includes all those activities that take place to convert from the old system to
the new. The new system may be totally new, replacing an existing system. Proper
implementation is essential to provide a reliable system to meet the organizational
requirements. Successful implementation may not guarantee improvement in the organization
using the new system, as well as, improper installation will prevent. There are four methods
for handling a system conversion. The Implementation Plan describes how the information
system will be deployed, installed and transitioned into an operational system. The plan
contains an overview of the system, a brief description of the major tasks involved in the
implementation, the overall resources needed to support the implementation effort, and any
site-specific implementation requirements. The plan is developed during the Design Phase
and is updated during the Development Phase the final version is provided in the Integration
and Test Phase and is used for guidance during the Implementation Phase. The
implementation phase ends with an evaluation of the system after placing it into operation of
time. The validity and proper functionality of all the modules of the developed application is
assured during the process of implementation. Implementation is the process of assuring that
the information system is operational and then allowing user to take over its operation for use
and evaluation. Implementation is the stage in the project where the theoretical design is
turned into a working system. The implementation phase constructs, installs and operated the
new system. The most crucial stage in achieving a new successful system is that it works
effectively and efficiently.
In today's technology-driven world, the reliance on electronic gadgets has surged, leading to
significant challenges in managing their maintenance and disposal. Customers often struggle
to find reliable repair services, resulting in inconvenience and frustration due to lengthy
processes, limited availability, and a lack of transparency regarding service status and pricing.
The problem at hand is the increasing reliance on electronic gadgets, which, while enhancing
convenience and connectivity, also creates significant challenges in their maintenance and
responsible disposal. Customers frequently encounter difficulties in accessing reliable repair
services, facing issues such as inconvenient booking processes, lack of transparency regarding
service availability, and inadequate communication about repair statuses. Furthermore, the
improper disposal of e-waste poses severe environmental hazards, with many users lacking
awareness of proper recycling practices and struggling to find accessible e-waste collection
services. The fragmented nature of existing solutions exacerbates these challenges, resulting
in inefficiencies and increased electronic waste in landfills. Thus, there is a critical need for a
comprehensive platform that integrates gadget repair services with e-waste management,
simplifying the user experience and fostering responsible electronic waste disposal.
CONCLUSION
10 . CONCLUSION
The project was successfully completed within the time span allotted. All the modules are
tested separately and put together to form the main system. Finally, the modules are tested
with real data and it worked successfully. Thus the system has fulfilled the entire objective
defined.
This project will help the customer to book their electronic appliances related services in
TECHREVIVE. Our goal of developing this “TECHREVIVE” has come to get a good result
without many defects.
The main motive for developing this system is for the welfare of the society by giving respect
to the time of each person and to protect the environment from electronic wastes related
pollution. Since our daily live depends on electronic gadgets it is required to provide services
related to it at any time in best manner.
FUTURE ENHANCEMENTS
The system has been designed in such a way that it can be modified with very little effort
when such needs arise in the future. New features can be added with slight modifications of
software which make it easy to expand the scope of this project. Though the system is
working on various assumptions, it can be modified easily to any kind of requirements.
Even though we have tried our best to present the information effectively and efficiently, yet
there can be further enhancement in the application. We have taken care of all the critical
aspects, which were needed to be taken care of. Because of fast changes in the world of
programming this system will gradually get outdated and less effective. For the time being it’s
possible to overcome problems by amendments and minor modifications to acknowledge the
need of fundamental design. Though the new system provides base for improving the
efficiency of operations, there are a lot of future enhancements that can be added to this
project. Keeping this in view, a provision has been made in the system to facilities easy
modification updating in the future. Any modification will not affect the normal working of
the system. It can also be converted into a mobile application.
APPENDICES
11. APPENDICES
Home Page
Login Page
User Registration
User Homepage
User Profile
User Complaint
Admin Dashboard
Add Yards
Technician Registration
Technician homepage
Generate Bill
def homepagetechnician(request):
if 'tid' in request.session:
techn=Technician.objects.get(id=request.session["tid"])
return render(request,"Technician/Technicianhomepage.html",{'data':techn})
else:
return redirect('guest:Home')
def TechnicianMyProfile(request):
if 'tid' in request.session:
techn=Technician.objects.get(id=request.session["tid"])
return render(request,"Technician/TechnicianMyProfile.html",{'data':techn})
else:
return redirect('guest:Home')
def TechnicianEditProfile(request):
if 'tid' in request.session:
techn=Technician.objects.get(id=request.session["tid"])
if request.method=="POST":
techn.technician_name=request.POST.get('txt_name')
techn.technician_contact=request.POST.get('txt_contact')
techn.technician_address=request.POST.get('txt_address')
techn.save()
return redirect("technician:technicianprofile")
else:
return render(request,"Technician/TechnicianEditProfile.html",{'data':techn})
else:
return redirect('guest:Home')
def TechnicianChangePass(request):
if 'tid' in request.session:
if request.method=="POST":
techcount=Technician.objects.filter(id=request.session["tid"],technician_password=request.P
OST.get('txt_curr')).count()
if techcount>0:
techn=Technician.objects.get(id=request.session["tid"],technician_password=reques
t.POST.get('txt_curr'))
techn.technician_password=request.POST.get('txt_new')
techn.save()
return redirect("technician:technicianhome")
else:
return render(request,"Technician/TechnicianChangePassword.html")
else:
return redirect('guest:Home')
def TechnicianAssignedService(request):
if 'tid' in request.session:
serv=Assignservicebook.objects.filter(technician=request.session["tid"])
return render(request,"Technician/ViewAllocatedServices.html",{'res':serv})
else:
return redirect('guest:Home')
def ConfirmServ(request,cid):
if 'tid' in request.session:
serv=Assignservicebook.objects.get(id=cid)
serv.asb_status=2
serv.save()
return redirect('technician:Myassignedservice')
else:
return redirect('guest:Home')
def DeleteServ(request,cid):
if 'tid' in request.session:
serv=Assignservicebook.objects.get(id=cid)
bokid=serv.servicebooking_id
sbok=Servicebook.objects.get(id=bokid)
sbok.Servicebook_status=1
sbok.save()
serv.delete()
return redirect('technician:Myassignedservice')
else:
return redirect('guest:Home')
def ConfirmedServices(request):
if 'tid' in request.session:
serv=Assignservicebook.objects.filter(technician=request.session["tid"])
return render(request,"Technician/ViewConfirmedServices.html",{'res':serv})
else:
return redirect('guest:Home')
def ServiceBill(request,bid):
if 'tid' in request.session:
serv=Assignservicebook.objects.get(id=bid)
if request.method=="POST":
Servicebill.objects.create(servicebill_amount=request.POST.get('txt_amount'),service
bill_noofdays=request.POST.get('txt_days'),servicebill_partamount=request.POST.get('txt_pa
rts'),servicebill_additionaldetails=request.POST.get('txt_replaced'),servicebill_details=request
.POST.get('txt_issue'),assignedservicebooking=serv)
serv.asb_status=3
serv.save()
bokid=serv.servicebooking_id
sbok=Servicebook.objects.get(id=bokid)
sbok.Servicebook_status=4
sbok.save()
return redirect('technician:viewconfimedservice')
else:
return render(request,"Technician/GenerateBill.html",{'data':serv})
else:
return redirect('guest:Home')
def logout(request):
del request.session['tid']
return redirect('guest:Home')
EwasteCollector registration
{% extends 'Admin/Head.html' %}
{% load static %}
{% block content %}
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Document</title>
</head>
<body>
<div id="tab">
<br>
<br>
<form method="post" enctype="multipart/form-data">
{% csrf_token %}
<table border="1" align="center">
<tr>
<th colspan="2"><i><b>Ewaste Collector Registration</b></i></th>
</tr>
<tr>
<td>Name:</td>
<td><input type="text" name="txt_name" required="required"></td>
</tr>
<tr>
<td>Contact:</td>
<td><input type="text" name="txt_num" required="required"></td>
</tr>
<tr>
<td>Email:</td>
<td><input type="email" name="txt_email" required="required"></td>
</tr>
<tr>
<td>Password:</td>
<td><input type="password" name="txt_pass" required="required"></td>
</tr>
<tr>
<td>Photo:</td>
<td><input type="file" name="file_photo" required="required"></td>
</tr>
<tr>
<td>Driving Licence:</td>
<td><input type="file" name="file_lphoto" required="required"></td>
</tr>
<tr>
<td>Vehicle Number:</td>
<td><input type="text" name="txt_vnumber" required="required"></td>
</tr>
<tr>
<td>Vehicle Modelname:</td>
<td><input type="text" name="txt_vname" required="required"></td>
</tr>
<tr>
<td>Vehicle Image:</td>
<td><input type="file" name="file_vphoto" required="required"></td>
</tr>
<tr>
<td colspan="2"><center><input type="submit"
name="btn_submit"> <input type="reset" name="btn_cancel"
value="Cancel"></center></td>
</tr>
</table>
<br>
<br>
<br>
<table border="1" align="center">
<tr><th colspan="10"><i><center>Ewaste Collectors</center></i></th></tr>
<tr>
<th>Sl No</th>
<th>Name</th>
<th>Contact</th>
<th>Email</th>
<th>Photo</th>
<th>Driving Licence</th>
<th>Vehicle Number</th>
<th>Vehicle Modelname</th>
<th>Vehicle Image</th>
<th>Action</th>
<tr>
{% for i in result %}
<tr>
<td>{{forloop.counter}}</td>
<td>{{i.EwasteCollector_name}}</td>
<td>{{i.EwasteCollector_contact}}</td>
<td>{{i.EwasteCollector_email}}</td>
<td><img src="{{i.EwasteCollector_photo.url}}" width="150" height="150"></td>
● Hardware Requirements
● Software Requirements
APPENDICES D: Bibliography
Book References:
Publications:
1. Dauzon, S., Bendoraitis, A., & Ravindran, A. (2016). Django: web development with
Python. Packt Publishing Ltd . Publisher Site | Google Scholar
2. Shaw, B., Badhwar, S., Bird, A., KS, B. C., & Guest, C. (2021). Web Development
with Django: Learn to build modern web applications with a Python-based framework.
Packt Publishing Ltd. Publisher Site | Google Scholar
3. Vincent, W. S. (2022). Django for Beginners: Build websites with Python and Django.
WelcomeToCode.. Publisher Site | Google Scholar
4. Kiddee, P., Naidu, R., & Wong, M. H. (2013). Electronic waste management
approaches: An overview. Waste management, 33(5), 1237-1250. Publisher Site | Google
Scholar
5. Mundada, M. N., Kumar, S., & Shekdar, A. V. (2004). E‐waste: a new challenge for
waste management in India. International journal of environmental studies, 61(3), 265-
279. Publisher Site | Google Scholar
Website References: