Chapter 7

METHODOLOGY
2.1. Introduction
This chapter mentions about methodology, necessity of methodology, software
development life cycle (SDLC), software Process model and others.

2.2. Methodology
A methodology is a system for structuring, planning and controlling the processes of
developing a system. Methodology defines the different associates use in the making
of the software.
Administrators utilize a basic procedure for organizing the conveyance of the
framework. The task is to create the real estate website by following a certain method.
There are most regular dangers and difficulties related with this kind of work. One
can expect to overcome those dangers and difficulties by simply having a procedure
set up which, when pursued, ensures achievement.
To create software, engineers need to pursue some system. In my venture I pursue
system development life cycle (SDLC) approach. Since utilizing this strategy, all the
work can be done in a well-ordered and planned way. System Development Life
Cycle (SDLC) is a procedure of seeing how a framework can be upheld if business
needs, plan the framework, creating it and conveying it to clients.

Figure 1: System Development Life Cycle (SDLC)

2.2.1. Feasibility Study
Feasibility study is a test of system proposition as per its usefulness, effect of the
association, capacity to address issues and viable utilization of assets. Amid
possibility examination for this task, following essential regions of intrigue are to be
considered. Ventures in achievability investigation:
 For a project team.
 Create system flowchart.
 Enumerate potential proposed system.
 Defined & evaluate performance and cost effective of each proposed
system. Select best proposed system.
 Prepare and report final project direct to management.

The four types of feasibilities are given below:

Technical Feasibility: A study of resources availability that may affect the ability
achieve an acceptable system. This evaluation determines whether the technology
needed for the proposal system is available or not. The technical needs of the system
may include:
Front end selection:
 Feasibility
 Robustness
 Easy to debug and maintain
 Must have a GUI that assists user who is not from IT background.
 Scalability and extensibility
I have selected HTML, CSS, JavaScript, jQuery and Bootstrap for front end
development. Back end selection:
 Efficiently data handling
 Efficient data retrieval and maintenance
 Easy to install
 Compatible
I have selected PHP and MySQL for back end development.

Economic Feasibility: Economic declaration is gradually the down line consideration

for several systems. Financial defense incorporates a wide scope of worries that
incorporates money saving advantage examination. In this we weight the expense of
advantages related with the applicant framework and on the off chance that it suits the
fundamental motivation behind the association i.e. benefit making, the task is making
to the examination and configuration stage.
The financial and 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
 The benefits in terms of reduced cost
  This feasibility detects whether the system can be created with the available
funds. The Real Estate Website does not require several amounts of money to
be developed. This can be done economically if planned specifically. So, it is
economically feasible.

Operational Feasibility: The operational feasibility is concerned with the

environment needed to successfully run the project. The system is operationally
feasibility as it is easy for the End users to operate it. It only needs the basic
information about Windows platform.
Schedule Feasibility: Time evaluation is the most necessary aspect in the
development of project. Time plan required for the improvement of this venture is
critical since greater advancement time impact machine time, cost and cause delay in
the improvement of framework.

2.2.2. Requirement Definition

At this step, we have to develop system requirements by using well known
requirement engineering tests. Requirement engineering has three parts that are:

 Requirement analysis
 Requirement specification
 Requirement validation

2.2.3. System Specification

At this segment we focus in ER-Diagram which shows the entity, attribute and
relationship with involving one to one, one to many, many to many, assign primary
keys, foreign keys and perform normalizations to reduce redundancy.

2.2.4. System Design

In this segment, system design works with two part that are overall and detailed
design. By large plan characterizes the structure of the product. Detail configuration
completes the entire program of the framework in which it characterizes the handling.
This project follows that.

2.2.5. Program Design and Coding

In this step we discuss about the programming languages that are used in this
proposed system. I used well known HTML, CSS, jQuery, Bootstrap, PHP, MySQL
etc. for this project.

2.2.6. Testing
Testing is a very crucial step in any project. It helps detect faults and bugs in the
system before publishing the project online. In this project, I have performed some
pre-planned test cases to verify the performance of our system.
2.2.7. Implementation
The project takes shape during the implementation phase. This phase involves the
construction of the actual project result. Programmers are occupied with encoding,
designers are involved in developing graphic material, contractors are building, the
actual reorganization takes place. It is during this phase that the project becomes
visible to outsiders, to whom it may appear that the project has just begun. The
implementation phase is the doing phase, and it is important to maintain the
momentum.

2.2.8. Maintenance
The Maintenance Phase occurs once the system is operational. It includes
implementation of changes that software might undergo over a period of time, or
implementation of new requirements after the software is deployed at the customer
location. The maintenance phase also includes handling the residual errors that may
exist in the software even after the testing phase. This phase also monitors system
performance, rectifies bugs and requested changes are made. This project will be
monitored all the time by the company selling properties.

2.3. Software Process Model

In the development of this project, waterfall model is used as it is a robust model and
very easy to understand. It is a sequential model where all the processes follow a
downward path like waterfall. It is also known as linear-sequential-life-cycle model.

Figure 1: Waterfall Model

 Chapter 3
Requirement Specification and Analysis
3.1. Business Process Model
Business process modeling is the analytical representation of any enterprise or
organization. This is a business process that can be changed or developed to improve
a business process. It is a graphical representation of a company’s business processes
or workflows as a means to identifying potential improvements.

3.2. General User

Figure 1: General User Process Model

3.3. Admin User

Figure 2: Admin User Process Model

3.4. Requirement Collection and Analysis

General user requirements are:
 View property
 Search property
 Find property details such as location, owner information, floor plan, videos
 Find contact information
3.5. Use Case Modeling and Description
Use case model for General user:

Figure 3: Use Case Model for General User

Admin user requirements are:

 Property entry
 Property image entry
 Edit property details
 Remove property
Use case model for Admin user:

Figure 4: Use Case Model for Admin User

 Chapter 4
System Design and Coding
4.1. Front-End Design
HTML, CSS and Bootstrap are used to create the front-end of this project. The use of
these tools made the website more responsive and smoother to navigate for the users.

4.1.1. HTML
Hypertext Markup Language (HTML) is the standard markup language for documents
designed to be displayed in a web browser. It can be assisted by technologies such
as Cascading Style Sheets (CSS) and scripting languages such as JavaScript.
Web browsers receive HTML documents from a web server or from local storage
and render the documents into multimedia web pages. HTML describes the structure
of a web page semantically and originally included cues for the appearance of the
document.
HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be embedded into
the rendered page. HTML provides a means to create structured documents by
denoting structural semantics for text such as headings, paragraphs, lists, links, quotes
and other items. []

4.1.2. CSS
Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language like HTML. CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript.
CSS is designed to enable the separation of presentation and content,
including layout, colors, and fonts. This separation can improve content accessibility,
provide more flexibility and control in the specification of presentation
characteristics, enable multiple web pages to share formatting by specifying the
relevant CSS in a separate .css file, and reduce complexity and repetition in the
structural content.
Separation of formatting and content also makes it feasible to present the same
markup page in different styles for different rendering methods, such as on-screen, in
print, by voice (via speech-based browser or screen reader), and on Braille-
based tactile devices. CSS also has rules for alternate formatting if the content is
accessed on a mobile device.
The name cascading comes from the specified priority scheme to determine which
style rule applies if more than one rule matches a particular element. This cascading
priority scheme is predictable. []
4.1.3. Bootstrap
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-
first front-end web development. It contains CSS- and (optionally) JavaScript-based
design templates for typography, forms, buttons, navigation and other interface
components. []

4.2. Back-End Design

PHP, jQuery, Ajax and MySQL are used in the development of this project. The use
of these tools made it easy to establish the logical parts of the project.

4.2.1. PHP
PHP is a general-purpose programming language originally designed for web
development. It was originally created by Rasmus Lerdorf in 1994; the PHP reference
implementation is now produced by The PHP Group. PHP originally stood
for Personal Home Page, but it now stands for the recursive initialism PHP: Hypertext
Preprocessor.
PHP code may be executed with a command line interface (CLI), embedded
into HTML code, or used in combination with various web template systems,
web content management systems, and web frameworks. PHP code is usually
processed by a PHP interpreter implemented as a module in a web server or as
a Common Gateway Interface (CGI) executable. The web server outputs the results of
the interpreted and executed PHP code, which may be any type of data, such as
generated HTML code or binary image data.

4.2.2. jQuery
jQuery is a JavaScript library designed to simplify HTML DOM tree traversal and
manipulation, as well as event handling, CSS animation, and Ajax. jQuery's syntax is
designed to make it easier to navigate a document, select DOM elements,
create animations, handle events, and develop Ajax applications. jQuery also provides
capabilities for developers to create plug-ins on top of the JavaScript library. This
enables developers to create abstractions for low-level interaction and animation,
advanced effects and high-level, theme able widgets. The modular approach to the
jQuery library allows the creation of powerful dynamic web pages and Web
applications.

4.2.3. AJAX
Ajax is a set of web development techniques using many web technologies on
the client side to create asynchronous web applications. With Ajax, web applications
can send and retrieve data from a server asynchronously (in the background) without
interfering with the display and behavior of the existing page. By decoupling the data
interchange layer from the presentation layer, Ajax allows web pages and, by
extension, web applications, to change content dynamically without the need to reload
the entire page.

4.2.4. MySQL
MySQL is the most popular database system used with PHP. Some key points are:

 MySQL is a database system that runs on a server

 MySQL is ideal for both small and large applications
 MySQL is very fast, reliable, and easy to use
 MySQL uses standard SQL
 MySQL compiles on a number of platforms
 MySQL is free to download and use

4.3. Interaction Design

The entity relationship diagram and data flow diagram along with the data dictionary
are shown in this segment.

4.3.1. Entity Relationship Diagram (ERD)

Figure 4: Entity-Relationship Diagram (ERD)

4.3.2. Data Flow Diagram
1st Level User:

Figure 4: 1st Level User Data Flow Diagram

1st Level Admin:

 Figure 4: 1st Level Admin Data Flow Diagram

4.4. Data Dictionary

Data Dictionary and Data storage is used to define a simpler software utility than a
catalogue. An index is firmly combined with the DBMS programming; it gives the
data put away in it to client and the DBA, yet it is by and large access by the different
programming modules of the DBMS, for example, DDL and DML compilers, the
inquiry streamlining agent, the exchange processor, report generators, and the
imperative master. Then again, a Data Dictionary is an information structure that
stores meta-information, i.e.; information about information. The product bundle for a
remain solitary Data Dictionary or Data Repository may collaborate with the product
modules of the DBMS; however, it is fundamentally utilized by the Team individuals,
Users and Admin of a PC framework for data asset administration. These systems are
used to maintain information on system hardware and software configuration,
documentation, application and users as well as other information 0relevant to system
administrator of the correlated system.

Admin:

Column Name Data Type Allow Nulls

id int(10) No

name varchar(20) No

email varchar(255) No

password varchar(255) No
Image:

Column Name Data Type Allow Nulls

id int(11) No

image1 text No

image2 text No

image3 text No

image4 text No

property_id int(11) No

Property:

Column Name Data Type Allow Nulls

id int(11) No

title varchar(20) No

bedroom int(11) No

hall int(11) No

kitchen int(11) No

bathroom int(11) No

balcony int(11) No

price varchar(20) No

sqr_price varchar(20) No
address text No

video text No

image text No

description varchar(300) No

location text No

property_owner varchar(20) No

property_type varchar(50) No

lot_size varchar(20) No

sold varchar(12) No

land_area varchar(20) No

date datetime No

air_conditioning int(11) No

wifi int(11) No

security int(11) No

parking int(11) No

gym int(11) No

Chapter 5
 Implementation and Testing
5.1. Home Page

i. Home
ii. About
iii. Properties
iv. Contact
v. Login (For Admin)

5.2. About Page

5.3. Properties
5.3.1. Property Details
Demo Property Title:
Description Section:

Floor Plan Section:

Details Section:

Video Section:
Location Section:

Related Properties Section:

5.4. Contact Page
5.5. Login (Admin):
Login Form:
Registration Form:

Dashboard:
Add Property Section:
Add Property Images Section:
View Property Section:
5.6. Implementation Requirements
Hardware Requirements:

 Minimum dual core processor and hardware

 2 GB of RAM or above
 1.8 GHZ processor or above
 200 MB of hard disk space

Software Requirements:

 Operating system Windows 7 or higher

 XAMPP
 Browser (Mozilla, Firefox, Opera or any other)
5.7. Testing
Test Plan:

Sl. No. Test Objectives

1. To check whether website runs or not

2. To check if the website displays all options or not

3. To check if all options are right or not

4. To check if property is created or not

5. To check if property images are added or not

6. To check if property page shows details or not

7. To check if property video is working or not

8. To check if property location is showing or not

9. To check if admin registration is working or not

10. To check if login option is working or not

11. To check if logout option is working or not

12. To check if admin panel is working or not

13. To check if sorting of properties is working or not

14. To check if recent property option is working or not

Table 5.1
Test 1:

Test Objective To check whether website runs or not

Test Data Running the website

Expected Result Website should display successfully

Test Result Website appears correctly

Conclusion Expected result matches actual result

Table 5.2

Test 2:

Test Objective To check if the website displays all options or not

Test Data Open Home page

Expected Result Home page should display all options successfully

Test Result Home page displays all options correctly

Conclusion Expected result matches actual result

Table 5.3

Test 3:

Test Objective To check if all options are right or not

Test Data Open different pages

Expected Result All pages should display successfully

Test Result All pages appear correctly

Conclusion Expected result matches actual result

Table 5.4
Test 4:

Test Objective To check if property is created or not

Test Data Open add property

Expected Result Property should be created successfully

Test Result Property is successfully created

Conclusion Expected result matches actual result

Table 5.5

Test 5:

Test Objective To check if property images are added or not

Test Data Open add property image

Expected Result Property images should be added successfully

Test Result Property images are successfully added

Conclusion Expected result matches actual result

Table 5.6

Test 6:

Test Objective To check if property page shows details or not

Test Data Select a property in properties page

Expected Result Property details should display successfully

Test Result Property details appear successfully

Conclusion Expected result matches actual result

Table 5.7
Test 7:

Test Objective To check if property page shows details or not

Test Data Select a property in properties page

Expected Result Property details should display successfully

Test Result Property details appear successfully

Conclusion Expected result matches actual result

Table 5.8

Test 8:

Test Objective To check if property location is showing or not

Test Data Select property location section

Expected Result Property location should display successfully

Test Result Property location details appear successfully

Conclusion Expected result matches actual result

Table 5.9

Test 9:

Test Objective To check if admin registration is working or not

Test Data Register using name, email, password

Expected Result Registration should be successful

Test Result Registration is successful

Conclusion Expected result matches actual result

Table 5.10
Test 10:

Test Objective To check if login option is working or not

Test Data Log in using credentials

Expected Result Login should be successful

Test Result Login is successful

Conclusion Expected result matches actual result

Table 5.11

Test 11:

Test Objective To check if logout option is working or not

Test Data Log out

Expected Result Logout should be successful

Test Result Logout is successful

Conclusion Expected result matches actual result

Table 5.12

Test 12:

Test Objective To check if admin panel is working or not

Test Data Open dashboard

Expected Result Dashboard should display successful

Test Result Dashboard appear successfully

Conclusion Expected result matches actual result

Table 5.13
Test 13:

Test Objective To check if sorting of properties is working or not

Test Data Select sort by an attribute

Expected Result Sorted properties should display successful

Test Result Sorted properties appear successfully

Conclusion Expected result matches actual result

Table 5.14

Test 14:

Test Objective To check if recent property option is working or not

Test Data Select recent properties

Expected Result Recent properties should display successful

Test Result Recent properties appear successfully

Conclusion Expected result matches actual result

Table 5.15
Test Results and Report:

Sl. No. Test Objectives Results

1. To check whether website runs or not Successful

2. To check if the website displays all options or not Successful

3. To check if all options are right or not Successful

4. To check if property is created or not Successful

5. To check if property images are added or not Successful

6. To check if property page shows details or not Successful

7. To check if property video is working or not Successful

8. To check if property location is showing or not Successful

9. To check if admin registration is working or not Successful

10. To check if login option is working or not Successful

11. To check if logout option is working or not Successful

12. To check if admin panel is working or not Successful

13. To check if sorting of properties is working or not Successful

14. To check if recent property option is working or not Successful

Table 5.16
 Chapter 6
Maintenance of the system
6.1. Introduction
Studies of maintenance phase of software development have revealed enormous costs,
generally, exceeding the development cost. In addition, in most cases the maintenance
data include the cog of rewriting, testing, debugging and integrating new ligatures into
the software. Sometimes such cost is called modification or enhancement costs and
treated as separate and distinct from maintenance caws. However, in practice they are
lumped together. In both cases, the maintenance or modification costs are strongly
related to the quality of the documentation.

6.2. Maintenance
Software Development has many phases, these stages incorporate Requirement
Engineering. Architecting, Design, Implementation, Testing. Programming
Development and Maintenance. Upkeep is the last phase of the product life cycle.
After the item has been discharged, the upkeep stage stays up with the latest with
condition changes and changing client prerequisites. In spite of the fact that product
does not product out, it needs upkeep for the accompanying reasons:

 It was delivered bugs. The bugs may be coding error, design error or analysis
error.
 The environment in which the software operates may change. For example:
The operating system may change or hardware platform may change
 The customer requirement may change. For example: The software requires
new features. Therefore, software needs maintenance.

6.3. Classification of Maintenance

 Corrective Maintenance
 Adaptive Maintenance
 Perfective Maintenance
 Preventive Maintenance

6.4. Description of Maintenance

Corrective Maintenance: Corrective maintenance can be defined as a maintenance
undertaking performed to distinguish, confine, and correct a blame so the fizzled
hardware, machine, or resource can be reestablished to an operational condition inside
the resistances or breaking points built up for in-benefit tasks.
Adaptive maintenance: Modification of a software product performed after delivery
to keep a software product usable in a changed or changing environment.
Perfective maintenance: Modification of a software product after delivery to
improve performance or maintainability.
Preventive maintenance: Modification of a software product after delivery to detect
and correct latent faults in the software product before they become effective faults.