A

Project Report
On

(For Software)

DEVELOPED BY

Parmar Zarna D. -- 72
Nayak Rashmi M. -- 73

B.E 7th SEMESTER

Nov/Dec, 2010

SUBMITTED TO

Department of Computer Engineering,

L.C. Institute of Technology,

Bhandu–384120

1
 L.C. INSTITUTE OF TECHNOLGY
BHANDU-384 120

CERTIFICATE
TO WHOM SO EVER IT MAY CONCERN

This is to certify that student(s) of B.E. Semester VII (Computer

Engineering) have completed their one full semester project work titled
“REAL ESTATE” satisfactorily in partial fulfillment of requirement of
Bachelor of Engineering degree of Computer Engineering of
Hemchandracharya North Gujarat University, Patan, in the year 2006.

(Mr.Kalpesh Patel) (Asst.Prof. S.J.Soni)

Project Guide H.O.D. (CE)
LCIT, Bhandu. LCIT, Bhandu.
Date:

ACKNOWLEDGEMENT
2
 The feeling of gratefulness to any one’s help directly arises from the bottom of
heart. A small but an important and timely help can prove to be a milestone in one’s
life.

Even human being has such kind of experience. Being human being, we also
have, the same feeling of gratefulness of today we have achieved an important
milestone in my life.

This project is dedicated to all the people, whom we met, took guidance, talked,
interviewed and learned something from them. At this occasion we sincerely thank all
of them while submitting this project report.

We would like to heartily thank Mr.Kalpesh Patel who had provided us

necessary information and guidance for the success of this project.

Last, we would like to extend thanks to all our classmates also. On this
occasion we would like to thank Asst.Prof.S.J.Soni (HOD, Computer Department)
without whom this would have not been possible. We are thankful to him for giving
time-to-time and valuable guidance during the project period and giving us guidance in
taking our curriculum decision and choosing, initiating and getting on with the project.

We always have felt the invisible help from the almighty, without the blessing
almighty, we could not have succeeded.

3
 INDEX

1. Project Overview…………………………………………………………………… 5

2. Project Profile……………………………………………………………………… 6

3. Project Plan………………………………………………………………………… 7

3.1 List of major activities, estimated time duration etc.

4. Process Model……………………………………………………………………… 8

5. Requirement Analysis……………………………………………………………... 10

5.1 Feasibility study.

5.2 Basic hardware and software requirements.
5.3 Functional Requirements.
5.3 DFD- Data Flow Diagrams.
5.4 ERD- Entity Relationship Diagram.

6. Design………………………………………………………………………………... 19
7. Coding……………………………………………………………………………….. 21

7.1 Coding scheme, language, tools etc.

8. Functionality of project\software\system…………………………………….. 24

9. User manual………………………………………………………………………... 33

10. Testing……………………………………………………………………………… 34

11. Dictionary…………………………………………………………………………. 39

12. Annexure………………………………………………………………………….. 41

12.1 References and Bibliography.

PROJECT OVERVIEW 4
 Real Estate is basically a website on Internet that provides the Information about
the Properties like Home, Hotel, Appartment, Land. The main parts of this website is
user (Builder, Buyer, Individual).

 USER (BUILDER,BUYER &INDIVIDUAL ETC..):

These are the many users of this website who find Propertis all over the
Gujarat. This website is for the public use for the organization or people.
The user wants to search (find) a properties by city, price range, property type.
This result is view by the user in the website. And the user also find a doctor any of
the particular field.

5
 PROJECT PROFILE

Project Title: REAL ESTATE

Institution: L.C. Institute of Technology,

Mehsana, Bhandu.
[North Gujarat University]

Front End Tool: ASP.NET (C#)

Back End Tool: Oledb

Documentation Tool: Microsoft Word

Operating System: Microsoft XP

Submitted By: Parmar Zarna - 72

Nayak Rashmi - 73

Submitted To: Computer Department,

L. C. Institute of Technology,
Bhandu. - 384120

6
 PROJECT PLAN

List of major activities, estimated time duration

etc.

MAJOR ACTIVITYES:
A major activity of project is specified bellow according to the following steps:

 First of all the user have to fill regression form. And also fill the details of
properties & details.
 After gaining access in any time he/she wants to update the information than
they will do.
 If any user wants to find another users , find properties (By specific area) than
they can do.

ESTIMATED TIME DURATION:

For the different tasks it required as per the following time duration:

 For the tasks identify need and benefits it required two days to complete.
 For the tasks design a system it required five days to complete.
 For the tasks design the functions and behaviors it required six days to
complete.
 For the tasks system design and coding it required five days to complete.
 For the tasks connectivity and checking project it required six days to complete.
 For the tasks run a system it required two days to complete.
In this way project required to nearest to one month.

PROCESS MODEL 7
 PROCESS MODEL

 LINEAR SEQUENTIAL MODEL

The Linear Sequential Model for software engineering is illustrates in figure.

This model is sometimes called the "classic life cycle " or the "waterfall model," the
linear sequential model suggests a systematic, sequential approach to software
development that begin at the system level and progresses through analysis, design,
coding, testing and maintenances. Modeled after the conventional engineering cycle,
the linear sequential model encompasses the following activities:

System/Information
Engineering

Analysis Design Code Test

 System/Information Engineering and Modeling:

Software is always part of a larger system (or business), work begins by
establishing requirements for all system elements and then allocating some subset of
these requirements to software. This system view is essential when software must
interface with other elements such as hardware, people, and analysis encompasses
requirements gathering at the system level with a small amount of top-level analysis

8
and design. Information engineering encompasses requirements gathering at the
strategic business level and at the business area level.

 Software Requirements Analysis:

The requirements gathering process is intensified and focused
specifically on software. To understand the nature if the program to be built, the
software engineer ("analyst") must understand the information domain for the
software, as well as required function, behavior, Performance and interfacing.
Requirements for both the system and the software are documented and reviewed
with the customer.

 Design:
Software design is actually a multi step process that focuses on four
distinct attributes of a program: data structure, software architecture, interface
representations, and procedural (algorithm) detail. The design process translates
requirement into representation of the software that can be assessed for quality before
code generation begins. Link requirements, the design is documented and becomes
part of the software configuration.

 Code generator:
The design must be translated into a machine-readable form. The code
generation step performs this task. if design is performed in a detailed manner, code
generation can be accomplished mechanistically.

 Testing:
Once code has been generated, program testing begins. The testing
process focuses on the logical internals of the software, assuming that all statements
have been tested, and on the functional externals that is, conducting tests to uncover
errors and ensure that defined input will produce actual results that agree with
required results.

9
  Maintenance:
Software will undoubtedly undergo change after it is delivered to the
customer (a possible exception is embedded software). Change will occur because
errors have been encountered, because the software must be adapted to
accommodate changes in its external environment (e.g., a change required because
of a new operating system or peripheral device), or because the customer requires
functional or performance enhancements. Software maintenance reapplies each of
the preceding phases to an existing program rather than a new one. The linear
sequential model is the oldest and the most widely used paradigm for software
engineering. However, criticism of the paradigm has caused even active supporters to
question its efficacy.

10
 REQUIREMENT ANALYSIS

 Feasibility study.

 Basic hardware and software requirements.

 Functional Requirements.

 DFD- Data Flow Diagram.

 ERD- Entity Relationship Diagram.

11
 FEASIBILITY STUDY

Software feasibility has Four Dimensions

Technology feasibility:

The software if technologically feasible as new technologies arrives the

technology that is used for the website development will not be outdated.

Finance feasibility:

Software can be completed at the cost the software organization, its clients, or
the market can afford.

Time feasibility:

The project can be completed in the give time. Project time to market beat the
competition.

Resources feasibility:

Organization has enough resources to Succeed.

12
 BASIC HARDWARE & SOFTWARE
REQUIREMENT

 Hardware Requirements :

The configuration of hardware for education of the project is as mention below.

Pentium IV Processor (Minimum Pentium II-450Mhz (Pentium III-650Mhz
recommended))
 color Monitor
 104 Keyboards
 500MB free on the drive where the OS is installed (usually C:\) and
 2.5 Gigs free on the installation drive (where VS.NET will be installed).
 RAM : 96 MB (128 MB recommended) for Windows 2000 Professional,
and
192MB (256 MB recommended) for Windows XP Professional.

 Software Requirements :

The necessary Operating system used to execute the project.

 Windows 2000 (Server or Professional), Windows XP, or Windows NT

4.0 Server.

The necessary Software used in developing the project is as mentioned

below.

 Front End Tool: - ASP .Net

 Back End Tool: - Oledb database, Code behind C#. Net
13
 FUNCTIONAL REQUIREMENTS.

 Input:
 The user Details.
 The Property Details.

 Process:
 User insert the details, And also store in data base as par needed.
 User also select any city (To find properties by some specialty )
 User wants to find Properties than he / she can do this operation.

 Output:
 After the above process, the user getting the information using
his/her requirement.

14
 DATA FLOW DIAGRAM (DFD)

The data flow diagram enables the software engineer to develop models of the
information domain and functional domain at the same time. As the DFD is refined into
greater levels of detail, the analyst performs an implicit functional decomposition of the
system. At the same time, the DFD refinement results in a corresponding refinement
of data as it moves through the processes that embody the application,

A few simple guidelines can aid immeasurably during derivation of a data flow
diagram:
(1) the level 0 or context level data flow diagram should depict the software/system as
a single bubble.
(2) primary input and output should be carefully noted.
(3) refinement should begin by isolating candidate processes, data objects and data
stores to defined at the next level.
(4) All the arrows and bubbles should be labeled with meaningful names.
(5) Information flow continuity must be maintained from level to level.
(6) One bubble at a time should be refined.

There is a natural tendency to overcomplicate the data flow diagram, This

occurs when the analyst attempt to show too much detail too early or represents
procedural aspects of the software in lieu of information flow.

15
LEVEL-0:-

System

User account Maintenance/change

password/change access password

Maintain album
Upload
privacy/Give
User Adverises/feedba Search User
Access Pernitions
ck/change
Estates
Usertype
/change access
password

16
 Level-1:-

Access
Privacy the
system

Put Advertisement

Maintain access
password Log in with login id or with
access password
Username, password, new psw, confirm psw
System User

Enter the username and password

Check the
username
User
And
Type,User ID
Password

Change
Login
Login Retrieve user the
information Change UserType
UserType
Information Uploading

Enter the Username, UserType

username and
password Login

Advertise Use the access password

Propertie Access the Registereduser Real
s system Estate
System

17
 ERD-Entity Relationship Diagram.

name Place
User
address Type Pries
ID

emai Propert
phone l y Type

UserTyp
e

Profile Real User

Estat
e
Syste
m

RE Properties Real
system Estate
system

18

Place category
 Descriptio
Type n

DESIGN

INTRODUCTION TO SYSTEM DESIGN

.
 Definition :
System design is a process of preparing of input process and the result
detail procedure. After gathering the facts through various techniques such as
questionnaires, interviews, analysis of documents and observation into all existing
system and recording these collected information in the proper format using DFD’s
decision table, flowcharts etc. The next step is to define the system in terms of user
requirements. This is referred to as logical design and then converted into physical
design.

 Logical design :
When the system analyst prepares the logical design of system, which
contains the details of the users requirements. The information flowing in and out of
the system and the required data resources. The logical design contains the following
information:
Specification about input data. The source of input data the document from
which it will be derived and the process of data preparation from the documents.
Specification about output reports the data contains in the reports, its formats and
frequency of generation of report.
Sepcification about data to be stored permanently in the system and its
format. Specifications about edit correction, backup procedures and data security
arrangement. Specification about implementation plans. Brief information about
current logical and physical system. brief information about the benefit of the new
system, its constraints and required resources to implement it.

19
  Physical design of system
Once the agreements are reached between the user and about the logical
design of the system, the system analysis can start with the physical design of the
system.Physical design of the system means the designing the computer part of the
information system. The physical design of the computer system involves the following
aspects.

 Stored data
Physical storage of data is on the secondary storage device like floppy disk,
hard disk and Magnetic tapes. The data is stored in the database. A database is a
collection of tables. Table is collection data items organized in the terms of collection
of rows. Table contains the stable information about the entities. When row is added
or deleted from a table, table affected, is said to be updating of table.
In online transaction processing system, the table is updated as soon as
transaction occurs but in a batch processing system table will be updated after
transaction performed.
Input and output
The major step is the system design is the preparation of input data format
and the design of output repots. The input design is the process of designing the input
data in a computer-based format.
While designing the input, try to produce the cost effective method and to
make sure that it is acceptable to the user and also the accuracy of data is to be
achieved because if the input data entered is not correct, the output will be not correct.
Computer procedure design
When the management accepts the input/output design proposal, the next
step to follow is the design of computer procedures. The analyst has to specify to
programmer, the input/output and processing details that are needed to the design the
specifying the computer procedures. These tools are flowcharts, data flow diagrams
etc.

20
 CODING

Coding schemes,languages,tools etc

 About Microsoft .NET:

Introduction to .NET and ASP.NET:

It’s being touted as theQ “next big thing.” Microsoft has invested millions in
marketing, advertising, and development to produce what it feels is the foundation of
the future Internet. It’s a corporate initiative, the strategy of which was deemed so
important, that Bill Gates himself, Microsoft Chairman and CEO, decided to oversee
personally its development.
It is a technology that Microsoft claims will reinvent the way companies carries
out business globally for years to come. In his opening speech at the Professional
Developers’ Conference (PDC) held in Orlando Florida in July of 2000, Gates stated
that a transition of this magnitude only comes around once every five to six years.
What is this show-stopping technology? It’s .NET.

What is .NET?
. NET is the result of a complete makeover of Microsoft’s software development
products, and forms part of the company’s new strategy for delivering software’s a
service. The key features that .NET offers include:

.NET Platform:
The .NET platform includes the .NET Framework and tools to build and operate
services, clients, and so on. ASP.NET, the focus of this book, is a part of the .NET
Framework.

21
.NET Products:
.NET products currently include MSN.NET, Office. NET, Visual Studio. NET,
and Windows Server 2003, originally known as Windows .NET Server. This suite of
extensively revised systems provides developers. With a friendly, usable environment
in which they may create applications.

With a range of programming languages including C++. NET, Visual Basic.

NET, ASP.NET, and C#. Because all these products are built on top of .NET, they all
share key components, and underneath their basic syntaxes. You’ll find they have
much in common.

.NET My Services
An initiative formerly known as "Hailstorm", .NET MY Services is a set of XML
Web Services1 currently being provided by a host of Partners, developers, and
organizations that are hoping to build corporate services and applications for devices
and applications, as well as the Internet.

The collection of My Services currently extends to passport, messenger,

contacts, email, calendars, profiles, lists, wallets, location, document stores,
application settings, favorite Websites, devices owned, and preferences for receiving
alerts.

What is ASP.NET?
The site to access and change the information. Many different programming
Technologies and supported languages have been developed to create Web
applications; PHP, JSP (using Java), CGI (using Perl), and ColdFusion (using CFML)
re just a few of the more popular ones. Rather than tying you to a specific technology
and language, however, ASP.NET lets you write Web applications using a variety of
familiar programming languages.

Finally, ASP.NET is based on the Microsoft .NET Framework. The .NET

Framework collects all the technologies needed for building Windows applications, eb

22
applications, and Web Services into a single package with a set of more than twenty
programming languages. To develop Websites with ASP.NET, you’ll need to
download the .NET Framework Software Development Kit, which I’ll guide you through
in the next few sections.

Even with all the jargon demystified, you’re probably still wondering: what
makesASP. NET so well? Compared with other options for building Web applications,
ASP.NET has the following advantages:

ASP.NET lets you use your favorite programming language, or at least one
That’s really close to it. The .NET Framework currently supports over twenty
Languages, four of which may be used to build ASP.NET Websites.

ASP.NET pages are compiled, not interpreted. Instead of reading and

interpreting your code every time a dynamic page is requested, ASP.NET compiles
dynamic pages into efficient binary files that the server can execute very quickly. This
represents a big jump in performance when compared with the technology’s
interpreted predecessor, ASP.

ASP.NET has full access to the functionality of the .NET Framework. Support
for XML, Web Services, database interaction, email, regular expressions, and many
other technologies are built right into .NET, which saves you from having to reinvent
the wheel.

ASP.NET allows you to separate the server-side code in your pages from the
HTML layout. When you’re working with a team composed of programmers and
design specialists, this separation is a great help, as it lets programmer’s modify the
server-side code without stepping on the designers’ carefully crafted HTML—and vice
versa.

23
 ABOUT OLEDB
.

 Oledb provides user interface to the database.

 The details of users who use the website are stored in the
database, This Data Source is used to keep record of user and
tables in Microsoft Access Database.

INTRODUCTION TO SYSTEM DESIGN

.
 Definition :
System design is a process of preparing of input process and the result
detail procedure. After gathering the facts through various techniques such as
questionnaires, interviews, analysis of documents and observation into all existing
system and recording these collected information in the proper format using DFD’s
decision table, flowcharts etc. The next step is to define the system in terms of
user requirements. This is referred to as logical design and then converted into
physical design.

 Logical design :
When the system analyst prepares the logical design of system, which
contains the details of the users requirements. The information flowing in and out of
the system and the required data resources. The logical design contains the following
information:
Specification about input data. The source of input data the document from
which it will be derived and the process of data preparation from the documents.

24
Specification about output reports the data contains in the reports, its formats and
frequency of generation of report.
Sepcification about data to be stored permanently in the system and its
format.Specifications about edit correction, backup procedures and data security
arrangement. Specification about implementation plans. Brief information about
current logical and physical system. brief information about the benefit of the new
system, its constraints and required resources to implement it.

 Physical design of system

Once the agreements are reached between the user and about the logical
design of the system, the system analysis can start with the physical design of the
system.Physical design of the system means the designing the computer part of the
information system. The physical design of the computer system involves the following
aspects.
 Stored data
Physical storage of data is on the secondary storage device like floppy disk,
hard disk and Magnetic tapes. The data is stored in the database. A database is a
collection of tables. Table is collection data items organized in the terms of collection
of rows. Table contains the stable information about the entities. When row is added
or deleted from a table, table affected, is said to be updating of table.
In online transaction processing system, the table is updated as soon as
transaction occurs but in a batch processing system table will be updated after
transaction performed.
Input and output
The major step is the system design is the preparation of input data format
and the design of output repots. The input design is the process of designing the input
data in a computer-based format.
While designing the input, try to produce the cost effective method and to
make sure that it is acceptable to the user and also the accuracy of data is to be
achieved because if the input data entered is not correct, the output will be not correct.
Computer procedure design

25
 When the management accepts the input/output design proposal, the next
step to follow is the design of computer procedures. The analyst has to specify to
programmer, the input/output and processing details that are needed to the design the
specifying the computer procedures. These tools are flowcharts, data flow diagrams
etc.

26
 Welcome Page:-

27
 Login Page:-

28
 Registration Page:-

 Put Advertisement Page:-

29
 Search Properties Page:-

 Search Users Page:-

30
 Latest Offer Page:-

31
FUNCTIONALITY OF SOFTWARE

1) Login page:-

 This is the login form.

 users enter their user name & Password and then Enter in to
the System.
 Particular user also can login with access password.

2)Register Form:-
 This is the registration form.
 User which is not already logged in then he or she can register
with the
The help of this form.
 There is Login information, Personnel information,
Authentication and access.

3)Change User Type:-

 This is the Profile form.
 User who is already registered can edit their information with the
help of this form.

4)Advertise Form:-
 This is the upload form.
 User can select any of the categories and upload more than one
images at a time then he or she can see that uploaded advertises in
that particular category.

32
5)Search Properties:-

 This is form to search properties.

 By this form user can simply select their requirements and
search related properties.

6)Search Properties:-

 This is form to search User.

 By this form user can search users like builders, contractors
etc... and contact them directly.

7) Latest Offers:-
 This is the latest offers form.
 In this form, user would be able to see the Latest Real Estates
projects currently being developed.

8) About Us:-
 This is the About Us form.
 In this there is a detail of company.

9)Contact Us:-

 This is the Contact Us form.

 In this there is a contact information about the company.

10) Log Out:-

 This is the log out form.

33
  User who is logged in can be successfully logged out of this.

USER MANUAL

To install the software:

1. Copy Folder from CD.

2. Run Setup.Exe and provide necessary information as setup needs.

3. Before you start Setup be sure that,

a. Your IIS (Internet Information Services) is Well Configured.
b. .Net Framework (Version 1.1 or version 2.0) is already installed.
c. Local Area Network is Well Configured.

34
 TESTING
 Introduction to Testing and Debugging.

 Testing Principles

 Testability

 Model of Testing

 Test strategy

35
 INTRODUCTION TO TESTING AND DEBUGGING

The phase of system development life cycle tests system design. Testing of
system decides whether the newly designed system works properly or not. After the
development of documentation manually about the system this stage is checked. And
if the system working properly then it will be considered for implementation and if isn’t
then system analyst is informed to find out generated errors or problems and to find
out its solutions. This process is known as debugging.
For any software system testing means to check out it’s coding. If there is not
any problem in the coding then that code is proper and efficient to design. If we are
not getting proper or required output then we have to debug the system coding. So,
the debugging is also a subpart of the testing section. If the system runs correctly
during testing then there is no need to debug.
During the testing of our project we have to face different types of errors.
Especially, database errors annoyed us but at last we solved it, successfully. Some of
the errors are listed below with their cause and solution.

Testing Principles

Following are the testing principles, which are used,

 All tests should be traceable to user requirements.
 Tests should be planned long before testing begins.
 Testing should begin in small and progress toward testing in the large.
 Exhaustive testing is not possible.
 To be most effective testing should be conducted by an independent third
party.

36
 TESTABILITY

Software testability is simply how easily a computer program can be tested.

The checklist that follows provides a set of characteristics that lead to testable
software.

 Operability.
 Observable.
 Controllability.
 Decomposability.
 Simplicity.
 Stability.
 Understandability.

Following are the attributes of the good test:

 A good test has a high probability of finding an error.

 A good test is not redundant.
 A good test should be “best of breed”.
 A good test would be neither too simple nor too complex.

37
 MODEL OF TESTING

There are several models for testing module some of them are as
follows:

 White Box Testing:-

As per our project, we have used white Box Testing Model because
independent paths of PHP files and loops are the cornerstones of the vast majority of
all algorithms implemented in the software. There are five different classes of the
loops, which can be defined as follows.
 Simple Loops.
 Nested Loops.
 Concatenated Loops.
 Unstructured Loops.
 Continuous Loops.

As per our project, we have used Simple Loops. The Concatenated loops can
be tested with the different PHP files of the project; all are independent of each other.

 Black Box Testing:-

Black-box testing attempts to find errors in the following Categories:

 Incorrect or missing function.
 Interface errors.
 Errors in fetching external data.
 Behavior or performance errors.
 Initialization and termination error.

Black-box testing is implementing on our project through test each and every
independent PHP file. For dependent files, we check the dependency and interface

38
after integrating all the files. For behavior or performance testing we first made demo
give it to our project guide and some employees to use and check performance.

TEST STRATEGY

A strategy provides a road map that describes the steps to be undertaken, and
how much effort, time and resources will be required. A testing strategy must
incorporate test planning, test design, test execution, and resultant data collection and
evaluation. The testing strategy followed by us constituted the following component
parts as:

To accomplish this there are some methods defined. They are:

Graph based Testing: In this method a graph of all objects with their
relationship with each other is created as Nodes and Links. Then each of the
relationship is studied separately so that a test case can be derived. In this study, all
the attributes of relationship like transitivity, symmetry and reflexivity is tested. Care
should be taken that no node and relationship remains uncovered.
Equivalence partitioning: This method divides the input domain of a program
into classes of data from which test cases can be derived. These classes, Known as
Equivalence Classes, represent a set of valid or invalid input conditions. It helps in a
manner that one test case alone uncovers number of errors that might otherwise
require more number of test cases.
Boundary value analysis: As the name suggests boundary value analysis
leads to selection of test cases that exercise on boundary values for a software
module i.e. if an input condition pertains to a range bounded by 2 values – an upper
and a lower, then test cases should be designed with values just above and just below
these values.

39
TEST STRATEGIES:

Testing is a set of activities that can be planned in advance and conducted

systematically, for this reason a template for software testing, consisting a set of steps
into which we can place specific test cases & testing methods, should be defined.
Testing is just like assurance to review of software product and related
documents for correctness, completeness, reliability, and maintainability. And it
includes assurance that the
system meets the specification and requirements for its intended use and
performance. The common view of the testing is to prove that are no error.
System testing is too much expensive as well as it is not possible for analyst to
prove that software is free and clear of error.

40
 DATA DICTIONARY

What is data dictionary?

A data dictionary is a catalogue of all elements in a system. It’s a

document that co-ordinate and confirms what specific data terms
means to different people in the organization.
It’s the basic reference work for finding the names and attributes of
data elements used throughout the system. These elements center to
meet user requirements and organization needs.
All data elements are included in the data dictionary.

Why it is so important?

To manage the details, both large and small systems have large quantities of
data flowing through them. If analysis elements to be left out. Therefore, the
information of the data flow should be recorded.

How can data dictionary be achieved?

To make data dictionary, composition of valid and normalized structure of data

storage is key point.
First milestone situates that at first, we have to define user requirements and
find best path to implement it.

Designing the normalized database.

Find best approach for storing and retrieving data.
Give a formal appearance to user for ‘Message passing criteria.’

41
 DATA BASE DESIGN

1. Properties Table:-

Field Name Data Type Description

Place Text City
Property Type Text Type of property
Description Text User address, more details.
Image Text Uploaded

2. User Table:-

Field Name Data Type Description

Place Text Login name

Pries Text File name
Property type Text Date time
User type Text Image path

3. Registration Table:-

Field Name Data Type Field Size Description

User ID Text (18,0) User Name
password Text 50 Password
email Text 50 User email id
User type Text - User Typess
Property type Text - Property type
Image Image 20 Image Path

42
 ANNEXURE
ANNEXURE

1. The Ultimate C#.NET and ASP.NET Black Book By: Karl

2. ASP.NET Web Developer’s Guide. By: Syngress Press

3. ASP.NET Unshielded By : Stephen Walther

4. ASP.NET Website Programming, .NET Edition: Problem, Design,

Solution By : Marco Bellinaso and Kevin

5. Software Engg. By: Pressman.

43