INTRODUCTION

E-commerce represents the direction of future trade development.

Promotion of e- commerce will bring great benefits to the society and the
economy. For example, e- commerce improves the speed and quality of services
of transaction, promotes the globalization of markets, and cuts down cost. For
these reasons, this project aimed to design and implement an online shopping
website for selling Asian food and groceries in the Helsinki area. The website is
designed for people who prefer online shopping of daily necessities, especially
Asian food. This website covers the entire process from product management,
classification and querying, to the shopping cart, and user order processing.
According to a simple market research, there are large domestic
supermarket chains located around every city in Finland and every corner in
Helsinki. However, the selection of commodities in these different supermarkets
is almost same, and there are only few Asian food items on the shelf. In
addition, only three large scale Asian supermarkets are located in Helsinki and
they are in the same place in the city centre. According to information received
from friends, a lot of Finnish people like Asian diet. Thus, the goal of this
project is to provide a platform for more and more Finnish people to be- come
familiar with Asian food and purchase it online, and to develop an independent
online shopping system based on ASP.NET and SQL Server.
In the future, this project could be used for the establishment of a
personal online shopping portal, or it could be sold to a company interested in
Asian product trading. The system includes both a front-end portal for
customers and a back-end management system used by administrators to
manage the website in the background. ASP.NET is used as the framework for
the project to facilitate software development, maintenance and upgrading.
Background system consists of Microsoft SQL Server as database and is written
in object-oriented C# language.
It will support both stand alone and also networking environment. The system
uses VB. Net Technology. The main modules involved in this system are:

Module wise description

Login

Login module is used to check whether the user is an authorized person to use
the system or not. For this the user should give the correct user name and
password.
The different types of users are
1. Admin
2. Reg. User
3. Visitor

System analysis
Market demand analysis
In the Helsinki area, a supermarket seems to be the main channel for people
shopping, both daily necessities and food items. However, according to a short
survey and talk with surrounding friends, a lot of people have a great interest in
Asian food. Some Finn- ish people seem to be tired of their native or Western
diet. They prefer to go to an Asian restaurant for lunch, such as sushi, fried
noodles and Chinese cuisine. Some of them even go to an Asian supermarket
every week, though it is located far away from their home. This project was
designed for those people, to provide an online website as a platform for them.
People could purchase different styles of food for cooking or eating while
sitting in front of the computer. They only need to click the product, pay it
online, and then wait for the delivery of their package in one or two days.

Selection of platform and technologies

This final year project used a B/S (Browser/Server) structure, three layers
operation mode, and at the same time, it was designed for Intranet/Internet. The
first layer is a browser, which is the system interface. The second layer is
application logic service. The third layer is a data link, which functions as the
system of data access service. This three-layer structure greatly simplifies the
load of the client computer, reduces system maintenance, updates costs and the
workload, and reduces the overall cost of the user. In such a structure, the user
interface is realized by a www browser, and very little of the business logic is
placed in the front end, i.e. the browser reach. The B/S structure of the software
only needs the management server and the client browser has no need for any
maintenance.

This project used the current mainstream computing mode for development.
The front- end development tool was ASP.NET which allows visualization to
build the sales mod- ule. The back-end code was done with fully object-oriented
C#. The ASP.NET is easy- to-use, universal and efficient. The back-end
database development tool used was SQL Server 2008. It is able to handle large
amounts of data while maintaining data integrity and provides a number of
senior management and data distribution functions. These two development
tools are powerful, and a good interface for development. Therefore, it is
feasible to employ this system.

System function requirements analysis

The implementation of the online shopping process is different from the
traditional way of shopping. First of all, the whole process of online shopping is
carried out through the network. Customers cannot see businesses and
commodities in real life, and they must understand the information on the goods
only through the network. The general pro- cess of online shopping is as
follows: businesses publish new product information on the web through the
system management function, and then customers browse these product details
through the system sales module, and can also search for more target- ed
product information according to their needs. For ease of administration, the
cus- tomer must be registered as a member of the site to buy a product and
choose the payment method and mailing option. After the arrival of the goods,
the customer in- spects and verifies whether the products are practical and
match the online description, and can then give a review for other customers.

Some famous online shopping sites such as Walmart, Amazon, and E-Bay were
stud- ied and analysed to establish a logical process of online shopping. Based
on this, the main functional requirements of this system were divided into two
modules: sales and system management. The sales module function allows the
customers to browse the goods. The customers are to be registered as members
in order to place products in the shopping cart and pay for them. System
management functions are used to the release of products, and to manage the
registered membership, product information, order, news, and comments.

Sales module functions analysis

To build the online shopping website for Asian food, the portal should have the
follow- ing sections and functions for the customers:

a) Member registration: Provides registration function. After the

registration, a user can pick products to the cart on the site, otherwise
only view product information.
b) Member Login: Allows a visitor to log in as a registered member. Each
visitor is only able to log in to one account.
c) Reclaim password: When a registered member forgets his/her password,
user name or mailbox, the password question and answer function will
support the re- claim of the password.
 d) Commodity information browsing: The home page displays special
columns for special offers, hot sales, recommended and newly released
products, and lists all products category navigation of the website.
e) Special offers module: The special offers module shows larger discounts
of goods.
f) Best-selling: According to the orders record, the home page displays the
top ten best-selling products.
g) Shopping cart: The products selected by a logged in member are
temporarily stored in the shopping car. The customer can modify the
number of purchases by viewing the cart.
h) New releases: According to the database information, the home page
displays the products released within the last three days or a week.
i) News: Home page rolling displays recent news entries according to the
time se- quence of the recent news.
j) Advertisements: Depending on the time, advertisements will be displayed
on the home page to publicize the different products. The above functions
form the basic pattern of the front-end website.

Background management system functions analysis

The system management module is used by the administrator to release

products. The background system functions consist of registered members,
product information, orders, news, and comments. The functional requirements
of the system management module are as follows:

a) Members function: Implementation of management of the members who

have registered on the website. An administrator can manage all members
of the site.
b) Products function: Managing the information of a product, such as
description, price, images, inventory and so on.
c) Order function: For the registered members’ orders in sales module, the
administrator will verify, and then deliver the products. Each order
corresponds to only one member, but it can correspond to multiple
products.
d) News function: Managing the news. A news data table can be updated
according to the current date.
e) Administrator function: Managing the basic information of the system
administrator, such as adding an administrator, modifying password. An
administrator can maintain the information of all members.
f) Administrator login: Only when logged in to the system management
homepage, the administrator can use all the features of the system
management module.
g) Release new products: Showing detailed information of new products for
customers.
 h) Logout: When the administrator clicks the "Logout", he/she will safety
exit.

In addition, not only for the security requirements, but also in order to
standardize the management of the sales module and management module of
the system, the follow- ing is to be done:

For customers: The non-registered members are only able to search and browse
prod- uct information, view special offers, sales ranking, new arrivals and news.
Shopping cart and user centre functions are for registered members only. For
administrators: If the administrator does not enter log in account and password,
he/she does not have access to the system management homepage. If the user
bypasses the system admin- istration login page and goes straight to the main
page, the system will be forced to return to the login page.

Data flow analysis

The data flow diagram is used to depict the logical model of the system, and
describes an integral module of the system and the relationship of each part, and
the flow of in- formation and data conversion.

Firstly, through the product management function in the background system, the
ad- ministrator saves product information into databases. Then, when a
customer is regis- tered as a site member, he/she can select and buy goods. After
the completion of the selection, choice of payment method and shipping
method, members submit an order. Finally, administrators deal with every new
order issued by the member. The top-level data flow diagram of the system is
shown in Figure 5.

For the system sales module, the customer provides data to the database,
including registration information, login information, purchase information and
the order infor- mation. For system management module, the data input is done
by the administrator, including the input of product information and news
information, and output of all the information could be viewed in sales module.
The entire data flow is shown in Figure 6

System structure design

The system structure and function is the core part in the system design. The
structure can be clearly seemed in the diagram. Each structural module is
analysed, in order to lay the foundation for design and implementation in the
future. According to the functional requirements, the system was divided into
two sections: sales module and man- agement module. The sales module is used
by customers. The management module is used by administrators. The entire
structure of the system is shown in Figure 7.
Module function design
The system is divided in the sales module and system management module.
Each module has several sub-modules. The sales module includes: the special
columns, shopping cart, membership centre, news, login and other sub-modules.
The system management module includes: product management, order
management, membership management, news management, administrator login
and other sub-modules. The de- sign of a specific module is explained in the
following sections.

Sales module design

Sales modules are used by customers to browse and order all kinds of products.
Figure 8 shows the structure of the system sales module.
Navigation is a fundamental component of any website. Although it is easy
enough to transfer the user from one page to another, creating a unified system
of navigation that works across an entire website takes more effort. For the
Asian Online Website, the special columns and functions design of the
navigation bar in sales module is as explained below:

1. Product special columns displays new arrivals, special offers, hot sales, sales
ranking and recommended. Each column is divided according to the product
information in a particular field of database table. For example, the products
displayed in special offers column are those with discounts of more than 20%.
New arrivals are products released within the previous three days or one week.
Sales ranking is organized according to the number of orders.

2. Shopping cart functions display the select item, view, and empty the cart.
Before the customer submits an order, information about all the selected
products is stored in the dataset of the implementation class file of the shopping
cart. When the order is submitted, the dataset is written into the database. The
user cannot use the submit function before they log in. If the user adds an item
into the shopping cart, the system prompts user login.

3. Membership centre displays registration, login, and reclaim password. For

registration function, the system requires the user to enter information
depending on the field of the database membership information in the data
table. Parity is achieved through various types of validation controls. Log in and
reclaim the password functions are also required data on the membership
information data sheet.

4. News management functions display news in the database on the home page,
while allowing the user to click on a specific news headline for more
information. 5. Login and registration: The system is to be emptied of the
members’ login information after they logout.

Background management system design

The background system management module is used by the administrators. It
consists of product information, orders, news, main category, secondary
category, comment management, member management and administrator
management. The system management module is shown in Figure 9.
Proposed System
 The aim of proposed system is to develop a system of improved facilities.
The proposed system can overcome all the limitations of the existing system.
The system provides proper security and reduces the manual work. The existing
system has several disadvantages and many more difficulties to work well. The
proposed system tries to eliminate or reduce these difficulties up to some extent.
The proposed system will help the user to reduce the workload and mental
conflict. The proposed system helps the user to work user friendly and he can
easily do his jobs without time lagging.

Expected Advantages of Proposed System

The system is very simple in design and to implement. The system

requires very low system resources and the system will work in almost all
configurations. It has got following features
1. Ensure data accuracy’s.
2. Proper control of the higher officials.
3. Reduce the damages of the machines.
4. Minimize manual data entry.
5. Minimum time needed for the various processing.
6. Greater efficiency.
7. Better service.
8. User friendliness and interactive.
9. Minimum time required.

FEASIBILITY STUDY

Feasibility study is made to see if the project on completion will serve the
purpose of the organization for the amount of work, effort and the time that
spend on it. Feasibility study lets the developer foresee the future of the project
and the usefulness. A feasibility study of a system proposal is according to its
workability, which is the impact on the organization, ability to meet their user
needs and effective use of resources. Thus when a new application is proposed
it normally goes through a feasibility study before it is approved for
development.
 The document provide the feasibility of the project that is being designed
and lists various areas that were considered very carefully during the feasibility
study of this project such as Technical, Economic and Operational
feasibilities. The following are its features:

TECHNICAL FEASIBILITY

The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs and procedures. Having
identified an outline system, the investigation must go on to suggest the type of
equipment, required method developing the system, of running the system once
it has been designed.
Technical issues raised during the investigation are:

1. Does the existing technology sufficient for the suggested one?

2. Can the system expand if developed?

The project should be developed such that the necessary functions and
performance are achieved within the constraints. The project is developed
within latest technology. Through the technology may become obsolete after
some period of time, due to the fact that never version of same software
supports older versions, the system may still be used. So there are minimal
constraints involved with this project. The system has been developed using
Java the project is technically feasible for development.

ECONOMIC FEASIBILITY

The developing system must be justified by cost and benefit. Criteria to

ensure that effort is concentrated on project, which will give best, return at the
earliest. One of the factors, which affect the development of a new system, is
the cost it would require.
The following are some of the important financial questions asked during
preliminary investigation:

1. The costs conduct a full system investigation.

2. The cost of the hardware and software.
3. The benefits in the form of reduced costs or fewer costly errors.
 Since the system is developed as part of project work, there is no manual
cost to spend for the proposed system. Also all the resources are already
available, it give an indication of the system is economically possible for
development.

3.4.4 BEHAVIORAL FEASIBILITY

This includes the following questions:
1. Is there sufficient support for the users?
2. Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when
developed and installed. All behavioral aspects are considered carefully and
conclude that the project is behaviorally feasible.

Introduction

Design is the first step into the development phase for any engineered
product or system. Design is a creative process. A good design is the key to
effective system. The term “design” is defined as “the process of applying
various techniques and principles for the purpose of defining a process or a
system in sufficient detail to permit its physical realization”. It may be defined
as a process of applying various techniques and principles for the purpose of
defining a device, a process or a system in sufficient detail to permit its physical
realization. Software design sits at the technical kernel of the software
engineering process and is applied regardless of the development paradigm that
is used. The system design develops the architectural detail required to build a
system or product. As in the case of any systematic approach, this software too
has undergone the best possible design phase fine tuning all efficiency,
performance and accuracy levels. The design phase is a transition from a user
oriented document to a document to the programmers or database personnel.
System design goes through two phases of development: Logical and Physical
Design.

4.1 LOGICAL DESIGN:

The logical flow of a system and define the boundaries of a system. It
includes the following steps:
1. Reviews the current physical system – its data flows, file content,
volumes , Frequencies etc.
2. Prepares output specifications – that is, determines the format, content
and Frequency of reports.
3. Prepares input specifications – format, content and most of the input
functions.
4. Prepares edit, security and control specifications.
5. Specifies the implementation plan.
 6. Prepares a logical design walk through of the information flow, output,
input, Controls and implementation plan.
7. Reviews benefits, costs, target dates and system constraints.

PHYSICAL DESIGN:

Physical system produces the working systems by define the design

specifications that tell the programmers exactly what the candidate system must
do. It includes the following steps.

1. Design the physical system.

2. Specify input and output media.
3. Design the database and specify backup procedures.
4. Design physical information flow through the system and a physical
design
5. Plan system implementation.
6. Prepare a conversion schedule and target date.
7. Determine training procedures, courses and timetable.
8. Devise a test and implementation plan and specify any new
hardware/software.
9. Update benefits , costs , conversion date and system constraints

Design/Specification activities:

1. Concept formulation.
2. Problem understanding.
3. High level requirements proposals.
4. Feasibility study.
5. Requirements engineering.
6. Architectural design.

INPUT DESIGN
The input design is the link between the information system and the
user. It comprises the developing specification and procedures for data
preparation and those steps are necessary to put transaction data in to a usable
form for processing can be achieved by inspecting the computer to read data
from a written or printed document or it can occur by having people keying the
data directly into the system. The design of input focuses on controlling the
amount of input required, controlling the errors, avoiding delay, avoiding extra
steps and keeping the process simple. The input is designed in such a way so
that it provides security and ease of use with retaining the privacy. Input Design
considered the following things:
1. What data should be given as input?
2. How the data should be arranged or coded?
3. The dialog to guide the operating personnel in providing input.
4. Methods for preparing input validations and steps to follow when error
occur.

Frontend
ASP.NET and .NET Framework
ASP.NET is the successor of Microsoft ASP (Active Server Pages), but it is
developed to be more powerful than ASP. It can be used to build dynamic
websites and web- based distributed applications, respond to data submitted by
the user from the HTML form, and access to the data or database, then return
the results to the browser. ASP.NET is a development platform provided
by .NET Framework and features a completely object-oriented programming
model, which includes an event-driven, con- trol-based architecture that
encourages code encapsulation and reuse. When coding ASP.NET applications,
programmers have access to classes in the .NET Framework. ASP.NET is
integrated with the .NET framework, which is divided into a large collection of
functional parts totalling more than 10,000 types [1;7]. In addition, it is easy to
deploy and configure. Figure 1 shows an overview of .NET Framework.
The most important aspect of the ASP.NET engine is that it runs in the runtime
environment of the CLR (common language runtime). CLR has some major
benefits: Firstly, it provides a pool of threads that can be used by various
classes, an object is automatically allocated by space, and unused memory for
inaccessible objects is reclaimed by the garbage collector. Secondly, the
compiler can verify that every call is valid at runtime, and whole categories of
low-level errors are completely obliterated by the safety layer. Thirdly, the
information about classes and members is only one of the types of metadata that
.NET stores in a compiled assembly. Figure 2 shows a high-level look at the
CLR and the .NET Framework.
ASP.NET uses solely OOP (object-oriented programming) language (at present
stage support to C #, VB, Jscript) to develop, using WYSIWYG (What You See
Is What YouADO.NET Data Access (And so on) XML File I/O Web Forms
Windows Forms Core System Classes (Threading, serialization, reflection,
collection) The .NET Class Library Compiler and Loader Code Verification and
Optimization Memory Management and Garbage Collection Code Access
Security The Common Language Runtime Get) editor to edit the web form. It
supports the separation of code and the content of the page [3]. Programmers
can take full advantage of the object-oriented inheritance, encapsulation,
reusability, and the characteristics of the event-driven for programming.
ASP.NET web form can be visually edited without having to worry about the
compiler automatically adding or modifying code will affect the script running.

Differences between PHP and ASP.NET

The most essential difference between PHP and ASP.NET is that PHP is a
program- ming language and ASP.NET is a development platform.
Approximately 1/3 of the web applications in the world are written in PHP at
present. Most of these PHP programs run on an Apache server. As a
programming language, PHP is independent of the op- erating platform. In
contrast to PHP, ASP.NET is a platform rather than language. The ASP.NET
program not only can be written in C#, but also can be written in any lan- guage
which was compiled to runs on .NET CLR. Usually, ASP.NET runs in
Windows platform and IIS server. In this sense, the difference between PHP and
ASP.NET, like iPhone and Widows 7. Choose one of them, is equivalent to
choose a style. [4]

ASP.NET consumes very large in terms of memory usage and execution time,
due in a long code path. For web-based applications, these limitations would be
a serious prob- lem, because on the web, application may be extended to
thousands of users per se- cond. Memory usage may also become a problem on
the Web server. On the other side, obviously the advantages of ASP.NET
depend on its simple design and imple- mentation. This is the dream of object-
oriented programming: Language flexible and support to complex object-
oriented features. In this sense, it could be able to interoper- ate with the
existing skills of programmers. Another advantage of ASP.NET is the de-
velopment environment. For example, developers can use WebMatrix (a
community- supported tools), Visual Studio .NET or Borland tools (such as
Delphi and C + + Build- er). Visual Studio allows programmer to set
breakpoints, tracking code snippet and view the call stack. All in all, it is a
complex debugging environment. Many other third party of the ASP.NET IDE
solution also will inevitably arise in the future. This project used ASP.NET as
development platform rather than PHP because the environment of Microsoft
(Windows + ASP.NET + SQL Server + Visual Studio 2010) is convenient than
LAMP (Linux + Apache + Mysql + PHP), and it is oriented-object
programming.

ADO.NET
The .NET Framework possesses its own data access technology, ADO.NET.
ADO.NET technology is a programming model to create a standards-based
system oriented for distributed data sharing applications. It is an extension of
the ADO (ActiveX Data Objects) technology and development, and superior to
ADO technology in in- teroperability, maintainability, programmability and
performance. ADO.NET contains many classes. Programmers use these classes
to get the data. ADO.NET is commonly used by programmers to access and
modify data stored in relational database systems, though it can also access data
in non-relational sources. The small miracle of ADO.NET is that it allows a
developer to write more or less the same data access code in web applications
that developers write for client-server desktop applications, or even single-user
applications that connect to a local database .
Generally web pages access a database with the following steps: first create and
open an ADODB connection object interface, and then bound to an object
corresponding data source (both named and unnamed data source), depending
on the requirements decide whether to create or not a record set. Finally the web
page is executed or opened to the corresponding table in the data source link.
Figure 4 shows the layered design between an ASP.NET application and a
database.

ADO.NET object model has five major components: connection, command,

dataset command, dataset, and data reader. Dataset in ADO.NET operates as a
data container, and is used when the application is disconnected from the
database. Dataset contains one or more data tables. Each data table contains a
collection of rows. Generally, a data table can be seen as a disconnected record
set. A data adapter works when con- necting to the database. The single data
adapter’s role is to use the data filling with data table, or return the modified
data table to the database. The data adapter requires a command object to
perform different database operations. The command object stores the SQL
statement or the name of a specified data access method procedure.[8] Each
data adapter has four attributes as follows:
Select Command: This command object is used to select data from the database.
Update Command: This command object is used to update existing records in
the database. Insert Command: This command object is used to insert a new
record to the database. Delete Command: This command object is used to delete
a database of existing records. Figure 4 interprets these objects and their
relationships.

Backend
A Basic introduction to Microsoft Access

MS Access is a database management tool that enables one to have good

command of data collected. The program enables one to retrieve, sort,
summarize and report results speedily and effectively. It can combine data
from various files through creating relationships, and can make data entry more
efficient and accurate.

Microsoft Access (MS Access) enables one to manage all important information
from a single database file. Within the file, one can use:

• Tables to store your data.

• Queries to find and retrieve specific data of interest.
• Forms to view, add, and update data in tables.
• Reports to analyze or print data in a specific layout.
• Data access pages to view or update, the data.

In MS Access, data is stored once in one table, but can be viewed from multiple
locations. When the data is updated in a Table, Query or Form, it is
automatically updated everywhere itAppears.

Establishment of MS Access database

All MS Access databases files are saved with extension .mdb or accdb
A database should have a separate table for every major subject, such as
pedigree records, Production data or Treatment information.
Data should not be duplicated in multiple tables.

 Microsoft Access provides three methods to create a database Database

Wizard(though easy, the wizard offers limited options to customize the
database)
 Using a template (This method works best if one can find and use a
template that closely matches the specific requirements)
 Creating a database directly(This is the most flexible method, but it
requires one to define each database element separately).

Relational Databases

A relational database is one whose components (tables, forms, queries

etc) are related (linked). The linkages between database components are
created by making relationship linksbetween them. The relationship can be
between:

 One component and another (one-to-one relationship),

 One component related to several other components (one-to-many)
 Several database components (many-to-many).
 Creation of relationships between database components reduces data
redundancy andenhances ease of access of the information.

Advantage
I have designed the given proposed system in the VB to automate the
process of Hotels. This project is useful for the authorities which keep track of
all the users registered in a particular state .The authority can add hotel
packages, room details, availability of rooms, booking etc.

The following steps that give the detailed information of the need of proposed
system are:

Performance:During past several decades, the records are supposed to be

manually handled for all activities. The manual handling of the record is time
consuming and highly prone to error.

To improve the performance of the Hotel Management System, the

computerized system is to be undertaken. This project is fully computerized and
user friendly even that any of the members can see the report and status of the
company.

Efficiency:The basic need of this website is efficiency. The website should be

efficient so that whenever a new user submits his/her details the website is
updated automatically. This record will be useful for other users instantly.

Control:The complete control of the project is under the hands of authorized

person who has the password to access this project and illegal access is not
supposed to deal with. All the control is under the administrator and the other
members have the rights to just see the records not to change any transaction or
entry.

Security:Security is the main criteria for the proposed system. Since illegal
access may corrupt the database. So security has to be given in this project.

DETAILED LIFE CYCLE OF PROJECT

We have used Waterfall Model as Software Engineering life Cycle Process. It is
the simplest; oldest and most widely used process model for software
development .This model acquires its name from the fact that classic software
life cycle is represented as a sequence of descending steps.

Requirement Analysis:
This process is also known as feasibility study. In this phase, the
development team studied the site requirement. They investigate the need for
possible dynamic representation of the site and increase security features. By
the end of feasibility study, the team furnishes a document that holds the
different specific recommendations for the candidate system. It also includes
personnel assignments, costs, project schedules, target dates etc. the
requirement gathering process is intensified and focused specially on software.
The essential purpose of this phase is to find the need and to define the problem
that needs to be solved. During this phase following facts were gathered.
 Determined the user need
 Identified the facts
 Establish the goals and objective for the proposed system
 Feasibility for the new system

7.2 System Analysis and Design:

In this phase the software’s overall structure and its nuances are defined.
In terms of client server technology the no of tiers needed for the package
architecture, database design, data structure design etc are defined in this phase.
Analysis and Design are very crucial in entire development cycle. Any glitch in
this phase could be expensive to solve in the later stage of software
development. Hence following is the essential approach taken during website
designing:
 DFD
 Database Designing
 Form Designing
 Pseudo code for methods
7.3 Testing:
Once the code is generated, the website testing begins. Different testing
methodologies are done to unravel the bugs that were committed during the
previous phases. Different testing methodologies are used:
 Acceptance testing
 White Box Testing
 Black Box Testing

E-R DIAGRAMS
DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a structured analysis and design tool that
canbeused for flowcharting. A DFD is a network that describes the flow of
data and the processes that change or transform the data throughout a
system. This network is constructed by using a set of symbols that do
not imply any physical implementation. It has the purpose of
clarifying system requirements and identifying major transformations. So it is
the starting point of the design phase that functionally decomposes the
requirements specifications down to the lowest level of detail. DFD can be
considered to an abstraction ofthe logic of an information-oriented or a
process-oriented system flow chart. For these reasons DFD’s are often referred
to as logical 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 a rectangular box.
PROCESS
A process shows a transformation or manipulation of data flow within the
system. The symbol used is an oval shape.
DATAFLOW
The data flow shows the flow of information from a source to its destination.
Data flow is represented 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 narrow 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 followed by an arbitrary number.
LOGIN DFD

REGISTRATION DFD
\ADMIN DFD

DATABASE DESIGN
A database is an organized mechanism that has the capability of
storing information through which a user can retrieve stored information in an
effective and efficient manner. The data is the purpose of any database and must
be protected.

The database design is a two level process. In the first step, user
requirements are gathered together and a database is designed which will meet
these requirements as clearly as possible. This step is called Information Level
Design and it is taken independent of any individual DBMS.
 In the second step, this Information level design is transferred into a
design for the specific DBMS that will be used to implement the system in
question. This step is called Physical Level Design, concerned with the
characteristics of the specific DBMS that will be used. A database design runs
parallel with the system design. The organization of the data in the database is
aimed to achieve the following two major objectives.
1. Data Integrity
2. Data independence
Normalization is the process of decomposing the attributes in an
application, which results in a set of tables with very simple structure. The
purpose of normalization is to make tables as simple as possible. Normalization
is carried out in this system for the following reasons.
1. To structure the data so that there is no repetition of data , this helps in
saving.
2. To permit simple retrieval of data in response to query and report request.
3. To simplify the maintenance of the data through updates, insertions,
Deletions.
4. To reduce the need to restructure or reorganize data which new
application Requirements arise.

RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):

A relational model represents the database as a collection of

relations. Each relation resembles a table of values or file of records. In formal
relational model terminology, a row is called a tuple, a column header is called
an attribute and the table is called a relation. A relational database consists of a
collection of tables, each of which is assigned a unique name. A row in a tale
represents a set of related values.

RELATIONS, DOMAINS & ATTRIBUTES:

A table is a relation. The rows in a table are called tuples. A tuple is an
ordered set of n elements. Columns are referred to as attributes. Relationships
have been set between every table in the database. This ensures both Referential
and Entity Relationship Integrity. A domain D is a set of atomic values. A
common method of specifying a domain is to specify a data type from which the
data values forming the domain are drawn. It is also useful to specify a name for
the domain to help in interpreting its values. Every value in a relation is atomic,
that is not decomposable.
RELATIONSHIPS:
1. Table relationships are established using Key. The two main keys of
prime importance are Primary Key & Foreign Key. Entity Integrity and
Referential Integrity Relationships can be established with these keys.
2. Entity Integrity enforces that no Primary Key can have null values.
3. Referential Integrity enforces that no Primary Key can have null values.
4. Referential Integrity for each distinct Foreign Key value, there must exist
a matching Primary Key value in the same domain. Other key are Super
Key and Candidate Keys.
5. Relationships have been set between every table in the database. This
ensures both Referential and Entity Relationship Integrity.

NORMALIZATION:
As the name implies, it denoted putting things in the normal form. The
application developer via normalization tries to achieve a sensible organization
of data into proper tables and columns and where names can be easily correlated
to the data by the user. Normalization eliminates repeating groups at data and
thereby avoids data redundancy which proves to be a great burden on the
computer resources. These includes:

1. Normalize the data.

2. Choose proper names for the tables and columns.
3. Choose the proper name for the data.

First Normal Form:

The First Normal Form states that the domain of an attribute must include
only atomic values and that the value of any attribute in a tuple must be a single
value from the domain of that attribute. In other words 1NF disallows “relations
within relations” or “relations as attribute values within tuples”. The only
attribute values permitted by 1NF are single atomic or indivisible values.
The first step is to put the data into First Normal Form. This can be donor by
moving data into separate tables where the data is of similar type in each table.
Each table is given a Primary Key or Foreign Key as per requirement of the
project. In this we form new relations for each nonatomic attribute or nested
relation. This eliminated repeating groups of data.
A relation is said to be in first normal form if only if it satisfies the
constraints that contain the primary key only.
Second Normal Form:
According to Second Normal Form, for relations where primary key
contains multiple attributes, no nonkey attribute should be functionally
dependent on a part of the primary key.
In this we decompose and setup a new relation for each partial key with its
dependent attributes. Make sure to keep a relation with the original primary key
and any attributes that are fully functionally dependent on it. This step helps in
taking out data that is only dependant on apart of the key.

A relation is said to be in second normal form if and only if it satisfies all the
first normal form conditions for the primary key and every non-primary key
attributes of the relation is fully dependent on its primary key alone.
Third Normal Form:
According to Third Normal Form, Relation should not have a nonkey
attribute functionally determined by another nonkey attribute or by a set of
nonkey attributes. That is, there should be no transitive dependency on the
primary key.
In this we decompose and set up relation that includes the nonkey attributes
that functionally determines other nonkey attributes. This step is taken to get rid
of anything that does not depend entirely on the Primary Key.
A relation is said to be in third normal form if only if it is in second normal
form and more over the non key attributes of the relation should not be depend
on other non key attribute.

TABLES STRUCTURE

Login

Order
 Registration

Shipping

FEATURES OF OS
      This project work is done on the windows 2000 professional, which is the
operating system. An operating system is a set of software tools designed to
make it easy for people or programmers to make optimum use of the computer.
People who use computers have different levels of needs and interest. These
peoples can be separated can be two groups, users and programmers. The user
wants a convenient set of commands to manage files of
data or programs, copy and run application package while a programmer used
as a set of tools that can be held together and debug programs.
      No matter where you are working, your computer will be easier to use and
manage, because Microsoft Windows 2000 Professional is more compatible and
more powerful than any workstation you’ve used before. The main features of
Windows 2000 Professional operating system are
  
1. Easier to use.
2. Easier to manage
3. More compatible
4. More powerful
PORTABILITY

1. Windows file protection protects core system files from being overwritten
by application installs.
2. Driver certification provides safeguards to assure you that device drivers
have not been tampered with and reduces your risk of installing non-
certified drivers.
3. Full 32 bit operating system minimizes the chance of application failures
and unplanned reboots.

MOBILITY

1. Hibernate turns off your computer and monitors after a predetermined

time while retaining your desktop on disk.
2. Offline viewing makes entire WebPages with graphics available for
viewing offline
3. Synchronization manager allows you to compare and update your offline
files and folders with those on the network.
4. Smart battery gives you a more accurate view of your battery’s life
enabling you to
MAINTAINABILITY

1. System preparation tool (sys prep) helps administrators clone computer

configuration systems and applications.
2. Set up manager provides a graphical wizard that guides administrators in
designing installation scripts.
3. Multilingual support allows users to easily create, read and edit
documentation in hundreds of languages.
4. Encrypting file system (EFS) encrypts each file with a randomly
generated key.
5. IP Security (IP Sec) support protected data transmitted across a network.

INTERNET CAPABILITY

1. Internet Information Services (IIS) 5.0 includes web and FTP server
support, as well as support for Front-page transactions, Active Server
Pages (ASP) and database connections.
2. Windows 2000 has strong development platform support for dynamic
HTML behaviors and XML.
3. Intelliforms alleviates the tedious of filling out forms on the web by
automatically entering your name, address or other information that you
have securely stored on your computer.

Software and Hardware Specifications

Hardware Specification
o Processor : Pentium III/AMD Athlone XP
o RAM : 128 MB
o Hard disk : 20 GB
o FDD : 1.44MB
o Monitor : 14 inch
o Mouse : 3 Button scroll
o CD Drive : 52 X
o Keyboard : 108 keys

Software Specification

o Operating System : Windows 2000/XP /Window7

o Languages : ASP
o Front End : HTML, ASP.NET
o Platform : Visual Studio
o Web Servers :
o Backend : MS Access
o Browser Program: Internet explorer/Mozilla Fireworks/Google
chrome

Code Details
The purpose of code is to facilitate the identification, retrieval of the items and
information. A code is an oriented collection of symbols design to provide
unique identification of an entry or attribute. Code is built with manually
exclusive features. Codes in all cases specify object which are physical or on
performance characteristics. They are used to give optimal distraction and other
information. Codes are used for identifying, accessing, storing and matching
records. The codes insure that only one value of the code with a single meaning
is correctly applied to give entity or attribute as described in various ways. Code
can also be design in a manner easily understood and applied by the user.
Coding Standard
The standard used in the development of the system is Microsoft
Programming standards. it includes naming conversions of variables, constants
and objects, standardized formats or labelling and commenting code, spacing,
formatting and indenting.

Naming Convention
Classes’ names and interface names will start with capital letter. The
function names will start with small letters and the first letter of each word in
the function name will be in capital letter.

Labels and Comments

Sufficient labels and comments are included in the description of it for
the benefits if the developer and other programmers who might examine it later.
User Interface
1. For all the entry screen frames are used which will show the type of the
user who is currently logged in and the menus.
2. Standard actions are used for standard actions.
3. Same font is related properties are used for similar screens.

The method of implementation and the time scale to be adopted are found out
initially. Next the system is tested properly and the users are trained in the new
procedures.

Testing Introduction
Software Testing is the process of executing software in a controlled
manner, in order to answer the question - Does the software behave as
specified?. Software testing is often used in association with the terms
verification and validation. Validation is the checking or testing of items,
includes software, for conformance and consistency with an associated
specification. Software testing is just one kind of verification, which also uses
techniques such as reviews, analysis, inspections, and walkthroughs. Validation
is the process of checking that what has been specified is what the user actually
wanted.
Validation : Are we doing the right job?
Verification : Are we doing the job right?
Testing is a set of activity that can be planned in advanced and conducted
systematically. Testing begins at the module level and work towards the
integration of entire computers based system. Nothing is complete without
testing, as it vital success of the system testing objectives, there are several rules
that can serve as testing objectives. They are
 
1. Testing is a process of executing a program with the intend of findingan
error.
2. A good test case is one that has high possibility of finding an
undiscovered error.
3. A successful test is one that uncovers an undiscovered error.
 
     If a testing is conducted successfully according to the objectives as stated
above, it would uncovered errors in the software also testing demonstrate that
the software function appear to be working according to the specification, that
performance requirement appear to have been met.
 
There are three ways to test program.
1. For correctness
2. For implementation efficiency
3. For computational complexity
 
Test for correctness are supposed to verify that a program does exactly what it
was designed to do. This is much more difficult than it may at first appear,
especially for large programs.
6.1 TEST PLAN
A test plan implies a series of desired course of action to be followed in
accomplishing various testing methods. The Test Plan acts as a blue print for the
action that is to be followed. The software engineers create a computer program,
its documentation and related data structures. The software developers is always
responsible for testing the individual units of the programs, ensuring that each
performs the function for which it was designed. There is an independent test
group (ITG) which is to remove the inherent problems associated with letting
the builder to test the thing that has been built. The specific objectives of testing
should be stated in measurable terms. So that the mean time to failure, the cost
to find and fix the defects, remaining defect density or frequency of occurrence
and test work-hours per regression test all should be stated within the test plan.
The levels of testing include:
1. Unit testing
2. Integration Testing
3. Data validation Testing
4. Output Testing
6.1.1 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software design
– the software component or module. Using the component level design
description as a guide, important control paths are tested to uncover errors
within the boundary of the module. The relative complexity of tests and
uncovered scope established for unit testing. The unit testing is white-box
oriented, and step can be conducted in parallel for multiple components. The
modular interface is tested to ensure that information properly flows into and
out of the program unit under test. The local data structure is examined to
ensure that data stored temporarily maintains its integrity during all steps in an
algorithm’s execution. Boundary conditions are tested to ensure that all
statements in a module have been executed at least once. Finally, all error
handling paths are tested.

Unit testing was done in Sell-Soft System by treating each module as

separate entity and testing each one of them with a wide spectrum of test inputs.
Some flaws in the internal logic of the modules were found and were rectified.

6.1.2 INTEGRATION TESTING

Integration testing is systematic technique for constructing the program

structure while at the same time conducting tests to uncover errors associated
with interfacing. The objective is to take unit tested components and build a
program structure that has been dictated by design. The entire program is tested
as whole. Correction is difficult because isolation of causes is complicated by
vast expanse of entire program. Once these errors are corrected, new ones
appear and the process continues in a seemingly endless loop.

6.1.3 VALIDATION TESTING OR SYSTEM TESTING

 This is the final step in testing. In this the entire system was tested as a
whole with all forms, code, modules and class modules. This form of testing is
popularly known as Black Box testing or System tests.
Black Box testing method focuses on the functional requirements of the
software. That is, Black Box testing enables the software engineer to derive
sets of input conditions that will fully exercise all functional requirements for a
program.
Black Box testing attempts to find errors in the following categories;
incorrect or missing functions, interface errors, errors in data structures or
external data access, performance errors and initialization errors and termination
errors.

6.1.4 OUTPUT TESTING OR USER ACCEPTANCE TESTING

The system considered is tested for user acceptance; here it should satisfy the
firm’s need. The software should keep in touch with perspective system; user at
the time of developing and making changes whenever required. This done with
respect to the following points

1. Input Screen Designs,

2. Output Screen Designs,
3. Online message to guide the user and the like.

The above testing is done taking various kinds of test data. Preparation of test
data plays a vital role in the system testing. After preparing the test data, the
system under study is tested using that test data. While testing the system by
which test data errors are again uncovered and corrected by using above testing
steps and corrections are also noted for future use.

Validation Checking:

At the culmination of integration testing, software is completely assembled as a

package; interfacing errors have been uncovered and corrected, and a final
series of software test-validation checks may begin. Validation can be defined
in many ways, but a simple definition (Albeit Harsh) is that validation succeeds
when software functions in a manner that can be reasonably expected by a
customer. Software validation is achieved through a series of black-box tests to
be conducted and a test procedure defines specific test cases that will be used in
attempt to uncover errors in conformity with requirements. Both the plan and
procedure are designed to ensure that all functional requirements are satisfied;
all performance requirements are achieved; documentation is correct and human
–Engineered and other requirements are met. Once the application was made
free of all logical and interface errors , inputting dummy data to ensure that the
software developed satisfied all the requirements of the user did validation
checks .However , the data are created with the intent of determining whether
the system will process them correctly .

Test cases:
Test case 1: Authentication
 Test case#: validity of name and password/priority (H, L)-High
 Test objective: To check the name of the user
 Test description: To check whether user name and password is valid or
not
 Requirements verified: valid user
. Test setup/reconditions:
Actions Expected results
1. Correct name and pwd entered The user will be logged in
2. Wrong name and pwd entered Generates an error report
Pass: yes ---- Condition pass:Fail:Problems/issues: None
Notes: successfully tested and executed.

Test case 2: e-mail verification

 Test case#: validation of e-mail/priority (H, L)-High
 Test objective: validity check for e-mail
 Test description: To check whether the e-mail is valid or not
 Requirements verified: valid e-mail

Sample codes
Default.aspx

<%@ImportNamespace="system.data"%>
<%@ImportNamespace="System.Data.OleDb"%>
<!DOCTYPEhtml>
<htmlxmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Fashion Store</title>
<metahttp-equiv="Content-Type"content="text/html; charset=iso-8859-1"/>
<linkrel="stylesheet"type="text/css"href="css/style.css"/>
<scriptrunat="server">

ProtectedSubsubmit_Click(ByVal sender AsObject, ByVal e AsSystem.EventArgs)

DimconnStringAsString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\
shopping.accdb;"
' Reads the values for the given user
DimqryStringAsString = "SELECT uname, pass, status, name, mail FROM login where uname
= '"&uname.Text&"';"
DimobjConnAsNewOleDbConnection(connString)
DimobjCmdAsNewOleDbCommand(qryString, objConn)
DimmyReaderAsOleDbDataReader

Try

DimgotUserAsBoolean = False
Dim stat AsString
DimmynameAsString
DimumailAsString
objConn.Open()
myReader = objCmd.ExecuteReader
WhilemyReader.Read
IfmyReader.Item("uname") = uname.TextAndmyReader.Item("pass") = pass.TextThen
gotUser = True
EndIf
myname = myReader.GetString(3).ToString()
stat = myReader.GetString(2).ToString()
umail = myReader.GetString(3).ToString()
EndWhile
Session("FirstName") = myname
Session("uname") = uname.Text
Session("umail") = umail
myReader.Close()
IfgotUser = FalseThen
lbl.Text = "Invalid User Name & Password, Please try again!"
ElseIf stat = "a"Then

' This will redirect the user to the home page of the site
Response.Redirect(<ahref="admin.aspx">admin.aspx</a>)
ElseIf stat = "u"Then
Response.Redirect(<ahref="user.aspx">user.aspx</a>)

EndIf
Catch ex AsException
lbl.Text = ex.ToString

Finally
objConn.Close()
EndTry
EndSub

</script>

</head>
<body>
<divid="mainblock">
<divid="innerblock">
<divid="toppanel">
<divclass="tp_heading">NEW FASHION STORE</div>
<divclass="tp_bg"><ahref="#"><imgsrc="images/
tp_logo.jpg"width="329"height="71"alt=""class="tp_logo"/></a>
<divclass="tp_txt1">Collect your favorite</div>
<divclass="tp_txt2">fashion store</div>
</div>
<divclass="fp_menutile"><fontcolor="white"><h2><center>Kindily Login First For Online
Shopping </center></h2></font></div>

</div>
<divclass="contentblock">
<divclass="contentpanel">

<FONTCOLOR="white">
<formid="frm"method="post"runat="server">
<center><tableborder="0"cellspacing="20"class="style3">

<tr><tdcolspan="3">Logout Successful....
<asp:ValidationSummaryShowMessageBox="true"ID="validationsummary"ShowSummary="false"Fo
reColor="Red"runat="server"/>

</td></tr>

<tr>
<tdcolspan="2"><h1><fontcolor="#66ffcc"face="System">Login </font></h1></td>

</tr>
<tr>
<tdclass="style7">User Name

</td>
<tdclass="style5"><asp:TextBoxrunat="server"ID="uname"></asp:TextBox></td><td>
<asp:RequiredFieldValidatorID="rfv"ErrorMessage="enter user
name"Display="None"ControlToValidate="uname"runat="server">
</asp:RequiredFieldValidator>
</td>
</tr>

<tr><tdclass="style7">Password
</td>
<tdclass="style5"><asp:TextBoxrunat="server"ID="pass"TextMode="Password"></
asp:TextBox></td><td>

<asp:RequiredFieldValidatorID="RequiredFieldValidator1"ErrorMessage="enter
Password"Display="None"ControlToValidate="pass"runat="server">
</asp:RequiredFieldValidator></td></tr>

<tr>
<tdclass="style7">

</td>
<tdclass="style5"><asp:Labelrunat="server"ID="lbl"></asp:Label>
</td>
</tr>
<tr><tdclass="style7"></
td><tdclass="style5"><asp:ButtonID="submit"Text="submit"runat="server"onclick="submit_
Click"/></td></tr>

<tr><td>New User<ahref="reg.aspx"> Click Here</a></td></tr>

</table>
</center>
</form>

</FONT>

</div>
</div>
<divclass="fp_bg">

<divid="footerblock">

<pclass="fp_txt1">new fashion store</a> @ 2008. All Rights Reserved.</p>

</div>
</div>
</div>
</div>
</body>
</html>

Registration.aspx
<%@ImportNamespace="System.Data.OleDb"%>
<!DOCTYPEhtml>
<htmlxmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Fashion Store</title>
<metahttp-equiv="Content-Type"content="text/html; charset=iso-8859-1"/>
<linkrel="stylesheet"type="text/css"href="css/style.css"/>

<scriptrunat="server"language="vbscript">
Dim con AsNewOleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\
shopping.accdb")

ProtectedSubbtnSubmit_Click(ByVal sender AsObject, ByVal e AsEventArgs)

Try

DimcmdAsOleDbCommand = NewOleDbCommand("insert into reg values('" + uname.Text + "','"

+ tname.Text + "','" + add.Text + "','" + city.Text + "','" + state.Text + "','" +
pin.Text + "','" + mob.Text + "','" + mail.Text + "')", con)
Dim cmd1 AsOleDbCommand = NewOleDbCommand("insert into login values('" + uname.Text +
"','" + pass.Text + "','" + sta.Text + "','" + uname.Text + "','" + mail.Text + "')",
con)
cmd.Connection = con
cmd1.Connection = con
con.Open()
cmd.ExecuteNonQuery()
cmd1.ExecuteNonQuery()
con.Close()
Response.Redirect(<ahref="regs.aspx">regs.aspx</a>)
Catch ex AsException
lbl.Text = ex.Message
EndTry

EndSub

</script>

</head>
<body>
<divid="mainblock">
<divid="innerblock">
<divid="toppanel">
<divclass="tp_heading">EBAY FASHION STORE</div>
<divclass="tp_bg"><ahref="#"><imgsrc="images/
tp_logo.jpg"width="329"height="71"alt=""class="tp_logo"/></a>
<divclass="tp_txt1">Collect your favorite</div>
<divclass="tp_txt2">fashion store</div>
</div>
<divclass="fp_menutile"></div>

</div>
<divclass="contentblock">
<divclass="contentpanel">

<FONTCOLOR="white">
<formid="frm"method="post"runat="server">
<center><tableborder="0"cellspacing="20">

<tr><tdcolspan="3">
<asp:ValidationSummaryShowMessageBox="true"ID="validationsummary"ShowSummary="false"Fo
reColor="Red"runat="server"/>

</td></tr><tr>
<tdcolspan="3">
<h1> Registration</h1>
</td></tr>
<tr>
<td>Name</td><td>
<asp:TextBoxID="tname"runat="server">
</asp:TextBox></td><td>
<asp:RequiredFieldValidatorID="RequiredFieldValidator1"ErrorMessage="Enter
Name"Display="None"ControlToValidate="tname"runat="server">
</asp:RequiredFieldValidator></td>
</tr>

<tr>
<td>ADDRESS</td><td>
<asp:TextBoxID="add"runat="server">
</asp:TextBox></
td><td><asp:RequiredFieldValidatorID="RequiredFieldValidator2"ErrorMessage="Enter
Address"Display="None"ControlToValidate="ADD"runat="server">
</asp:RequiredFieldValidator></td>
</tr>
<tr>
<td>CITY</td><td>
<asp:TextBoxID="city"runat="server">
</asp:TextBox></
td><td><asp:RequiredFieldValidatorID="RequiredFieldValidator3"ErrorMessage="Enter
city"Display="None"ControlToValidate="city"runat="server">
</asp:RequiredFieldValidator></td>
</tr>
<tr>
<td>STATE</td><td>
<asp:TextBoxID="state"runat="server"></asp:TextBox></td><td>
<asp:RequiredFieldValidatorID="RequiredFieldValidator4"ErrorMessage="Enter
State"Display="None"ControlToValidate="state"runat="server">
</asp:RequiredFieldValidator></td>
</tr>

<tr>
<td>PIN NO.</td><td>
<asp:TextBoxID="pin"runat="server"MaxLength="6"></asp:TextBox></td><td>
<asp:RegularExpressionValidatorID="RegularExpressionValidator2"runat="server"
ErrorMessage="Enter Correct Pin Code"ControlToValidate="pin"
Display="Dynamic"ForeColor="#FF3300"SetFocusOnError="True"
ValidationExpression="\d{6}">
</asp:RegularExpressionValidator>
</td>
</tr>

<tr>
<td>MOBILE NO.</td><td>
<asp:TextBoxID="mob"runat="server"MaxLength="10"></asp:TextBox></td><td>
<asp:RegularExpressionValidatorID="RegularExpressionValidator4"runat="server"
ErrorMessage="Enter Correct Mobile No"ControlToValidate="mob"
Display="Dynamic"ForeColor="#FF3300"SetFocusOnError="True"
ValidationExpression="[987]\d{9}">
</asp:RegularExpressionValidator>
</td>
</tr>

<tr>
<td>E-MAIL</td><td>
<asp:TextBoxID="mail"runat="server"></asp:TextBox></
td><td><asp:RegularExpressionValidatorID="RegularExpressionValidator1"runat="server"
ErrorMessage="Enter Correct E Mail"ControlToValidate="mail"
Display="Dynamic"ForeColor="#FF3300"SetFocusOnError="True"
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*"></
asp:RegularExpressionValidator>

</asp:RequiredFieldValidator></td>
</tr>
<tr>
<td>User Name</td><td>
<asp:TextBoxID="uname"runat="server"></asp:TextBox></td><td>
<asp:RequiredFieldValidatorID="RequiredFieldValidator7"ErrorMessage="Enter
State"Display="None"ControlToValidate="uname"runat="server">
</asp:RequiredFieldValidator></td>
</tr>
<tr>
<td>PASSWORD</td><td>
<asp:TextBoxID="pass"runat="server"TextMode="Password"></asp:TextBox></td><td>
<asp:RequiredFieldValidatorID="RequiredFieldValidator5"ErrorMessage="Enter
password"Display="None"ControlToValidate="pass"runat="server">
</asp:RequiredFieldValidator></td>
</tr>

<tr>
<td></td><td>
<asp:TextBoxID="sta"runat="server"Text="u"Visible="false"></asp:TextBox></td><td>
</td>
</tr>

<tr>
<td></td><td>

<asp:ButtonID="Button1"runat="server"Text="Submit"onclick="btnSubmit_Click"></
asp:button></td><td><asp:LabelID="lbl"runat="server"></asp:Label>

</td>
</tr>

</table>
</center>
</form>

</FONT>

</div>
</div>
<divclass="fp_bg">

<divid="footerblock">

<pclass="fp_txt1">spsm college</a>@ 2008. All Rights Reserved.</p>

</div>
</div>
</div>
</div>
</body>
</html>

User.aspx
<!DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0
Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-
transitional.dtd"><htmlxmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Fashion Store</title>
<metahttp-equiv="Content-Type"content="text/html; charset=iso-8859-1"/>
<linkrel="stylesheet"type="text/css"href="css/style.css"/>
<linkrel="stylesheet"type="text/css"href="css/coin-slider.css"/>
<scriptrunat="server">

ProtectedSubPage_Load(ByVal sender AsObject, ByVal e AsSystem.EventArgs)

IfNotIsPostBackThen
IfSession("FirstName") IsNothingThen
Session("FirstName") = "Aspdotnet"

lbl.Text = Convert.ToString(Session("FirstName"))
lbl1.Text = Convert.ToString(Session("FirstName"))
Else
lbl.Text = Convert.ToString(Session("FirstName"))
lbl1.Text = Convert.ToString(Session("FirstName"))
EndIf
EndIf

EndSub
</script>
</head>
<body>
<form>
<divid="mainblock">
<divid="innerblock">
<divid="toppanel">
<divclass="tp_heading">EBAY FASHION STORE</div>
<divclass="tp_bg"><ahref="#"><imgsrc="images/
tp_logo.jpg"width="329"height="71"alt=""class="tp_logo"/></a>
<divclass="tp_txt1">Collect your favorite</div>
<divclass="tp_txt2">fashion store</div>
</div>
<divclass="fp_menutile"><ahref="user.aspx"class="menu1">HOME</a><imgsrc="images/
tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="men.aspx"class="menu2">MEN</a><imgsrc="images/
tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="women.aspx"class="menu2">WOMEN</a><imgsrc="images/
tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="kids.aspx"class="menu2">KIDS</a><imgsrc="images/
tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="ourstore.aspx"class="menu2">Our
Store</a><imgsrc="images/tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="services.aspx"class="menu2">services</a><imgsrc="images/
tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="collection.aspx"class="menu2">collection</a><imgsrc="images/
tp_divider.gif"width="2"height="59"alt=""class="tp_divider"/>
<ahref="contact us.aspx"class="menu2"> Contact Us</a></div>
<divclass="fp_shoppingbg"><imgsrc="images/
tp_image.jpg"width="13"height="11"alt=""class="tp_image1"/>
<divclass="tp_txt3"><ahref="Default1.aspx">LogOut</
a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<asp:LabelID="lbl"runat="server"></asp:Label></div>
</div>
</div>
<divclass="contentblock">
<divclass="contentpanel">
<divclass="cnt_headingblock"><imgsrc="images/
cnt_btn1.gif"width="13"height="13"alt=""class="cnt_btn1"/>
<imgsrc="images/cnt_heading11.jpg"width="151"height="30"alt=""class="cnt_heading"/></
div>
<divstyle="float:left; padding-bottom:55px;">

<center>
<tableborder="0"cellspacing="20">
<tr><tdcolspan="3"align="center"><fontcolor="white">Men Collection</font></td></tr>
<tr>
<td>
<ahref="men.aspx"><imgsrc="images/casual%20(6).jpg"height="200"width="200"/></a>
</td>
<td>
<ahref="men.aspx"><imgsrc="images/W3%20(2).jpg"height="200"width="200"/></a>
</td>
<td><ahref="men.aspx"><imgsrc="images/men%20sleepwear
%20(1).jpg"height="200"width="200"/></a>
</td>
</tr>

<tr><tdcolspan="3"align="center"><fontcolor="white">Women Collection</font></td></tr>

<tr>
<td>
<ahref="women.aspx"><imgsrc="images/sari%20(2).jpg"height="200"width="200"/></a>
</td>
<td><ahref="women.aspx"><imgsrc="images/wo%20jeans%20(9).jpg"height="200"width="200"/
></a>
</td>
<td>
<ahref="women.aspx"><imgsrc="images/salwar%20(7).jpg"height="200"width="200"/></a>
</td>
</tr>

<tr><tdcolspan="3"align="center"><fontcolor="white">Kids Collection</font></td></tr>
<tr>
<td><ahref="kids.aspx"><imgsrc="images/boys%20dress
%20(30).jpg"height="200"width="200"/></a>
</td>
<td><ahref="kids.aspx"><imgsrc="images/kidsimage%20(8).jpg"height="200"width="200"/
></a>
</td>
<td><ahref="kids.aspx"><imgsrc="images/kidsimage%20(2).jpg"height="200"width="200"/
></a>
</td>
</tr>

<tr><tdcolspan="3"align="center"><fontcolor="white">beauty Collection</font></td></tr>
<tr>
<td><imgsrc="images/jew%20(27).jpg"height="200"width="200"/>
</td>
<td>
<imgsrc="images/1.jpg"height="200"width="200"/>
</td>
<td>
<imgsrc="images/cosmetics%20(15).jpg"height="200"width="200"/>
</td>
</tr>

<tr><tdcolspan="3"align="center"><fontcolor="white">shoes Collection</font></td></tr>

<tr>
<td>
<imgsrc="images/wfootwear%20(19).jpg"height="200"width="200"/>
</td>
<td>
<imgsrc="images/L%20soes%20(10).jpg"height="200"width="200"/>
</td>
<td>
<imgsrc="images/shoes%20(6).jpg"height="200"width="200"/>
</td>
</tr>

<tr><tdcolspan="3"align="center"><fontcolor="white">other Collection</font></td></tr>

<tr>
<td>
<imgsrc="images/1%20(3).png"height="200"width="200"/>
</td>
<td>
<imgsrc="images/toy%20(8).jpg"height="200"width="200"/>
</td>
<td>
<imgsrc="images/bags.jpg"height="200"width="200"/>
</td>
</tr>

</table>
</center>

</div>

<divclass="cnt_headingblock"><imgsrc="images/
cnt_btn1.gif"width="13"height="13"alt=""class="cnt_btn1"/>
<imgsrc="images/cnt_heading2.jpg"width="260"height="30"alt=""class="cnt_heading"/></
div>
<ahref="#"><imgsrc="images/
cnt_readmore.gif"width="88"height="26"alt=""class="cnt_readmore"/></a>
<divclass="cnt_headingblock"><imgsrc="images/
cnt_btn1.gif"width="13"height="13"alt=""class="cnt_btn1"/>
<imgsrc="images/cnt_heading4.jpg"width="175"height="30"alt=""class="cnt_heading"/></
div>
<divstyle="float:left;
width:650px;"><imgsrc="images/cnt_paypal.gif"width="219"height="84"alt=""class="cnt_pa
ypal"/>
</div>
<divclass="cnt_headingblock"><imgsrc="images/
cnt_btn1.gif"width="13"height="13"alt=""class="cnt_btn1"/>
<imgsrc="images/cnt_heading3.gif"width="210"height="22"alt=""class="cnt_heading"/></
div>
<divclass="cnt_innerblock1">
<divclass="cnt_inner1">

</div>
</div>
</div>
<divclass="rightpanel">
<divclass="rp_headingblock">&nbsp;&nbsp;&nbsp;*
<asp:LabelID="lbl1"runat="server"></asp:Label></div>
<divclass="rp_block1">
<ahref="myorder.aspx"class="menu2">
<divclass="rp_listblock"><imgsrc="images/
rp_btn2.gif"width="8"height="8"alt=""class="rp_btn3"/>
<pclass="rp_listtxt">My Order</p></a>
</div>
<ahref="shipadd.aspx"class="menu2">
<divclass="rp_listblock"><imgsrc="images/
rp_btn2.gif"width="8"height="8"alt=""class="rp_btn3"/>

<pclass="rp_listtxt"> Shipping Info</p></a>

</div>

<ahref="uchangepass.aspx"class="menu2">
<divclass="rp_listblock"><imgsrc="images/
rp_btn2.gif"width="8"height="8"alt=""class="rp_btn3"/>
<pclass="rp_listtxt">Change Password</p>
</div>

</div>
<divclass="rp_headingblock"><imgsrc="images/
rp_btn1.gif"width="13"height="13"alt=""class="cnt_btn1"/>
<imgsrc="images/rp_heading2.jpg"width="160"height="28"alt=""class="cnt_heading"/></
div>
<divclass="rp_block2">
<divstyle="float:left; width:130px; border-right:1px solid #1E1E1E;">
<divclass="rp_txt1">Items must be returned with in</div>
<divclass="rp_txt1">Refund will be given as : </div>
</div>
<divstyle="float:left; width:100px;">
<divclass="rp_txt1">7 Days</div>
<divclass="rp_txt1"style="clear:left; margin-top:25px;">Credit</div>
</div>
</div>
<divclass="rp_headingblock"style="margin-top:15px;"><imgsrc="images/
rp_btn1.gif"width="13"height="13"alt=""class="cnt_btn1"/>
<imgsrc="images/rp_heading3.jpg"width="88"height="30"alt=""class="cnt_heading"/></div>
<divclass="rp_block2">
<imgsrc="images/rp_image1.jpg"width="256"height="71"alt=""class="rp_image1"/></div>
</div>
<divclass="fp_bg">
<divid="footerblock"><ahref="home page.aspx"class="fp_txt">Home Page</a>
<pclass="fp_divi">|</p>
<ahref="payment.aspx"class="fp_txt">Payments</a>
<pclass="fp_divi">|</p>
<ahref="shipping.aspx"class="fp_txt">Shipping</a>
<pclass="fp_divi">|</p>
<ahref="#"class="fp_txt">Terms</a>
<pclass="fp_divi">|</p>
<ahref="contact us.aspx"class="fp_txt">Contact Us</a>
<pclass="fp_divi">|</p>
<ahref="our stor.aspx"class="fp_txt">Our Store</a>
<pclass="fp_divi">|</p>
<ahref="services.aspx"class="fp_txt">rp_image1services</a>
<pclass="fp_divi">|</p>
<ahref="collection.aspx"class="fp_txt">collection</a>

</div>
</div>
</div>

</form>
</body>
</html>

Screen Shots

Default.aspx

User.aspx
 Men.aspx

Women.aspx
Kids.aspx

Reg.aspx
RegistrationSuccesfull.aspx

Login.aspx
Shipping.aspx

Shippings.aspx
Shippingss.aspx
Problems and Solutions
At the beginning, I was a novice of ASP.NET and during this project I came
across many problems. There is not a systemic module to study ASP.NET and
MS SQL in the school. I was reading a lot of books and studying from online
tutorials, then summed up some experience from doing this project. After
studying and analysing some famous B2C and C2C website designs, such as
ebay.com, amazon.com, walmart.com, I was inspired and began to design the
layout of this website. While doing the development, the biggest problem was
the design of database table and schema. Finally, I success- fully configured the
connection with ASP.NET and SQL Server.
The details of the problems encountered in the process of system development
were as follows: When adding static control to dynamic pages, the required
information could not be obtained. Each time a request was submitted to the
server, the client page would be reloaded. If this situation had been ignored, the
expected data could not have been submitted to the server. The solution was to
add breakpoints in the behind-code of the page, and single-step debugging,
which eventually resolved the problem. During the process of solutions, I
recognized the importance of the debugging method.
6.2 Further Development
The Asian Online website can run on the local host successfully. However,
compared with other famous shopping websites, there still are shortages to be
improved by fur- ther development. First of all, the payment function is not an
actual link to the bank. Considering the security and authentication, it is huge
work to implement an integral online payment system, although I could only
develop an API to the bank. Secondly, according to discussions with some
friends, it would be better to add some dynamic graphic and use GDI+ in
ASP.NET to give a good user experience. Thirdly, if a chat function for
transactions were developed, it would not be limited to chat. Merchants and
customers could also quickly query about and modify their information.

Conclusion

The project entitled Online shopping system was completed successfully. The
system has been developed with much care and free of errors and at the same
time it is efficient and less time consuming. The purpose of this project was to
develop a web application and an android application for purchasing items from
a shop.

This project helped us in gaining valuable information and practical

knowledge on several topics like designing web pages using html &css,
usage of responsive templates, designing of android applications, and
management of database using mysql . The entire system is secured. Also the
project helped us understanding about the development phases of a project and
software development life cycle. We learned how to test different features of a
project.
This project has given us great satisfaction in having designed an
application which can be implemented to any nearby shops or branded shops
selling various kinds of products by simple modifications.

There is a scope for further development in our project to a great extend. A

number of features can be added to this system in future like providing
moderator more control over products so that each moderator can maintain their
own products. Another feature we wished to implement was providing classes
for customers so that different offers can be given to each class. System may
keep track of history of purchases of each customer and provide suggestions
based on their history. These features could have implemented unless the time
did not limited us..
References

1. MacDonald M, Szpuszta M. Pro ASP.NET, Second

Edition. Unit- ed States of American: Apress; 2007.
2. Microsoft Corporation [online]. The .NET Framework
Stack;
URL:http://blogmstechnology.blogspot.fi/2009/10/
netframeworkstack.html

3.URL: http://drupal.org/project/wysiwyg.
4. Perfect Web Tutorials [online]. ASP.NET vs PHP-
complete comparisons;
URL: http://perfectwebtutorials.com/2012/asp-net-vs-
php-complete-comparisons
5. Microsoft Corporation [online]. Microsoft SQL Server.
MSDN.
URL:http://msdn.microsoft.com/enus/library/
bb545450.aspx.
6. How tech [online].Advantages of SQL Server over
Oracal.
URL: http://www.ehow.com/list_6921255_advantages-
sql-server-over-oracle.html
7. TechTerms.com[online].DBMS.
URL:http://www.techterms.com/definition/dbms
8. Tutorialspoint[online]ADO.NETObject Model.
URL:http://www.tutorialspoint.com/vb.net/
vb.net_database_access.htm