Chap3 Design Strategy

Zwwinger: Major Project Report 201
Chapter 3
DESIGN STRATEGY
Sikkim Manipal Institute Of Technology Page 20

1
3. DESIGN STRATEGY FOR THE SOLUTION:

3.1 Data Flow Diagram:
Administrator
Request Response
Request
ZWWINGER
ZWWINGER Existing User
System
System Response
00
Request Response
00
New User
Figure: 3.1. Context diagram or 0 Level DFD Diagram

1

1
LEVEL 1 DFD
Request Emailid, password
User User Data

User
User
Sign
Sign Up
Up View
View
Sign
Sign In
In
0.1
0.1 0.3
0.3
0.2
0.2
Retrieve Data
Registration Data User Data User Data
USER ACCOUNT DB
Updated Data User Data Searched Data
Manage
Manage profile
profile Manage
Manage Search
Search friends
friends
activities
activities
0.4
0.4 0.6
0.6
0.5
0.5
User Information User Information User Name
Fig: 3.2 LEVEL 1 DFD

1
LEVEL 2 DFD FOR USER SIGN UP
Invalid Data
User Data
Get
Get user
user
Registration
Registration Verify
Verify
0.1.1
0.1.1 User Data
0.1.2
0.1.2
Valid Data
USER ACCOUNT DB
Fig: 3.3 LEVEL 2 DFD FOR USER SIGN UP
LEVEL 2 DFD FOR USER SIGNIN
Emailid, password
Invalid Data Authentic user

Get
Get user
user
Authenticate
Authenticate View
Sign View user
user
Sign in
in
home
home
details
details
Emailid, password 0.2.2
0.2.2 0.2.3
0.2.1 0.2.3
0.2.1
User Data User Data
0.1.1
0.1.1
Display information

1
USER ACCOUNT DB
Fig: 3.4 LEVEL 2 DFD FOR USER SIGNIN
LEVEL 2 DFD FOR VIEW
SCRAPS DB
Display Retrieve Scraps Display Display User Data
View
View View
View Friend
Friend
View
View Scraps
Scraps Picture
Picture Request
Request View
View Picture
Picture
Comments
Comments
0.3.1
0.3.1 0.3.3
0.3.3 0.3.4
0.3.4
0.3.2
0.3.2
0.1.1
0.1.1 0.1.1
0.1.1
0.1.1
0.1.1
User Data Retrieve Comments Retrieve Request Retrieve Picture
COMMENTS DB FRIEND REQUEST DB PICTURE INFO DB
View
View User Data Display
Message
Message
0.3.5 User Data

0.3.5
0.1.1
0.1.1
Retrieve Message Display
MESSAGE DB User Data

1
USERACCOUNT DB
Fig: 3.5 LEVEL 2 DFD FOR CHECKING
LEVEL 2 DFD FOR MANAGE PROFILE
User Data
Invalid Data Valid Data

Get
Get Profile
Profile
Details
Details Validate
Validate Data
Data Update
Update
Profiles
Profiles
0.4.1
0.4.1 0.4.2
0.4.2
User Data 0.4.3
0.4.3
0.1.1
0.1.1
USERACCOUNT DB
New User Data
Fig: 3.6 LEVEL 2 DFD FOR MANAGE PROFILE

1
LEVEL 2 DFD FOR MANAGE ACTIVITIES
USERACCOUNT DB
User Data
User Data User Data User Data User Data
Send/Delete
Send/Delete Send/Delete View
Send/Delete View Friend
Friend
Scraps
Scraps Comments
Comments View/Remove
Request
Request View/Remove
0.5.1
0.5.1 0.5.2 Picture
Picture
0.5.2
0.5.3
0.5.3
0.5.4
0.5.4
0.1.1
0.1.1 0.1.1
0.1.1
0.1.1
0.1.1
Scrap Retrieve Comment Retrieve Friends Retrieve Picture Retrieve
Data scrap Data Comment Data Request Data Picture
SCRAPS DB COMMENTS DB FRIEND REQUEST DB PICTURE DB
User Data
Send/Delete
Send/Delete
Message
Message
Report
Report
0.5.5
0.5.5
0.5.6
0.5.6
0.1.1
0.1.1
0.1.1
0.1.1
1
Message Data Retrieve Message User Data
MESSAGE DB FEEDBACK DB
Fig: 3.7 LEVEL 2 DFD FOR MANAGE ACTIVITIES
LEVEL 2 DFD FOR SEARCH FRIENDS
User Data
Search
Search User Information Prepare Display
Prepare List
List
0.6.1
0.6.1 0.6.2
0.6.2
Retrieve Data User Name
USER ACCOUNT DB
Fig: 3.8 LEVEL 2 DFD FOR SEARCH FRIENDS

1
LEVEL 1 DFD FOR ADMINISTRATOR
Admin Username, password
Admin Data
Admin
Admin
Login
Login
0.1
0.1
Admin Data
ADMINSTRATOR DB
Action
Action
View 0.3
0.3
View User
User Admin Data
0.2
0.2

1
User Data Action Data
FEEDBACK DB USERACCOUNT DB
Fig: 3.9 LEVEL 1 DFD FOR ADMINISTRATOR
LEVEL 2 DFD FOR ADMINISTRATOR LOGIN
Adminname,password
Invalid Data Authentic Admin

Get
Get Admin
Admin
Authenticat
Authenticat View
Login View Admin
Admin
Login Details
Details ee Home
Home
0.1.1
0.1.1 Adminname,password 0.1.2
0.1.2 0.1.3
0.1.3
Admin Data Admin Data

0.1.1
0.1.1
ADMINISTRATOR DB
Fig: 3.10 LEVEL 2 DFD FOR ADMINISTRATOR LOGIN
LEVEL 2 DFD FOR VIEW USERS BY ADMINISTRATOR
FEEDBACK DB ADMINISTRATOR DB

1
User Data Admin Date
View
View
User
User
Display
0.2.1
0.2.1
User Data
USER ACCOUNT DB
Fig: 3.11 LEVEL 2 DFD FOR VIEW USERS BY ADMINISTRATOR
LEVEL 2 DFD FOR ACTION ON USER
ADMINISTRATOR DB
Admin Data
Block/Unblock
Block/Unblock
0.3.1
0.3.1
0.2.2
0.2.2
Action Data
USERACCOUNT DB
Fig: 3.12 LEVEL 2 DFD FOR ACTION ON USER

1
3.2 Entity Relationship Diagram
The Data Flow Diagram does not reveal the relationships between the various data
elements involved in the system. These relationships are the most important features in
the database system. This relationship is stated using an E-R Diagram.
The most important consideration in designing the database is how the information will
be used. The various applications and procedures that will use the database introduce the
requirements upon the structure of the data.
Databases are used to store structured data. The structure of this data, together with other
constraints, can be designed using a variety of techniques, one of which is called entity-
relationship modeling or ERM. The end-product of the ERM process is an entity-
relationship diagram or ERD. Data modeling requires a graphical notation for
representing such data models. An ERD is a type of conceptual data model or semantic
data model.
The first stage of information system design uses these models to describe information
needs or the type of information that is to be stored in a database during the requirements

1
analysis. The data modeling technique can be used to describe any ontology (i.e. an
overview and classifications of used terms and their relationships) for a certain universe
of discourse (i.e. area of interest). In the case of the design of an information system that
is based on a database, the conceptual data model is, at a later stage (usually called
logical design), mapped to a logical data model, such as the relational model; this in turn
is mapped to a physical model during physical design. Note that, sometimes, both of
these phases are referred to as "physical design".
There are a number of conventions for entity-relationship diagrams (ERDs). The classical
notation is described in the remainder of this article, and mainly relates to conceptual
modeling. There are a range of notations more typically employed in logical and physical
database design.

1

1
Figure: 3.13 ER-Diagram
3.3 TABLES
3.3.1 Useraccount
Name Constraints Data Type

Emailid PRIMARY KEY Varchar(80)
password NOT NULL Varchar(80)
dob NOT NULL Date
sex NOT NULL Varchar(80)
firstname NOT NULL Varchar(80)
lastname NOT NULL Varchar(80)
secqns NOT NULL Varchar(80)
secans NOT NULL Varchar(80)
address NOT NULL Varchar(80)
Country NOT NULL Varchar(80)
City NOT NULL Varchar(80)
Pin NOT NULL Varchar(80)
Phone1 NOT NULL Varchar(80)
Phone2 NOT NULL Varchar(80)
School NOT NULL Varchar(80)
College NOT NULL Varchar(80)
University NOT NULL Varchar(80)
Relationship NOT NULL Varchar(80)
Work_status NOT NULL Varchar(80)
Interest_in NOT NULL Varchar(80)
Wall_post NOT NULL Varchar(80)
About_me NOT NULL Varchar(80)

1
Language NOT NULL Varchar(80)

Status NOT NULL Varchar(80)
Table: 3.1 Table – useraccount
3.3.2. friendrequest:
Requestid PRIMARY KEY number
FOREIGN KEY [REFERENCE

emailid Varchar(80)
BY useraccount]
fromid NOT NULL Varchar(80)
status NOT NULL Varchar(80)
reqdate NOT NULL date
Table: 3.2 Table - friendrequest
3.3.3. Scrap
scrapid PRIMARY KEY number
emailid FOREIGN KEY [REFERENCE Varchar(80)

1
BY useraccount]
message NOT NULL Varchar(80)
date NOT NULL date
Table: 3.3 Table – scrap
3.3.4. Picinfo
picid PRIMARY KEY number

emailid Varchar(80)
BY useraccount]
pictitle NOT NULL Varchar(80)
Table: 3.4 Table – picinfo
3.3.5. Comment
commentid PRIMARY KEY number

1

picid number
BY picinfo]
commentdesc NOT NULL Varchar(80)
emailid Varchar(80)
BY useraccount]
commentdate NOT NULL Date
Table: 3.5 Table – comment
3.3.6. Message
messageid PRIMARY KEY number

emailid Varchar(80)
BY useraccount]
message NOT NULL Varchar(80)
dt NOT NULL Date
Table: 3.6 Tables – Message
3.3.8. Feedback

emailid Varchar(80)
BY useraccount]

1
Feedbackdesc NOT NULL Varchar(80)
Reportedemailid NOT NULL Varchar(80)

feedbackdate NOT NULL Date
Table: 3.8 Tables – Feedback
3.3.9. Administrator
username PRIMARY KEY Varchar(80)
password NOT NULL Varchar(80)
Table: 3.9 Table – administrator
3.4 Relational Schema Diagram:
Useraccount
emailid
password firstname lastname dob sex secqns secans Address country

1
City Pin Phone School college univer

relationship Workstatus interest wallpost
aboutme language status
friendrequest
requestid emailid fromid status reqdate
Scrap
scrapid emailid fromid message sdt
Message
messageid emailid fromid message mdt
Picinfo
picid emailid pictitle
Comment
commentid emailid picid commentdesc cdt
Feedback
emailid feedbackdesc reportemailid feedbackdate
Administrator
username password
Figure: 3.14 Relational Schema Diagram

Chap3 Design Strategy

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chap3 Design Strategy

Uploaded by

Copyright:

Available Formats

Zwwinger: Major Project Report 201

Sikkim Manipal Institute Of Technology Page 20

3. DESIGN STRATEGY FOR THE SOLUTION:

Figure: 3.1. Context diagram or 0 Level DFD Diagram

Sikkim Manipal Institute Of Technology Page 21

Sikkim Manipal Institute Of Technology Page 22

Request Emailid, password

User User Data

Registration Data User Data User Data

Updated Data User Data Searched Data

User Information User Information User Name

Fig: 3.2 LEVEL 1 DFD

Sikkim Manipal Institute Of Technology Page 23

LEVEL 2 DFD FOR USER SIGN UP

Fig: 3.3 LEVEL 2 DFD FOR USER SIGN UP

LEVEL 2 DFD FOR USER SIGNIN

Invalid Data Authentic user

User Data User Data

Sikkim Manipal Institute Of Technology Page 24

Fig: 3.4 LEVEL 2 DFD FOR USER SIGNIN

LEVEL 2 DFD FOR VIEW

Display Retrieve Scraps Display Display User Data

COMMENTS DB FRIEND REQUEST DB PICTURE INFO DB

0.3.5 User Data

MESSAGE DB User Data

Sikkim Manipal Institute Of Technology Page 25

Fig: 3.5 LEVEL 2 DFD FOR CHECKING

LEVEL 2 DFD FOR MANAGE PROFILE

Invalid Data Valid Data

New User Data

Fig: 3.6 LEVEL 2 DFD FOR MANAGE PROFILE

Sikkim Manipal Institute Of Technology Page 26

LEVEL 2 DFD FOR MANAGE ACTIVITIES

User Data User Data User Data User Data

Data scrap Data Comment Data Request Data Picture

SCRAPS DB COMMENTS DB FRIEND REQUEST DB PICTURE DB

Message Data Retrieve Message User Data

Fig: 3.7 LEVEL 2 DFD FOR MANAGE ACTIVITIES

LEVEL 2 DFD FOR SEARCH FRIENDS

Retrieve Data User Name

Fig: 3.8 LEVEL 2 DFD FOR SEARCH FRIENDS

Sikkim Manipal Institute Of Technology Page 28

LEVEL 1 DFD FOR ADMINISTRATOR

Admin Username, password

Sikkim Manipal Institute Of Technology Page 29

Fig: 3.9 LEVEL 1 DFD FOR ADMINISTRATOR

LEVEL 2 DFD FOR ADMINISTRATOR LOGIN

Invalid Data Authentic Admin

Admin Data Admin Data

Fig: 3.10 LEVEL 2 DFD FOR ADMINISTRATOR LOGIN

LEVEL 2 DFD FOR VIEW USERS BY ADMINISTRATOR

Sikkim Manipal Institute Of Technology Page 30

Fig: 3.11 LEVEL 2 DFD FOR VIEW USERS BY ADMINISTRATOR

LEVEL 2 DFD FOR ACTION ON USER

Fig: 3.12 LEVEL 2 DFD FOR ACTION ON USER

Sikkim Manipal Institute Of Technology Page 31

3.2 Entity Relationship Diagram

Sikkim Manipal Institute Of Technology Page 32

Sikkim Manipal Institute Of Technology Page 33

Sikkim Manipal Institute Of Technology Page 34

Name Constraints Data Type

Sikkim Manipal Institute Of Technology Page 35

Language NOT NULL Varchar(80)