Database Design:

T a b l e :Membership NAME UserID Pasword Type DATA TYPE Varchar Varchar Varchar SIZE 50 50 50 CO NSTRAINT Primary key DESCRIPTION Id of the User Pasword of the User Type of user

Ta ble: Perso na l NAME UserID Full Name DATA TYPE Varchar Varchar SIZE 50 50 CO NSTRAINT Primary key DESCRIPTION Id of the User Name of user

Age Sex Caste Religion

Marital Status Heig ht DOB Mother tongue Qualification

Varchar Varchar Varchar varchar

Varchar Varchar datetime Varchar Varchar

10 8 18 100
10 3 8 20 100 Not null Not null

Male/female Not null

Unmaried, widow/widower,divorc ed,separated Heig ht Date Of Birth

City
State Country

Varchar
Varchar Varchar

50
50 50 Not null Default Constraint

Bombay, Guwahati Delhi..

India

Ta ble: Prof essio na l Cult ure NAME UserID DATA TYPE Varchar 50 10 10 50 3 SIZE 50 CO NSTRAINT Primary & Foreign key DESCRIPTION Id of the User Government, Private Income Mobile No. Occasional, Regular, No Yes, No

Occu pationDet Varchar ail Varchar Annual Income Contact Varchar Drink Smoking varchar char

Table: PartnerPreferences

Field Name

DATA TYPE

SIZE

CONSTRAINT

DESCRIPTION

UserID minAge maxAge Sex Height Color Caste City State Religion

Varchar int int Varchar int varchar Varchar Varchar Varchar Varchar

50 8 8 8 8 20 18 50 50 50

Primary +Foreign key

Unique UserId

Male/female

Fair , Whitish

Bombay, Channai etc Bihar,Kerela etc Hindu,Muslim

Table: UserImage NAME UserID Image DATA TYPE Varchar Blob SIZE 50 50 CONSTRAINT Primary key Refernces Foreign key DESCRIPTION Id of the User Image of user

Table: InboxMessageDetails

Field Name

DATA TYPE

SIZE

CONSTRAINT

DESCRIPTION

Sl No UserID Msg

Int Varchar Varchar

8 50 100

Identity, Primary Key Primary +Foreign key Not null Reference Membership Unique UserId

fromUser

Varchar

50

Foreign key

Table: SentMessageDetails

Field Name

DATA TYPE

SIZE

CONSTRAINT

DESCRIPTION

Sl No

Int

Identity Primary Key Reference Membership

UserID

Varchar

50

Foreign key

Msg

Varchar

100

Not null Reference Membership

ToUser

Varchar

50

Foreign key

ER DiagramAge Password Type Cast Membership Religion UserID Name UserID Sex DOB

Personal

City

State

Marital Status

Country

Data Flow Dia grams:

DFD means data flow diagram. Before develo ping software,
p ro grammer

should have a clear picture of DFD.

A DFD shows the movement of data throu gh the different transformations o r proceses in the s y stem. A DFD or data flow diagram is a graphical representation that depicts the information flow and the transformation that are applied to data it moves from in put to out put. Data Flow Diagram (DFD) i s used to define the flow of the sy stem and i t s resources such a s information. Data Flow Dia grams are a way of ex presing sy stem requirements in a graphical manner. DFS re presents one of the most in genious tools used f o r structured a n a l ysis.

A DFD is also known as a bubble chart. It has the pur pose of Clarif y ing sy stem re quirements and identif y ing maj o r transformations that wil become pro grams in system design. Named circles show the proceses and data named arows represent flows and a rectan gle re presents a source o r sink.

The Data Flow Dia gram b a s i c a l y serves two pur poses. 1. Provide a graphical tool, which can be used effectivel y by the a n a l y st to ex plain the understandin g of the s y stem to the user. 2. They can be effectivel y converted into structured charts, which effectively h e l p in the designing of the s ystem?

There are only five symbols that are used in the drawing of data flow diagrams EXTERNAL ENTITY An external entity is a source or destination of a data flow. Only those entities which originate or receive data are represented on a data flow diagram. The symbol used is an oval containing a meaningful and unique identifier PROCESS A process shows a transformation or manipulation of data flows within the system. The symbol used is a rectangular box: DATAFLOW A data flow shows the flow of information from its source to its destination. A data flow is re resented by a line, with arrowheads showing the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents. DATA STORE A data store is a holding place for information within the system: It is represented by an open ended narow rectangle. Data stores may be long-term files such as sales ledgers, or may be short-term accumulations: for example batches of documents that are waiting to be processed. Each data store should be given a reference folowed by an arbitrary number. RESOURCES FLOW A resource flow shows the flow of any physical material from its source to its destination. For this reason they are sometimes refered to as physical flows. The physical material in question should be given a meaningful name. Resource flows are usualy restricted to early, high-level diagrams and are used when a description of the physical flow of materials is considered to be important to help the analysis.
p

Level 0:

Context Diagram

Database

Takes User Send Confirmation Registration Mails

Manipulate

Admin