Final Project

ONLINE SHOPPING

Researcher Supervisor

MUHAMMAD ABDULLAH ZAFAR Mr. MUHAMMAD MOOSA
Roll no # 575
Session: 2011-2015
BS.CS Weekend B

DEPARTMENT OF COMPUTER SCIENCE

BEGINNING

(In the name of Allah Almighty the most beneficent the merciful)

Recite! in the name of your Lord who created
Created man, out of a (mere) clot of congealed blood –

Recite! And thy Lord is Most Generous –
He who taught (the use of) the Pen –
Taught man that which he knew not.
(Al-Alaq 1-5)

ii

DEDICATION

Dedicated To:

My loving father, who has ever been the real source of my
inspiration,

My mother, who is symbol of affection and courage for me,
My sweet sisters and brother who always helped me in course

of my life,
And

My Respected Teacher
Mr. MUHAMMAD MOOSA

iii

DECLARATIONS

I hereby declare that up to my knowledge this project has been performed for the
first time by me and it is result of my teacher’s efforts as well as the references that i have
obtained from other resources. I hereby certify that this dissertation has not already been
accepted in substances for any other degree not it is being submitted concurrently in
candidate for any other degree.

MUHAMMAD ABDULLAH ZAFAR

iv

FORWARDING SHEET

The project entitled “Online Shopping” prepared and submitted by an

individual work of a student of BS Honrs. In Computer Science at ISLAMIA
UNIVERSITY BAHAWALPUR to fulfill the partial requirement of the degree under my
guidance and I am satisfied with the quality of his work.

______________________ ______________________
Project Supervisor Project Examiner

___________________
Academic Coordinator

v

ACKNOWLEDGEMENT

I am thankful to Allah Almighty that i have taken efforts in this project. However,
it would not have been possible without the kind support and help of Him. We would like
to extend my sincere thanks to all of him.

The special thank goes to my helpful supervisor, Mr. Muhammad Moosa. The
supervision and Supports that he gave truly help the progression and smoothness. The
Co-operation is much indeed appreciated.

Last but not least i would like to thank my parents that make me able to face all
difficulties and to stand too far.

Muhammad Abdullah Zafar

vi

ABSTRACT

Title: Online Shopping
Page:
Researcher: 54
Department:
University: Muhammad Abdullah Zafar
Year: Computer Science
Degree: The Islamia University of Bahawalpur
2011-2015
BS.CS

The Project is designed to create a platform for users to Purchase products of
different categories online.

The project includes Two Different links one for Admin site and other is for user
site. A database is created for such purpose and all products are taken dynamically.

Admin can manage all updates of the site like
 Adding Categories
 Adding Companies
 Adding Models
 Adding Products
 Adding Pages
 Adding News

User can view products with company, model and price and purchase online by
adding into cart. If user is Registered to the site then login is required otherwise
Registration is compulsory

vii

CONTENTS

ONLINE SHOPPING ..........................................................................................................a
BEGINNING ...................................................................................................................... ii
DEDICATION................................................................................................................... iii
DECLARATIONS............................................................................................................. iv
FORWARDING SHEET .................................................................................................... v
ACKNOWLEDGEMENT ................................................................................................. vi
ABSTRACT...................................................................................................................... vii
CONTENTS..................................................................................................................... viii
CHAPTER 1 ....................................................................................................................... 1

1.1 Website................................................................................................................. 1
1.2 Overview .............................................................................................................. 1
1.3 What information does it provide?....................................................................... 2
1.4 Websites as businesses ......................................................................................... 2
1.5 Content based sites ............................................................................................... 2
1.6 Product or service based sites............................................................................... 2
1.7 Personal web pages .............................................................................................. 3
1.8 Motivations........................................................................................................... 4
1.9 Sites of academics ................................................................................................ 4
1.10 Criticisms.......................................................................................................... 4
CHAPTER 2 ....................................................................................................................... 5
2.1 Preliminary Investigation ..................................................................................... 5

2.1.1 Request Analysis........................................................................................... 5
2.1.2 Feasibility Study ........................................................................................... 5
2.1.3 Linear Sequential Model............................................................................... 6
2.1.4 Software Development Process Model:........................................................ 7
2.1.5 Background ................................................................................................... 8
2.2 Existing System................................................................................................... 8
2.3 Need of Website ................................................................................................... 8
2.4 System Features.................................................................................................... 8
2.5 Scope .................................................................................................................... 9
CHAPTER 3 ..................................................................................................................... 10

viii

3.1 Rational Unified Process.................................................................................... 10
3.2 Project Description............................................................................................. 10

3.2.1 User ............................................................................................................. 10
3.2.2 Customer ..................................................................................................... 11
3.2.3 Administrator interface ............................................................................... 11
3.3 Risk Factors........................................................................................................ 11
3.4 Global Factor...................................................................................................... 11
CHAPTER 4 ..................................................................................................................... 12
4.1 User / Customer.................................................................................................. 12
4.2 Use Case Name: View Home............................................................................. 13
4.3 Use Case Name: Products .................................................................................. 15
4.4 Use Case Name: Select category........................................................................ 17
4.5 Use Case Name: Log in...................................................................................... 19
4.6 Use Case Name: View About Us ....................................................................... 21
4.7 Use Case Name: View Contact Us..................................................................... 23
4.8 User Sitemap ...................................................................................................... 25
4.9 User View........................................................................................................... 26
CHAPTER 5 ..................................................................................................................... 27
5.1 User / Admin ..................................................................................................... 27
5.2 Administrator Log In.......................................................................................... 28
5.3 Use Case Name: Add ......................................................................................... 30
5.4 Use Case Name: View........................................................................................ 32
5.5 Use Case Name: Edit/Del................................................................................... 34
5.6 Admin Sitemap................................................................................................... 36
5.7 Admin view ........................................................................................................ 37
CHAPTER-6 ..................................................................................................................... 38
6.1 Database Design................................................................................................. 38
6.2 Final Database Tables ........................................................................................ 38
6.2.1 Admin table................................................................................................. 38
6.2.2 Cart table..................................................................................................... 38
6.2.3 Category table ............................................................................................. 38
6.2.4 Comment table ............................................................................................ 39

ix

6.2.5 Company table ............................................................................................ 39
6.2.6 Customer table ............................................................................................ 39
6.2.8 Model table ................................................................................................. 40
6.2.9 News table................................................................................................... 40
6.2.10 Page table ................................................................................................... 40
CHAPTER 7 ..................................................................................................................... 41
7.1 Website Development ........................................................................................ 41
7.2 Conceptual Design ............................................................................................. 41
7.2.1 Screen Resolution: ...................................................................................... 41
7.2.2 Page Margins: ............................................................................................. 41
7.2.3 Horizontal Scrolling:................................................................................... 41
7.2.4 Browsers: .................................................................................................... 41
7.2.5 Display Speed: ............................................................................................ 41
GLOSSARY ..................................................................................................................... 42
BIBLIOGRAPHY............................................................................................................. 44

x

CHAPTER 1

INTRODUCTION

1.1 Website

A website is a place on the internet where we can get the information and
knowledge about any topic of our own desire or choice related to site which we are
visiting. Or one can say that a person who is visiting a site is logically present on the
spot.

A website is a collection of Web pages, images, videos or other digital assets
that is hosted on one or several Web server(s), usually accessible via the Internet.

All publicly accessible websites are seen collectively as constituting the
"World Wide Web". The pages of websites can usually be accessed from a common
root URL called the homepage. The URLs of the pages organize them into a
hierarchy, although the hyperlinks between them control how the reader perceives the
overall structure and how the traffic flows between the different parts of the sites.

Some websites require a subscription to access some or all of their content.
Examples of subscription sites include many business sites, parts of many news sites,
academic journal sites, gaming sites, message boards, Web-based e-mail, services,
social networking website, and sites providing real-time stock market data.

1.2 Overview

Organized by function a website may be
 a personal website
 a commercial website
 a government website
 a non-profit organization website

It could be the work of an individual, a business or other organization and is
typically dedicated to some particular topic or purpose. Any website can contain a
hyperlink to any other website, so the distinction between individual sites, as
perceived by the user, may sometimes be blurred.

1

1.3 What information does it provide?

A website should provide each and everything for which purpose it is being
developed. Through a website it has become easier for us to get the information of
any kind and also to communicate with concerned person.

For a common person (non-IT professional) a website is most comprehensive
reliable media by which he/she can access easily everywhere in the world. As for
related to our own requirement, nothing is out of reach. We should say a website is a
media on the net by which a world is becoming as small place (global village) as if we
are present in the same place at the same time. Not only for a professional computer
user but for a non-IT professional a website is more useful and easiest way to get in
touch over the world. Just by putting the site of our own choice can get all the
information related to that particular field.

For example for a doctor, it has become easier to discuss different problems
and share his/her knowledge with others.

1.4 Websites as businesses

Turning a website into an income source is a common practice for web-
developers and website owners. There are several methods for creating a website
business which fall into two broad categories, as defined below.

1.5 Content based sites

Some websites derive revenue by selling advertising space on the site (see
contextual ads). Typically such a site will not sell products or services to its users, but
instead will provide information or other content, usually for free. This is a similar
model to a free magazine or newspaper, which derives revenue from the advertisers
who pay to appear alongside the useful content. However, with a website, the
advertising revenue earned may be based on the number of times viewers click on the
ad, or the number of times the page containing the ad is seen by a viewer. There is a
wide range of monetizing used on such sites and the sites themselves are actively
traded and bought and sold as going concerns.

1.6 Product or service based sites

Some websites derive revenue by offering products or services. In the case of
e-commerce websites, the products or services may be purchased at the website itself,
by entering credit card or other payment information into a payment form on the site.

2

While most business websites serve as a shop window for existing brick and mortar
businesses, it is increasingly the case that some websites are businesses in their own
right; that is, the products they offer are only available for purchase on the web.

Guides have been published which explain how to create a variety of types of
websites including those in both the above categories.

Websites occasionally derive income from a combination of these two
practices. For example, a website such as an online auctions website may charge the
users of its auction service to list an auction, but also display third-party
advertisements on the site, from which it derives further income.

1.7 Personal web pages

World Wide Web pages created by an individual to contain content of a
personal nature. The content can be about that person or about something he or she is
interested in. Personal web pages can be the entire content of a domain name
belonging to the person (which would then be a personal website), or can be a page or
pages that are part of a larger domain on which other pages are located - an example
of one such larger site is GeoCities. Another example would be a student's website for
school. Personal web pages are often used solely for informative or entertainment
purposes. Defining personal web page is difficult, because many domains or
combinations of web pages that are under the control of a single individual can be
used by the individual for commercial purposes, ranging from just the presentation of
advertising, to electronic commerce: the sale of goods, services or information; in fact
eBay began as the personal web page of Pierre Omidyar.

Personal web pages may be as simple as a single page or may be as elaborate
as an online database with gigabytes of data. Many Internet service providers offer a
few megabytes of space for customers to host their own personal web pages.

The content of personal web pages varies and can, depending on the hosting
server, contain anything that any other websites do. However, typical personal web
pages contain images, text and a collection of hyperlinks. Many can contain
biographical information, résumés, and blogs. Many personal pages will include
information about the author's hobbies and pastimes, and information of interest to
friends and family of the author.

3

1.8 Motivations

Many people maintain personal web pages because they are the most effective
medium to express their opinions or creative endeavors that, otherwise, simply would
not have an outlet. These types of sites may contain short fiction such as short stories
or samples of artwork. Other netizens view the concept of personal web pages with a
more metaphysical bent, placing value in the concept of owning space in and
"residing" in cyberspace and on the World Wide Web. This can also extend to the
ownership of personal domain names and the associated personal web pages and e-
mail addresses connected to those domains, although with the advent of affordable
web hosting fewer people own or manage their own personal servers. Currently, the
vast majority of casual internet users tend to utilize personal web pages included in
the free services provided by social networking sites such as MySpace and Blogger.
Blogging is an emerging trend and has simplified the process of creating a space of
one's own.

1.9 Sites of academics

Academic professionals (especially at the college and university level) are
often given space for creating and storing personal web documents, including
personal web pages, on the sites of their employers.

1.10 Criticisms

A common pejorative term for a personal web page is vanity site. This term is
often used by other internet users who consider personal web pages with no real
practical purpose or useful content to be pathologically narcissistic and a waste of
bandwidth.

4

CHAPTER 2

REQUIREMENT ANALYSIS

2.1 Preliminary Investigation

When the request was made For Final Project, our Project Guide Mr.
Muhammad Moosa assigned us the project since this was the time I had approached
him regarding my requirement of a project work. After reviewing the request I set
about with the first of the system activity: the preliminary investigation. I can divide
the task in three steps as...

2.1.1 Request Analysis
The request was studied carefully to assess what was exactly required. The

focus being on the task of determining precisely what originator wants.

2.1.2 Feasibility Study
An important outcome of the preliminary investigation is the determination

that the system requested is feasible. There are three aspects in the feasibility study of
the preliminary investigation.

Planning activities must be done before starting the project. Once the project is
started, project control begins. During planning, all the activities that management
needs to perform are planned. While during project control, the plan is executed and
updated. The project monitoring and control activities are spread over the
development life cycle of the software, and their basic goal is to ensure that the plan is
being followed.

The basic goal of planning is to look into the future, identify the activities that
need to be done to complete the project successfully, and plan the scheduling and
resource allocation for these activities.

The input to the planning activity is the requirements specifications. The
output phase is the plan, which is a document describing different aspects of the plan.

It is important to go through a series of predictable steps that helps you to
create a timely and high quality results. To provide stability, control and organization
for my project development I adopted a linear sequential model. It is also known as
‘classic life cycle’ or ‘water-fall model’.

5

It suggests a systematic, sequential approach to software development that
begins at analysis and progresses through design, coding and testing.

Analysis Designing Coding Testing

Fig. 4.1 the Linear Sequential Model

System/information
2.1.3 LineaErnSgeinqeueernintigal Model

 Analysis
To understand the nature of the project, I had discussions with my technical head
about the Online Shopping Site. As a result of these discussions, I analyzed the
information domain for the project. I also analyzed the current “Online Shopping.

 Design
Site design is actually a multi step process that focuses on data structure, Site

architecture, Language and procedural details.
 As a data structure design - database design is very crucial part of
developing a Online Shopping System. I designed different tables as per
requirement analysis. I also decided the fields of a record, primary key for the
database, field according to which the database should be sorted etc.
 As a Site architecture design – I used different templates for
developing a Online Shopping site. The biggest benefit is distribution and
support of the applications. Basically there are 2 templates in this application.
Admin Site
User Site
Coding
The design must be a translated into a functional site. The code generation step

performs this task. I decided to use PHP language, HTML, JAVA Script and
Adobe Dreamviewr to accomplish code generation.

6

 Testing
Once code has been generated, program testing begins. The testing process

focuses on the logical internals of the project, ensuring that all statement had been
tested.

2.1.4 Software Development Process Model:
The goal of any development effort is to produce some product. A development

process is a set of activities, together with an ordering relationship between activities,
which if performed in a

 Relationship, will procedure the desired product. A process model is an
abstract representation of a development process.
 In a software development effort, the goal is to produce high quality
software.

The development process is, therefore the sequence of activities that will
produce such software. A software development process model specifies how
these activities are organized in the entire software development effort.
 The purpose of specifying a development process model is to suggest an
overall process for developing software.
 A simplest process model is the waterfall model, which states that are
phases are organized in a linear order. A project begins with a feasibility study.
On successfully demonstration the feasibility of the project, the requirement
analysis and project planning begins. The design starts after the requirements
analysis is complete, the code is integrated and testing is done. On successfully
testing, the system is installed. After this, the regular operation and maintenance
of the system takes place.
 There are some other model also, via. Prototyping, iterative
enhancement, the spiral model etc. the basic idea behind prototyping is that
instead of freezing the requirements before any design of coding can proceed, a
throw away prototype is built to help understand the requirements.
 Development of prototype undergoes design, coding, and testing. But each
of these phases is not done in a formal manner. By using this prototype, the client
can get a feel of the system, since the interactions with the prototype helps client
gets a better understanding of the requirements.
 Prototyping is an attractive idea for complicated and large systems for
which there is not existing manual process.

7

2.1.5 Background
The Internet is changing every foundation of private and business life and the

world website is a key factor in this revolution. Establishing a website can be one of
the most important business moves you make and when website is about education it
should be according to the need. Because of the enormous potential and significant
investment involved, it is essential that you make this move carefully. This part of
document provides project specifications and discusses the feasibility study of
shopping website. It will provide scope and main goal of system.

Website is one of the main sources of knowledge these days for any person but
fortunately we don’t have such source through which user or customer can enhance,
share their knowledge & skills with others. The input of this document is the result of
survey, based on customer’s views & preliminary prototype work done by me.

2.2 Existing System

The existing system of shopping center is not computer based. All takes from
inventory to customer‘s shopping are performed manually .There is not any feature
that can generate quick report and add customer. Till there is no computer base
system to provide quick calculation for customers the system has been generated to
store the information of customers as it provides convenience to the administrator that
he can easily add the products view them and can check the record of all customers
immediately.

2.3 Need of Website

First there is a lot of paper work in order to associate different section of
shopping .like report, customer‘s record. Extra forms and fields that isn’t customer are
facing first time products of second time. If second time then Existing report of that
customer etc.

Secondly in order to check previous status regarding products or customer ‘s
information etc. the reports are found registers and now it will be done just by
searching process on computer and product can be assign to any customer through
computer against each product.

Thirdly: to get each and every information rapidly and perfect on time.

2.4 System Features

With the discussion between administrators we have agreed on the following

system features.

8

1. The system must have ability to add the customer’s record in a
database and whenever administrator wants to retrieve that data it is very easy
for him to view his customers.
2. Shopping website is dynamic so he can access it any where he wants
to.
3. Customer can also use this site with its login and password and has
access to see new brands of products.
All the users of the website are given special information about latsest brands
of different products through the static page view.

2.5 Scope

This document describes:-
1. The approach and work associated with developing the system.
2. Provides estimated time lines.

9

CHAPTER 3

ANALYSIS AND DESIGN

3.1 Rational Unified Process

The rational unified process is a software development process that provides a
disciplined approach to assigning tasks and responsibilities within a development
organization. Here is a brief description of the process,

This Iterative, risk driven process is divided into four primary phases.
1. Inception
2. Elaboration
3. Construction
4. Transition

3.2 Project Description

In doctor project there are three fields of interest

1. User
2. Customer
3. Administrator Interface

Figure

Adminstrator Customer

User

3.2.1 User
Here we will describe how a user interacts with web site.

When user enters URL in browser then first page welcomes the user and gives
summary about customer and its services. From this page user can move to any other
link. It contains different links for navigation of site. Now we describe the links one
by one.

10

3.2.2 Customer
A customer is client, buyer or purchaser is usually used to refer to a current

buyer or user of the product of an individual or an organization called supplier, seller
or vendor. This is typically through purchasing or renting goods or services.
3.2.3 Administrator interface

Here we will describe how Administrator interacts with web site.
For the security reason I have hidden the Administration interface and only
Administrator (User and Customer) knows how he reached on this.

When Administrator enters, he will have to enter on web space allowed which is
specific for administrator, where he will provide his Log in ID and Password, on
verification Administration area on web where he can administrate the info like add
new product, view product, add new company of product and new models etc.

3.3 Risk Factors

 The site has to be easy for non-technical people to use.
 What if the system is immediately flooded with the users?

3.4 Global Factor

 In most part of the world, all adults spent most of their time on internet. They
have limited time available for reading books and are usually willing to pay earn as
much as knowledge from this media.
 Online shopping information.
 Other shopping sites provide 24- hour access, response time ranging from
overnight to very few days.

11

CHAPTER 4
CUSTOMER

4.1 User / Customer View Home

View Products

View About Us

View Contact Us

12

4.2 Use Case Name: View Home

Description:
 This use case describes the process to visit the main Page of the
application.

Actors:
 Customer / User

Use Case Diagram

User Home

Pre Conditions:
1- User or Member must write URL in the browser access the home
page

Flow of Events
Primary Scenario:-
1. User or Member will open the browser
2. User or Member enter the correct URL
3. User or Member will access the main page
4. User or Member can access the menu link of the application
5. This use case ends
Exceptions: The required URL not provided
Secondary Scenario:
1. User can cancel operation at any time

Post Condition:
The record of the application deleted.

13

Activity diagram of view Home

Start

Enter the Shopping site URL
Home Page
Select Home

View Home Page

End

14

4.3 Use Case Name: Products

Description:
 This use case describes the process to get information about products.

Actors:
 Customer / User

Use Case Diagram:

Customer’s shopping

User

Pre Conditions:
 User must view the Shopping site.

Flow of Events:

Primary Scenarios:
 Use case begins when user clicks Product’s link.
 Product page will be shown to user.

Secondary Scenarios:
 User does not request for page and “cancel” the activity.

Post Conditions:
 User closes the browser.

15

Activity diagram of Products

Start

Enter the Shopping site URL
Home Page
Select Products

View Products Page

End

16

4.4 Use Case Name: Select category

Description:
 This use case describes the process toselct Categories of products.

Actors:
 Customer / User

Use Case Diagram:

Categories

User

Pre Conditions:
 User must view the Shopping site.

Flow of Events:

Primary Scenarios:
 Use case begins when user clicks Category’s link.
 Product page will be shown to user.

Secondary Scenarios:
 User does not request for page and “cancel” the activity.

Post Conditions:
 User closes the browser.

17

Activity diagram of Select Category

Start

Enter the Shopping site URL
Home Page
Select Categorys

View Categorized Products

End

18

4.5 Use Case Name: Log in

Description:
 This use case describes the process by which user will log in on the
web site.

Actors:
 Customer / User

Use Case Diagram:

User Customer Log In

Pre Conditions:

 User customer must view the Shopping web site.
Flow of Events:
` Primary Scenarios:

 The use case starts when the user clicks on Login link.
 User will enter login name and password.
 The system will verify information..
Secondary Scenarios:
 Information not valid.
 user closes the browser
Post Conditions:
 User will log in.

19

Activity diagram of Log in:

Start

Enter the Shopping site URL
Home Page
Select Log in

View login page
Enter Email Id n Pass

End

20

4.6 Use Case Name: View About Us

Description:
 This use case describes about products.

Actors:
 Customer / User

Use Case Diagram: About Us

User About Us

Pre Conditions:
 User must view the shopping web site.

Flow of Events:
Primary Scenarios:
 Use case begins when user clicks About Us link.
 About us page will be shown to user.
Secondary Scenarios:
 User does not “cancel” the activity.

Post Conditions:
 User closes the browser.

21

Activity diagram of view About Us:

Start

Enter the Shopping site URL
Home Page
Select About Us

View About Us Page

End

22

4.7 Use Case Name: View Contact Us

Description:
 This use case describes the process to get information about us.

Actors:
 Customer / User

Use Case Diagram:

User Contact Us

Pre Conditions:
 User must view the Shopping site.

Flow of Events:
Primary Scenarios:
 Use case begins when user clicks About us link.
 About us page will be shown to user.
Secondary Scenarios:
 User does not request for page and “cancel” the activity.

Post Conditions:
 User closes the browser.

23

Activity diagram of view Contact Us:

Start

Enter the Shopping site URL
Home Page

Select Contact us
View contact Us Page

End

24

4.8 User Sitemap

User
Home

Register Log in/ Products About Us Contact Us
logout All Products

Category

Log In Needed Product User Logged In
info
Add to Cart

25

4.9 User View

26

CHAPTER 5
ADMIN

5.1 User / Admin

Add category Home Login
add Company Administrator
Add Model
Add Product
Add Customer

Add Pages

Add News
Logout

27

5.2 Administrator Log In

Description:
 This use case describes the process by which user administrator will
log in on the web site.

Actors:
 User Administrator

Use Case Diagram:

User Administrator User Log In

Pre Conditions:
 User Administrator must view the Shopping web site.

Flow of Events:
Primary Scenarios:
 The use case starts when the administrator enters secret URL.
 The system will display login screen.
 User Administrator will enter login name and password.
 The system will verify information.
 Main menu will be shown to the system.
Secondary Scenarios:
 Information not valid.
 Administrator closes the browser

Post Conditions:
 Administrator will log in.

28

Activity diagram of Log in:

Start

Enter the Secret URL
Login Page

Enter Email Id n Pass
View Home

` End



29

5.3 Use Case Name: Add

Description:
 This use case describes the process to enter the data..

Actors:
 User Administrator

Use Case Diagram:

Administrator Add New

Pre Conditions:
 Administrator must view the web site.

Flow of Events:
Primary Scenarios:
 Use case begins when administrator clicks Add link.
 Add new page will be shown to administrator.
Secondary Scenarios:
 User does not request for page and “cancel” the activity.

Post Conditions:
 User closes the browser.

30

Activity diagram of Add New

If Not Login Start

Enter the secret URL
If Log In
Admin Page

Select The
Add NewLink

Add new data

Add The View The
Information Information

End

31

5.4 Use Case Name: View

Description:
 This use case describes the process to view the data..

Actors:
 User Administrator

Use Case Diagram:

Administrator View data

Pre Conditions:
 Administrator must view the web site.

Flow of Events:
Primary Scenarios:
 Use case begins when administrator clicks View link.
 Information page will be shown to administrator.
Secondary Scenarios:
 User does not request for page and “cancel” the activity.

Post Conditions:
 User closes the browser.

32

Activity diagram of View

Start

Enter the secret URL

If Not Login If Log In

Admin Page

Select The
View Link

View data

End

33

5.5 Use Case Name: Edit/Del

Description:
 This use case describes the process by which administrator will edit/
delete member on the web site.

Actors:
 Administrator

Use Case Diagram:

Administrator Edit/delete

Pre Conditions:
 Administrator must view the Shopping web site.

Flow of Events:
Primary Scenarios:
 Use case begins when administrator clicks Edit/Delte link.
 View page will be shown.after action.

Secondary Scenarios:
 Information not valid.
 Administrator closes the browser

Post Conditions:
 Administrator will edit/delete.

34

Activity diagram of Edit/Del:

Start

If Not Login Enter the secret URL
If Log In

Admin Page

Select The
View Link

View data

Edit The Delete The
Information Information

End

35

5.6 Admin Sitemap

Admin
Login
Home

Admin Category Company Model Product Customer Pages News

Add View

Edit
Del

36

5.7 Admin view

37

CHAPTER-6
TECHNICAL & DATABASE DESIGN

6.1 Database Design

These activities shall consist of:
 Designing appropriate database structures to store those identified
persistent classes which identified during database design
 Defining techniques and strategies for storing and retrieving persistent
data in such a way that the performance criteria for the project are met.

6.2 Final Database Tables

Database tables and their relationships and constraints in SQL server view is
given below.
6.2.1 Admin table
This table has data for admin login

6.2.2 Cart table
This table has data for products user selected for cart

6.2.3 Category table
This table has data for different categories

38

6.2.4 Comment table
This table has data for user comments

6.2.5 Company table
This table has data for different companies added

6.2.6 Customer table
This table has data for user registration / login

6.2.7 Mobile table
This table has data for different products added

39

6.2.8 Model table
This table has data for different models of products

6.2.9 News table
This table has data for latest news

6.2.10 Page table
This table has data for Main Navigation Pages.

40