Ch. 3 Designing The Project

Chapter No.
3
Designing the Project
CHAPTER 3
37
Chapter No. 3
3.1 Introduction
In order to design a web site, the relational database must be designed first.
Conceptual design can be divided into two parts: The data model and the process
model. The data model focuses on what data should be stored in the database while
the process model deals with how the data is processed. To put this in the context of
the relational database, the data model is used to design the relational tables. The
process model is used to design the queries that will access and perform operations
on those tables.
3.2 Purpose
Purpose is to:
Understand a system.
Understand the different phases of system developments life cycle.
Know the components of system analysis.
Know the components of system designing.
3.3 Scope
My focus is to develop and design the complete online website according to
requirements. In designing phase I develop complete user side and as well as admin
site for users and administrator simultaneously. In designing phase back end coding
is most important by which we develop our graphical site. So, my scope is to design
and develop my website completely.
38
Chapter No. 3
3.4 Activity Diagrams
System Flow for Admin
Here is the flow of login into system for administrator.
S SYS
Sys
39
Chapter No. 3
Fig 3.1 System Flow for Admin
40
Chapter No. 3
System Flow for Customer
41
Chapter No. 3
Fig 3.2 System Flow for Customer
3.5 Architectural Representation (Architecture Diagram)
3.5.1 Data Flow Diagram
First Level DFD for Admin
42
Chapter No. 3
First Level DFD for Customer
43
Chapter No. 3
3.6 Class Diagram

Class diagram depicts the attributes and functions of the classes used in the system.
44
Chapter No. 3
3.7 Entity Relationship Diagram

Entity relationship diagram depicts the different entities and
The relationships among them.
45
Chapter No. 3
3.8 Sequence Diagrams

Login sequence for admin
46
Chapter No. 3
Fig 3.3 Sequence Diagram for login
User Diagram for View Products.
47
Chapter No. 3
Fig 3.4 Sequence Diagram for View Products
Customer Diagram for Register him.
Fig 3.5 Sequence Diagram for Customer Registration
Customer Diagram for View Products.

48
Chapter No. 3
Fig 3.6 Sequence Diagram for Customer to View Products
Administrator diagram for Add, Delete and View user and Customer.
Fig 3.7 Sequence Diagram for Administrator to Add, Delete and View user and
Customer
Administrator diagram for Add, Delete and View product.

49
Chapter No. 3
Fig 3.8 Sequence Diagram for Administrator to Add, Delete and View Products
3.9 Deployment Diagram

50
Chapter No. 3
Rapid application development is a software development methodology, which involves
iterative development and the construction of prototypes. It is a merger of various
structured techniques, especially the data driven Information Engineering with
prototyping techniques to accelerate software systems development. We use RAD Model
when Requirements are clear.
Fig 3.9 Rapid Application Development Model (RAD)

Advantages of the RAD methodology
There are following advantages of RAD
Flexible and adaptable to changes.
RAD generally incorporates short development cycles - users see the

RAD product quickly.
RAD involves user participation thereby increasing chances of early

user community acceptance.
RAD realizes an overall reduction in project risk.
51
Chapter No. 3
A system
Fig 3.10 system diagram

3.10 Database Model (Database Diagrams)
The database diagrams and table design show all the database Model which given as
below.
SQL SERVER
SQL SERVER 2012 is used in this online application.
DATABASE
A database is a structured collection of data. Data refers to the characteristics of people,
things and events. SQL server stores each data item in its own fields. In SQL Server, the
fields relating to a particular person, ting or event are handled together to form a single
complete unit of data, called a record (it can also be referred to as raw or an occurrence).
Each record id made up of a number of fields. No two fields in a record can have the
same field name.
During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time,
you define any additional fields or change the definition of existing fields.
SQL Server Tables
SQL Server stores records related to each other in a table. Different tables are created for
the various groups of information. Related tables are grouped together to form a database.
52
Chapter No. 3
Primary Key
Every table in SQL Server has a field or combination of fields that uniquely identifies
each record in the table. The unique identifier is called the Primary Key. or simple the
Key. The primary key provides the means to distinguish one record from all other in a
table. It allows the user and the database system to identify, locate and refer to one
particular record in the database.
Relational Database
Sometimes all the information of interest to a business operation can be stored in a one
table. SQL Server makes it very easy to link the data in multiple tables. Matching an
employee to the department in which they work is one example.
Foreign Key
When a field in the one table matches the primary key of another field is referred to as a
foreign key. A foreign is a field or group of fields in one table whose values match those
of the primary key of another table.
Referential Integrity
Note only those SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
Data Abstraction
A major purpose of a database system is to provide users with an abstract view of the
data. This system hides certain details of how the data is stored and maintained.
53
Chapter No. 3
Tables
There are following tables that are designed for this online application:
3.9.1 Admin Login.
Table 3.1
3.9.2 Customer.
Table 3.2
54
Chapter No. 3
3.9.3 Product.
Table 3.3
3.9.4 Product Category.
55
Chapter No. 3
Table 3.4
3.9.5 Product Groups
.
Table 3.5
3.7.6 Post a job.
Table 3.6
56
Chapter No. 3
3.9.7 Job Category.
Table 3.7
3.9.8 Job Group.
Table 3.8
3.9.9 Comments.
Table 3.9
57
Chapter No. 3
3.11 Graphical User Interface

The graphical user interface provides the ways to user to interact with the system easily.
Admin Login
Admin provides User Id and password then click on login button for login.
58
Chapter No. 3
Admin Area
In this area admin can perform all the actions that are suitable.
59
Chapter No. 3
Home Page
Home page displays Ads to the guest user and link for registration and also area for user
login.
60
Chapter No. 3
Products Detail page
This page displays the whole detail of ads and also the comments.
61
Chapter No. 3
Customer Area
Here the registered users (customers) can post, update and delete their own Ads.
62
Chapter No. 3
User Registration Page

A guest/visitor can become the user/customer of the website by the following form.
63
Chapter No. 3
Post Ads Page

Here the user/customer posts ads by providing the following information.
64
Chapter No. 3
Post Job Page

Here the user/customer can posts the jobs ads by filling the following form.
65
Chapter No. 3
About US Page
This page describes the vision and mission of the application.
66
Chapter No. 3
Contact Us Page
This page provides the contact information for the users to administrator.
67

Ch. 3 Designing The Project

Uploaded by

Document Information

Original Title

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

Ch. 3 Designing The Project

Uploaded by

Copyright:

Available Formats

Chapter No.

Understand the different phases of system developments life cycle.

Know the components of system analysis.

Know the components of system designing.

Fig 3.1 System Flow for Admin

System Flow for Customer

First Level DFD for Customer

3.6 Class Diagram

3.7 Entity Relationship Diagram

3.8 Sequence Diagrams

Fig 3.3 Sequence Diagram for login

User Diagram for View Products.

Fig 3.4 Sequence Diagram for View Products

Customer Diagram for Register him.

Fig 3.5 Sequence Diagram for Customer Registration

Customer Diagram for View Products.

Fig 3.6 Sequence Diagram for Customer to View Products

Administrator diagram for Add, Delete and View product.

3.9 Deployment Diagram

Fig 3.9 Rapid Application Development Model (RAD)

Flexible and adaptable to changes.

RAD generally incorporates short development cycles - users see the

RAD involves user participation thereby increasing chances of early

RAD realizes an overall reduction in project risk.

Fig 3.10 system diagram

3.9.7 Job Category.

3.11 Graphical User Interface

User Registration Page

Post Ads Page

Post Job Page

You might also like