Database Design and Implementation

Database and Web Database Systems Individual Assignment Page 1 of 33
Level 2 Asia Pacific Institute of Information Technology 2014
Table of Contents
1.0 INTRODUCTION .......................................................................................................................... 2
1.1 System Requirement ................................................................................................................... 3
1.1.1 Software Requirement .......................................................................................................... 3
1.1.2 Hardware Requirement......................................................................................................... 4
2.0 Proposed System............................................................................................................................. 5
3.0 Entity Relationship Diagram........................................................................................................... 6
3.1 List of Entity types:..................................................................................................................... 6
3.2 List of Relationships: .................................................................................................................. 7
3.3 Entity Relationship Diagram:...................................................................................................... 7
4.0 Mapping ERD to Relational Model................................................................................................ 8
5.0 Normalization ................................................................................................................................. 9
5.1 FIRST NORMAL FORM (1NF)................................................................................................. 9
5.2 SECOND NORMAL FORM (2NF) ......................................................................................... 10
5.3 RELATIONS IN THIRD NORMAL FORM (3NF)................................................................. 10
6.0 Table Design & Structure ............................................................................................................. 11
7.0 SQL: DDL Statements .............................................................................................................. 14
8.0 SQL: DML Statements ................................................................................................................. 16
9.0 CRYSTAL REPORTS.................................................................................................................. 19
10.0 Toolbar........................................................................................................................................ 21
11.0 FORM DESIGN (SNAPSHOTS)............................................................................................... 23
12.0 SUMMARY................................................................................................................................ 32
13.0 REFERENCES ........................................................................................................................... 33

1.0 INTRODUCTION
E-commerce is fast gaining ground as an accepted and used business prototype. More and more
business houses are implementing web sites providing functionality for performing commercial
transactions over the web. It is reasonable to say that the process of shopping on the web is
becoming commonplace.
So, the main objective of this project is to develop a general purpose e-commerce store where user
can easily browse and search the mobile phones as per their choice. By computerizing it, it became
possible to overcome the limitations and make the system operations more efficient. The complexity
in handling data and records of the manual system got reduced and became easier by computerizing
the system.
Being more specific, this online mobile sale system can perform the basic functions like browsing
and searching of mobile phones. The users are required to register on the website for getting access
to the database and query result retrieval. Upon registration completion, each user has an account by
which they can view the whole system. The account contains complete information of the user
entered during the registration and allows the user to search mobile phones by different types like,
by latest phones available in the market, by price range that suits the user and also by the popular
company names. In this system, user can buy the mobile phones by providing some details like,
billing address, shipping address, and after confirming the order the user will have to chose the
payment type by which they want to pay the price of the phone i.e., either by Cash delivery or by
debit card. User will be getting the e-mail notification to their registered email-ID when the order
will get confirmed. User can also view their purchase history and can delete the history if required.
The master user of this system is the Administrator who can login using a master password and once
a user is authenticated as the admin, he/she can access and modify information stored in the database
of this system. This includes adding of mobile phones which are latest in the market, updating of the
phones in price or quantity and deleting the phones which gets outdated from the database.

1.1 System Requirement
System requirements are expressed in a software requirement document. The software requirement
specification (SRS) is the official statement of what is required of the system developers. This
requirement document includes the requirements definition and the requirement specification. The
software requirement document is not a design document. It should set out what the system should
do without specifying how it should be done. The requirement set out in this document is complete
and consistent.
The software specification document satisfies the following:
1. It specifies the external system behaviors.
2. It specifies constraints on the implementation.
3. It is easy to change.
4. It serves as reference tool for system maintainers.
5. It record forethought about the lifecycle of the system.
6. It characterizes acceptable response to undesired events.
1.1.1 Software Requirement
Software plays an important role in any project development. One should understand which software
to use which can be more compatible to use and handle both as a user and as an administrator. Being
the administrator, I have used Windows 7 as an operating system as it is more reliable and faster as
compared to other operating system. The other latest versions of operating system are not very good
as many users are still using Windows 7 and also very familiar to it.
So, the software’s used for the development of the system:
1. Front-end Tool: Google Chrome, Mozilla Firefox
2. Middle-end Tool: Microsoft Visual Studio 2010 with C#
3. Back-end Tool: Microsoft SQL Server 2008
4. Microsoft Office Visio 2007
5. Microsoft Office Word

1.1.2 Hardware Requirement
S. No. Hardware used Specification
1. Monitor LCD 15” screen (HP)
2. Keyboard Intex Wired
3. Mouse Intex Wired
4. Hard drive 40GB(gigabyte) hard drive
5. RAM 512 MB(megabyte) and above
6. Processor 2.6 GHz Intel Pentium IV and above
7. Graphics On board graphics card, 8MB(Megabyte)
8. System type 1GHZ(gigahertz)32-bit(x86), 64-bit(x64)

2.0 Proposed System
The e-commerce mobile sale system is a very vast system as it contains the details of all the mobiles
of various brands and also the database of all the features of mobile phones which will be very
difficult to be handled manually in the paper.
 The system contains unique user ID and password for both administrator and customer.
 The system will allow the customers to browse the system and can search the mobiles only
by using their unique ID.
 The system computerizes all data of the mobiles and also the details of administrator as well
as customers.
 Only administrator will be having the power of accessing the database of the system.
 Validation at the time of entering data, so no chance of duplication of data.
 Administrator will be keeping the data base up to date by regular updating.
 Security problem issues are solved by this automated system.
 Reducing the cost of maintaining system.
 To provide various report facility at the time of order confirmation.
 Cost effective and less manpower required.
The customer is privileged with the following services:
 Register as a customer by providing certain personal details.
 Can browse and search the mobiles in the store only by authenticated email-ID and
password.
 Shopping cart is provided to the customer for addition and deletion of the mobile.
 Purchase can be done in two types i.e., either by cash delivery or by debit card.
 An email-notification will be received after the payment confirmation.
 View all the purchase history and can even delete the history.
Administrator is privileged with the following services:
 Login as the master user using a master password.
 Add, update and delete the inventory and inventory details.

3.0 Entity Relationship Diagram
An entity-relationship (ER) diagram is a data modeling technique that creates a graphical
representation of the entities, and the relationships between entities, within an information system.
There are basically three main components which we consider while making ERD:
 The entity- Entity is a person, object, place or event for which we want to store information.
 The Attributes- Attributes are the properties of the entities and relationship. Attributes are
elementary pieces of information attached to an entity. Attributes are represented as oval.
 The relationship- A relationship is a named collection or association between entities or used to
relate two or more entities with some common attributes or meaningful interaction between the
objects. Degree of a relationship is indicated in 1, M and N form.
3.1 List of Entity types:
S. No Entity Attributes
1. Customer name, emailID, password
2. Admin emailID, password
3. Profile email, Name, Nationality, DOB, Education, Gender, Phone,
Occupation, Company, Work, Contact, Address
4. Inventory InventoryName, ModelNum, VendorName, Quantity, Date
5. Inventory_details ModelNum, Price, OS, Color, P_Camera, Internet, Sim, Network,
S_Size, S_type, S_Camera, Internal, Expand, Process, Torch, Music
6. Cart emailID, ModelNum, Quantity, Price
7. Purchase_details email_ID, model_no, qty, cost, dat

3.2 List of Relationships:
S. No Relation Type Entity Types Involved
1. Search Customer, Mobile
2. Edit Customer, Profile
3. Add Admin, Mobile
4. Manage Admin, Inventory
5. Has Mobile, features
6. added to Mobile, Cart
7. Place order Cart, Purchase_details
3.3 Entity Relationship Diagram:
Customer
name
emailID password
OS Color
has
search Mobile
Latest
By Price By Vendor
has
Inventory_
details
S_ Camera
P_Camera Internet
Network
Sim
Process
S_Size
Expand
Internal
S_type
Torch
Music
added to Cart
Price
emailID ModelNum
Quantity
Place
order
Purchase_details
email_ID
model_no
cost
qty
datAdmin
add
emailID password
manage
Inventory
VendorName
ModelNum
Quantity
Date
InventoryName
edit
Profile
Name
email
Nationality
DOB
Phone
Gender
Education
Company
Contact
Occupation
work
Address
1
M 1
M
NMedit
Profile
1
1
M 1
1
M
M
1
ModelNum
Price

4.0 Mapping ERD to Relational Model
Step 1: Mapping of Strong Entity Type
S. No Entity Type Relation
1. Customer Cutomer (name, emailID, password)
2. Admin Admin(emailID, password)
3. Inventory Inventory (InventoryName, ModelNum, VendorName, Quantity, Date)
Step 2: Mapping of Weak Entity Type:
S. No Entity Type Relation
1. Profile Profile (email, Name, Nationality, DOB, Education, Gender, Phone,
Occupation, Company, Work, Contact, Address)
2. Inventory_details Inventory_details (ModelNum, Price, OS, Color, P_Camera, Internet,
Sim, Network, S_Size, S_type, S_Camera, Internal, Expand, Process,
Torch, Music)
Step 3: Mapping Of 1:M Relationship:
Relation Entities Approach Relation
manage Admin, Inventory Primary Key Inventory (InventoryName, ModelNum,
VendorName, Quantity, Date)
add Admin, Mobile Primary Key Admin (emailID, password)
has Mobile,
Inventory_details
Inventory_details (ModelNum, Price, OS,
Color, P_Camera, Internet, Sim, Network,
S_Size, S_type, S_Camera, Internal, Expand,
Process, Torch, Music)
Place_order Cart,
Purchase_details
Foreign Key Cart (Price, emailID, ModelNum, Quantity)
Purchase_details (email_ID, model_no, qty,
cost, dat)
Step 3: Mapping Of M:N Relationship:
Relation Entities Approach Relation
search Customer, Mobile Cross-reference Customer_search_Mobile(Latest, By Price,
By Vendor)

5.0 Normalization
Normalization is the process of organizing data in a database. This includes creating tables and
establishing relationships between those tables, according to rules designed both to protect the data
and to make the database more flexible by eliminating redundancy and inconsistent dependency.
Purpose: Normalization is a technique for producing a set of relations with desirable properties,
given the data requirements of an enterprise. Three most commonly used normal forms are first
(1NF), second (2NF) and third (3NF) normal forms. Based on functional dependencies among the
attributes of a relation a relation can be normalized to a specific form to prevent possible occurrence
of update anomalies.
Insertion anomaly
: Inability to add data to the database due to absence of other data.
Deletion anomaly
: Unintended loss of data due to deletion of other data.
Update anomaly
: Data inconsistency resulting from data redundancy and partial update
Normal Forms
: These are the rules for structuring relations that eliminate anomalies.
5.1 FIRST NORMAL FORM (1NF)
A relation is said to be in first normal form if the values in the relation are atomic for every attribute
in the relation. By this we mean simply that no attribute value can be a set of values or, as it is sometimes expressed, a
repeating group.
Relations already in 1NF
Customer
Inventory
Profile
Inventory_details
Customer_search_mobile
Relations not in 1NF
Admin

5.2 SECOND NORMAL FORM (2NF)
A relation is said to be in second Normal form, it is in first normal form and it should satisfy any one
of the following rules.
 Primary key is not a composite primary key
 No non key attributes are present.
 Every non key attribute is fully functionally dependent on full set of primary key.
RELATIONS IN 2NF
Customer
Admin
Inventory
Profile
Inventory_details
5.3 RELATIONS IN THIRD NORMAL FORM (3NF)
A relation is said to be in third normal form if there exists no transitive dependencies.
RELATIONS IN 3NF
Customer
Admin
Inventory
Profile
Inventory_details

6.0 Table Design & Structure
1) Register
CONSTRAINTS:
PRIMARY KEY: emailID
FOREIGN KEY: ---
2) Inventory
CONSTRAINTS:
PRIMARY KEY: ModelNum
FOREIGN KEY: ---

3) Inventory_details
CONSTRAINTS:
PRIMARY KEY: ---
FOREIGN KEY: ---

4) Profile
CONSTRAINTS:
PRIMARY KEY: ---
FOREIGN KEY: ---
5) Cart
CONSTRAINTS:
PRIMARY KEY: emailID, ModelNum, Quantity
FOREIGN KEY: ---

7.0 SQL: DDL Statements
DDL is abbreviation of Data Definition Language. It is used to create and modify the structure of
database objects in database.
Examples: CREATE, ALTER and DROP statements
1) Register
CREATE TABLE [dbo].[register] ( [name] [varchar] (20) NOT NULL, [emailID] [varchar] (25)
NOT NULL, [password] [varchar] (20) NOT NULL, PRIMARY KEY [emailID] )
2) Inventory
CREATE TABLE [dbo].[Inventory] ( [InventoryName] [varchar] (50) NOT NULL, [ModelNum]
[varchar] (50) NOT NULL, [VendorName] [varchar] (50) NOT NULL, [Quantity] [int] NOT
NULL, [Date] [varchar] (20) NOT NULL, PRIMARY KEY [ModelNum] )
6) Purchase_details
CONSTRAINTS:
PRIMARY KEY: email_ID, model_no, dat
FOREIGN KEY: ---

3) Inventory_details
CREATE TABLE [dbo].[Inventory_details] ( [ModelNum] [varchar] (50) NOT NULL, [Price]
[varchar] (20) NOT NULL, [OS] [varchar] (50) NOT NULL, [Color] [varchar] (10) NOT NULL,
[P_Camera] [varchar] (15) NOT NULL, [Internet] [varchar] (15) NOT NULL, [Sim] [varchar]
(10) NOT NULL, [Network] [varchar] (10) NOT NULL, [S_Size] [varchar] (15) NOT NULL,
[S_type] [varchar] (15) NOT NULL, [S_Camera] [varchar] (15) NOT NULL, [Internal] [varhcar]
(15) NOT NULL, [Expand] [varchar] (15) NOT NULL, [Process] [varchar] (25) NOT NULL,
[Torch] [varchar] (5) NOT NULL, [Music] [varchar] (5) NOT NULL )
4) Profile
CREATE TABLE [dbo].[Profile] ( [email] [varchar] (25) NOT NULL, [Name] [varchar] (20)
NOT NULL, [Nationality] [varchar] (10) NOT NULL, [DOB] [varchar] (20) NOT NULL,
[Education] [varchar] (50) NOT NULL, [Gender] [varchar] (10) NOT NULL, [Phone] [varchar]
(30) NOT NULL, [Occupation] [varchar] (20) NOT NULL, [Company] [varchar] (50) NOT
NULL, [Work] [varchar] (30) NOT NULL, [Contact] [varchar] (10) NOT NULL, [Address]
[varchar] (50) NOT NULL )
5) Cart
CREATE TABLE [dbo].[cart] ( [emailID] [varchar] (25) NOT NULL, [ModelNum] [varchar]
(50) NOT NULL, [Quantity] [int] NOT NULL, [Price] [varchar] (20) NULL, PRIMARY KEY
[emailID], [ModelNum], [Quantity] )
6) Purchase_details
CREATE TABLE [dbo].[Purchase_details] ( [email_ID] [varchar] (25) NOT NULL, [model_no]
[varchar] (10) NOT NULL, [qty] [int] NOT NULL, [cost] [int] NOT NULL, [dat] [varchar] (40),
PRIMARY KEY [email_ID], [ model_no] , [dat] )

8.0 SQL: DML Statements
DML is abbreviation of Data Manipulation Language. It is used to retrieve, store, modify, delete,
insert and update data in database.
Examples: SELECT, INSERT, UPDATE, DELETE and INNER JOIN statements
SELECT STATEMENTS
Login of Customer and Admin – This step is used to login the customer so that he can browse and
search the mobile phones in the store. Admin can manage the store only after the login with the
master email-ID and password.
"select * from register where emailID =@username and password=@password"
Profile of Customer – In this, the customers will retrieve the email-ID from the registration page
and then the user of the store can update their profile.
"select * from register where emailID =@username"
INSERT STATEMENTS
Registration of Customer– In this, the customer who are currently not the user of the store have to
do registration first, so that they can get the username and password for browsing and searching
the mobile phones in the store.
"insert into register values('" + txt_name.Text + "','" + txt_email.Text + "','" + txt_password.Text +
"')"
Add Inventory by the Admin– In this, the admin can add the mobile phones in the store which are
either out of stock, or latest launched in the market for the customer.
"insert into Inventory values('" + txt_invent.Text + "','" + txt_model.Text + "','" +
ddl_vendor.SelectedItem + "','" + ddl_quantity.SelectedItem + "','" + dt + "')"
Add Inventory Details by the Admin– In this, the admin can add the mobile phone details which
will be helping the customer while searching the mobile phones in the store very easily.
"insert into Inventory_details values('" + txt_model.Text + "','" + txt_price.Text + "','" +
ddl_os.SelectedItem + "','" + ddl_color.SelectedItem + "','" + ddl_pcamera.SelectedItem + "','" +
ddl_internet.SelectedItem + "','" + ddl_sim.SelectedItem + "','" + ddl_network.SelectedItem + "','"

+ ddl_size.SelectedItem + "','" + ddl_screen.SelectedItem + "','" + ddl_scamera.SelectedItem + "','"
+ ddl_internal.SelectedItem + "','" + ddl_expand.SelectedItem + "','" + ddl_process.SelectedItem +
"','" + ddl_torch.SelectedItem + "','" + ddl_music.SelectedItem + "')"
Purchase Details by Customer– In this, after making the payment for the purchased mobile phone
from the store, the customer will get the order details of the item he purchased.
"insert into Purchase_details values('" + lbl_user.Text + "','" + model_no + "','" + qty + "','" + cost
+ "','" + dat + "')"
Profile Updating by Customer– In this, the customer who is the user of the store can update their
profile.
"insert into Profile values('" + email +"','"+ txt_name.Text + "','" + ddl_nation.SelectedItem + "','"
+ txt_dob.Text + "','" + ddl_edu.SelectedItem + "','" + ddl_gender.SelectedItem + "','" +
txt_phone.Text + "','" + txt_occ.Text + "','" + txt_com.Text + "','" + workduration + "','" +
txt_contact.Text + "','" + txt_address.Text + "')"
Items Add to Cart by Customer– In this, the customer can add the mobile phones to the shopping
cart if they wish to purchase that mobile in future or after some time.
"insert into cart values('" + lbl_user.Text + "','" + lbl_model.Text + "','" + ddl_quantity.Text + "','"
+ price + "')"
UPDATE STATEMENTS
Update Inventory by Quantity by Admin– In this, the admin can update the mobile phones in the
store by increasing or decreasing the quantity as per the demands of the customer.
"update Inventory set Quantity=@qty where ModelNum = @model"
Update Inventory by Price by Admin– In this, the admin can update the mobile phones in the store
by increasing or decreasing the price according to the market demands.
"update Inventory_details set Price=@price where ModelNum = @model"

DELETE STATEMENTS
Delete Inventory by Quantity by Admin– In this, the admin can delete the mobile phones which are
outdated in the market or whose demands are not very high.
"delete from Inventory where ModelNum = @model"
INNER JOIN STATEMENTS
Updating the Inventory by Admin– In this, the admin can update the mobile phones by quantity and
price after selecting the vendor name and model number from two different tables, i.e. Inventory
and Inventory details.
" SELECT InventoryName,VendorName,Quantity,Price FROM Inventory INNER JOIN
Inventory_details ON Inventory.ModelNum=Inventory_details.ModelNum WHERE
Inventory_details.ModelNum=@model"

9.0 CRYSTAL REPORTS
1) Inventory Report
Description:
The INVENTORY REPORT displays the details of the inventory added by the admin in the store. It
consists of the inventory name, model number, vendor name, quantity and date of the mobile phones
added to the store.
When the admin wants to see the detailed list of all the mobile phones added along with the date, this
report will be helpful so that by viewing this report, any required changes/modifications can easily
be made to the database.

2) Purchase History Report
Description:
The report PURCHASE HISTORY displays details of all the mobile phones purchased by that
particular customer. It consists of the email ID, model number, quantity, price and date of the
purchased item.
When the customer wants to see the detailed list of mobile phones along with the purchased date,
this report will be helpful so that by viewing this report, customer can easily delete the purchase
history as per the choice.

10.0 Toolbar
A toolbar has been provided in the customer’s view level which consists of icons like Home, Profile,
Search Mobiles, View Cart and the Purchased History which serves as a link to the respective pages.
It will help the customer to find all the process easily. If Home icon is clicked, it redirects to the
Home page of the customer and similarly the link button will allow the customer a proper logout.
Customers can
easily logout of the
website by clicking
this icon.
By clicking this icon,
customers can easily view
the purchased history
done by his ID along with
the date so that he can
delete the history if
needed.
customers can easily view
the shopping cart, if he had
added any mobile phones
for the future purchase and
then after he can make
payment for the same.
customers can easily search the
mobile phones by latest phones
available in the store or by
price range that suits their
budget or by selecting the
vendor name of their choice.
By clicking this icon, the
customers can easily update
their profile as per their
choice
By clicking this
icon, the
customers can
easily view the
home page

A toolbar has been provided in the admin view level which consists of icons like Home, Add
Inventory and Update Inventory which serves as a link to the respective pages. It will help the admin
to find all the process easily. If Home icon is clicked, it redirects to the Home page of the admin and
similarly the link button will allow the admin a proper logout.
admin can easily update
or delete the mobile
phones available in the
store.
admin can easily add
the inventory and
inventory details in the
store.
By clicking this
icon, the admin
can easily view
the home page
Admin can easily
logout of the website
by clicking this icon.

11.0 FORM DESIGN (SNAPSHOTS)
1) REGISTRATION – USER
Description: Any user coming to this page can register to the website by providing required
details. The details being provided should not violate the validation rules otherwise registration
will not be allowed.
2) LOGIN PAGE – ADMIN, USER
Description: Registered users can login to the website by using a specific emailID and password.
This will redirect the user to a different view level where the user will be availed various services
like searching, purchasing or adding and updating the inventory.

3) UPDATE PROFILE – CUSTOMER
Description: Registered users can update their profile in which the email-ID will be same but
other necessary details can be changed or updated. All the fields should be filled otherwise the
updating will be failed, as there is proper validation in every field. After click on submit button,
message will appear that Profile updated successfully.
4) SEARCH MOBILES – CUSTOMER
Description: Registered users can easily browse and search the mobile phones by Latest phones
available in the store or by price range or by vendor name.

5) SEARCH MOBILES BY LATEST – CUSTOMER
Description: Registered users can easily browse and search the mobile phones just by clicking on
the Latest radio-button, which will show all the latest phones available in the store.

6) GET DETAILS BY LATEST – CUSTOMER
Description: Registered users can easily get the details of the mobile phone selected just by
clicking on the Get Details button, which will show all the features of the mobile with image
available in the store.
7) ADD TO CART BY LATEST – CUSTOMER
Description: Registered users can easily add the mobile phone selected to the shopping cart just
by clicking on the ADD TO CART link-button, which will directly show the message that item is
added to the cart.

8) ADDED TO SHOPPING CART – CUSTOMER
Description: Registered users can easily view that the mobile phone selected is added to the
shopping cart after clicking the View Cart icon, which also has Remove link-button by which
customer can remove the item selected in the cart. It is also showing the estimated total value of the
item selected. There is a Place Order button by which customer can place order for the selected item.
9) DETAILS OF THE ADDRESS – CUSTOMER
Description: Registered users have to provide the details of the address like billing address and
shipping address for making payment. There is a check-box which after clicking the shipping
address will be same as billing address. There is a payment method by which customer wants to do
the payment i.e. Cash on Delivery or by Debit Card. No field should be left blank as there is
validation, which will result in the failure of the payment after clicking the Confirm Payment button.

10) CONFIRM PAYMENT BY CASH DELIVERY – CUSTOMER
Description: After filling all the necessary details correctly, registered users have to click the
Confirm Payment button which will show the message that Payment is done successfully and the
order details will directly be sent to the respective email-ID.
11) ORDER DETAILS – CUSTOMER
Description: After showing the message that Payment is done successfully, the order details will
appear providing all the details of the purchased item.

12) E-MAIL NOTIFICATION – CUSTOMER
Description: After showing the message that Payment is done successfully, email notification will be
directly sent to the customer’s email-ID.
13) NO ITEM ADDED TO CART – CUSTOMER
Description: If no item is added to the cart, then this screen will appear after clicking View Cart
icon.
14) PURCHASE HISTORY – CUSTOMER
Description: After clicking on the purchase-history icon, customer can view the past history of all
the purchased items and can delete the history if needed.

15) ADD INVENTORY – ADMIN
Description: After clicking on the Add Inventory icon, admin can add the mobile phones and also
the details respective of that mobile.
16) ADDING OF INVENTORY – ADMIN
Description: After filling all the necessary details of the mobile phones on click of the Submit
button, admin can add the mobile phone in the store and the database for the customer. As soon as
the submit button is clicked, the message will appear that Inventory added successfully.

17) UPDATING OF INVENTORY – ADMIN
Description: After clicking on the Update Inventory icon, Admin can update the details of the
mobile by price or by quantity. After clicking on the update button, the message will appear that
Updated Successfully.
18) DELETING OF INVENTORY – ADMIN
Description: After clicking on the Delete button, Admin can delete that particular mobile from the
database which gets outdated in the market or if not in demand. After clicking on the Delete button,
the message will appear that Deleted Successfully.

12.0 SUMMARY
The Internet has become a major resource in modern business, thus electronic shopping has gained
significance not only from the entrepreneur’s but also from the customer’s point of view. “Website
design is like a shop interior, where everything should look perfect and interactive which attracts
more users. So, we have designed the project to provide the user with easy navigation and retrieval
of data as much as possible.
In this project, the user is provided with an e-commerce web site that can be used to buy mobile
phones online. To implement this as a web application we used ASP.NET as the Technology.
ASP.NET has several advantages such as enhanced performance, scalability, built- in security and
simplicity. To build any web application using ASP.NET we need a programming language such as
C#, VB.NET and so on. C# was the language used to build this application. MySQL was used as
back-end database since it is one of the most popular open source databases, and it provides fast data
access, easy installation and simplicity.
A good shopping cart design must be accompanied with user-friendly shopping cart application
logic. It should be convenient for the customer to view the contents of their cart and to be able to
remove or add items to their cart. The shopping cart application described in this project provides a
number of features that are designed to make the customer more comfortable. This project helps in
understanding the creation of an interactive web page and the technologies used to implement it. The
building of the project has given me a precise knowledge about how ASP.NET is used to develop a
website, how it connects to the database to access the data and how the data and web pages are
modified to provide the user with a shopping cart application.

13.0 REFERENCES
 Websites
1) SQL INNER JOIN
w3cschoolsadmin. (2013). SQL INNER JOIN. Available:
http://www.w3schools.com/sql/sql_join_inner.asp Last accessed 4th April 2014.
2) api_user. (2008). SQL server 2008 advantages. Available:
http://www.scribd.com/doc/7256095/SQL-Server-2008-Advantages Last accessed 12th
April 2014
3) INSERT STATEMENTS IN SQL BY C#
marc. (2012). write insert query in c#. Available:
http://stackoverflow.com/questions/9954900/how-to-write-insert-query-in-c Last accessed
14th April 2014.
4) GRIDVIEW DATABINDING
Msoft. (2013). GridView.DataBind Method. Available: http://msdn.microsoft.com/en-
IN/library/fkx0cy6d.aspx Last accessed 12th April 2014.
5) SQL UPDATE
w3cschoolsadmin. (2013). SQL UPDATE. Available:
http://www.w3schools.com/sql/sql_update.asp Last accessed 15th April 2014.
6) FOREGIN KEY CONSTRAINT
w3cschoolsadmin. (2013). SQL FOREIGN KEY Constraint. Available:
http://www.w3schools.com/sql/sql_foreignkey.asp Last accessed 18th April 2014.
 Books
7) Pearson Education Limited, “The Essence of DataBase forth edition”, 1998, Cornwall.

Database Design and Implementation

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (15)

Similaire à Database Design and Implementation

Similaire à Database Design and Implementation (20)

Dernier

Dernier (20)

Database Design and Implementation