PANCHDHARA

ACKNOWLEDGEMENT

This project report bears the imprint of many persons who are either
directly or indirectly involved in successful completion of this project.

I consider it is a privilege and an opportunity to express my deep

gratitude and indebtedness to Mr. Avinash Sharma (COSMO INFO
SOLUTIONS) Lucknow for giving me an opportunity to undertake this
project and the valuable guidance and supervision, keen interest and
constructive and valuable suggestions in solving several intricate problems
and encouragement throughout the course of this project.

This project would remain incomplete without making due

acknowledgement to all those who gave me invaluable help and cooperation
and to the hundreds of the people to whom I interacted during the project.

1
 PANCHDHARA

INDEX

S. No CONTENTS PAGE NO.

1. Acknowledgement ………………………………………...2
2. Introduction ……………………………………………. . 5

3. Objective and Scope of Project…………………………... 6-7

4. Identification of Need …………………………………... .8

5. Problem Statement
………………………………………. .9

6. System Analysis…………………………………………. .10-14

7. Software Requirement Specification ……………………… 15-27

8. Software Engineering Paradigm Applied………………………28-31

 Waterfall Model

 Prototyping Model

9. High Level Design……………………………………………..32-40

10. Database Design……………………………………………… 41-43

11. Screen Shots……………………………………………………..44-49

2
 PANCHDHARA
12. Software Cost Estimation ……………………………………....50-
51

13. Testing………………………………………………………… 52-56

System implementation………………………………………….57

System maintenance……………………………………………..58

14. Conclusion ………………………………………………………59

15. Future Scope…………………………………………………….59

16. Bibliography…………………………………………………… 59

1.INTRODUCTION

Real estate is a business, not a profession. Real estate is sometimes

inaccurately spoken of as a profession, but it is essentially a business. A
profession applies science, art or learning to the use of others, the profit to
the professor or person applying it being incidental; whereas a business is
engaged in primarily for profit, and the profit is to the one engaging in the
business.

3
 PANCHDHARA
The Real Estate EProperty Management system is an
online buying and selling of Flats and Apartments. The main idea of this
project is to computerize the process of buying and selling of properties.
The Real Estate E-Property Management system is defined as property
management system by professionals to save time and work. By using this
system buyers can get details of property in their desired location and
according to there need.

Features of the Site:

It has the features of providing all the information online (through the
internet) about flats, Rentals, and other properties

● The Panchdhara site is a special purpose web site

● This site includes the advance search of Flats and properties according to
the need

of the customer.

● It lets customers search for the categories they would be interested in

and also search for the agents for the particular query.

● The site acts as a middle-ware for the Customers and Panchdhara PVT
LTD.

4
 PANCHDHARA

Objective & Scope of the Project

Objective :

Panchdhara is a website portal own and maintain by Panchdhara PVT LTD.

This portal is designed to work like a bridge between our customer and our
partner.

We have made the Panchdhara so easy and simple.so,that the user can
easily use to fullfill his\her requirement without any difficulty and problem.
We offer wide range of services such as Flat Booking, Flat Enquiry Services,
and payment services. Our value for money services gives you fun in buying
amazing properties and make them a rejuvenating experience for you.

Specific Objective of the Site

Some of the client requirement and objectives of this site is as follows:-

● To increase the connectivity of customers to business.

● To decrease the amount of time loss during the buying of flats.

● To facilitate Customers search for the flats in the desired location.

So, these are some of the objectives which we have to accomplish .

Scope:

The main Scope of study:

● Real Estate E Property Management system project is

developed for those who are searching property according to
their criteria or near by location.
5
 PANCHDHARA
● It contain all the information of Categories by Customer.

● Seller can post ad of their property on the website with

complete details about property and contact information.

● It provide information to the customer about a particular offer.

● Buyers visit this website, search property and contact seller.

● Seller can read all these massages from their inbox and
respond to the buyer.

● This is an online web application so it is available 24×7 to both

buyers and sellers.

● This latest system computerizes the entire work of property

buying and selling

● It should maintain proper log data.

● It should have Administrator for verifying details of customers.

6
 PANCHDHARA

Identification of Need :

For identifying the need of the System, we consider the following:

The performance of the System:

The performance of the System basically depends on the System

Design, tools used in the system, coding, etc. The performance of the
system should be fast, accurate & reliable.

The Information being supplied and its form

The information being supplied should be very precise, correct and

updated. All the information regarding project should be collected from
the reliable source.

The efficiency of the existing System

The existing System is not well efficient which provokes to develop the new
System with some modifications in the older system wherever required.
If the existing System is not that much efficient, as required for
better results & performance, then it should be converted into the
new advanced & more efficient System.The new System should be
well efficient, fast as compared with the older one to show better results
than previous one.

The security of the data and software

7
 PANCHDHARA
The Security of both Data & Software is the most important and
prime thing in the System Analysis & Design. Data & Software should
be kept secured from the unreliable sources otherwise it leads to the
Piracy of both data & Software. For proper security username and
password is provided to every user of the system. They can access
the system as per their authority

Problem Definition:

The existing system in the organization is not completely

computerized. The system is not working smoothly; therefore the
organization has decided to replace it with a completely computerized
one. The problems, which the existing system faces, are:

Low Functionality :

With the existing system, the biggest problem was the low
functionality of the department. The problem faced hampered the work
of the department. For all the tasks like entering the Employee data,
attendence, worked hours, Loan and Advance, and some other useful
tasks.

Security :

Security concerns were also one of the motives of the department for
the need of the software. In the registers, the data is not secure as
anybody can tamper with the data written in the registers. Also for
the security of the registers, lots of problems arise to store the
registers in a secure place and the appointments of security
personnel can also cost a bit. Whereas in the software, just a
password makes it absolutely secure from the reach of unauthorized
users.

Data Redundancy:

8
 PANCHDHARA
In the case of manual system, the registers are maintained in which, a
lot of data is written. Therefore, there is a problem in the registers
that the same data may be repeated again and again. Against the
employee id, a lot of data will be repeated which will cause a lot of problems
at the time of query as well as at the time of preparing the reports
because a single data that will be left mistakenly will largely affect the
report and subsequently, the performance of the department. In the
software the concept of primary key and foreign key is used very efficiently,
which will prevent the redundancy of data that will prove to be very
beneficial to the organization because it will nullify the human error
completely

 Review of literature
 Procedure
 Forms

The tools of structured analysis:

 DFD
 Data Dictionary
 Decision Tree and Structured English

9
 PANCHDHARA
Initial investigation:
 Problem definition and project initiation
 Determining the requirements
 Needs identification
 Dimension of planning
 Determination of feasibility

Feasibility Analysis:
 System Performance definition
 Identification of system objectives
 Description of outputs

Preliminary Investigation:

 Evaluation of project request is major purpose of preliminary

investigation.

 It is the collecting information that helps committee members to

evaluate merits of the project request and make judgment about the
feasibility of the proposed projects.
 To answer the above questions, system analysts discuss with different
category of person to collect facts about their business and their
operations.
 When the request is made, the first activity the preliminary
investigation begins.
 Preliminary investigation has three parts-

1. Request clarification

10
 PANCHDHARA
2. Feasibility study
3. Request approval

Feasibility Study:

The feasibility report of the project holds the advantages and flexibility of
the project. This is divided into three sections:

 Economical Feasibility
 Technical Feasibility
 Operational Feasibility

1. Economical Feasibility:

A systems financial benefit must exceed the cost of developing that

system. i.e. a new system being developed should be a good investment for
the organization.

The proposed system is economically feasible because:

 The system requires very less time factors.

 The System reduce paper cost.
 The system will provide fast and efficient automated environment
instead of slow and error prone manual system, thus reducing
both time and man power spent in running the system.
 The system will have GUI interface and very less user-training is
required to learn it
 The system will provide service to view various information for
proper managerial decision making.

11
 PANCHDHARA

2. Technical Feasibility:

Technical feasibility centres around the existing computer system

((hardware and software) whether it can support the addition of proposed
system, if not, to what extent it can support and the organization’s capacity
to acquire additional components.

Our proposed system is technically feasible because –

 The hardware and software required are easy to install and handle

 The necessary hardware configuration and software platform is

already there

 The system supports interactivity with the user through GUI

Proposed system is technically feasible because of the following reasons:-

 It’s required less system resources.

 Expandability will be maintained in the new system. New modules can
be added later on the application, if required in the future.
 The application will have User-friendly Forms and Screens, all
validation checks. So the new system guarantees accuracy, reliability,
ease of access and data security.

3. Behavioural Feasibility:

Behavioural feasibility determines how much effort will go in the proposed

information system, and in educating and training the users on the new
system, along with the new ways of conducting the business. Behavioural
study strives on ensuring that the equilibrium of the organization and status
quo in the organization neither are nor disturbed and changes are readily
accepted by the users.

12
 PANCHDHARA

The proposed system is behaviourally feasible because of the following:The

users will accept it because they are already acquainted with computers.

This system is also meant for the general user. Nowadays the Internet is
almost familiar to everyone. So, it is not difficult for the user to use the
system, in fact they feel comfortable in using this system.

Most of the users are familiar with the web browser and the process of
booking the auditorium will be simplified for the users. The organization is
definitely ready to welcome the computerized system.

Software Requirement Specification

Introduction:

The project titled (panchdhara) real estate Management System is a

real estate management system which is developed for those who are
searching property according to their criteria or near by location. It
provide information to the customer about a particular offer

This is an online web application so it is available 24×7 to both

buyers and sellers.
This latest system computerizes the entire work of property buying and
selling

13
 PANCHDHARA

“Panchdhara” is a web application written for 32-bit or more windows

operating system, designed to help users buy and rent property .our
software is easy to use for both beginners and advanced users. It
features a familiar and well thought-out an attractive user interface
,combined with strong searching insertion and reporting capabilities.

Purpose:

The purpose of this application are as follows:

1. The software is for automation of library.

2. It provides following to operator.

3. Can enter details related to a particular book.

4. Can enter details related to a particular student\user.

5. Can read and write information about any member.

6. Can update, create, delete the record of membership as per

requirement and implementation plants.

Scope:

Panchdhara is basically updating the manual real estate system into

an internet based so that the users can know the details of the
property, availability of the property for renting.

The project is specifically designed for the use of real estate users.
The product will work as a complete user interface for real estate
management process .

14
 PANCHDHARA

Requirement Analysis and Planning Steps:

GANTT Chart:

A standard technique employed in recent times to keep track of a project's

progress is the Gantt chart named after the industrial engineer Henry Gantt
(1861-1919). They are easy to draw, easy to understand and readily
adaptable to other planning approaches (e.g. Pert Charts).

Each task displayed in the Gantt chart is listed below:

1.1 Identify needs and benefits

Identification of Need and Project Constraints
Meet with customers
Establish Product Statement
Milestone: Product Statement defined
Preparing Feasibility Study
Milestone: Feasibility Study Completed

15
 PANCHDHARA
1.2 Preparing Software & Hardware Requirement Study
Define Software Scope
Information Description
Functional Description
Behavioural Description
Validation Criteria
Hardware Requirement Study
Milestone: SRS Complete

1.3 Define desired output/control/input (OCI)

Define Keyboard functions
Define modes of interaction.
Define import functions
Review OCI with customer
Milestone: OCI define

1.4 Isolate software elements

Milestone: Software elements defined

Research availability of existing software
Research text editing components
Research image editing components
Research MS Word document migration components
Milestone: Reusable components identified

1.5 Database preparation

Milestone: Database preparation complete

1.6 Coding
Milestone: Coding completes

16
 PANCHDHARA

GANTT CHART:

Tabular description of Gantt chart is given below:

Jan Feb March April May

D
1
Task a 2 1 2 6 1 2 5 1 2 5
Start Finish 5 4/ 15/
Name y 5/ 4/ 4/ / 6/ 6/ / 5/ 5/ /
/ 2 5
s 1 2 2 3 3 3 4 4 4 5
1
Project 15/1/20 17/1/20 3
Definition 19 19
+/System 6
Overview 18/1/20 23/1/20
and 19 19
Analysis
Requirem 24/1/20 6/2/201 1
ent 19 9 4
Gatherin

17
 PANCHDHARA
g and
Software
Requirem
ent
Specifica
tion
(SRS)
Tools and 5
7/2/201 11/2/20
Technolo
9 19
gy
Data 1
12/2/20 21/2/20
Flow 0
19 19
Diagrams
Designin 22/2/20 13/3/20 2
g 19 19 0
14/3/20 24/4/20 4
Coding
19 19 2
25/4/20 28/4/20 3
Rework
19 19
Final 29/4/20 1/5/201 2
Report 19 9

PERT Chart:

A PERT chart is a project management tool used to schedule, organize, and

coordinate tasks within a project. PERT (stands for Program Evaluation
Review Technique), a methodology developed by the U.S. Navy in the 1950s
to manage the Polaris submarine missile program. A PERT chart presents a
graphic illustration of a project as a network diagram consisting of
numbered nodes (either circles or rectangles) representing events, or
milestones in the project linked by labelled vectors (directional lines)

18
 PANCHDHARA
representing tasks in the project. The direction of the arrows on the lines
indicates the sequence of tasks.

A PERT chart presents a graphic illustration of a project as a network

diagram consisting of numbered nodes (either circles or rectangles)
representing events, or milestones in the project linked.

The PERT chart is sometimes preferred over the Gantt chart, another

popular project management charting method, because it clearly illustrates
task dependencies. On the other hand, the PERT chart can be much more
difficult to interpret, especially on complex projects. Frequently, project
managers use both techniques.

System Feature:

Description and Priority:

The product offers the following Key features:

 Web based Application

 Client-server architecture

 Supports for both intranet and internet operations

 Highly scalable and extendible

Functional Requirements:

General Constraints:

19
 PANCHDHARA
There are some of the general constraints that is pre-conditions, post-
conditions and business rules which we need to maintain in our system they
are listed below

Pre-Conditions

• The user has to register before writing the exam.

• User has to select the exam from the given list of exams by the
administrator.

Post-Conditions

• The user should finish the exam within the time specified by the
administrator.
• Results should be displayed to the user immediately after finishing the
exam.
Business Rules

• The non-registered users cannot take up the exams.

• The user should finish the exam within the time limit

External Interface Requirements:

User Interface:
The user interface is an important part of this software and will make the
software very user friendly.

• Input Screen: The input screen should have some icons that will be
used for opening the browse window and importing the input files. It
should also show the files that are being imported. This screen should
also have a time line over which the imported files can be placed and
the duration of the files in the presentation can be adjusted

20
 PANCHDHARA

• Preview Screen: The preview screen should be able to show the

presentation slides, video and the table of contents as a complete
multimedia presentation.
• Publish Screen: The publish screen must get the input from the user
about where to store the presentation. It should show some animation
representing the status of the publishing wizard.

 Hardware Interface:

It is recommended that the minimum configuration for clients is as

appended below:-

 Processor : Pentium Series (1.6GHz or above)

 RAM : 1 GB
 Hard Disk : With 40GB or above

 Monitor : SVGA Monitor

 CD Drive : 52X or above

 Keyboard : Normal/Multimedia

 Mouse : Normal

 Software Interface:
21
 PANCHDHARA
 Front end : PHP 5.5
 Back end : MYSQL 5.6
 Tools : Net Beans8.0.1,xamp
 Languages : PHP,CSS ,HTML ,Java SCRIPT
 Operating System : Windows XP ,7,8
 Web Server : Apache

 Communication Interface:

 Client on Internet will be using HTTP protocol.

 Client on Intranet will be using TCP/IP protocol.
 A Web Browser such as IE 5.0 or equivalent.

Non-Functional Requirements:

Performance Requirements:
To achieve good performance the following requirements must be
satisfied

 Scalability: The ease with which a system or component can be

modified to fit the problem area.

 Portability: The ease with which a system or component can be

transferred from one hardware or software environment to another.

 Security: It is the ideal state where all information can be

communicated across the internet / company secure from
unauthorized persons being able to read it and/or manipulate it. It is

22
 PANCHDHARA
also the process of preventing and detecting unauthorized use of
one’s computer.

 Maintainability: The ease with which a software system or

component can be modified to correct faults,
improve performance, or other attributes, or adapt to a changed
environment.

 Reliability: The ability of a system or component to perform its

required functions under stated conditions for a specified
period of time.

 Reusability: The degree to which a software module or other work

product can be used in more than one computing program or software
system.

Safety Requirements:
Database is an important aspect of any system. So it is required to
take backup of the database. Special exception handling mechanism
should be in place to avoid system error.
In case scenarios where data integrity can be compromised,
measures should be taken to ensure that all changes are made
before system is shutdown. The user must have a registered
account to use all facility of the web application

Security Requirements:
• Only registered students are able to access the test.
• The test can be made available on specific date and
time.
• The no. of times student access test can be set.
• The login and logoff time per student is available
Software Quality Attribute:

23
 PANCHDHARA
1. Functionality: The capability to provide functions which meet stated
and implied needs when the software is used.

2. Reliability: The capabilities to be maintain a specified level of

performance.

3. Usability: The capability to be understood, learned and used.

4. Efficiency: The capability to provide appropriate performance

relative to the amount of resources used.

5. Maintainability: The capability to modified for the purpose of

making corrections and improvement

6. Portability: The capability to adopted for different specified

environments without applying actions or means other than those
provided for this purpose in the product

Other Requirements:

Appendix A: Glossary :
• HTML: HypertextMarku Language is a markup language used
to design static web pages.
• MySQL: MySQL Database is the database management system
that delivers a flexible and cost effective database platform to
build robust on demand business applications.
• HTTP: Hypertext Transfer Protocol is a transaction oriented
client/server protocol between web browser & a Web Server.
• HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL
(secure socket layer)
• TCP/IP: Transmission Control Protocol/Internet Protocol, the
suite of communication protocols used to connect hosts on the
Internet. TCP/IP uses several protocols, the two main ones being
TCP and IP.

24
 PANCHDHARA
Appendix B: Analysis Model:

25
 PANCHDHARA
2. Software Engineering Paradigm Applied

Software engineering is a layered technology. The foundation for software

engineering is the process layer. Software engineering processes the glue
that holds the technology layers together and enables ratios and timely
development of computer software. Process defines a framework for a set of
key process areas that must be established for effective delivery of software
engineering technology.

Software engineering methods provide the technical how-to’s for building

software. Methods encompass a broad array of tasks that include
requirements analysis, design, program construction, testing and support.
Software engineering tools provide automated or semi-automated support
for the process and the methods. When tools are integrated so that
information created by one tool can be used by another tool, a system for
the support of software development, called computer software engineering
is established.

The following paradigms are available:

1. The Waterfall Model

2. The Prototyping Model

The Waterfall Model:

• The waterfall Model originally proposed by bohem is a

software process models that tuples.
• The iterative nature of prototyping with the controlled and
systematic aspects of the linear.
• Sequential model.
• Using the waterfall model website is developed in a series
of incremental releases.

26
 PANCHDHARA
This model is also known as Linear Sequential Model. In this model the
software development is carried out in six phases. This classical model
suggests well-defined activities to be carried out in every phase of
development. This method is called waterfall model because it is similar to a
waterfall and all the activities are done sequentially.

 Feasibility Study
 Requirement Analysis
 Design
 Coding
 Testing
 Implementation & Maintenance

Feasibility
Study
Requiremen
t Analysis
Design

Coding

Testing
Implementation
Fig.: The Waterfall & Maintenance

Model

The Prototyping Model:

The Prototyping model is similar to the waterfall model with some

differences. It has been noticed by several system analysts that most of the
time, the customer is not sure about the functionality he requires in the
software product. In such cases, it is not considered a good practice to
develop a product as only perceived by the software development team.

27
 PANCHDHARA
Before preparing the SRS documents, the customers must also understand
the functionality of the product. Under such circumstances, the prototyping
model for software development is used. In this approach a quick design of
the product is prepared and shown to the customer. Prototype is a toy
representation of the software modified. As per the suggestion of the
customer, the prototype is rebuilt and modified. Once the customer accepts
the design the design phase according to the waterfall model start

The Project is based on Prototype Model as

The basic idea of prototyping is that instead of freezing the requirements

before any design or coding can proceed, a throwaway prototype is build to
help understand the requirements. This prototype is developed based on the
prototype obviously undergoes design, coding & testing, but each of these
phases is not done very formally or thoroughly. By using this prototype the
client can get an actual feel of the system, because the interactions with the
prototype can enable the client to better understand the requirements of
the desired system.

Design Code Test

In this Project used Prototype Model because the system is

complicated and large and there is no existing system (computerized)
prototyping is an attractive idea. In this situation letting the client test the
prototype provides the variable inputs, which help in determining the

28
 PANCHDHARA
requirements of the system. It is also an effective method of demonstrating
the feasibility of a certain approach.

Some Advantages of Prototype model:

 Reduces development time.

 Reduces development costs.

 Requires user involvement.

 Developers receive quantifiable user feedback.

 Facilitates system implementation since users knows what to expect.

 Results in higher user satisfaction.

 Exposes developers to potential future system enhancements.

Use case diagram:

29
 PANCHDHARA

USER
REGISTRATION

LOGIN

BOOKING

USER

QUERIES

FEEDBACK &
RATING

30
 PANCHDHARA

VIEW
REGISTRATION

LOGIN
ADMIN

VIEW BOOKING

VIEW
QUERIES

FEEDBACK &
RATING

31
 PANCHDHARA

Data Flow
Diagrams
Context/Zero Level DFD:

Responce
Return

Admin user

Panchdhara
(real estate)
Request Request

32
PANCHDHARA

19

33
 PANCHDHARA
2. E-R Diagram:

Price

[Type a
quote

34
 PANCHDHARA

UML(Unified
Modeling
Language)

Class Diagram:

A Class is a category or group of things that has similar attributes and

common behavior. A Rectangle is the icon that represents the class it is

35
 PANCHDHARA
divided into three areas. The upper most area contains the name, the
middle; area contains the attributes and the lowest areas show the
operations. Class diagrams provides the representation that developers
work from. Class diagrams help on the analysis side, too.

Class Diagram:
tblAvailableblock
tblReg tblBlock category
Id
Id Blockid
Id
RegNo Block no
Block name
Name Isbooked
Crdt
ContactNo Crdt
Updt
Email Updt
IsActive
Password IsActive
tblProperty
Isverified
Updt Id
Crdt tblContactus tblReplycontact Address
IsActive Price
Id Id
Bedroom no
Name Contactid
Bathroom no
Contact Reply
Area
Message Crdt
Image
Updt Updt
tblProfile Flat id
Crdt Isactive
isactive
Id
RegId
Picture
tblFeedback
Gender
State Id
City Name
tblFeedback reply
Add Email
Pin Contactno
Id
DOB Message
Rply id
Rating
Rply
updt
updt

Object Diagram

An object diagram is a graph of instances, includingobjects and data

values. A static object diagram is an instance of a class diagram; it shows
a snapshot of the detailed state of a system at a point in time. The use
of object diagrams is fairly limited, namely to show examples of data
structure

36
 PANCHDHARA

Object Diagram:
tblAvailableblock
tblReg tblBlock category
Id=011
Id=11 Blockid=0011
Id=01
RegNo=101 Block no=01
Block name=gomti
Name=ethan Isbooked=0
Crdt=21/04/2019
ContactNo=*** Crdt=21/04/2019
Updt=22/04/2019
Email=xyz@gmail.com Updt=22/04/2019
IsActive=1
Password=123 IsActive=1
tblProperty
Isverified=1
Updt=22/04/2019 Id=0111
Crdt=21/04/2019 tblContactus tblReplycontact Address=xyz,lko
IsActive=1 Price=11402154
Id=111 Id=1111
Bedroom no=2
Name=xyz Contactid=111
Bathroom no=1
Contact=*** Reply=xyz
Area=12000sqm
Message=xyz Crdt=21/05/2019
Image=xyz.jpg
Updt=22/04/2019 Updt=22/05/2019
tblProfile Flat id=01111
Crdt=21/04/2019 Isactive=1
Isactive=1
Id=11
RegId=101
Picture=.jpg
tblFeedback
Gender=m
State=xyz Id=11
City=xyz Name=ethan tblFeedback reply
Add=xyz Email=xyz@gmail.com
Pin=226016 Contactno=***
Id=11
DOB=21/09/2018 Message=xyz
Rply id=11
Rating=***
Rply=abcabcabc
Updt=22/04/2019
Updt=23/04/2019

37
 PANCHDHARA

Database
Design

38
 PANCHDHARA

Table1: Admin login

Column Name Length Data type Constraints

Username 20 Varchar Primary key
Password 45 Varchar Not null

Table2: Add Property

Column Name Length Data type Constraints

property_name 30 Varchar Not null
Ven_id 10 Varchar Primary key
Ven_name 45 Varchar Not null
Place 45 Varchar Not null
Country 45 Varchar Not null
Address 100 Varchar Not null
Phn 20 Varchar Not null
Description 40 Varchar Not null

Table8: Member Login

Column Name Length Data type Constraints

username 45 Varchar Not null
Password 45 Varchar Not null

Table9: Member Registration

Column Name Length Data type Constraints

First name 45 Varchar Not null
Last name 40 Varchar Not null
username 100 varchar Not null
Email 100 Email Not null
Password 20 Varchar Not null
Rpassword 20 Varchar Not null
File 150 Varchar Not null

Table12: Add Realtor

39
 PANCHDHARA
Column Name Length Data type Constraints
name 20 varchar Primary key
Photo BLOB Not null
Description 50 Varchar Not null
phone 10 INT Not null
E-mail 40 Email Not null

Screen
Shots
40
PANCHDHARA

41
PANCHDHARA

42
PANCHDHARA

43
PANCHDHARA

44
PANCHDHARA

45
PANCHDHARA

46
 PANCHDHARA

Software Cost Estimation

Line of Code:

Program length (LOC) can be used to predict program characteristics e.g.

person-month effort and
ease of maintenance.
The measure was first proposed when programs were typed on cardswith
one line per card.

Advantages:
 Simple to measure
Disadvantages:
 Defined on code: it cannot measure the size of specification
 Based on one specific view of size: length. What about complexity and
functionality !!
 Bad s/w may yield more LOC
 Language dependent

Function Point &LOC:

FPscan be used to estimate LOC depending on the average number of LOC

per FP for a given language
 LOC = AVC * number of function points
AVC is a language-dependent factor varying from approximately 300 for
assemble language to 12-40 for a 4GL .

47
 PANCHDHARA

Testing:

INTRODUCTION TO SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of
components, sub-assemblies, assemblies and/or a finished product It is the process of exercising
software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific testing
requirement.

TYPES OF TESTING:

Unit testing:
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately
to the documented specifications and contains clearly defined inputs and expected results.

Integration testing:

48
 PANCHDHARA
Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components were
individually satisfaction, as shown by successfully unit testing, the combination of components is
correct and consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.

Functional Test:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions, or

special test cases. In addition, systematic coverage pertaining to identify Business process flows;
data fields, predefined processes, and successive processes must be considered for testing.
Before functional testing is complete, additional tests are identified and the effective value of
current tests is determined.

System Test:
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

49
 PANCHDHARA

White Box Testing:

White Box Testing is a testing in which in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is purpose. It is used
to test areas that cannot be reached from a black box level.

Black Box Testing:

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box .you cannot “see” into it. The test provides inputs and
responds to outputs without considering how the software works.

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the software
lifecycle, although it is not uncommon for coding and unit testing to be conducted as two
distinct phases.

Test strategy and approach:

Field testing will be performed manually and functional tests will be written in detail.

Test objectives:

 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested:

50
 PANCHDHARA
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

Integration Testing:
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.

The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.

Test Results:

All the test cases mentioned above passed successfully. No defects encountered.

Acceptance Testing:
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results:

All the test cases mentioned above passed successfully. No defects encountered.

Test Cases:

Project History
Project ID Panchdhara
Test Case History
Created By Vishal chaudhary Date Created 25-04- 2019
By
Reviewed Ms. Avinash Sharma Date Reviewed 28-04-2019

51
 PANCHDHARA
By By
Approved Kumar Raghav Date Last 30-04-2019
By Updated
Test Vishal chaudhary
Executed By

SYSTEM IMPLEMENTATION

The purpose of System Implementation can be summarized as follows:

making the new system available to a prepared set of users (the
deployment), and positioning on-going support and maintenance of the
system within the Performing Organization (the transition). At a finer level
of detail, deploying the system consists of executing all steps necessary to
educate the Consumers on the use of the new system, placing the newly
developed system into production, confirming that all data required at the
start of operations is available and accurate, and validating that business
functions that interact with the system are functioning properly.
Transitioning the system support responsibilities involves changing from a
system development to a system support and maintenance mode of
operation, with ownership of the new system moving from the Project Team
to the Performing Organization.
Once the design model of “PANCHDHARA ” is created, it is implemented
as a prototype, examined by end-users and modified by developers, i.e. us,

52
 PANCHDHARA
based on their comments. To accommodate this iterative design approach, a
broad class of interface design and prototyping tools has evolved.
This phase consists of the following processes:
Prepare for System Implementation, where all steps needed in advance
of actually deploying the application are performed, including preparation
of both the production environment and the Consumer communities.
Deploy System, where the full deployment plan, initially developed during
System Design and evolved throughout subsequent lifecycle phases, is
executed and validated._
Transition to Performing Organization, where responsibility for and
ownership ofthe application are transitioned from the Project Team to the
unit in the Performing Organization that will provide system support and
maintenance.

53
 PANCHDHARA
SYSTEM MAINTENANCE

Software once designed & developed needs to be maintained till end of

software / system life. When the system is fully implemented, analyst must
take precautions to ensure that the need for maintenance is controlled
through design and testing and the ability to perform it is provided through
proper design practices.
Maintenance is necessary to eliminate errors in the working system during
its working life and to tune the system to any variations in its working
environment. Often small system deficiencies are found as a system is
brought into operations and changes are made to remove them. System
planners must always plan for resource availability to carry out these
maintenance functions. The importance of maintenance is to bring the new
system to standards.
The term “Software Maintenance” is commonly used to refer to the
modifications thatare made to a software system in its initial release.
Maintenance requirements for information systems
(a) From 60% to 90% of the overall cost of software during the life of a
system is spend on maintenance.
(b) Often maintenance is not done very efficiently.
(c) Software demand is growing at a faster rate than supply. Many
programmers spending more time on systems maintenance than on new
software development.
The keys to reduce the need of maintenance, while making it
possible to do essential tasks more efficiently, are as follows:
 More accurately defining the user’s requirements during systems
development.
 Making better Systems documentation.
 Using proper methods of designing processing logic and communicating
it to project team members.

54
 PANCHDHARA
 Utilizing theexisting tools and techniques in an effective way.

Conclusion:

The objective of the Real Estate management system is to handle

the activity of searching and booking of the properties. The
software keeps track of all the information about the properties
available in areas, their cost, their complete details and total
number of block available in the area. The user will find it easy
in this automated system rather than using the manual writing
system. The system contains a database where all the
information will be stored safely. The system is user-friendly and
error free.

Future Scope
This project is handles the booking and renting of flats and
properties and in future the need of flats will increase which this
project can handle very efficiently without any error. Its simple
and sorted UI will help first time user to work on it without any
difficulty.So,we can assume that in the coming year the use of
the site will increase to a great extend.

10. BIBLOGRAPHY:

55
 PANCHDHARA

1. Python-W3 schools.com
2. Python- geeksofgeeks.com
3. Python:The Complete Reference- Martin Brown
4. MySql for Python

56