6. Detail Planning

Ch-6: Detail Planning

Online Real Estate Portal Using Google Map 38


6.1 Data Flow Diagram6.2 Usecase Diagrams6.3 Activity Diagrams6.4 ER Diagram



6.1 Data Flow Diagram

A graphical representation that depicts information flow and the transformation those is applied, as data moves from input to output are knows as “Data flow Diagram”. The DFD is also known as “Bubble Chart”. The DFD may be partitioned in two levels hat represent Increasing information flow and functional details. The 0th level DFD represent the entire software elements as single bubble. As the 0th level DFD is partitioned, additional processes are brought out to reveal more details.

Notations Used in the DFD:

A Rectangle represents an external entity. It represents the source and destination of the System data.

The circles represent a process transform incoming or outgoing data.

The Double circles represent a process transform incoming or outgoing data and also further level description.

An Arrow represents a data item or a collection of data item. The Arrow head indicates the direction of the data flow.

These two Lines are display the table name or view.


Ch-6: Detail PlanningThe steps in creating the data flow diagram is divided into three stages or levels of DFD construction are as follows:

Context Diagram:

This diagram is created to describe the source and destination data will be processed or

in other words the diagram is used to describe the system in general / global system of

the entire existing. In this diagram there is no storage. Consists of a process and

describe the scope of a system. Consists of a process and describe the scope of a

system.

Zero Diagram:

This diagram is created to describe the stages of the process in the context diagram, a

more detailed penjabarannya. On this system there may be data storage.

Detailed Diagram:

This diagram is created to describe the data flow in more play more phases of the

process in the diagram is zero. In a level should be, there are only 7 to 9 processes.

Numbering level in the DFD:

Name Level Name Diagram Processes

0 Context

1 Diagram 0 1.0, 2.0, 3.0, 4.0, . . .

2 Diagram 1.0 1.1, 1.2, 1.3, 1.4, . . .

3 Diagram 1.1 1.1.1, 1.1.2, . . .



(0 level DFD for Real Estate Portal)



(1st level DFD for Real Estate Portal )



(2nd level DFD for Real Estate Portal)(Registration Process)



(2nd level DFD for Real Estate Portal)(Login Process)



(2nd level DFD for Real Estate Portal)(Searching Process)



(2nd level DFD for Real Estate Portal)(Payment Process)



(2nd level DFD for Real Estate Portal)(Mail/SMS Process)



(2nd level DFD for Real Estate Portal)(Manage Property Process)



(2nd level DFD for Real Estate Portal)(Manage Advertise Process)



(2nd level DFD for Real Estate Portal)(Post Requirement Process)



(2nd level DFD for Real Estate Portal)(Post Property Process)



(2nd level DFD for Real Estate Portal)(Setting Process)



6.2 Usecase Diagrams

[6.2.1] Login Usecase:



[6.2.2] Registration Usecase:



[6.2.3] Location using Google Map Usecase:



[6.2.4] Search Usecase:



[6.2.5] Purchase Home Usecase:



[6.2.6] Admin Usecase:



[6.2.7] General Usecase:



6.3 Activity Diagrams

[6.3.1] Buyer Activity Diagram:



[6.3.2] Admin Activity Diagram:

6.4 Entity Relationship Diagrams Online Real Estate Portal Using Google Map 62


For database application, the entity relationship approach can be used effectively for modeling some parts of the problem. The ER modeling approach is used to help design information system.

The main focus is of ER modeling is the data items in the system and the relationship between them. It aims to create a conceptual schema for the data from the user’s perspective. The model thus created is a high level data model that is independent of any database model. The schema can later be used during the development of the database. The ER models are frequently represented as ER diagrams and use the 3 major abstractions to describe data.

Entities: Entities are distinguishable objects that can be represented in the database. It is a building block of database. An entity instance is a specific that represents an entity.

Relationship: It is an association among several entities .It establishes a connection between a pair of logically related entities. Separate entities can have relationship with each other.

Attributes: They are the properties of the entities that differentiate it from other entities and provide information about an entity.

The mapping cardinalities among the entities are as follows: One to One: An entity is associated with at most one entity and vice-versa.

One to Many: An entity in A is associated with any number of entities in b, but b can be associated with at most one entity in A.

Many to Many: An entity is associated with any number of entities and vise-versa.

ER diagrams often use symbols to represent three different types of information.

Boxes are commonly used to represent entities.

Diamonds are normally used to represent relationships.

Ovals are used to represent attributes.

Lines linking attribute to entity sets and entity sets to relationship sets

E.R.Diagram




Documents

6. Detail Planning