A
PROJECT REPORT
ON
“REAL ESTATE”
SUBMITTED BY:
THAKKAR MANSI (140390116014)
TEAM ID: 26030
IN FULFILLMENT FOR THE AWARD OF THE DEGREE
OF
BACHLOR OF ENGINEERING
IN
INFORMATION TECHNOLOGY
APR – MAYM 2018
S.P.B PATEL ENGINEERING COLLAGE, LINCH
SAFFRONY INSTITUTE OF TECHNOLOGY
GUJARAT TECHNOLOGICAL UNIVERSITY, AHMEDABAD
GUJARAT TECHNOLOGICAL UNIVERSITY, AHMEDABAD
S.P.B. PATEL ENGINEERING COLLEGE
SAFFRONY INSTITUTE OF TECHNOLOGY
CERTIFICATE
This is to certify that the project entitled REAL ESTATE is a bonafied report of the work carried out by THAKKAR MANSI – 140390116014 under the guidance of Mr.Parimal Patel for the successful completion of project, Information technology at Saffrony Institute of Technology-Linch, Mehsana, Gujarat.
To the best of my knowledge and belief, this work embodies the work of candidate herself/himself, has duly been completed, fulfils the requirement of the ordinance relating to the completion of project and is up to the standard in respect of content, presentation and language for being referred to the examiner.
Prof.parimal Patel Pro.akshay Kansara
(Internal Guide) (HOD CE-IT)
Acknowledgement
I Would like to thanks Pro.Mr.parimal Patel for their support and guidance toward me for completion of project. I also would like to thanks all those who knowingly or unknowingly help to me all thought my project.
Many are responsible for the knowledge and experience I have gained during project and thought course. With profound sense of gratitude and regards I acknowledge for extended by my friends for their support in completion this project.
Abstract
• My project report on “real estate” which is the website related to the estate.
• This website solve problem of his/her estate related.
• In this website seller upload their property and find a broker for sell the property
• Broker show the property which upload by seller and contract with seller.
• In this website registration is a free of cost. So any broker or seller register on it.
• Seller gives review to the broker so broker profile has strong.
• In this website seller give the money to broker via PayPal account in advance.
INDEX
1. INTRODUCTION…………………………………………………………………9
1.1 Problem Summary and Introduction…………………………………………………………………..9
1.2 Aim and objective of the project……………………………………………………10
1.3problem specification……………………………………………………………..…10
1.4plan of work………………………………………………………………………….10
1.5material/tool required…………………………………………………………………10
2 PROJECT MANAGEMENT……………………………………………………….14
2.1Milestones And Deliverables……………………………………………………….14
2.2Risk Management……………………………………………………………………14
2.3Risk Identification…………………………….………………………………….. ..15
2.4Risk Analysis…………………………………….…………………………………15
2.5Risk Planning………………………………………………………………………15
3. SYSTEM ANALYSIS AND REQUIREMENT……………………………………..17
3.1 System Feasibility………………………………………………………………….17
3.2 requirement of system…………………………………………………………….20
3.3Functional requirements……………………………………………………………21
3.4Non-Functional requirements………………………………………………………21
3.5design constrain…………………………………………………………………….21
4. System Design…………………………………………………………….23
4.1 E-R diagram………………………………………………………………………..23
4.2 System flow diagram………….……………………………………………………25
4.3 use case diagram……………………………………………………………………27
4.4 data flow diagram…………………………………………………………………..31
4.5 Class Diagram………………………………………………………………………34
5. DATA DICTIONARY…………………………………………………………………37
CONCLUSION………………………………………………………………………..40
REFRENCES………………………………………………………………………….41
APPENDIX………………………………………………..…………………………..42
PPR
AEIOU Canvas
Empathy Canvas
Ideation Canvas
Product Development Canvas
LIST OF FIG.
4.1 E-R DIAGRAM 24
4.2 System flow diagram 26
4.3(a) Seller use case 28
4.3(b) Admin use case 29
4.3(c) Broker use case 30
4.4(a) Data flow diagram DFD Level-0 32
4.4(b) Data flow diagram DFD level-1 33
4.5 Class diagram 35
LIST OF TABLE:
1.4.1 Plan of work-month 1 10
1.4.2 Plan of work-month 2 11
1.4.3 Plan of work 11
5.1 Data dictionary-postproperty_sell 38
5.2 Data dictionary-postproperty_rent 39
5.3 Data dictionary –postrequirenment_sell 39
Chapter-1
Introduction
Chapter 1
Introduction
1.1problem summary & Introduction
1.1.1 Problem summary
If seller sell the property but manual process very long. Seller find the broker and contract with broker. Broker is good or not. Then very difficult sell the property
Seller not direct contact with the buyer because of broker has more idea about the buyer. So must contact with buyer.
There was some problem with manual process so make a online application to solve the problem of seller.
1.1.2 Introduction
Project subject is a general term that covers multiple engineering disciplines including Electrical, Mechanical, Chemical, Computer etc. I am learning project subject with guide name Prof.Mr.parimal patel.
The designing concept is a focus on applying the 'engineering design process, in which engineers develop new products or processes with a primary emphasis on functional utility.
The design process is methodical series of steps that engineers use in creating functional products and process. Also this term use for finding the problem and implementing solution easily.
The Project usually works with a team of engineers and other designers to develop conceptual and detailed designs. We may work with industrial designers and marketers to develop the product concept and specifications, and may direct the design effort.
Design thinking has come to be defined as combining empathy for the context of a problem, creativity in the generation of insights and solutions, and rationality in analyzing and fitting various solutions to the problem context.
1.2Aim and objectives of the project..
• The system should have login box.
• The admin should have all type of property.
• The admin should maintain property.
• The system is very useful for the seller.
• The user must book their property for the sell or rent.
• The admin user can inform to the seller or agent for regarding the property and update the property.
• The broker contract with seller for the sell the property.
• Referral user gives property to the seller for the sell the property.
• Seller give review to the broker
1.3problem specification
Real estate is a mobile application. That is solve daily problem for the seller and broker. Seller and broker are register to this application. Registration is free of cost so any seller, broker Register their detail. Seller uploads their property on this application. Broker check the property if property nearest of his then broker applies for the contract. Sellers check the profile of broker. After check the profile seller give to contract with the broker.
1.4 Plan of their work
Month 1
Task Week 1 Week 2 Week 3 Week 4
PPR 1
PPR 2
PPR 3
PPR 4
Table 1.4.1
Month 2
Task Week 1 Week 2 Week 3 Week 4
PSAR 1
PSAR 2
PSAR 3
PSAR 4
PSAR
Table 1.4.2
Task Month 3 Month 4
Canvas
UML diagram
Report
Table 1.4.3
1.5Materials / Tools required.
Application technology:-
Database Design (my sql)
Form Design
Coding
Testing
Reporting Tool (Data Report)
Web server
Smart phone
Tool , Technology & Language
Technology:-
Language:-
HTML
CSS
JAVASCRIPT
Type script
Tool:-
Chapter-2
PROJECT MANAGEMENT
CHAPTER-2
PROJECT MANAGEMENT
2.1 Milestones and Deliverables
When planning for the project, a series of milestones are established. These milestones are end-point for software activity. At each milestone in our project some formal output for project generated. It may be in form of report.
Some milestones in our project are discussed as below:
-Requirements Gathering
-Requirement of various functionality for GUI
-Creating a Design, Creating a GUI Forms
– System Flow Diagram
-Add functionality Coding and Implementation
-System testing each time when I want to check error.
Deliverables:
A deliverable is a project report that is delivered to use. It is usually delivered at the end of some major phase such as specification and design.
2.2. Risk management
Risk management is concerned with identifying risks and drawing up plans to minimize their effect on a project. A risk is a probability that some adverse circumstance will occur.
Project risks affect scheduling or resources.
Product risks affect the quality or performance of the software being developed.
Business risks affect the organization developing or producing the software.
2.3. Risk identification
Identify project, product and business risks. Risk identification is the first stage of Risk Management. It is concern with discovering possible risks to the project. In principle, this should not be assessed or prioritized at this stage, although in practice risks with very minor consequences or very low probability risk are not usually considered.
1. Technology risks
2. People risks
3. Organization risks
4. Requirement risks
5. Estimation risk
2.4. Risk analysis
Assess probability and seriousness of each risk. Probability may be very low, low, moderate, high or very high. Risk effects might be catastrophic, serious, tolerable or insignificant.
2.5. Risk planning
Consider each risk and develop a strategy to manage that risk,
– Avoidance strategies:
The probability that the risk will arise is reduced.
– Minimization strategies:
The impact of the risk on the project or product will be reduced
– Contingency plans:
If the risk arises, contingency plans are plans to deal with that risk.
Chapter-3
SYSTEM ANALYSIS AND REQUIREMENT
CHAPTER- 3
SYSTEM ANALYSIS AND REQUIREMENT
3.1System Feasibility:-
1) Technical feasibility
A study of resource availability that may affect the ability to achieve an acceptable system. This evaluation determines whether the technology needed for the proposed system is available or not.
• Can the work for the project be done with current equipment existing software technology & available personal?
• Can the system be upgraded if developed?
• If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may include:
Front-end and back-end selection
An important issue for the development of a project is the selection of suitable front-end and back-end. When we decided to develop the project we went through an extensive study to determine the most suitable platform that suits the needs of the organization as well as helps in development of the project.
The aspects of our study included the following factors.
Front-end selection:
• It must have a graphical user interface(GUI) that assists employees that are not from IT background.
• capability and extensibility.
• Flexibility.
• Robustness.
• According to the organization requirement.
• Platform independent.
• Easy to debug and maintain.
• Event driven programming facility.
• Front end must support some popular back end like Ms Access.
• Asynchronous request handing
• Accessibility.
• Use command line interface(CLI).
According to the above stated features we selected VB6.0 as the front-end for developing our project.
Back-end Selection:
• Multiple user support
• Database asministrtion.
• Scalability.
• Security concerns, authentication and authorization.
• Data information.
• Symbolic phonetic.
• File manager
• Version control.
• Efficient data handling.
• Provide inherent features for security.
• Efficient data retrieval and maintenance.
• Stored procedures.
• Popularity.
• Operating System compatible.
• Easy to install.
• Various drivers must be available.
• Easy to implant with the Front-end.
According to above stated features we selected Ms-Access as the backend.
The technical feasibility is frequently the most difficult area encountered at this stage. It is essential that the process of analysis and definition be conducted in parallel with an assessment to technical feasibility. It centers on the existing computer system (hardware, software etc.) and to what extent it can support the proposed system.
2) Economical feasibility
Economic justification is generally the “Bottom Line” consideration for most systems. Economic justification includes a broad range of concerns that includes cost benefit analysis. In this we weight the cost and the benefits associated with the candidate system and if it suits the basic purpose of the organization i.e. profit making, the project is making to the analysis and design phase.
The financial and the economic questions during the preliminary investigation are verified to estimate the following:
• The cost to conduct a full system investigation.
• The cost of hardware and software for the class of application being considered.
• The benefits in the form of reduced cost.
The proposed system will give the minute information, as a result the performance is improved which in turn may be expected to provide increased profits.
This feasibility checks whether the system can be developed with the available funds. The human safety app & device does not require enormous amount of money to be developed. This can be done economically if planned judicially, so it is economically feasible.
3) Operational Feasibility
It is mainly related to human organizations and political aspects. The points to be considered are:
What changes will be brought with the system?
What organization structures are disturbed?
What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time?
The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform.
4) Schedule feasibility
Time evaluation is the most important consideration in the development of project.
The time schedule required for the developed of this project is very important since more development time effect machine time, cost and cause delay in the development of other systems.
Every softwear development work more fast and reliable complete then time management are most important.
A reliable Income Driven Lifecycle can be developed in the considerable amount of time.
3.2Requirement Of System
Project Requirements
Hardware Requirement
The selection of hardware is very important in the existence and proper working of any software. When selecting hardware, the size and requirements are also important.
Hardware Requirement
• Pentium 4 1.6 GHz.
• Internal storage 16GB
• For computer: 2GB RAM (min.) and 120 GB HDD
Software Requirement
The selection of Software is very important in the existence and proper working of any hardware. When selecting hardware or Software, the size and requirements are also important.
Development side:
• Visual Studio Code
• My SQL
User (End User):
• Internet Explorer 6.0
• mozila
3.3Functional requirements
1. registration
2. login
3. Minimum of 1 MB RAM is required for loading the application.
4. Use only for computer and laptop
3.4Non Functional requirements
• Performance – for example Response Time, Throughput, Utilization.
• Scalability
• Capacity
• Availability
• Reliability
• Maintainability
• Serviceability
• Security
• Regulatory
• Manageability
• Data Integrity
• Usability
3.5Design constraints
• GUI is only in English.
• Login and password is used for identification of user and there is no facility for guest.
Chapter-4
SYSTEM DESIGN
CHAPTER – 4
SYSTEM DESIGN
4.1E-R Diagram
• An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical representation of entities and their relationships to each other, typically used in computing in regard to the organization of data within databases or information systems.
• An entity-relationship diagram (ERD) is a data modeling technique that graphically illustrates an information system’s entities and the relationships between those entities. An ERD is a conceptual and representational model of data used to represent the entity framework infrastructure.
• An entity-relationship model is a systematic way of describing and defining a business process.
• The main components of ER models are entities and the relationships that can exist among them, and databases.
• Diagrams created to represent these entities, attributes, and relationships graphically are called entity–relationshipdiagrams.
Fig 4.1
4.2system flow diagram
• "Flow chart" redirects here. For the poem, see flow chart.
• A flowchart is a type of diagram that represents an algorithm, workflow or process, showing the steps as boxes of various kinds, and their order by connecting them with arrows. This diagrammatic representation illustrates a solution model to a given problem.
• Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.
Flowchart is in the how to work our app?
• First step is user start the app if user is new then registration else user login.
• If user want to login then user require password and email id in other case password is wrong then user not successfully login.
• After successfully login if user is seller or renter then check this activity.
• If user is broker then check the broker activity
• In seller/rent activity take photo of property and uploaded it and write information about the property.
• Broker check the property that uploaded by seller.
• If property nearest of his then he contract with the seller.
• Broker find a buyer and told detail of the property
• After find the buyer contract with seller and sold the property.
• After sold the property broker take a commission of them.
Fig 4.2
4.3use case diagram
Use case diagram:- A use case diagram is a graphic depiction of the interactions among the elements of a system.
Use case diagram is used to capture the dynamic nature of a system. It consists of use cases, actors and their relationships. Use case diagram is used at a high level design to capture the requirements of a system.
So it represents the system functionalities and their flow. Although the use case diagrams are not a good candidate for forward and reverse engineering but still they are used in a slightly differently way to model it.
Purpose of use case diagram:-
• Used to gather requirements of a system.
• Used to get an outside view of a system.
• Identify external and internal factors influencing the system.
• Show the interacting among the requirements are actors.
Seller use case:
Fig 4.3(a)
Admin use case:
Fig 4.3(b)
Broker use case:
Fig 4.3(c)
4.4 Data Flow Diagram
Data flow diagram:-
A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and outputs. As its name indicates its focus is on the flow of information, where data comes from, where it goes and how it gets stored.
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modelling its process aspects. A DFD shows what kind of information will be input to and output from the system, how the data will advance through the system, and where the data will be stored.
Purpose of data flow diagram:-
Data flow diagrams provide a graphical representation of how information moves between processes in a system.
Data flow diagrams follow a hierarchy; that is, a diagram may consist of several layers, each unique to a specific process or data function.
DFD Level 0:
Fig 4.4(a)
DFD Level 1:
Fig 4.4(b)
4.5Class diagram:
Class diagram:- The class diagram is a static diagram. It represents the static view of an application. Class diagram is not only used for visualizing, describing and documenting different aspects of a system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the constraints imposed on the system. The class diagrams are widely used in the modelling of object oriented systems because they are the only UML diagrams which can be mapped directly with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It is also known as a structural diagram.
Purpose of the class diagram:-
• Analysis and design of the static view of an application.
• Describe responsibilities of a system.
• Base for component and deployment diagrams.
• Forward and reverse engineering.
Class diagram:
Fig 4.5
Chapter 5
Data Dictionary
Chapter 5
DATA DICTIONARY
Data Dictionary:-
A data dictionary is a file or a set of files that contains a database's metadata. The data dictionary contains records about other objects in the database, such as data ownership, data relationships to other objects, and other data.
The data dictionary is a crucial component of any relational database. Ironically, because of its importance, it is invisible to most database users. Typically, only database administrators interact with the data dictionary.
Purpose of Data Dictionary diagram:-
• In order to manage the details in large-scale systems.
• To communicate a common meaning for all of the elements in the system.
• To document features of the system.
• To locate errors and omissions in the system.
Table name: postproperty_sell
Primary key: login_id
Description: to store details of the seller or agent
Sr_no Fields Data type Description
1 Property_type Varchar(50) Residential or commercial property
2 city Varchar(50) User city name
3 Locality Varchar(50) Area of user
4 Address Varchar(50) Address of user
5 Name Varchar(50) Name of the seller
6 Mobile no Int(10) Mobile no of seller
7 Login_id Int(12) Login id of the user
Table 5.1
Table name: postproperty rent
Primary key: sell id
Description: to store the detail of the person who rent their property
Sr_no Fields Data type Description
1 Property_type Varchar(50) Residential or commercial property
2 City Varchar(50) User city name
3 Locality Varchar(50) Area of user
4 Address Varchar(50) Address of the user
5 Name Varchar(20) Name of the user
6 Mobile no Int(10) Mobile no of the user
7 Bedrooms Int(3) No of bedrooms
8 Plot_area Double(50) Area of land
9 Monthly_rent Double(20) Rent per month
Table 5.2
Table name: postrequirement_sell
Primary key: login_id
Description: to store details of person for requirenment selling property
Sr_no Fields Data type Description
1 Property_type Varchar(50) Residential or commercial property
2 city Varchar(50) User city name
3 Locality Varchar(50) Area of user
4 Address Varchar(50) Address of user
5 Name Varchar(50) Name of the seller
6 Mobile no Int(10) Mobile no of seller
7 Login_id Int(12) Login id of the user
Table 5.3
Conclusion
• This mobile application is very useful for any seller and broker because of there is free of cost registration.
• Seller can upload their property any time.
• Seller deal with any broker for sell the property
• Brokers make their profile strong.
References
• www.ipindiaonline.gov.in
• www.uspto.gov.in
• www.softwaretesting.com
• www.w3school.com
• https://firebase.google.com/
APPENDIX
PPR:
DESIGN ENGINEERING CANVAS:
AEIOU SUMMARY :
EMPATHY MAPPING CANVAS
IDEATION CANVAS:
PRODUCT DEVELOPMENT CANVAS: