Prem

218368
“RENTAL PROPERTY”
A PROJECT REPORT
Submitted by
PREM NITINKUMAR PAREKH
181110107029
In partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
in
COMPUTER ENGINEERING
MAHAVIR SWAMI COLLEGE OF ENGINEERING AND
TECHNOLOGY, SURAT
Gujarat Technological University, Ahmedabad
April, 2022
Gujarat Technological University MSCET

218368
Mahavir Swami College of Engineering and Technology

BMEF Campus, Bharthana Road, Vesu, Surat, Gujarat 395017
CERTIFICATE
This is to certify that the project report submitted along with the project entitled
Rental Property has been carried out by Prem Nitinkumar Parekh under my
guidance in partial fulfillment for the degree of Bachelor of Engineering in
Computer Engineering, 8th Semester of Gujarat Technological University,
Ahmadabad during the academic year 2021-22.
Prof. Ms. Riddhi Desai Prof. Ms. Alpa Valand

Internal Guide Head of the Department

218368

218368
Mahavir Swami College of Engineering and Technology

BMEF Campus, Bharthana Road, Vesu, Surat, Gujarat 395017
DECLARATION
We hereby declare that the Internship / Project report submitted along with the
Internship / Project entitled Rental Property submitted in partial fulfillment for
the degree of Bachelor of Engineering in Computer Engineering to Gujarat
Technological University, Ahmedabad, is a bonafide record of original project
work carried out by me / us at Itabtech Infosys under the supervision of Mr.
Nikunj Vaghasiya and that no part of this report has been directly copied from
any students’ reports or taken from any other source, without providing due
reference.
Name of the Student Sign of Student
1 ______________________ _______________
Gujarat Technological University i MSCET

218368
ACKNOWLEDGEMENT
The satisfaction that accompanies the successful completion of any task would be
incomplete without the mention of people whose ceaseless corporation made it possible,
whose constant guidance and encouragement grown all effort with success.
Our sincere thanks to our Faculty guide: Prof. Ms. Riddhi Desai, External Guide: Mr.
Nikunj Vaghasiya and H.O.D: Prof. Ms. Alpa Valand for providing valuable guidance
throughout our project work. Whenever we were confused about anything, they were
always there to help us.
We are thankful to Gujarat Technological University to giving the opportunity for assigning
this Summer Internship work.
Prem Nitinkumar Parekh (181110107029)
Gujarat Technological University ii MSCET

218368
ABSTRACT
This Software Requirements Specification provides a complete description of all

the functions and specifications of Rental Property. With the help of this people
can easily rent their property, buy property on rent, also they can register
themselves as owner/ customer. This website is fully based on Bangalore city,
Karnataka but customers from any place can register themselves and can buy
properties on rent. Categories like Apartments, houses, villas, etc., are also
available for user and owner. Other features like one can get complete
information related to the website and their works, founders, co- founders etc.
Gujarat Technological University iii MSCET

218368
List of Figures
Fig 1.3 Organization chart................................................................................2
Fig 2.3 Schematic Layout of company’s operation..........................................5
Fig 3.6.1 Phases of waterfall model…...............................................................10
Fig 4.8.3 Google Map API.................................................................................21
Fig 5.1.1 Use-case Diagram of registered user..................................................25
Fig 5.1.2 Use-case Diagram for Unregistered Owner........................................26
Fig 5.1.3 Use-case Diagram for Unregistered User...........................................26
Fig 5.1.4 Use-case Diagram of Registered Owner.............................................27
Fig 5.1.5 Use-case Diagram of admin................................................................28
Fig 5.3.1.1.1 Home page for CRUD form................................................................39
Fig 5.3.1.1.2 Registration form for CRUD..............................................................39
Fig 5.3.1.1.3 Login form for CRUD….....................................................................40
Fig 5.3.1.1.4 News Archives....................................................................................40
Fig 5.1.1.1.5 View news for CRUD.........................................................................40
Fig 5.3.1.1.6 Edit news for CRUD...........................................................................41
Fig 5.3.1.1.7 Delete news for CRUD.......................................................................41
Fig 5.3.1.1.8 Add news for CRUD...........................................................................41
Fig 5.3.1.1.11.1 Google map with database..................................................................42
Fig 5.3.1.1.11.2 Google map without database.............................................................43
Fig 5.3.1.1.11.3 Implementation of Google map directly.............................................43
Fig 6.1.1 Home page…......................................................................................44
Fig 6.1.2 Signup page for user...........................................................................45
Fig 6.1.3 Signup for owner................................................................................46
Fig 6.1.4 Explore homes....................................................................................47
Fig 6.1.5 Refer & Earn......................................................................................47
Fig 6.1.6 About us.............................................................................................47
Fig 6.1.7 Information for owner........................................................................48
Fig 6.1.8 Property Management information for owner...................................49
Fig 6.1.9 How the website functions- information for owner...........................50
Fig 6.1.10 FAQ…................................................................................................51
Fig 6.1.11 Terms & Condition............................................................................51
Fig 6.1.12 Privacy Policy....................................................................................52
Fig 6.1.13 Flats for rent.......................................................................................52
Fig 6.1.14 Contact us...........................................................................................53
Fig 6.1.15 Customer Support...............................................................................53
Fig 6.1.16 Login User..........................................................................................53
Fig 6.1.17 User Dashboard..................................................................................54
Fig 6.1.18 Change user profile............................................................................54
Fig 6.1.19 Change user password…....................................................................54
Fig 6.1.20 Explore home after login....................................................................55
Fig 6.1.21 After accepting ..................................................................................55
Gujarat Technological University iv MSCET

218368
Fig 6.1.22 After accepting terms.........................................................................55

Fig 6.1.23 Owner Login- Send OTP...................................................................56
Fig 6.1.24 Enter OTP for owner login................................................................56
Fig 6.1.25 Owner Dashboard..............................................................................56
Fig 6.1.26 Properties of owner............................................................................57
Fig 6.1.27 Change owner profile.........................................................................57
Fig 6.1.28 Add property- Owner.........................................................................58
Fig 6.1.29 Login for Admin................................................................................59
Fig 6.1.30 Admin Dashboard..............................................................................59
Fig 6.1.31 Customer list......................................................................................60
Fig 6.1.32 Pending owner list.............................................................................60
Fig 6.1.33 Accepted owner list...........................................................................60
Fig 6.1.34 List of countries.................................................................................61
Fig 6.1.35 List of States......................................................................................61
Fig 6.1.36 List of Cities......................................................................................62
Fig 6.1.37 List of added Area.............................................................................62
Fig 6.1.38 List of Attributes................................................................................63
Fig 6.1.39 List of Properties...............................................................................63
Fig 6.1.40 Settings for Email..............................................................................64
Fig 6.1.41 List of Frequently Asked Questions..................................................64
Fig 6.1.42 List of Property Booking...................................................................65
Fig 6.1.43 List of Scheduled Visits.....................................................................65
Fig 6.1.44 List of Inquiry....................................................................................65
Fig 8.2 Photograph of Visit by Mentor..........................................................70
Gujarat Technological University v MSCET

218368
List of Tables
Table 3.6.4 Group Dependencies.........................................................................12
Table 3.7 Gantt Chart for Internship Schedule.................................................13
Table 4.8.2.1 Meaning of XAMPP.........................................................................19
Table 4.8.2.2 Components of XAMPP...................................................................20
Table 5.2.1 Database for Category......................................................................29
Table 5.2.2 Database for City..............................................................................29
Table 5.2.3 Database for Area.............................................................................29
Table 5.2.4 Database for Company Info.............................................................30
Table 5.2.5 Database for Countries.....................................................................30
Table 5.2.6 Database for Customers...................................................................30
Table 5.2.7 Database for Customer Master.........................................................31
Table 5.2.8 Database for Distributor...................................................................31
Table 5.2.9 Database for Email Setting...............................................................31
Table 5.2.10 Database for Faq...............................................................................31
Table 5.2.11 Database for Members.....................................................................32
Table 5.2.12 Database for Member Staff..............................................................32
Table 5.2.13 Database for Owner Details.............................................................33
Table 5.2.14 Database for Process........................................................................33
Table 5.2.15 Database for Process Assign............................................................33
Table 5.2.16 Database for Process Inner..............................................................33
Table 5.2.17 Database for Process Status.............................................................34
Table 5.2.18 Database for Products......................................................................34
Table 5.2.19 Database for Property Attributes.....................................................34
Table 5.2.20 Database for Property Booking.......................................................35
Table 5.2.21 Database for Property Images.........................................................35
Table 5.2.22 Database for Property Owner..........................................................35
Table 5.2.23 Database for Property Visit.............................................................36
Table 5.2.24 Database for Rentprop4u Setting....................................................36
Table 5.2.25 Database for Rent Property.............................................................36
Table 5.2.26 Database for States..........................................................................37
Table 5.2.27 Database for Table Attributes..........................................................37
Table 5.2.28 Database for Table Attributes Input Field.......................................37
Table 5.2.29 Database for Table Attributes Input Option....................................38
Table 5.2.30 Database for User Inquiry................................................................38
Table 5.2.31 Database for User Type...................................................................38
Table 5.3.1.1.9 Database for News...........................................................................42
Table 5.3.1.1.10 Database for User.............................................................................42
Table 5.3.1.1.11 Database for Google APIs...............................................................43
Table 7.2.1 Test Cases........................................................................................69
Table 8.3.1 Continuous Evaluation (CE-I) ........................................................71
Table 8.3.2 Continuous Evaluation (CE-II) .......................................................71
Gujarat Technological University vi MSCET

218368
List of Abbreviations
HTML Hyper-Text Markup Language
CSS Cascading Style Sheet
SQL Structured Query Language
PHP Hypertext Preprocessor
XAMPP Cross-platform, Apache, DeMaria (MySQL), PHP, Perl
API Application Programming Interface
VS code Visual Studio Code
DB Database
OTP One Time Password
MVC Model, View, Controller
CRUD Create, Read, Update, Delete
LOC Lines Of Code
Gantt Generalized Activity Normalization Time Table
GB Gigabyte
SSD Solid State Drive
HDD Hard Disk Drive
Mbps Megabits per second
Gujarat Technological University vii MSCET

218368
Table of Contents
Declaration……..............................................................................................................i
Acknowledgment……....................................................................................................ii
Abstract …….................................................................................................................iii
List of Figures …….......................................................................................................iv
List of Tables …….........................................................................................................vi
List of Abbreviations ……............................................................................................vii
Table of Contents ……................................................................................................viii
Chapter 1 Overview of the Company .............................................................................1
1.1 History...........................................................................................................1
1.2 Different products..........................................................................................1
1.3 Organization chart ........................................................................................2
1.4 Capacity of plant ..........................................................................................2
Chapter 2 Overview of different departments.................................................................3
2.1 Details about the work being
carried out in each department. ...........................................................................3
2.2 List the technical specifications of major equipment
used in each department…............................................................................4
2.3 Schematic layout of
operations for manufacturing of end product. .............................................5
2.4 Details about each stage of production. ........................................................5
Chapter 3 Introduction to Internship..............................................................................7
3.1 Internship Summary......................................................................................7
3.2 Purpose..........................................................................................................7
3.3 Objective ......................................................................................................8
3.4 Scope……………………………….............................................................8
3.5 Technology and Literature Review ..............................................................9
3.6 Internship Planning…………......................................................................10
3.6.1 Internship Development Approach and Justification ...................10
3.6.2 Internship Effort and Time, Cost Estimation ...........................................12
3.6.3 Roles and Responsibilities ...........................................................12
3.6.4 Group Dependencies ....................................................................12
3.7 Internship Scheduling...................................................................................13
Chapter 4 System Analysis ............................................................................................14
4.1 Study of Current System ..............................................................................14
4.2 Problem and Weaknesses of Current System ..............................................14
4.3 Requirements of New System .....................................................................14
Gujarat Technological University viii MSCET

218368
4.4 System Feasibility .......................................................................................14

4.4.1 Does the system contribute to the overall objectives
of the organization? ..................................................................14
4.4.2 Can the system be implemented using the current technology
and within the given cost and schedule constraints ...................14
4.4.3 Can the system be integrated with other systems
which are already in place? ........................................................15
4.5 Process in New System.................................................................................15
4.6 Features of New System................................................................................15
4.7 List of Main Modules....................................................................................16
4.8 Selection of Software....................................................................................16
4.8.1 CodeIgniter – Overview.................................................................16
4.8.1.1 Why CodeIgniter?.......................................................................16
4.8.2 XAMPP – Overview......................................................................19
4.8.3 Google APIs – Overview...............................................................21
4.8.4 The Languages Used for Web Development.................................24
4.8.5 Editor: Visual Studio Code............................................................24
Chapter 5 System Design ...............................................................................................25
5.1 System Design & Methodology ...................................................................25
5.2 Database Design...........................................................................................29
5.3 Input / Output and Interface Design.............................................................39
5.3.1 Samples of Forms, Reports, and Interface ....................................39
5.3.1.1 Tasks in CodeIgniter...................................................................39
5.3.1.1.1 Home Page...............................................................................39
5.3.1.1.2 Register....................................................................................39
5.3.1.1.3 Login........................................................................................40
5.3.1.1.4 News Archives.........................................................................40
5.31.1.5 View News................................................................................40
5.3.1.1.6 Edit News.................................................................................41
5.3.1.1.7 Delete News.............................................................................41
5.3.1.1.8 Add News.................................................................................41
5.3.1.1.9 Database Structure for News....................................................42
5.3.1.1.10 Database Structure for User...................................................42
5.3.1.1.11 Task to Implement Google Map APIs...................................42
Chapter 6 Implementation .............................................................................................44
6.1 Implementation Environment ......................................................................44
6.2 Modules Specifications.................................................................................66
6.3 Results...........................................................................................................66
6.4 Result Analysis.............................................................................................66
Gujarat Technological University ix MSCET

218368
Chapter 7 Testing.............................................................................................................67
7.1 Testing Plan....................................................................................................67
7.1.1 Black Box Testing...........................................................................67
7.1.2 White Box Testing...........................................................................67
7.1.3 Unit Testing.....................................................................................68
7.1.4 Integration Testing...........................................................................68
7.2 Test Results and Analysis...............................................................................69
7.2.1 Test Cases........................................................................................69
Chapter 8 Conclusion and Discussion..............................................................................70
8.1 Overall Analysis of Internship Viabilities......................................................70
8.2 Photographs and date of Surprise Visit by institute Mentor...........................70
8.3 Dates of Continuous Evaluation (CE-I and CE-II) ....................................... 71
8.4 Problem Encountered and Possible Solutions.................................................71
8.5 Summary of Internship work..........................................................................72
8.6 Limitations and Future Enhancement.............................................................73
References.........................................................................................................................74
Appendix............................................................................................................................75
Gujarat Technological University x MSCET

218368 Overview of the Company
CHAPTER –1
OVERVIEW OF THE COMPANY
Itabtech Infosys is a multi-skilled software service provider with a highly competent

workforce and a strong global presence.
We have an Immense Expert in Our Team with Several Years of Experience. A leader’s
responsibility is to help their organization and the people they serve to grow and prosper.
Successful leadership is the ability to create and sustain enough momentum to assure that
the marketplace and competitors don’t pass you by. This requires leaders to prepare for the
future, while equally staying on point with the present. The constant distraction in our daily
work lives makes it difficult for leaders to do both; yet with solid preparation what seems
impossible becomes highly probable.
1.1 HISTORY
From 2015 till the present, we take up the most innovative project of the world and
implement them with the Rapid Agile Development. We make sure you never get a bloated
project scope document when it comes to the timeline estimation, budget estimation, and
maintaining the quality standards. All clauses are kept real and genuine.
We have always worked with the real inventors to create disruptive technologies that have
never been built before. In the world when everyone speaks of expertise, we are the real
experience holders to create exciting and innovative products. We are taking up the brilliant
ideas and have been nailing them completely for 5 years. Quality has always been in our
prime focus and that’s the reason why we have evolved as the most trusted IT firm in India.
We challenge our products to go through the different layers of the quality checks to make
sure that the final product is completely immaculate.
1.2 DIFFERENT PRODUCTS OF WORK
 Mylens.Mu
Mylens.Mu is a Mauritian-based online retailer of contact lenses, it quickly evolved

into one of the leading providers of contact lenses on the internet.MyLens.mu is
dedicated to providing you with a simple, hassle-free way to replace your contact
lenses. At MyLens.Mu, you will receive the exact same contact lenses your doctor
prescribed, delivered to your door, at a great price.
 And other are OKBMU.com, bmbookcentre.mu etc.
Gujarat Technological University 1 MSCET

218368 Overview of the Company
1.3 ORGANIZATION CHART
Fig 1.3 Organization Chart
Like this, there is 15+ resources strength in the team members of the company and all the
other categories of the departments are mentioned below
1.4 CAPACITY OF PLANT
 The approximate capacity of the company/plant is 15+ resources strength.

218368 Overview of different department
CHAPTER 2
OVERVIEW OF DIFFERENT DEPARTMENT
 The different departments in our company are: -

 Website Design, Website Development, Mobile App Development, Ecommerce
Solution, Digital Marketing
2.1 DETAILS ABOUT THE WORK BEING CARRIED OUT IN EACH

DEPARTMENT.
 Website Design
o We bring years of experience and expertise in a variety of industries to our
website design projects. To ensure success, we take time to understand your
unique needs, customize a solution and deliver it exactly as per your need.
 Graphic Design
o Design a website that is fully customized, search engine optimized,
conversion-optimized design, enhanced user experience and enables easy
access to your online content on mobile and tablet devices. We work for high
quality, attractive and eye-catching website design.
 Website Development
o Using the best-in-class technology, we build websites and apps that perform
well and work exactly as per your requirements. With a full team of
developers working on advanced solutions, we tailor interactive development
based on client needs.
 Mobile App Development
o It is crystal clear that the demand of mobile apps has escalated in all
businesses. To cope with that, we become your accelerator to design and
develop brilliant mobile applications. Sassy infotech Pvt. Ltd is a top-notch
mobile app development company offering mobile application development
services for iPhone, iPad and Android.
 Ecommerce Solution
o Our eCommerce solutions allow large and small organizations to grow their
business online. We specialize in custom-tailored eCommerce website
solutions at affordable prices. We've provided solutions to a variety of
industries including real estate, tours and travel, fashion and many more.
 CMS Solution
o Our CMS development gives you a high level of flexibility that will
eventually translate into profitability. By using cutting-edge technologies and
combining our experience with your vision, we build you an optimal solution,
and provide training and support long after your project is finished.

 Digital Marketing
o Complete digital marketing solutions to build an effective online presence of
your website within your target market to display your business in front of
more and more customers. Increase brand awareness through online platforms
like SEO, social media marketing, and email marketing.
 Web Consultation
o Web consulting services help companies to get their website evaluated for the
aspects which need optimization. With the right focus on the optimization of
the website elements, the consulting professional’s design strategies and
innovative solutions for driving business growth.
 Support & Maintenance
o Maintenance Services to keep your websites updated with the latest
technology that is used to build your web application with updated Company
Information, Company Services, Products portfolio, Client testimonial, etc. on
the website as all information provided by the client.
2.2 LIST THE TECHNICAL SPECIFICATION OF MAJOR

EQUIPMENT USED IN EACH DEPARTMENT.
 The processor of the computer is i5/i7.
 Ram should be min. of 8GB
 SSD or HDD of 256 GB anyone can work
 Platforms like CodeIgniter, VS code, etc. are required
 Languages like PHP, Python, HTML, etc. are required
 Wi-Fi connection min. speed should be 2Mbps per computer
 These are some technical specifications used in all the departments of the
plant/company

2.3 SCHEMATIC LAYOUT OF OPERATIONS FOR

MANUFACTURING OF END PRODUCT.
Fig 2.3 Schematic Layout of company’s operation
This schematic includes both the frontend and backend development processes of the plant.
2.4 DETAILS ABOUT EACH STAGE OF PRODUCTION.
(1) UX/UI Design
User experience design (UX design, UXD, UED, or XD) is the process of creating
evidence-based, interaction designs between human users and products or websites.
Design decisions in UX design are driven by research, data analysis, and test results
rather than aesthetic preferences and opinions. Unlike user interface design, which
focuses solely on the design of a computer interface, UX design encompasses all
aspects of a user's perceived experience with a product or website, such as
its usability, usefulness, desirability, brand perception, and overall performance. UX
design is also an element of the customer experience (CX), which encompasses all
aspects and stages of a customer's experience and interaction with a company.
(2) Front end
 Markup and web languages such as HTML, CSS, JavaScript, and ancillary
libraries commonly used in those languages such as Sass or jQuery
 Asynchronous request handling and AJAX
 Single-page applications (with frameworks like React, Angular, or Vue.js)
 Web performance (largest contently paint, time to interactive, 60 FPS animations
and interactions, memory usage, etc.)

 Responsive web design

 Cross-browser compatibility issues and workarounds
 End-to-end testing with a headless browser
 Build automation to transform and bundle JavaScript files, reduce images size...
with tools like Webpack or Gulp.js
 Search engine optimization
 Accessibility concerns
 Basic usage of image editing tools such as GIMP or Photoshop
 User Interface
(3) Back end
 Scripting languages like PHP, Python, Ruby, Perl, Node.js, or Compiled

languages like C#, Java or Go
 Automated testing frameworks for the language being used
 Application Data Access
 Application Business Logic
 Database administration
 Scalability
 High availability
 Security concerns, authentication, and authorization
 Software Architecture
 Data transformation
 Backup methods and software
Note that both positions, despite possibly working on one product, have a very
distinct set of skills.
(4) Database
A database is an organized collection of data, so that it can be easily accessed and

managed.
Database handlers create a database in such a way that only one set of software
program provides access of data to all the users.
The main purpose of the database is to operate a large amount of information by
storing, retrieving, and managing data.
There are many dynamic websites on the World Wide Web nowadays which are
handled through databases. For example, a model that checks the availability of rooms
in a hotel. It is an example of a dynamic website that uses a database.
There are many databases available like MySQL, Sybase, Oracle, MongoDB,
Informix, PostgreSQL, SQL Server, etc.
Modern databases are managed by the database management system (DBMS).
SQL or Structured Query Language is used to operate on the data stored in a database.
SQL depends on relational algebra and tuple relational calculus. A cylindrical
structure is used to display the image of a database.

218368 Introduction to Internship
CHAPTER 3
INTRODUCTION TO INTERNSHIP
Investing in property is one of the best decisions you can make. It’s worth it because you
can make a small yet steady income by renting it. But, putting your home on lease comes
with a variety of hassles. How to find a tenant, how to know if the tenant will take care of
the house or not, what if the tenant appears to be a fraud, and much more.
So, this website is all about renting properties and with the best level of tenant-to-owner
security so one can easily move in without hassle in a place or house with minimum
documentation and maximum level of security, satisfaction, no men in the middle, etc.
providing the best user experience and features like OTP verification through e-mail,
booking/scheduling the meet directly with the owner this is some features and function of
our website.
3.1 INTERNSHIP SUMMARY
Rental property or say “rentprop4u” is designed for the purpose of renting a property of an
individual. On this website, an individual can register themselves as a user and can book the
properties and gain access to the features related to the account or they can register
themselves as owner by providing their property details, personal details and get verified by
the admin of the website and gain the access of other features from their respective account.
Rental property is a web-based project. It is designed to let registered users search and book
a property that is posted by registered owners. OTP is sent to the user's/ owner's Email for
verification. Owners can add property from their dashboard. Admin needs to approve
owners and set their password which should be sent via email by the owner personally. so,
the security level is well maintained for both user and owner to stay hassle-free. We also
provide one-point contact for all queries of the customer’s features this is some security
level details provided in our software. so, there are well enough security features on the
website. features like customer support and customers feedback form are also provided.
Categories like apartments, villas, houses, farmhouses, studio apartments, etc. options are
available for the owners to give their desired property on rent also users can find all these
options and can schedule a meeting with the owner and can also book the property with the
owner.it also contains the admin side he/she can manage the data received from the client-
side like activating of account, deleting the account, updating an account, generating
passwords for owners, etc. also google map APIs are used for the location of the property or
user/owner registered in the website.
3.2 PURPOSE
 No time-consuming paperwork.
 Certified listings.
 One-point contact.
 No interference from landlords.

 Delivery as per promise as what you see is what you get. For these, features like
booking and scheduling.
 Providing security like OTP verification, providing passwords by admin directly for
owners, etc.
3.3 OBJECTIVE
To provide hassle-free paperwork for both owner and tenant. Also, to provide maximum
security services for an individual user/Owner so there should no men in the middle at the
time of dealing or brokerage fee. To provide the best user interaction and user interface also
users can get what they see as the satisfaction of the property there should be no fake/ fraud
with both owner and user so the same certified listing feature is available on our website.
To provide the best customer support and feedback at a one-point contact support system.
lastly to provide properties on rent or to buy properties on rent.
3.4 SCOPE
What it can do: -

 Users/Owners OTP verification Through E-mail.
 Providing passwords only for owners by admin.
 Providing customer care support feature with a feedback form.
 The viewing, scheduling, and booking of the properties can be done.
 Activation/deactivating of user owner account
 Updating, adding, and deleting personal details of users/owners
 Updating, adding, and deleting details of properties.
 Other features include categories like for owner, Quick links, Contact Us, and Flats
for rents in Bangalore by type/area can access and use all features of the website.
What it can’t do: -

 Not able to send a personal e-mail containing a password created by the admin for
the owner
 Not able to pay rent or deposit
 Not able to send OTP on mobile devices
 Not able to take request a demo from specialists
 Cannot apply for a partnership- feature to yet working
 Not able to receive a message from individuals from the client-side
 One-point contact feature not available

3.5 TECHNOLOGY AND LITERATURE REVIEW
PRIOR ART SEARCH:
(1) Rental property caching and searching system and process
Author: Arthur Thibodeau

Year: 2000
Description:
A computer system and computer-implemented process for determining availability of
rental property is disclosed. The computer implemented process includes inputting and
storing data representing multiple sets of attributes for each of a plurality of rental property
addresses and creating a plurality of records, one for each set of attributes for each of the
plurality of rental property addresses. The process further comprises combining the
plurality of records into one searchable master table, and periodically updating the plurality
of records by inputting updated data for one or more of the multiple sets of attributes for the
plurality of rental property addresses. To search for property availability, the user inputs
one or more search parameters based on one or more desired attribute sets from the multiple
sets of attributes to build a search query to search the master table for records of available
rental property addresses. Matching rental properties are displayed. The process and
software may also include providing a web-based hyperlink for each available rental
property address that sends a user to a predetermined web address.
(2) Making a Rental Property Home
Author: Hazel Easthope

Year: 2013-14
Description:
English-language literature on the relationship between home and dwelling has largely
focused on the benefits of homeownership and (to a lesser extent) social rental in
facilitating ontological security. Less consideration has been given to the experiences of
private tenants. This paper draws on findings of a study on security of occupancy to discuss
the ability of private renters to exercise control over their dwellings in Australia. The paper
discusses the limitations of Australian legislation, within its policy, market and cultural
context, in enabling private tenants to exercise control over their dwellings, and compares
the Australian situation with Germany to demonstrate that alternative approaches that afford
more control to private tenants are possible in rental systems dominated by private rental.
The paper concludes with a call for a wider debate about the importance of home and the
impact of social norms regarding the purpose of different types of tenure on housing policy
and thus on the rights and well-being of tenants.

3.6 INTERNSHIP PLANNING
 Case study on rental property modules

 Learn about CodeIgniter
 Learn about MVC architecture
 Create a simple CRUD form
 Learn about google APIs
 Implement google map APIs
 Implement google map APIs with database, without database
 Explore the given live project “rentprop4u.com” or Rental property
 Setup the given live project into the VS code with XAMPP
 Study the functionality of the project
 Find the errors and complete the website with a database
 Learn about sending mail with localhost from XAMPP
3.6.1 Internship Development Approach and Justification
Systems Development Life Cycle Method: -

Systems Development, is a process consisting of the two major steps of systems analysis
and design. The system development life cycle method is classically thought of as the set of
activities that analysts, designers, and users carry out to develop and implement the
information system.
The Software development Model used is the “Waterfall Model”.
“The waterfall model is a sequential design process, used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall)
through the phases of conception, initiation, analysis, design, construction, testing,
production/implementation, and maintenance.”
The Waterfall Model was the first Process Model to be introduced. It is also referred to as a
“linear sequential life cycle model”. It is very simple to understand and use. In a
waterfall model, each phase must be completed fully before the next phase can begin. This
type of model is basically used for the project which is small and there are no uncertain
requirements. In this model, the testing starts only after the development is complete. In the
waterfall model phases do not overlap.
Requirement
Design
Implementation
Verification
Maintenance
Fig 3.6.1 Phases of waterfall model

Justification: 
The most probable phases through which it progresses downwards are
• Definition Study/Analysis: During this phase research is being conducted which
includes brainstorming about the software, what it is going to be and what purpose is
it going to fulfil.
• Basic Design: If the first phase gets successfully completed and a well thought out
plan for the software development has been laid then the next step involves
formulating the basic design of the software on paper.
• Technical Design/Detailed Design: After the basic design gets approved, then a
more elaborated technical design can be planned.
• Construction: In this phase the source code of the programs is written.
• Testing: At this phase, the whole design and its construction is put under a test to
check its functionality. If there are any errors then they will surface at this point of the
process.
• Integration: in the phase of Integration, the company puts it in use after the system
has been successfully tested.
• Management and Maintenance: Maintenance and management is needed to ensure
that the system will continue to perform as desired.
Advantages Of the Waterfall Model:
• This model is simple and easy to understand and use.

• It is easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
• In this model phases are processed and completed one at a time. Phases do not
overlap.
• Waterfall model works well for smaller projects where requirements are very well
understood.
Disadvantages Of the Waterfall Model:
• Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-thought-out in the concept stage.
• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.

• Not a good model for complex and object-oriented projects.

• Poor model for long and ingoing projects.

Not suitable for the projects where requirements are at a moderate to high risk of
changing.
3.6.2 Internship Effort and Time, Cost Estimation
 Cost Estimation: -
- No budgetary contains were imposed on software. So, finance is not the problem.
- Thus, the project’s overall feasibility is normal, and therefore we have undertaken
this project.
 Time: -
- Project is initiated with specified deadlines.
- The duration allotted to complete the project is 3 months which is enough time to
build this system.
- Our schedule was we had to report ourselves at the company every Saturday as
our work was based on “work from home”.
 Effort: -
- Different tasks were given to us like learning about CodeIgniter
- Completing the given task and reporting them through offline and online modes
3.6.3 Roles and Responsibilities
After a careful review of software requirements specifications, we divide the project

into three different modes: (1) Implementation Mode (2) Coding Mode (3) Testing
Mode. Therefore, roles can be defined as Programmer, Tester & troubleshooter.
Here we are three members of the project and we play these three roles as per the
requirements of the project.
3.6.4 Group Dependencies
Table 3.6.4 Group Dependencies

ACTIVITY MEMBERS DESCRIPTION
ANALYSIS Member-3 Analysis was carried out by all the members and also
reviewed by the external guide.
TESTING Member-3 The testing of the website was done by us by dividing

the forms Internally.
The coding part of the website was divided and

CODING Member-3 completed by us with help of our external guide so that
work consumes less time.

3.7 INTERNSHIP SCHEDULING
Gantt Chart
Table 3.7 Gantt Chart for Internship Schedule
Task Name Start Finish Feb Mar Apr
Analysis 01-02-2022 05-02-2022
Learn about
CodeIgniter & 07-02-2022 12-02-2022
MVC architecture
Create CRUD 14-02-2022 26-02-2022

form
Learn & 28-02-2022 05-03-2022
Implement google
map APIs
Analysis of given 07-03-2022 19-03-2022
live project
Work on live 21-03-2022 17-04-2022
project
Testing phase 18-04-2022 23-04-2022

218368 System Analysis
CHAPTER 4
SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM
In the existing system, any user can see/ search the available properties on the website but
only registered users can book/schedule a visit to a property. Registered owners can post the
property they want to rent with the property details. Admins have to approve these
properties and can also remove users, owners, and properties when they want. When user/
owner registers themselves they will receive OTP on their email for verification to activate
their account.
4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM
Admin has to personally send an email to the owner for password and different links for
owners to use. Owner cannot directly access to his login link from website. He can access
this from his email. User cannot pay the rent amount from website. OTP cannot be sent on
phone number. One point contact is not available. User query is not received by support
team
4.3 REQUIREMENTS OF NEW SYSTEM
The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The existing system has
several disadvantages and many more difficulties to work well. The proposed system tries
to eliminate or reduce these difficulties up to some extent. The proposed system will help
the user to reduce the workload and mental conflict. New System allows new security
features to the website. User interface should be easy to understand.
4.4 SYSTEM FEASIBILITY
4.4.1 Does the System Contribute to The Overall Objectives of The Organization?
An important outcome of the preliminary investigation is the determination that the

system requested is feasible. The feasibility study is carried out to examine the like hood
that the system will be useful to organization.
4.4.2 Can the System Be Implemented Using the Current Technology and Within the
Given Cost and Schedule Constraints
The feasibility of our project has been judged on the basis of time, technology,
resources available, and project length.
 Time: -
- Project is initiated with specified deadlines.

- The duration allotted to complete the project is 3 months which is enough time to
complete this system, so as far as the time is concerned this project is feasible

 Technology: -
- This project is built on CodeIgniter platform, XAMPP Server, VS Code Editor by
using these Languages: HTML, CSS, SQL, jQuery, JavaScript, PHP As far as the
technical risk is negligible, so problem is feasible.
 Resources: -
- We need good knowledgeable software engineers. We need Internet Network
connection, Internet Information Services and XAMPP Server. Also, proper
development tool is needed to prepare documentation.
- We have all the resources in the desired amount.
 Project Size: -
- The Project size might be around 10000 LOC. This is just the rough assumption
because we don’t have any basis of this type of past projects.
 Finance: -
- No budgetary contains were imposed on software. So, finance is not the problem.
- Thus, the project overall feasibility is normal and therefore we have undertaken
this project.
4.4.3 Can the System Be Integrated with Other Systems Which Are Already in Place?
Yes, the system can be integrated with other systems which are already in place because it
works as per the requirements of the clients and doesn’t conflict with other functionality of
the system. So, it can be integrated.
4.5 PROCESS IN NEW SYSTEM
 Sign-in and other features for owner directly on website

 One-point contact to make available
 User should able to book a demo with specialist
 Owner can set password by themselves
 Visitors should able to fill feedback form and data should be collected by support
team
 Outside properties other than Bangalore might be available.
4.6 FEATURES OF NEW SYSTEM
 To send OTP on phone number.

 Give payment option for user to owner.
 Refer and earn option to make available
 Payment through UPI.
 AI bot chat support
 24x7 Customer Support

4.7 LIST OF MAIN MODULES
Rental Property Website Project Modules:

List of main modules used in this project are mentioned below:
 Admin Module
 User Module
 Owner Module
4.8 SELECTION OF SOFTWARE
4.8.1 CodeIgniter - Overview

CodeIgniter is a simple, elegant and powerful toolkit with a very small footprint, used by
those developers who want to create full-featured Web Applications. CodeIgniter is an
Open-Source PHP Framework. It has a very rich set of functionalities, which will increase
the speed of website development work. As there are various sources through which
websites can be developed, but CodeIgniter is preferred over the others
4.8.1.1 Why CodeIgniter?
i. Handling Bugs/Error Handling
If you are one of those who wish to develop websites that are flawless and deliver
exceptional functionality and design, you need to check out CodeIgniter. A simple
user interface is provided that lends a hand in finding any errors or bugs that are
preventing the smooth functioning of the website and eventually affecting the user
experience.
The errors in the code are precisely displayed without any hassle. This is as why
most of the developers prefer CodeIgniter whenever they are asked to develop a
bug-free website that doesn’t compromise on the overall quality. All you need to
do is to seek help from a professional that has great expertise in delivering the
finest web development services.
ii. Customizability
As a developer, you can always customize the website as per the requirements,
which also doesn’t squander their precious time. As per the experts, CodeIgniter is

the only framework that provides ease of customizability compared to the

numerous options available in the market.
Instant error fixing and configuring the files in a simplified form are primary
reasons for the need to rely on CodeIgniter, especially whenever someone is
seeking promising custom website development services. It would be great if you
consult a renowned professional who can help you get things done to harmonize
the business needs.
iii. Security
For all those seeking the most secure platform for web development, undoubtedly,
CodeIgniter is a perfect choice! The platform offers enhanced security features
that are enough to depict the overall reliability of this platform. The different
encryption and decryption features have made this platform a lot more reliable
than any other platform in the market.
A lot of web developers prefer building e-commerce websites containing payment

gateway in CodeIgniter, which require adequate security standards in a website.
Deploying a payment gateway on your website isn’t a piece of cake and
eventually requires great efforts, which isn’t in the case of CodeIgniter. You can
get the finest experience of deploying plugins and customizing your website in
numerous ways.
iv. . User-friendly Interface
One can get the ease of developing a great website with the finest interface offered
by CodeIgniter. Whether you are expecting a website with dynamic functionality
or on a hunt for the platform that can provide you with the best responsive website
experience, you can always rely on CodeIgniter. You just need to emphasize
finding the right CodeIgniter web development company that can cater to your
diverse business needs.
It won’t be wrong to say that you can get the flexibility and enhanced UI from
CodeIgniter that makes it the ideal choice for all web developers around the globe.

v. Hassle-Free Migration
When we talk about database updates and migration, CodeIgniter lets a user
migrate from one server to another. There are several companies that rely on
CodeIgniter just because of the fact that it provides adequate migration support
services.
No matter where your old data was kept, you can always shift the same to this
platform without any hassle. Just in case there are some issues, one can get proper
support from the vast community that can be the best thing that you can get from a
web development platform. The professionals are always available to serve you
with the right solution for your technical glitches.
vi. The MVC-Based System
The biggest reason to rely on CodeIgniter is the fact that this platform is based on
MVC (Model View Controller) which enhances the overall dependency of this
platform. MVC enables Test-Driven Development, which simply means that the
developer can precisely develop and test the modules as per the requirements.
Apart from this, MVC enhances the development procedure and also offers easy
integration with the JavaScript frameworks. The design is also improved in
CodeIgniter with the use of MVC.
vii. Quick Development
Most of the businesses choose CodeIgniter for web development purposes just
because it offers quick development services that one can’t expect from any other
framework. Thus, it is crucial to rely on this powerful framework if someone is
expecting quick development services without any hassle.
Development in CodeIgniter requires less code as compared to the other

platforms, which is a great benefit for the ones that are expecting better
functionality on their website with minimal code. One can consider consulting any
renowned CodeIgniter development company for detailed information about the
same.

4.8.2 XAMPP – Overview
XAMPP is a free and open-source cross-platform web server solution stack package
developed by Apache Friends, consisting mainly of the Apache HTTP
Server, MariaDB database, and interpreters for scripts written in
the PHP and Perl programming languages. Since most actual web server deployments use
the same components as XAMPP, it makes transitioning from a local test server to a live
server possible.
XAMPP's ease of deployment means a WAMP or LAMP stack can be installed quickly and
simply on an operating system by a developer, with the advantage that common add-in
applications such as WordPress and Joomla! can also be installed with similar ease
using Bitnami.
Table 4.8.2.1 Meaning of XAMPP
Letter Meaning
X An ideographic letter referring to cross-platform
A Apache, or its expanded form, Apache HTTP Server
M MariaDB (formerly MySQL)
P PHP
P Perl

Table 4.8.2.2 Components of XAMPP

Components included with XAMPP
Component On Windows On Linux On macOS
Apache Yes Yes Yes
MariaDB Yes Yes Yes
PHP Yes Yes Yes
phpMyAdmin Yes Yes Yes
OpenSSL Yes Yes Yes
Webalizer Yes - 2.23-04 Yes - 2.23-05 Yes - 2.23-05
FileZilla FTP Server Yes No No
Mercury Mail Transport System Yes No No
Strawberry Perl Yes No No
Tomcat Yes No No
XAMPP Control Panel Yes No No
APR No Yes Yes
APR-utils No Yes Yes
cUrl No Yes Yes
expat No Yes Yes
FPDF No Yes Yes
FreeTDS No Yes Yes
Freetype2 No Yes Yes
GD No Yes Yes
gdbm No Yes Yes
gettext No Yes Yes
ICU4C Library No Yes Yes
IMAP C-Client No Yes Yes
Libapreq No Yes Yes
Libpng No Yes Yes
libxml No Yes Yes
Libxslt No Yes Yes
mcrypt No Yes Yes
mhash No Yes Yes
Ming No Yes Yes
mod_perl No Yes Yes
ncurses No Yes Yes

4.8.3 Google APIs – Overview

Google Maps API is a set of application programming interfaces that lets us talk to its
services. It will allow us to build simple apps to very sophisticated location-based apps for
Web, iOS, and Android.
Figure 4.8.3 Google Map API
API Key
Getting an API Key from the Google Cloud Platform is the first step before using any of the
Google Maps API Services.
 Create An API Key

 Enable Billing
 Protect Your API Key & Libraries
 Enable Desired Libraries

Maps API
Using Maps API, you can:
 Show Google Maps on the browser, iOS, or Android devices.

 Place or pin a Marker on the map when you want to indicate a specific geographic
coordinate (latitude and longitude).
 Show an InfoWindow which is a popover so you can show more information about
a place above the marker when clicked.
 Draw a polygon that covers a specific area on the map based on a number of
coordinates specified in an ordered sequence.
 Create a polyline which is a path on the map based on a number of coordinates
specified in an ordered sequence. The path line will be created between two lines,
then the second to the third, and so on.
Geocoding API
 Geocoding is a process of converting a street address to geographic coordinates

(latitude & longitude).
 Reverse Geocoding is the opposite, it converts geographic coordinates to an actual
human-readable address.
 When you choose your own location from an app, such as a food delivery app, the
app will have to convert the user coordinates that are coming from the device GPS
to an actual human-readable address.
Places API
1. Nearby Search Request allows us to get different places based on:
 location: could be either the user’s current location or any other location that you
want to get nearby places from.
 Type: could be restaurants, bars, etc.
 radius: determines how far you want to get the places from.

The response object will have most of the information about places such as name, address
and coordinates.
2. Text Search Request allows us to get different places based on the text string. For example:
“restaurants in Toronto.”
3. Place Details Request will provide more information about a place such as a website
address, phone number, opening hours for a week or reviews, and many more.
To get specific place information, you’ll need to use place_id that you can get from Nearby
Search Request or Text Search Request.
4. Autocomplete API will allow you to show suggested street addresses in a drop-down list
under the input field as the user types, which is very handy when a user denies sharing a
location or location service is not supported by his/her browser or device.
Distance Matrix API

Distance Matrix API calculates the travel distance and time between two or more addresses
based on transportation modes such as driving, walking, bicycling, and transit.
Directions API
Direction API allows you to calculate the travel distance and duration between two or more
locations, similar to the Distance Matrix API.
Using its client-side library, we can actually create a direction path on the map based on
various transportation modes.
Geofencing API
Using the Geofencing API, we can detect a device when it crosses into a specific region or
radius on the map.
For example, when the food delivery driver enters the geofencing area of your house, your
app will detect them and says the delivery driver is here.

4.8.4 The Languages Used for Web Development

I have used HTML, CSS, JavaScript, jQuery, SQL, PHP for developing website.
4.8.5 Editor: Visual Studio Code

Visual Studio Code, also commonly referred to as VS Code, is a source-code editor made
by Microsoft for Windows, Linux and macOS. Features include support
for debugging, syntax highlighting, intelligent code completion, snippets, code refactoring,
and embedded Git. Users can change the theme, keyboard shortcuts, preferences, and
install extensions that add additional functionality.

218368 System Design
CHAPTER 5
SYSTEM DESIGN
5.1 SYSTEM DESIGN & METHODOLOGY
Use-case Diagram for Registered User
Fig 5.1.1 Use case Diagram of registered user

Use-case Diagram for Unregistered Owner
Fig 5.1.2 Use-case Diagram for Unregistered Owner
Use-case Diagram for Unregistered User
Fig 5.1.3 Use-case Diagram for Unregistered User

Use-case Diagram of Registered Owner
Fig 5.1.4 Use-case Diagram of Registered Owner

Use-case Diagram of admin
Fig 5.1.5 Use-case Diagram of admin

5.2 DATABASE DESIGN
 Table 1: - Category
 Primary Key: - id
 Description: - Category of interior
Table 5.2.1 Database for Category
 Table 2: - City
 Description: - list of cities
Table 5.2.2 Database for City
 Table 3: - City_area
 Description: - list of area
Table 5.2.3 Database for Area

 Table 4: - Company_info
 Description: - information about company owner
Table 5.2.4 Database for Company Info
 Table 5: - Countries
 Description: - list of countries
Table 5.2.5 Database for Countries
 Table 6: - Customers
 Description: - list of customer information
Table 5.2.6 Database for Customers

 Table 7: - customer_master
 Description: - list of customers
Table 5.2.7 Database for Customer Master
 Table 8: - distributor
 Description: - list of distributors
Table 5.2.8 Database for Distributor
 Table 9: - email_settings
 Description: - email setting for sending email
Table 5.2.9 Database for Email Setting
 Table 10: - faq

 Description: - frequently asked questions with answers
Table 5.2.10 Database for FAQs

 Table 11: - members

 Description: - list of members
Table 5.2.11 Database for Members
 Table 12: - members_staff

 Description: - list of Admin/owner
Table 5.2.12 Database for Member Staff

 Table 13: - owner_details

 Primary Key: - owner_id
 Description: - table for details of owner
Table 5.2.13 Database for Owner Details
 Table 14: - process

 Description: - Table for process
Table 5.2.14 Database for Process
 Table 15: - process_assign

 Description: - table for assigning process
Table 5.2.15 Database for Process Assign
 Table 16: - process_inner

 Description: - table for internal process
Table 5.2.16 Database for Process Inner

 Table 17: - process_status

 Description: - table for process status (pending, completed, in_process)
Table 5.2.17 Database for Process Status
 Table 18: - products

 Description: - Table for products
Table 5.2.18 Database for Products
 Table 19: - property_attributes

 Description: - table for storing furnished type
Table 5.2.19 Database for Property Attributes

 Table 20: - property_booking

 Description: - table for storing booking details
Table 5.2.20 Database for Property Booking
 Table 21: - property_images

 Description: - table for storing property images if uploaded
Table 5.2.21 Database for Property Images
 Table 22: - property_owner

 Description: - table for owner details with property
Table 5.2.22 Database for Property Owner

 Table 23: - property_visit

 Description: - Table for visiting schedule
Table 5.2.23 Database for Property Visit
 Table 24: - rentprop4u_setting

 Description: - Table for settings
Table 5.2.24 Database for Rentprop4u Setting
 Table 25: - rent_property

 Description: - table for storing property details
Table 5.2.25 Database for Rent Property

 Table 26: - states

 Description: - list of states
Table 5.2.26 Database for States
 Table 27: - table_attributes

 Description: - list of attributes such as: car parking, garden, pets, etc.
Table 5.2.27 Database for Table Attributes
 Table 28: - table_attributes_input_field

 Description: - list of input field: text field, text area, dropdown, number
Table 5.2.28 Database for Table Attributes Input Field

 Table 29: - table_attributes_input_option

 Primary Key: - option_id
 Description: - table for storing attribute
Table 5.2.29 Database for Table Attributes Input Option
 Table 30: - user_inquiry

 Description: - list of inquiries sent by user
Table 5.2.30 Database for User Inquiry
 Table 31: - user_type

 Description: - table for storing user type
Table 5.2.31 Database for User Type

5.3 INPUT/ OUTPUT AND INTERFACE DESIGN
5.3.1 Sample Of Forms, Reports And Interface
5.3.1.1 Tasks in CodeIgniter
Register, Login, Dashboard using CodeIgniter

Update, Delete data CodeIgniter
Implement google map API
5.3.1.1.1 Home Page
Fig 5.3.1.1.1 Home page for CRUD form
5.3.1.1.2 Register
Fig 5.3.1.1.2 Registration form for CRUD

5.3.1.1.3 Login
Fig 5.3.1.1.3 Login form for CRUD
5.3.1.1.4 News Archives
Fig 5.3.1.1.4 News Archives
5.3.1.1.5 View News
Fig 5.3.1.1.5 View news for CRUD

5.3.1.1.6 Edit News
Fig 5.3.1.1.6 Edit news for CRUD
5.3.1.1.7 Delete News
Fig 5.3.1.1.7 Delete news for CRUD
5.3.1.1.8 Add News
Fig 5.3.1.1.8 Add news for CRUD

5.3.1.1.9 Database Structure For News
Table 5.3.1.1.9 Database for News
5.3.1.1.10 Database Structure For User
Table 5.3.1.1.10 Database for User
5.3.1.1.11 Task To Implement Google Map APIs
Implement google map with database

Implement google map without database
Implement direct google map for single location
Google Map With Database
Fig 5.3.1.1.11.1 Google map with database

Table 5.3.1.1.11 Database for Google APIs
Google Map Without Database
Fig 5.3.1.1.11.2 Google map without database
Implementation Of Direct Google Map For Single Location
Fig 5.3.1.1.11.3 Implementation of Google map directly

218368 Implementation
CHAPTER 6
IMPLEMENTATION
6.1 IMPLEMENTATION ENVIRONMENT

 Home Page
Fig 6.1.1 Home page

 This is the main front-end of the rentprop4u where visitors(non-registered) can
see/search for property which have been uploaded for providing on rent by respective
owners, register themselves as user/owner to rent/see/book properties.

 User Signup
Fig 6.1.2 Signup page for user
 Here is the process of user-signup where user is supposed enter his/her details and
OTP for email verification. After the OTP matches, he/she is registered as user.

 Owner Sign up
Fig 6.1.3 Signup for owner
 Here is the process of owner-signup where Owner is supposed enter his/her details
and OTP for email verification. After the OTP matches, he/she is registered as owner.

 Explore homes
Fig 6.1.4 Explore homes
 Here, non-registered user can only view property details from explore option but cannot
book the property because they need to login before doing so.
 Get Started/ Refer& Earn
Fig 6.1.5 Refer & Earn
 Here user can refer the person from whom they got to know about the website.
 About us
Fig 6.1.6 About us

 Here details about the founder and CEO are given.

 For owner- owner
Fig 6.1.7 Information for owner
 Here details are given for owner to understand about the features available.

 For owner- property management
Fig 6.1.8 Property Management information for owner
 Here details are given for owner to understand about property management.

 For owner- how it works
Fig 6.1.9 How the website functions- information for owner
 Here details are given for owner to understand how the website work

 For owner- FAQ
Fig 6.1.10 FAQ

 Here, Frequently Asked Question are given along with their answers.
 Quick links- T&C
Fig 6.1.11 Terms & Conditions
 Here Terms & Conditions about the website are given which are to be followed by
both user and owner.

 Quick links- privacy policy
Fig 6.1.12 Privacy Policy
 Here privacy policy details are mentioned.
 Flats for rent
Fig 6.1.13 Flats for rent
 Here the property which are to be rented are displayed.

 Contact us
Fig 6.1.14 Contact us
 This form is for contacting the tech-team regarding any queries.
 Customer Support
Fig 6.1.15 Customer Support
 Here the registered/non-registered user/owner can contact the customer support team
for their issues/queries.
 Login- user
Fig 6.1.16 Login User
 This is the login pop-up for user with login details

 After user login
Fig 6.1.17 User Dashboard

 This is the dashboard page for user after login.
Fig 6.1.18 Change user profile

 This is the page for changing profile details like: first name, last name, email
id, etc.
Fig 6.1.19 Change user password

 User can also change their password if they want to.

 Explore home After user login
Fig 6.1.20 Explore home after login

 This page is for explore homes after the user has logged in.
 After accept
Fig 6.1.21 After accepting

 Here user can select number of tenants and provide/change other details.
 After accept terms
Fig 6.1.22 After accepting terms

 Here user can select the mode of payment.

 After owner login
Fig 6.1.23 Owner Login- Send OTP
 This page is owner login with button for sending OTP to mail.
Fig 6.1.24 Enter OTP for owner login
 This page is for entering OTP which is sent on mail.
Fig 6.1.25 Owner Dashboard
 This is owner dashboard after login.

Fig 6.1.26 Properties of owner
 Here owner can see his/her properties which are verified by the admin.
Fig 6.1.27 Change owner profile
 This is edit profile page for owner. Here he/she can change details like: first
name, last name, email, etc.

 Add property
Fig 6.1.28 Add property- Owner
 This page is to add property for owner. Here the owner can enter the details of
his/her property.

Admin
 Login
Fig 6.1.29 Login for Admin
 This is admin login with login details.
 Dashboard
Fig 6.1.30 Admin Dashboard
 This is admin’s dashboard after login.

 Customer list
Fig 6.1.31 Customer list
 This page shows the list of both accepted and pending customers.
 Owner- pending owner
Fig 6.1.32 Pending owner list
 This page shows the list of pending owners.
 Owner- accepted owner
Fig 6.1.33 Accepted owner list
 This page shows the list of accepted owners.

 Location- Country list, state list, city list, area list
Fig 6.1.34 List of countries
 This page shows the list of accepted & pending countries.
Fig 6.1.35 List of States
 This page shows the list of accepted & pending states

Fig 6.1.36 List of Cities
 This page shows the list of accepted & pending cities.
Fig 6.1.37 List of added Area
 This page shows the list of inserted accepted & pending areas.

 Attribute list
Fig 6.1.38 List of Attributes
 This page shows the list of attributes.
 Rent property
Fig 6.1.39 List of Properties
 This page shows the list of accepted & pending properties.

 Setting- email
Fig 6.1.40 Settings for Email

 This page shows the email settings.
 FAQ list
Fig 6.1.41 List of Frequently Asked Question
 This page shows the list of Frequently Asked Questions with their Answers.

 Booking list
Fig 6.1.42 List of Property Booking

 This page shows the list of booking property.
 Schedule list
Fig 6.1.43 List of scheduled visits

 This page shows the list of scheduled visits to a property.
 Inquiry list
Fig 6.1.44 List of Inquiry

 This page shows the list of inquiries sent by the customers (both user and
owner of property).

6.2 MODULES SPECIFICATIONS

 Admin Module
 Admin can approve the users, Owners, Properties, Country, State, City, Area,
etc.
 Admin can view all property information.
 Admin can view all pending user/owner list.
 Admin can view all accept/approved user/owner list.
 Admin can add user/owner/property/area/city/state/country directly
 User Module
 User can register himself/herself and then he/she can directly login after
verifying the OTP send on email.
 User can search for a property based on area.
 User can book an available property according to his/her need.
 Owner Module
 Owner can register himself/herself but she/he cannot login directly after
registering. Admin have to approve the owner and also admin has to generate
a password for the owner and send these details on respective owner’s email.
 Owner can add his property he/she wants to give on rent.
6.3 RESULTS
 Some results of the project came as expected and some were not
 Some feature results are not yet being working or being redirected to something like
one page to another due to requirements
 Finding the details related to project helped us to overcome problems
 Like sending OTP through E-mail
 Creating password for owner by admin
 Sending links for owner sign-in by admin via e-mail
6.4 RESULT ANALYSIS
 After a lot of research and discussion on sending OTP on a mobile number or e-mail
for verification purposes, we came to the conclusion that sending OTP via e-mail for
the verification will be more secure and easier than sending it on a mobile number
 We decided not to let the owner set his/her password because we have to provide a
verified listing of the owner so that the user can get a genuine property listing. So,
we provided a feature to the admin that he/she can set the password for the owners
and send the login details to their registered e-mail address.

218368 Testing
CHAPTER 7
TESTING
When a system is developed, it is hoped that it performs properly. In practice, however,

some errors always occur. The main purpose of testing a system is to find the errors and
correct them. A successful test is one that finds an error
7.1 TESTING PLAN
 To ensure that during operation the system will perform as per specifications.
 To make sure that the system meets the user’s requirements during operation.
 To verify that the controls incorporated in the system function as intended.
 To see that when correct inputs are fed to the system the outputs are correct.
 To make sure that during operations, incorrect input, processing and outputs will be
detected.
7.1.1 Black Box Testing
The functionality of the application was tested with the requirement specification. This was
done to ensure that the functionality expected was captured as per the requirement
specified.
This testing is also known as functional testing. Black Box Testing is a software testing
technique whereby the internal functionality of the item being tested is not known to the
tester. For example, in a black box test on software design, the tester only knows the inputs,
what the expected outcomes are, and not the program arrives at those outputs. The tester
does not ever examine the programming code and does not need any further knowledge of
the program other than its specifications.
7.1.2 White Box Testing
This is basically done to ensure that the logic applied is correct and to check where the code
fails. This is done by knowing the logical flow of the functionality and implementation.
White box testing is used because:
 Logic errors and incorrect assumptions are most likely to be made when coding
“special cases”. Need to ensure that these execution paths are tested.
 May find assumptions about execution paths to be incorrect and so make design
errors. The white box can pick these errors out.

218368 Testing
7.1.3 Unit Testing
Since the system is made by dividing it in modules, all the modules play an important role
in the system so each unit had to be individually tested. The development was done in
iteration and after each iteration was completed, test cases were prepared and all the
features tested. During development, developers
test their own code. When the test is passed, they are moved over for integration testing.
Testing was done to ensure both the functionality and the security aspects of the system.
The test cases designed must involve the execution of the operation with different user roles
and privileges.
7.1.4 Integration Testing
After testing the individual units, the package as a whole has been tested. Thus, we follow
the “Bottom-Up Approach” for testing. All the modules were tested separately also and
together also for both, the performance and the output accuracy.

218368 Testing
7.2 TEST RESULTS AND ANALYSIS
System analysis involves breaking down a system to identify its functions, roles, and the
environment in which it will be expected to operate. Within this activity are the tasks of
performing a feasibility study and requirements engineering. System analysis is therefore
very important throughout any software development process as it plays a significant
determining factor in the success of any software project in terms of usefulness and delivery
within established constraints; and based on how well it is performed, it can make the
difference between software products which are maintainable and those which quickly
become obsolete.
Whether software is developed sequentially or iteratively, system analysis is performed in
some way. The output of system analysis is a system specification document which
becomes a major input into other software development process activities such as system
design, programming, and testing
7.2.1 Test Cases
Table 7.2.1 Test Cases

Test Test Condition Expected Output Actual Output Remark
Id
1 Send e-mail: User Receive OTP on Getting OTP on E-mail N/A
Registration E-mail
2 Send e-mail: Owner Receive OTP on Getting OTP on E-mail N/A
Registration E-mail
3 Setting password for Creating Not able to create To make the

the owner passwords by password by themselvesoption
themselves and receiving passwordavailable for
by admin for login owner to set
purpose their account
password
themselves
4 Customer feedback To receive data Option not yet available To able to
form receive data
5 Payment option Able to make Not able to payments Yet to make
payments payment
option
available
6 Changing user User should able to User is able to change N/A
password change their their password
password

218368 Conclusion and Discussion
CHAPTER 8
CONCLUSION AND DISCUSSION
8.1 OVERALL ANALYSIS OF INTERNSHIP VIABILITIES
- The project “rentprop4u.com” or rental property was successfully completed with

minimal errors.
- We have completed all the strategies discussed for the project development
- Yet there are some features that are not in working mode and they are kept for the
future enhancement
- The project is able to run on minimal specifications of the computer device
- We are also able to send auto email as a project feature which includes OTP for the
verification purpose
8.2 PHOTOGRAPHS AND DATE OF SURPRISE VISIT BY

INSTITUTE MENTOR
Fig 8.2 Photograph of visit by mentor

8.3 DATES OF CONTINUOUS EVALUATION (CE-I AND CE-II)
Table 8.3.1 Continuous Evaluation (CE-I)

Week No. Dates:
1 01-02-2022 to 05-02-2022
2 07-02-2022 to 12-02-2022
3 14-02-2022 to 19-02-2022
4 21-02-2022 to 26-02-2022
5 28-02-2022 to 05-03-2022
6 07-03-2022 to 12-03-2022
7 14-03-2022 to 19-03-2022
8 21-03-2022 to 26-03-2022
9 28-03-2022 to 02-04-2022
10 04-04-2022 to 09-04-2022
11 11-04-2022 to 16-04-2022
12 18-04-2022 to 23-04-2022
Table 8.3.2 Continuous Evaluation (CE-II)

Date: 23-04-2022
8.4 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTION
1. Not able to send OTP on mobile number as text messages

Solution: - Alternative option currently working is sending OTP through E-mail.
2. Owner not able to sign-in directly from the main page
Solution: - Sending owner sign-in links directly to their mail address
3. Owners are not able to set password by themselves during registration
Solution: - The Current feature working for this is admin generates the passwords
for owners, approves them as registered owners and then sends them all the links
also containing the password.
4. Refer and earn option is not working for now
Solution: - No solution for now
5. Not able to book a demo with specialist
Solution: - No solution for now

8.5 SUMMARY OF INTERNSHIP WORK
Rental property or say “rentprop4u” is designed for the purpose of renting a property of an
individual. On this website, an individual can register themselves as a user and can book the
properties and gain access to the features related to the account or they can register
themselves as owner by providing their property details, personal details and get verified by
the admin of the website and gain the access of other features from their respective account.
Rental property is a web-based project. It is designed to let registered users search and book
a property that is posted by registered owners. OTP is sent to the user's/ owner's Email for
verification. Owners can add property from their dashboard. Admin needs to approve
owners and set their password which should be sent via email by the owner personally. so,
the security level is well maintained for both user and owner to stay hassle-free. We also
provide one-point contact for all queries of the customer’s features this is some security
level details provided in our software. so, there are well enough security features on the
website. features like customer support and customers feedback form are also provided.
Categories like apartments, villas, houses, farmhouses, studio apartments, etc. options are
available for the owners to give their desired property on rent also users can find all these
options and can schedule a meeting with the owner and can also book the property with the
owner.it also contains the admin side he/she can manage the data received from the client-
side like activating of account, deleting the account, updating an account, generating
passwords for owners, etc. also google map APIs are used for the location of the property or
user/owner registered in the website.

8.6 LIMITATIONS AND FUTURE ENHANCEMENT
 Limitations: -
o Not able to send OTP on mobile number as text messages
o Owner not able to sign-in directly from the main page
o Not able to get feedback from the visitors
o Not able to book a demo with specialist
o One-point contact is not available yet
o Owner not able to create a password by themselves
o Refer and earn is not working for now
o Not able to make payments
 Future Enhancement: -
o Sign-in and other features for owner directly on website
o To send OTP on mobile phone
o Give payment option for user to owner
o One-point contact to make available
o User should able to book a demo with specialist
o Owner can set password by themselves
o Refer and earn option to make available
o Visitors should able to fill feedback form and data should be collected by
support team

218368
REFERENCES
 https://en.wikipedia.org/wiki/Front-end_web_development
 https://en.wikipedia.org/wiki/User_experience_design
 https://en.wikipedia.org/wiki/Visual_Studio_Code
 https://en.wikipedia.org/wiki/XAMPP
 https://patents.google.com/patent/US6839720
 https://softauthor.com/what-is-google-maps-api/
 https://www.google.com/imgres?imgurl=https%3A%2F%2Fredblink.com%2Fw
p-content%2Fuploads%2F2019%2F07%2Fapplication-stack-langauges_full-
stack-
development.jpg&imgrefurl=https%3A%2F%2Fredblink.com%2Fbecome-full-
stack-developer-2019-
roadmap%2F&tbnid=RGWkYjJB3DUPcM&vet=12ahUKEwiCi8HO56z3AhVU
g2MGHS9MBB8QMygPegUIARDXAQ..i&docid=_0yhnMSHekvhHM&w=873
&h=501&q=schematic%20layout%20for%20full%20stack%20web%20develop
ment&ved=2ahUKEwiCi8HO56z3AhVUg2MGHS9MBB8QMygPegUIARDXA
Q
 https://www.phptpoint.com/codeigniter-overview/
 https://www.seasiainfotech.com/blog/10-benefits-of-using-codeigniter-for-web-
development/
 https://www.tandfonline.com/doi/full/10.1080/02673037.2013.873115?scroll=top
&needAccess=true

Prem

Uploaded by

Document Information

Original Description:

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

Prem

Uploaded by

Copyright:

Available Formats

218368

PREM NITINKUMAR PAREKH

In partial fulfillment for the award of the degree of

Gujarat Technological University, Ahmedabad

Gujarat Technological University MSCET

Mahavir Swami College of Engineering and Technology

guidance in partial fulfillment for the degree of Bachelor of Engineering in

Computer Engineering, 8th Semester of Gujarat Technological University,

Ahmadabad during the academic year 2021-22.

Prof. Ms. Riddhi Desai Prof. Ms. Alpa Valand

Gujarat Technological University MSCET

Gujarat Technological University MSCET

Mahavir Swami College of Engineering and Technology

Name of the Student Sign of Student

Gujarat Technological University i MSCET

Prem Nitinkumar Parekh (181110107029)

Gujarat Technological University ii MSCET

This Software Requirements Specification provides a complete description of all

Gujarat Technological University iii MSCET

Gujarat Technological University iv MSCET

Fig 6.1.22 After accepting terms.........................................................................55

Gujarat Technological University v MSCET

Gujarat Technological University vi MSCET

CSS Cascading Style Sheet

SQL Structured Query Language

PHP Hypertext Preprocessor

XAMPP Cross-platform, Apache, DeMaria (MySQL), PHP, Perl

API Application Programming Interface

VS code Visual Studio Code

OTP One Time Password

MVC Model, View, Controller

CRUD Create, Read, Update, Delete

LOC Lines Of Code

Gantt Generalized Activity Normalization Time Table

SSD Solid State Drive

HDD Hard Disk Drive

Mbps Megabits per second

Gujarat Technological University vii MSCET

Gujarat Technological University viii MSCET

4.4 System Feasibility .......................................................................................14

Gujarat Technological University ix MSCET

Gujarat Technological University x MSCET

Itabtech Infosys is a multi-skilled software service provider with a highly competent

1.2 DIFFERENT PRODUCTS OF WORK

Mylens.Mu is a Mauritian-based online retailer of contact lenses, it quickly evolved

 And other are OKBMU.com, bmbookcentre.mu etc.

Gujarat Technological University 1 MSCET

1.3 ORGANIZATION CHART

Fig 1.3 Organization Chart

1.4 CAPACITY OF PLANT

 The approximate capacity of the company/plant is 15+ resources strength.

Gujarat Technological University 2 MSCET

OVERVIEW OF DIFFERENT DEPARTMENT

 The different departments in our company are: -

2.1 DETAILS ABOUT THE WORK BEING CARRIED OUT IN EACH

Gujarat Technological University 3 MSCET

2.2 LIST THE TECHNICAL SPECIFICATION OF MAJOR

Gujarat Technological University 4 MSCET

2.3 SCHEMATIC LAYOUT OF OPERATIONS FOR

Fig 2.3 Schematic Layout of company’s operation

2.4 DETAILS ABOUT EACH STAGE OF PRODUCTION.

(1) UX/UI Design

(2) Front end