0% found this document useful (0 votes)
107 views40 pages

New Weekend Housing Report

This document is a project report submitted by 4 students for their Bachelor of Technology degree. It describes the development of an Android application called "Weekend Destination" under the guidance of Prof. D. T. Mane. The application aims to provide a platform for users to find weekend getaway destinations. It allows users to view listings of hotels, houses and places uploaded by agents. Users can book listings, view bookings and confirm bookings. The report includes sections on problem definition, literature survey, proposed system requirements, design diagrams, coding, testing, results and future work. It was submitted to fulfill degree requirements at Rajarambapu Institute of Technology.

Uploaded by

Shubham Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
107 views40 pages

New Weekend Housing Report

This document is a project report submitted by 4 students for their Bachelor of Technology degree. It describes the development of an Android application called "Weekend Destination" under the guidance of Prof. D. T. Mane. The application aims to provide a platform for users to find weekend getaway destinations. It allows users to view listings of hotels, houses and places uploaded by agents. Users can book listings, view bookings and confirm bookings. The report includes sections on problem definition, literature survey, proposed system requirements, design diagrams, coding, testing, results and future work. It was submitted to fulfill degree requirements at Rajarambapu Institute of Technology.

Uploaded by

Shubham Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 40

RAJARAMBAPU INSTITUTE OF TECHNOLOGY,

RAJARAMNAGAR
(AN AUTONOMOUS INSTITUTE)

PROJECT REPORT

ON

“Weekend Destination – An Android Application”

DEPARTMENT OF INFORMATION TECHNOLOGY


SUBMITTED BY

Mr. Shubham Patil 1804066

Mr. Hrishikesh Mhetre 1954005

Ms. Bhagyashri Suryawanshi 1954015

Ms. Utkarsh Patil 1953006

Under the Guidance of

Prof. D. T. Mane Sir

Year

2021-2022
Kasegaon Education Society’s
RAJARAMBAPU INSTITUTE OF TECHNOLOGY
(An Autonomous Institute)

Rajaramnagar, Sakharale- Village, Sangli- Dist, MH-415 414

2021-2022

CERTIFICATE
This is to certify that the project work titled “Weekend Destination-An Android
Application” is submitted by Mr. Hrishikesh Mhetre, Miss Utkarsha Patil, Miss Bhagyashri
Suryawanshi, Mr. Shubham Patil for the partial fulfillment of the requirement for the degree
of Bachelor of Technology in Information Technology at Rajarambapu Institute of
Technology (An autonomous Institute), Affiliated to Shivaji University, Kolhapur. This
final report is the record of the student’s work carried out under my supervision and guidance.

Prof. D. T. Mane Dr. S. A. Thorat Dr. N.V.Dharwadkar

Guide Head IT Dept. Head CSE Dept.

Dr. Mrs. S. S. Kulkarni

Director

External Examiner:

1. ……………………………… (Name: )

Place:

Date:

2
ACKNOWLEDGEMENT
.
It is our foremost duty to express our deep sense of gratitude and respect to the
guide Prof. D. T. Mane for his uplifting tendency and inspiring us for taking up this project
work successfully.

We are also grateful to Dr. S. A. Thorat (Head of Department of Information


Technology) and Dr. N.V.Dharwadkar (Head of Department of Computer Science) for
providing all necessary facilities to carry out the project work and whose encouraging part
has been a perpetual source of information.

We are highly indebted to Dr. Mrs. S. S. Kulkarni for their guidance and
constant supervision as well as for providing necessary information regarding the project &
also for their support in completing the project.

We also thank all staff members of our Department for their timely help and
encouragement, which help us in completing our project work.

We are indebted to the library personnel for offering all the help in completing
the project work. Last but not least we are thankful to our colleagues and those who helped us
directly or indirectly throughout this project work.

3
DECLARATION

We declare that this report reflects our thoughts about the subject in our own words. We have

Sufficiently cited and referenced the original sources, referred or considered in this work. We

have not misrepresented or fabricated or falsified any idea/data/fact/source in this our

submission. We understand that any violation of the above will be cause for disciplinary

action by the Institute.

Name Enrollment No. Signature


Hrishikesh Mhetre 1954005
Utkarsha Patil 1953006
Bhagyashri Suryawanshi 1954015
Shubham Patil 1804066

4
ABSTRACT

 This application is designed to attend to all needs from buying property,


selling property or renting property in India. Here we found the better
opportunities to invest your value of entire life. Property portal help us to
maintain the database of various property and agents information. It not
only help us to maintain the agent information but here we also allow
agents to access the portal updated information across the global
environment.
 If we looking to buy, sell, rent, invest and lease a property then here is the
better place to think forward. We know that it is tiring to call individual
property agents, arrange appointment, finding better time for appointment
and they will assist you.
 For such complex process we provide a one simple online application
which require your basic information and we will proceed you to your
required plans.
 Keywords: Android, Android Application, Firebase, Agents, Java, etc.

5
Contents
1. Introduction

2. Problem Life Cycle


2.1. Problem Selection
2.2. Problem Definition
2.2.1 Objective
2.2.2 Relevance
2.3 End User
3. Literature Survey and Motivation

4. Proposed System and Requirement Specification


4.1. Software Requirements
4.2. Software Application Requirement
4.3. Hardware Requirements
4.4. Logical Database Requirements (for database systems only)
4.5. Scope of Project

5. Design
5.1 Data Flow Diagram
5.2 Class Diagram
5.3 Entity Relation Diagram
5.4 Sequence Diagram
5.5 Component Diagram
5.6 User Interface Design
5.7 Activity Diagram
6. Coding and Code Template
6.1 Code Outlines
6.2 Explanation of functions and classes
6
6.3 Implementation
7. Testing
7.1 Testing Methods
7.2 Test Cases
8. Result and Discussion
9. Conclusion and Future Work
9.1 Conclusion
9.2 Future Work

10. References
10.1 Paper References
10.2 Websites

7
List of Figures

Sr. No. Figure Name Page No.


1. Data Flow Diagram of the System 15

2. Class Diagram 17

3. ER Diagram 18

4. Sequence Diagram 19

5. Activity Diagram 22
6. Welcome Page 26
7. Login Page 26
8. Registration page 27
9. Update Profile 27
10. Hotel, house, place Upload list 28
11. Preview 28
12. Customer Home Page 29
13. Booking Menu 29
14. Find House 30
15. Fresh plan 30
16. Under Booking 31
17. Confirm booking 31
18. Fire store Section 37
19. Firebase Section 37
20. Trello Workflow 38

8
CHAPTER 1

Introduction

Day by day our urban life is getting busier and it is quite a hassle to look for To-
Lets wandering around the city. For people of this category online house rental system is a
relief. Here people can easily find the information about rooms, flats or houses just by
sitting in front of their laptop or smart phone.

The system we are going to develop has various features to make life easier for the
urban people. Here tenants can choose from a large variety of houses which meets their
requirements. Also landlords can rent or sell their house or flats via this online system just
by a click of a button. So it will helpful for not only tenants but also for the house owners.
The application will be developed keeping all the key features in mind for both the renters
and owners.

Real Estate App UI is a Flutter theme intended for the rental and sale of real
estate houses. Users can access the real estate market, rent or buy houses, apartments,
offices or villas. It is also possible to contact the different real estate agents that are
available. Everything was made with a detail-oriented style and followed by the most
recent UI/UX trends. Clean code & Layers are well-organized, carefully named, and
grouped. Use of the "provider" package to manage the states.

9
CHAPTER 2

Problem Life Cycle

2.1 Problem Selection

All existence system has some drawbacks like involvement of middle man between
customer and owner for money settlement also there is one main important drawback is it
require more time for booking appropriate place for stay.

2.2 Problem Definition


 Property promises to be the most preferred way of finding your dream property and
we are committed to help you make a wiser property decision, as a buyer or seller. We
understand the needs and concerns of individual’s, Brokers and builders and provide
them a common platform for realizing max benefits and security from real estates.

 Provide a superior real-estate experience by making it easier, faster, secure and


accurate to find buyers for your valuable property. We give our ease to use and also
we will maintain a good relationship with the customers, Brokers, Sellers for
properties.

2.2.1 OBJECTIVE
 The admin should have all the type of authority. He should maintain property.
Admin identify property type as it is residential or commercial property.

 The user should book the property for sell or rent with detail of property.

 The system is very useful for the companies or builders that can post and edit their
properties and their personal info and admin can monitor records of all of them.

 To increase the tourism in rural area by providing information about rural tourism
places

2.2.2 Relevance
The Weekend Destination System governance the main concern of automating real estate
management system. Whenever the concern about automating real estate properties then you
can think forward with this application

10
2.3 End Users
The end users of this system will be property dealers, builders, hotels, buyers, and business
industries

11
CHAPTER 3

Literature Rreview and Motivation

In older days when we want purchase a property we can’t directly communicate


with the owners. We must contact with the help of mediators, but the mediators takes lot of
amount and it is also time consuming process. In older days the property dealing procedure
consist of many steps like finding agent, appoint correct meeting time, location and so on. Up
till now there was no Security in Online Real Estate System, Registration form improves the
security by limiting user.

A boom in the demand for “sustainability” and “smartness” has led to these terms
often being used in conjunction. Cities contribute more than 70 per cent of world greenhouse
gases while occupying only 2 per cent of global land area. Changes in climatic conditions,
such as rising sea levels and global urbanization, call for eco-friendlier buildings. It has been
estimated that by 2020 all buildings in countries with advanced economies will have a
sustainability rating. This need for sustainability requires due attention. Real estate, valued
at $215 billion in 2015 and rising, attracts investors because of its return potential. If it is to
continue attracting investors, it needs to be sustainable. By 2020, invest-able real estate will
have risen by more than 55 per cent since 2012. While “going green”, “clean energy”, and
“building for the future” are critical concepts, sustainability holds a key position in SRE.
[Dr. Cynthia Changxin Wang]

MOTIVATION

 The world is becoming digital with the increasing use of smartphones and apps. The
convenience offered by apps is the reason why people are getting addicted to them.
This application is online real estate application through which a user can access its
information and manage all the tasks.

12
CHAPTER 4

Proposed System and Requirement Specification


4.1 Software requirements

 OS Architecture: 64 Bit
 Operating system: Windows 10, Ubuntu 20.04
 Language: Java 14
 Database: NoSQL Database (Firebase)
 Browser: Any of Google Chrome, Firefox, Safari, etc.

4.2 Software applications requirements

 Android Studio
 Firebase
 Fire store
 Firebase Authentication
 Trello
 Slack

4.3 Hardware requirements


 Processor: Intel i5 or higher processor
 RAM: 8 GB and higher
 Hard disk: 20GB
 Android device for testing
Monitor: Dell Professional 18 inch Full HD Monitor

13
4.4 Logical Database Requirements(for database systems only)
The logical database requirements include the retention of the following data elements.
This list is not a complete list and is designed as a starting point for development.

Weekend Housing Listing


Customer first name Customer last name

Customer Email Customer phone number

Confirmation number Customer Password

Place name Place images

Place Address Booking dates

4.5 SCOPE OF PROJECT

The scope of this project is as following:

 The real of World Wide Web have spread across millions of household, so
naturally, Internet has become by far the best platform for real estate marketing
today.

 There are lot of real estate companies who advertise their property online so idea
behind developing this application is that their property can also sell or buy rental
property using this. These application are not widely popular but in future, they
have large scope of growth.

 The system is very useful for the companies or builders that can post and edit their
properties and their personal info and admin can monitor records of all of them.

14
CHAPTER 5

Design

This chapter illustrates the approaches taken to design the system for Weekend Housing
Listing android application. It discusses system design and gives an overview of the systems
processes. Then, the database schema of the system is illustrated. Lastly, the user interface
design has been developed.

5.1 Data Flow Diagram (DFD)

FIRST PHASE

15
Second phase

Third phase

16
5.2 Class Diagram

17
5.3 E-R Diagram

18
5.4 Sequence Diagram

5.5 Component Diagram

19
5.6 User Iinterface design

User interface is important to meet user expectations and support the effective functionality
of an application. A well-executed user interface facilitates effective interaction between the
user and the program, app or machine through contrasting visuals, clean design and
responsiveness. When designing a UI for your site, it's important to consider the user's
expectations in terms of accessibility, visual aesthetic and ease of use. An optimal mix of
effective visuals and efficient responsiveness will improve app’s conversion rates, as it
anticipates the needs of the user and then satisfies those needs.

Screen Name Description

Login Log into the system using register email and password

Registration Register using new user personal detail’s. It contain username, email,
password.

Forgot Password Password recovery system using email.

Delete Account Delete user Account and personal details.

Dashboard This user dashboard activity contain user previous booking,user details
and go for new reservation of Housing.

Find home Search house/hotel as per your choice.

Preview findhome In this activity user will visit house/hotel details.

Freshplan System recommended plan

Preview freshplan In this activity user will visit house/hotel details.

Booking process After visiting Preview page you can book with personal details.

Booking section Findhome and Freshplan Booking details in this activity shown.

Support Customer needed calls and Message support.

20
5.7 Activity Diagram

21
CHAPTER 6

CODING/CODE TEMPLATE

6.1 Code Module outlines


Seller side

 Authentication
 User dashboard
 Profile extraction and update profiles for both side
 Add products from producer side
 Show Booking
 Display received booking
 Accept or reject booking.

Buyer side

 Authentication
 User dashboard
 Select plan
 Go for booking
 Fill details and booking
 Show booking
 Wait for conformation of booking.

22
6.2 Explanation of Functions and Classes with input and output
parameters
 Authentication: This module checks the authenticity of the user and according to
its accessibility level redirects either on the consumer dashboard or producer dashboard.

 User dashboard: This module consists of various options depending upon is it


buyer or seller. If the user is a buyer then it can see all the products, search products, add
products in a cart, and place order. Apart from this it can also edit profiles. On the other
hand, Seller dashboard consists of their product details, received booking from customer,
payment status, seller can add new products.

 Add house, place in application: seller can add various house, place, hotel
according to their category such as selling for rent, weekend etc.

 Display hotel/house/place details : It contains main crux of project that is it display


all house, place, hotel that are selling for rent or weekend for example, If seller is selling
one house for weekend enjoyment so the place get notified in application section.
 Booking in buyer side : Customers can view and choose house, place, hotel as per
needs and buy it for weekend or rent.

 Payment: It takes care of secure, safe and fast payment options.

 Display received booking: seller should get details of booking given by customer.

 Profile: This module is common on both sides. the user can update and check its
own profile details.

6.3 Project structure environment settings

To change various settings for your Android Studio project, open the Project Structure
dialog by clicking File > Project Structure. It contains the following sections:

● SDK Location: Sets the location of the JDK, Android SDK, and Android NDK that
your project uses.

● Project: Sets the version for Gradle and the Android plugin for Gradle, and the
repository location name.

● Modules: Allows you to edit module-specific build configurations, including the


target and minimum SDK, the app signature, and library dependencies. See Modules, below.

23
6.4 Modules and Environment
The Modules settings section lets you change configuration options for each of your project's
modules. Each module's settings page is divided into the following tabs:

● Properties: Specifies the versions of the SDK and build tools to use to compile the
module.

● Signing: Specifies the certificate to use to sign your app.

● Flavors: Lets you create multiple build flavors, where each flavor specifies a set of
configuration settings, such as the module's minimum and target SDK version, and the
version code and version name. For example, you might define one flavor that has a
minimum SDK of 15 and a target SDK of 21, and another flavor that has a minimum SDK of
19 and a target SDK of 23.

● Build Types: Lets you create and modify build configurations, as described in
Configuring Gradle Builds. By default, every module has debug and release build types, but
you can define more as needed.

● Dependencies: Lists the library, file, and module dependencies for this module. You
can add, modify, and delete dependencies from this pane. For more information about module
dependencies, see Configuring Gradle Builds.

24
6.3 Implementation

Welcome Page Login Page

25
Registration page Update Profile

26
Upload list seller side Preview

27
Customer home Page Booking Menu

28
Find house Fresh plan

29
Booking Confirm Booking

30
Under booking (buyer side) booking accept or
reject(seller side)

31
7.Testing
Testing is a method to check whether the actual software product matches expected
requirements and to ensure that the software product is Defect free. It involves execution of
software/system components using manual or automated tools to evaluate one or more
properties of interest. The purpose of software testing is to identify errors, gaps or missing
requirements in contrast to actual requirements.

7.1 Testing Methods

7.1.1 Functional Testing:

Testing is normally achieved by user interface initiated test flows. Not just the flow of a use
case is tested, but the various business rules are also tested. Testing is done by certifying the
requirements. i.e. whether the application is working based on the requirements.

This is functionality testing and here you will test functionalities like:
 Verify whether the hotel, place, home cards are shown w.r.t the location.
 Verify whether the application cards are now overlapping each other.
 Verify whether the review count for each card is in sync with the reviews given.
 Check whether adding a new house for a location reflects in the list.
 Verify whether the restaurants are listed based on the filtering rule of application.

7.1.2 Android UI Testing:

This is an user-centric testing of the application. In this test phase, items such as visibility of
text in various screens of the app, interactive messages, alignment of data, the look and feel
of the app for different screens, size of fields etc. are tested under this.

 Verify whether the cards are shown properly aligned with the mobile screen size.
 Verify whether the image of the house is shown as expected.
 Verify whether the card details, name of house, type, address etc., are shown properly
aligned.
 Verify whether the scrolling of the list is glitch free and the cards are not shown
misaligned when a long list of cards is scrolled etc.

32
7.1.3 Compatibility Testing:

This testing is done mostly in the form of two matrices of OS Vs app and Device model Vs
app. Usually, a list of supported OS (and sometimes devices) is provided by the product
owner or customer.

Those conditions include:


 When an OS like Android is taken into account, 7 base versions are found neglecting
the number of patch releases/EPs.
 Can you guess the types of Android devices currently working all over the globe?
1000? 2000? Wrong! The correct answer is 24000. There are 24000 types of unique
Android devices that are present and active in the world.
 With variations such as these, compatibility testing plays a vital role in certifying an
android app.
 We not only need to validate the OS and type of the device but also validate few other
features which fall into compatibility testing.

The features include:


 Screen size
 Screen resolution
 Network connectivity

7.1.4 Interface Testing:

In other words, it is also termed as Integration testing. This testing is done after all the
modules of the app are completely developed, tested individually and all the bugs are fixed
verified.

Interface testing includes tests like a complete end to end testing of the app, interaction with
other apps like Maps, social apps etc, usage of Microphone to enter text, usage of Camera to
scan a barcode or to take a picture etc.

Those conditions include:


 Verify whether the user is able to book place in freshplan.
 Verify whether the user is able to view the menu of setting of profile.
 Verify whether the user is able to avail a PayTM coupon while booking.
 Verify whether the user is able to view the location of the restaurant on Google Maps.
 Verify whether the user is able to open the phone dialer and call the support team etc

33
7.1.5 Network Testing:

Those conditions include:


 The app should talk to the intermediate service so as to carry out the process.
 During this testing, request/response to/from the service is tested for various
conditions.
 This test is mainly done to verify the response time in which the activity is performed
like refreshing data after sync or loading data after login etc.
 This is done for both strong wifi connection and the mobile data network. This is an
in-house testing.

7.1.6 Performance Testing:

Performance of the application under some peculiar conditions are checked.

Those conditions include:


 Low memory in the device.
 The battery in extremely at a low level.
 Poor/Bad network reception.

Performance is basically tested from 2 ends, application end, and the application
server end

7.1.7 Interrupt Testing:

This type of testing is also known as Offline Scenario Verification. Conditions where the
communication breaks in the middle are called as offline conditions.

Those conditions include:


 Data cable removal during data transfer process.
 Network outage during the transaction posting phase.
 Network recovery after an outage.
 Battery removal or Power On/Off when it is in the transactional phase.

34
7.2 Test Cases:

Test case Testing Precondition Steps Test data Expected Status


ID type result

TC1 Functional Application Open application All card of Cards Pass


Testing should installed ->Login as application should be
on specific registered user load on
device. specific
column and
they should
get open.
TC2 Interface Application Open application Freshplan All added Pass
Testing should installed ->Login as section plan should
on specific registered user get listed in
device. Proper
->Select freshplan recycler
Application card from view.
should open on dashboard
device.

TC3 Compatibility Application Install application Lunching of Application Pass


Testing should installed on android application should get
on two or more version 8.0 and open on
device. android version android
6.1 v8.0 and
v6.1
TC4 Interrupt Application Open application Findhome Data Pass
Testing should installed ->Login as section Loading
on specific registered user recycler should get
device. ->open findhome view data. stop and
card user can’t
Application ->go to setting do booking.
should open on ->turn on airplane
device. mode
TC5 Android UI Application Open application Preview of Preview of Pass
testing should installed ->Login as clicked place/hotel
on specific registered user hotel/place. should load
device. ->open freshplan in well UI
section form, it
Application ->select one place don’t
should open on for booking overlap
device. each other
TC6 Security Application Open Application Login For Pass
Testing should installed ->go for login system incorrect
on specific credential
device. application
generate
Application toast
should open on message of
device. invalid
login

35
8: Result and Discussion

Fire store real-time database

Firebase

36
Trello workflow

37
CHAPTER 9: CONCLUSION AND FUTURE
WORK

This chapter concludes the report of this project. This chapter starts with discussing
the achievements of this project. Following that, it describes the limitations in the
system. It then proposes and recommends some features to be added to the system.
Finally, the chapter ends by concluding remarks.

9.1 ACHIEVEMENTS:
The project has gone through a series of activities to develop a complex solution for
House listing system. After analysis of the project’s goal and research
direction, a set of objectives were established, as specified in Chapter 1.2. All the
activities done during the project were attempts to realize these objectives. At the end
of the project, the developed prototype software has fulfilled these objectives by the
following means:

 Objective #1: bring the real estate industry online and enabling real estate industry
participant to benefit from the internet.

 Objective #2: To provide a portable product that can access anywhere and anytime.

 Objective #3: To increase the tourism in rural area by providing information about
rural tourism places.

 Objective #4: Provided best plan for customer as per his need.

 Objective #5: Provided a better platform to customer for selecting better place by city
searching.

project was time-consuming. It has been tried to implement as many features as


possible within the very limited timeframe. It has successfully satisfied the Functional
Requirements. Some Non-functional Requirements of the system are not implemented. These
requirements have top priority and reflect the most needed features. Some requirements are
not implemented due to time constraints. However, their absence would not result in major
operational issues as they are the lower priority features. These features could be
implemented in the future.

38
9.2 Future Work

In addition to the unfinished requirements, there are other possibilities of further improving
the project. The respondent of user acceptance testing also suggest some improvement ideas.
The improvements may include:

 Real-time Video calling from buyer and seller section.

 Chat section for buyer and seller section.

 Extra details for hotel, place, house for choosing better option for enjoyment.

 Booking can be placed via virtual assistants or Chabot. This will bring ease among
the users.

39
CHAPTER 10: REFERENCES
10.1 Paper References

1.Anirudh, V., Akhil, C. and Kailash, G.: Online real estate portal. Int. Res. J. Eng.
Technol. 5(1) (2018)

2.Dan, H., Grant, O., Karen, C., Terhilda, G., Heather, Q., Joanne, T.: Access to radiology
reports via an online patient portal: experiences of referring physicians and patients. J. Am.
Coll.E Radiol. 12(6) (2015)

3.Kristy, K.B., Omobolanle, O.O., Sharon, E.P., Rebeccah, B.B., Michael, D.H., Kenneth,
W.S., Richard, A.P., William, H.N., Benjamin, K.P.: Postoperative Care Using a Secure
Online Patient Portal: Changing the (Inter)Face of General Surgery. In: Proceedings of
American College of Surgeons 101st Annual Clinical Congress, Scientific Forum, Chicago
(2015)

10.2 Websites
1. Programming in My Way- An Informative YouTube Channel by Mr. Mandle Sir.

2. Small Academy You tube Channel important videos regarding application security.

3. For old Methodology approach we got valuable suggestion from ganga reddy sir.

4. https://www.indeed.com/career-advice/career-development/user-interface.

5. https://www.guru99.com/software-testing-introduction-importance.html

40

You might also like