Presentation

On
COTTAGE CLAMAINT
Team Id:

Group Id:
Prepared By:

Guided By : Collage Professor Name

CONTENT
Introduction
Problem statement
Objectives
Related Background
Tools & Technology
System Flow
Modules in Project
DATA DICTIONARY
Diagrams
ER/CLASS DIAGRAM
USE CASE DIAGRAM
ACTIVITY DIAGRAM
SEQUENCE DIAGRAM

COMPONENT DIAGRAM
COLLABORATION DIAGRAM
DEPLOYMENT DIAGRAM
Snapshots of GUI
Expected outcome
Advantages
Limitations
Future work
References

INTRODUCTION
The purpose of this Project is to develop a dynamic website and an android mobile
application which will be helpful to users to find Cottages and also helps the users to
get information regarding Cottages available in the city.
This system is very easy to use, for using this system user have to register themselves
on our website. Till now people have to suffer from here to there for finding Cottages.
This is the system in which user get some new features like timing available to visit,
Broker-based Cottages or Non Broker Cottages, Transport facilities available nearby,
Add to wish list, Rent agreement, Online payment procedure, Due payment reminder,
Get discount, Feedback and Reviews all such facilities we are going to provide in our
system.

PROBLEM STATEMENT
1. Time Consideration
Increased time taken by personnel. It is very tedious job to find a proper
Cottages as per your choice and for the other.
At the time of searching Cottage, all the records have to be scanned and even
after the people cant be sure that they will be able to find a proper Cottage.
In addition, owner wants to update their records each time a deletion or
addition.

2. Cost Consideration :
A large numbers of people are involved to maintain the whole
system that is very expensive.
Unreliable and inefficient data entry.
Redundant data storage.

3. Need for system:

The existing system is very slow and needs more time to search and

maintain each and every detail.

Retrieval of required information is become difficult and time consuming.
Security of data is very critical issue which has to consider in the current
system there is no data security.
Same data is maintained in various file which is leading to redundancy of
data.
Report generation is very tedious job. The in-charge of preparing report has
to refer more than one file.

OBJECTIVES
Time Effective and Cost Effective :
Property site is available to anybody and anywhere. This saves a lot of time of the
customer and in a very little span the register user may look the whats an offer
on the special products purchasing. This plan cost offered in economic too.

Database Creation :
A database of the registered users will be created and this will help the users to
fetch the details of recent Cottage as per requirements. There is a separate database
for administrator for updating the site.

Mobility :
Internet is available to everybody anywhere anytime here, this makes the site
highly mobile.

 Wide Approach :
Any person can visit it. User can register with or without photographs.
Therefore it has a wide range of users. 31

Security :
Proper authorization and authentication provisions have been made for the
security of the site so that only the registered user can look the special offer
details. Without proper login no one is allowed to access the special offer list of
this site.

Flexible :
The site is flexible to any expansion or contraction in the future. For example:
sending email confirmation to the email as well as through sms after the
registration. If new property added on the website, the sms alert will be
available for mobile users.

RELATED BACKGROUND
At the time of searching Cottage, all the records have to be scanned and
even after the people cant be sure that they will be able to find a proper
Cottage.
People Finding Cottages by door to door which take too much time.
Till now people have to suffer from here to there for finding Cottages.

TOOLS AND TECHNOLOGY

Front-End Tool : Python
Back-End Tool : MySql
Server : Apache
Documentation Tool : Python Editor

SYSTEM FLOW DIAGRAM

Start
View the site
No

Is
Registered?

Yes
Login

No
(Admin )
Manage location
Manage User
Manage Category
Manage Payment

(Cottage owner )

Is
Authorize?
Yes

Registration

( User)

Manage profile

Manage Profile

Select Category

Search Cottage

Add Cottage

Book Cottage
Make Payment

Manage Report

Give Feedback

Manage Feedback
Log Out
Stop

MODULES IN PROJECT
1. Administrator Module (Admin):
. In administrator module administrator allow the Cottages to be uploaded and active that
Cottages to show other user who search for Cottages.
. Administrator can add new category and type of Cottages to the system so that users can add
their Cottages according to the category and type.
. Administrator can delete the Cottages.
. Administrator can recover the password by providing the username and email.
. Administrator can view the requirements and feedback which are posted by different user
and responses to that requirement.

2. Cottage Owner :
To post Cottages on website the Cottage owner has to register first.
After successful registration Cottage owner can login to proceed ahead.
If Cottage owner forgot the password he can recover it easily by providing the
username and email id.
He can also make changes in his profile.
Cottage Owner can upload his Cottage for rent.
Cottage is posted on website after successful payment transaction.
After rent he can delete his Cottage house.
He can also send feedback to the Admin.

3. Broker / Agent :
Broker is having the same functionality as Cottage owner. The main
advantage of Broker is that if the user want to take a house on rent but he
does not have knowledge of computer and internet then he can take that
Cottage through broker.
The other advantage is that if the user has not its own Cottage for rent but
he has good contact with different Cottage Owners then he can upload the
Cottage details on website.

4. Renter :
Renter has to register first.
After registration Renter can login to proceed ahead.
If Renter forgot the password he can recover it easily by providing the
username and email id.
Renter can search Cottages from different location and city. After that he can
send request to the Cottage owner or Broker to book that Cottage.
If Cottage is not found at particular location or city he can post his
requirement on website about Cottage to the admin.
Renter can view uploaded Cottage by Cottage owner.
Renter can also view the response send by the admin. He can also send a
feedback to the admin.

5. Search Module :
In search module user can search for different types of Cottages
uploaded by registered user.
User will get to know all information about Cottage, its
location, area, its approximate price, owner details etc.
In search module user can search Cottage according to his
budget.

DATA DICTIONARY
.
.
.
.

Table name :- Login

Primary Key:- Login_ID
Foreign Key:-powner_id
Description:- This table contains information about user name and password.
No

Field

Datatype(size)

Constraints

Description

Login_id

Int

Primary Key

To store user identification.

powner_id

Int

Not Null

Email_id

Varchar(50)

Unique Key

Password

Varchar(30)

Not Null

To store password

User_type

Varchar(30)

Not Null

Store the user type.

To store property owner

registration maximum id.
Store the user email id.

.
.
.

Table name :- State.

Primary Key:- State_ID
Description:- This table contains information about city.

No

Field

Datatype(size)

Constraints

Description

State_ID

Int

Primary Key

To store state id.

State_name

Varchar(30)

Not Null

To store state name.

.
.
.
.

Table name :- City

Primary Key:- City_ID
Foreign Key:- State_ID
Description:- This table contains information about State.

No

Field

Datatype(size)

Constraints

City_ID

Int

Primary Key

City_name

Varchar(30)

Not Null

State_ID

Int

Foreign key
(state)

Description
To city id.
To store city
name.
To store state id

.
.
.
.

Table name :- Area

Primary Key:- Area_ID
Foreign Key:- City_ID
Description:- This table contains information about State.

No

Field

Datatype(size)

Constraints

Description

Area_ID

Int

Primary Key

Area_name

Varchar(30)

Not Null

To store area
name.

City_ID

Int

Foreign key
(city)

To store city id

To area id.

.
.
.

Table name :- Category.

Primary Key:- Cat_ID
Description:- This table contains information about category of property.

No

Field

Datatype(size)

Constraints

Description

Cat_ID

Int

Primary Key

To store category
id.

Cat_name

Varchar(50)

Not Null

To store category
name.

.
.
.
.

Table name :- User_reg

Primary Key:- User_ID
Foreign Key:- State_ID,City_ID,Area_ID.
Description:- This table contains information about User.
No

Field Name

Data type(size)

Constraints

Description

User_ID

Int

Primary key

User_name

Varchar(30)

Not Null

To store user name

Password

Varchar(30)

Not Null

To Store the password

Email_id

Unique Key

Not Null

To store email address

Gender

Varchar(6)

Not Null

Describe gender

Phone_no

BigInt(10)

Not Null

To store Phone number

Address

Varchar(255)

Not Null

Valid address

State_ID

Int

Foreign key
(state)

Store the state id.

City_ID

Int

Foreign key
(city)

Store the city id.

10

Area_ID

Int

Foreign key
(area)

Store the area id.

To store user id

.
.
.
.

Table name :- CottageOwner_reg

Primary Key:- Powner_ID.
Foreign Key:-State_ID,City_ID, Area_ID.
Description:- This table contains information about property owner information
No

Field Name

Data type(size)

Constraints

Description

Powner_ID

Int

Primary key

Powner_name

Varchar(20)

Not Null

To store Cottage owner

name

User_name

Varchar(20)

Not Null

To store user name

Password

Varchar(30)

Not Null

To Store the password

Gender

Varchar(6)

Not Null

Describe gender

Address

Varchar(255)

Not Null

To store address

State_ID

Int

Foreign key
(state)

To store state id

City_ID

Int

Foreign key
(city)

To store city id

To store Cottage owner id

Continue..

No

Field Name

Datatype(size)

Constraints

Description

Area_ID

Int

Foreign key
(area)

10

Email_id

Unique Key

Not Null

To store email address

11

Phone_no

Number(10)

Not Null

To store Phone number

12

Pin_no

Number(6)

Not Null

To store Pin code

number

To store area id

.
.
.
.

Table name :- Cottage

Primary Key:- P_ID
Foreign Key:- State_ID,City_ID,Area_ID,Cat_ID,Powner_id.
Description:- This table contains information about Cottage.
No

Field Name

Data type(size)

Constraints

Description

P_ID

Int

Primary key

P_name

Varchar(50)

Not Null

To store Cottage name.

Cat_ID

Varchar(15)

Foreign key
(category)

To Store the category of

Cottage.

State_ID

Varchar(20)

Foreign key
(state)

To store state id.

City_ID

Varchar(6)

Foreign key
(city)

To store city id.

Area_ID

Int

Foreign key
(area)

To store the area id.

Description

Varchar(40)

Not Null

To store the description of

Cottage.

Image

Varchar(100)

Not Null

To store image of the Cottage.

To store Cottage id.

Continue..

No

Field Name

Datatype(size)

Constraints

Description

Price

Int

Not Null

To store price of Cottage.

10

Powner_ID

Int

Foreign key
(CottageOwner
_reg)

To store Cottage owner

id.

.
.
.

Table name :- FeedBack.

Primary Key:- Feedback_ID
Description:- This table contains information about user feedback for doctors.

No

Field

Datatype(size)

Constraints

Description

Feedback_ID

Int

Primary Key

Name

Varchar(10)

Not Null

To store name who send

the feedback

Date

Varchar(8)

Not Null

To store date

Email-ID

Varchar(20)

Not Null

To store email-id

Message

Varchar(40)

Not Null

To store feed back

messages.

To store feedback id.

.
.
.
.

Table name :- Payment

Primary Key:- Pay_ID
Foreign Key:- User_ID.
Description:- This table contains information about payment.
No

Field Name

Data type(size)

Constraints

Description

Pay_ID

Int

Primary key

To store payment id.

User_ID

Int

Foreign Key
(User_reg)

To store user id.

Amount

BigInt

Not Null

To Store the amount of

Cottage.

Pay_date

Date

Not Null

To store date of payment.

Status

Varchar(20)

Not Null

To store status of payment.

DIAGRAMS

ER / CLASS DIAGRAM

Password

Email_id

Manage

ADMIN

M 1 1

view

Password

Pow_id
Cottage Owner

pay_id

pow_name

Has

Payment

1
1

M
A_id

User_id

Area

cat_id

A_name
Category

Add

View

F_msg
Give

p_id

M
F_id

FEEDBACK

User

Cottage

Password

User_id

Give

name

Select
Search

p_date

book
search

USE CASE DIAGRAM

Login
Cottage owner
registration
Manage User

Manage location
Manage Category

Admin

Manage Payment
Manage feedback
Generate Report

Logout

Registration
Login
Manage Profile
View Category
Search Cottage
View Cottage
User

Book Cottage
Make Payment

Feedback
Log out

Log in

Select Category

Add Cottage

Cottage Owner
Logout

ACTIVITY DIAGRAM

[Admin Activity Diagram]

View site
Valid?
No
Login

Manage
User

Manage
Location

Manage
Category

Manage
Payment

Logout

Yes

Cottage Owner
Registration

Manage
Feedback

Manage
Report

[User Activity Diagram]

View site
No
Valid?
Registration

No

Yes
Login

Edit Profile

Search Cottage

Book Cottage

Logout

Yes

Make Payment

Feedback

[Owner Activity Diagram]

View site
No
Registration

Valid?
No

Yes
Login

Manage Profile

Yes

Select Category

Logout

Add Cottage

SEQUENCE DIAGRAM

Sequence Diagram for Admin

:Admin

:System
Login(id , password)

:Database
Request(id , password)
Select

Success
Manage state(s_id , name)

Return(id , password)
Request(s_id , name)
insert

Success
Manage City (c_id , name)
Success
Manage Area(a_id , name)
Success
Manage category(cat_id ,cat_name)

Return (s_id , name)

Request (c_id , name)
Request(c_id , name)

insert

Request (a_id, name)

Return (a_id ,name)

insert

Request (cat_id ,cat_name)

insert

Success
Manage Cottage owner(powner_id ,Name)
Success
View user detail(Reg_id)

Return (cat_id, cat_name)

Request (powner_id, name)
Return(powner_id,name)

Insert

Request (Reg_id)
Select

View detail

Return (Reg_ID)

P.T.O.

View Cottage (p_id, powner_id)

Request(p_id , powner_id)
Insert

Success

Manage Payment(pay_id, user_name)

Return(p_id, powner_id)

Request(pay_id , user_name)
Insert

Success

Return(pay_id, user_name)

Manage feedback(feedback_id,)
Request(feedback_id)
Success

Logout
Successfully Logout

Return(feedback_id)

Select

Sequence Diagram for User

:User

:System
Registration(Reg_id , password)

:Database
Request(Reg_id , password)
Select

Success
Login(id , password)

Return(Reg_id , password)
Request(id , password)
insert

Success
View category (cat_id )
Success
search Cottage (p_id )
Success
View Cottage (p_id )

Return (id , password)

Request (cat_id )
Request(cat_id )

insert

Request (p_id)
Return (p_id ,name)

Select

Request (P_id )
Select

Success
Book Cottage (p_id)
Success
Make payment(pay_id,user_id)
Success

Return (P_id)
Request (p_id)
Return(p_id)
Request (pay_id,user_id)
Return(pay_id,user_id)

Insert

Insert

P.T.O.

Give feedback(feedback_id)
Request(feedback_id)
Success

Logout
Successfully Logout

Return(feedback_id)

Insert

Sequence Diagram for Cottage Owner

:Cottage
Owner

:System

:Database

Login(id , password)
Request(id , password)
Select
Success

Return(id , password)

Manage Profile(Reg_id)

Request (powner_id)

Get Detail
Select category(cat_id,)
Success
Add Cottage (p_id)
Success
Logout
Successfully Logout

Return(powner_id)

Give

Request (cat_id )
Return(cat_id)

Give

Request (p_id)
Return(p_id)

Give

COLLABORATION DIAGRAM

Admin Side Collaboration Diagram:

System
1: Login
2: Manage State
3. Manage City
4: Manage Area
5: Manage Category
6: Manage Cottage Owner
7: View User detail
8: Manage Payment
9: Manage Feedback
10: Logout

1:1 Request Login

2:1 Request Manage State
3:1Request Manage City
4:1 Request Manage Area
5:1 Request Manage Category
6:1 Request Manage Cottage owner
7:1 Request View user detail
8:1 Request Manage Payment
9:1 Request Manage Feedback
10: Logout

1:1:1:1 Success login detail

2:1:1:1 Success State detail
3:1:1:1 Success City detail
4:1:1:1 Success Area data
5:1:1:1 Success Category data
6:1:1:1 Success Cottage Owner detail
7:1:1:1 Success User detail
8:1:1:1 Success Manage Payment
9:1:1:1 Success Feedback detail
10:1:1:1 Logout Successfully

Admin

Database

1:1:1 Return Login

2:1:1 Return State data
3:1:1 Return City data
4:1:1 Return Area data
5:1:1 Return Category data
6:1:1 Return Cottage Owner detail
7:1:1 Return User detail
8:1:1 Return Payment
9:1:1 Return Feedback detail
10:1:1 Logout

User Side Collaboration Diagram:

1:1: Request Login detail
2:1: Request Manage Profile
3:1: Request View Category
4:1: Request Search Cottage
5:1: Request View Cottage
6:1: Request Book Cottage
7:1: Request Make Payment
8:1: Give Feedback
9:1: Logout

System
1:1:1:1: Success login detail
2:1:1:1: Success Manage Profile
3:1:1:1: Success View Category
4:1:1:1: Success Search Cottage
5:1:1:1: Success View Cottage
6:1:1:1: Success Book Cottage
7:1:1:1: Successfully Make Payment
8:1:1:1: Successfully Give Feedback
9:1:1:1: Logout

1: login detail
2: Manage Profile
3: View Category
4: Search Cottage
5: View Cottage
6: Book Cottage
7: Make Payment
8: Give Feedback
9: Logout

User

Database

1:1:1 Return login

2:1:1 Return Manage Profile
3:1:1 Return Request View Category
4:1:1 Return Request Search Cottage
5:1:1 Return Request View Cottage
6:1:1 Return Request Book Cottage
7:1:1 Return Request Make Payment
8:1:1 Return Request Give Feedback
9:1:1 Logout

Property Owner Side Collaboration Diagram:

1:1 Request Login detail
2:1 Request Manage Profile
3:1 Request Select Category
4:1 Request Add Cottage
5:1 Logout

System
1: login detail
2: Manage Profile
3: Select Category
4: Add Cottage
5: Logout

1:1:1:1 Success login detail

2:1:1:1 Success Manage Profile
3:1:1:1 Success Category List
4:1:1:1 Success Add Cottage
5:1:1:1 Logout

Cottage Owner

Database

1:1:1 Return login

2:1:1 Return Manage Profile
3:1:1 Return Category list
4:1:1 Return Cottage
5:1:1 Logout

DEPLOYMENT DIAGRAM

DATA FLOW DIAGRAM

 Level 0 DFD :

 Level 1 DFD :

 Level 2 DFD :

FEATURES
Save time of search.
Give a modification power to sites owner. So, Administrator of site can make any changes
such like can add a new Cottage category and Cottage type details on the working
windows.
Administrator can also change the Banner.
Location based Cottages.
Splash Screen.
Login / Registration.
Cottage Category.

 Timings available to visit.

Broker based Cottages or Non Broker Cottages.
Transport Facilities Available nearby.
Conversation between Cottages.
Advanced Filters for owners who have many Cottage
accommodation across city.
Facilities Available with Cottage Details.
Status of Cottage (Like availability of Cottage room in how many
upcoming days Cottage will be vacant).
Online Payment Procedure for rent.
Due payment, alerts or reminder from owner.

 Photo gallery.
Rent Agreement of Contract facilities and document submission medium.
Details Facilities for each Cottage with plan.
Food Chart or Menu.
Feedbacks and Review.
Social Media Integration.
Rules and Regulations.
Terms and conditions of Cottage.
Quick search to paying guest.
Add favourite searches to list.

 Add to Wish list (*).

Refer a Cottage and get discount.
Map facility available.
Like, Comment, Post of View Cottage Page.
Call the paying guest owner.
Share search result with your friends.

ADVANTAGES
Time Consuming
User Friendly
People can find Cottages easily According to their need and
requirements.
This Application Reduces the cost for finding Cottages.
Fast searching.
User friendly environment.
Ease of access.
People can find Cottages easily Accordingly to their need and
requirement.
This Application Reduces the cost for finding Cottages.
Best offers and details on hand.
Cool Graphics.

LIMITATIONS
Cottage details are displayed for the limited number of days.
It doesnt cover the international market.
Advance search facility is available for only registered user.
Only few cities Cottage can be uploaded.
It doesnt have online agreement facility.

FUTURE WORK
Following are some of the enhancement proposed to be implemented in final version.
Lease option should be provided regarding properties.
Give access of website on mobile and PDAs
Send SMS to Cottage owner who have registered and uploaded his Cottage.
Giving Cottage site for all metro cities.
Upload videos / 3d views of the Cottage Houses.

THANK YOU