Essay: Online shopping system

1. INTRODUCTION

The business-to-consumer aspect of electronic commerce (e-commerce) is the most visible business use of the World Wide Web. The primary goal of an e-commerce site is to sell goods and services online.
This project deals with developing an e-commerce website for online computer and its related parts selling. It provides the user with a catalogs of different computer parts available for purchase in the store. In order to facilitate online purchase a shopping cart is provided to the user.
In order to develop an e-commerce website, a number of Technologies must be studied and understood. These include server and client side scripting techniques, implementation technologies such as .NET, programming language (such as C#, ASP.NET), relational databases (SQL Server 2008).
This is a project with the objective to develop a basic website where a consumer is provided with a shopping cart application and also to know about the technologies used to develop such an application.
This document will discuss each of the underlying technologies to create and implement an e-commerce website.

1.1 Project summary
The main goal of this project was to create a shopping cart, which allows customers to shop and purchase the Webyep products online. Moreover, the project is also designed in such a way it lets admin person manage the products information online.
The Webyep online sells wine cellars (store). Customers can orders products, and they will be contacted to further process the orders.

1.2 Purpose
The purpose of this document is to present a detailed description of the online shopping system. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli.

1.3 Scope

This system will be an online shopping system for selling products online. This system will be design to assist consumer to compare prices and make purchases, without having to leave their homes or offices from around the globe. The system provides an online shopping facility with a simple shopping cart.

1.4 Objectives
The objective of the system is to develop simple & easy way to purchasing products.
The main objective of this system is to sale online products of Webyep.
The system is capable of maintaining details of various customers, products and storing all the day-to-day transactions such as generation of shipment address bill, handling customers and updating of stores.

1.5 Literature Review and Technology used

1.5.1Microsoft Visual Studio-2010 with ASP.NET
What is ASP.NET?
ASP.NET is a development framework for building web pages and web sites with HTML, CSS, JavaScript and server scripting. ASP.NET is a server-sideWeb application framework designed for Web development to produce dynamic Web pages. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. ASP.NET allows you to use a full featured programming language such as C# (pronounced C-Sharp) or VB.NET to build web applications easily.

1.5.2. Advantages of Using ASP.NET :

‘ ASP.NET drastically reduces the amount of code required to build large applications.
‘ ASP.NET makes development simpler and easier to maintain with an event-driven, server-side programming model.
‘ ASP.NET pages are easy to write and maintain because the source code and HTML are together.
‘ The source code is compiled the first time the page is requested. Execution is fast as the Web Server compiles the page the first time it is requested. The server saves the compiled version of the page for use next time the page is requested.
‘ The HTML produced by the ASP.NET page is sent back to the browser. The application source code you write is not sent and is not easily stolen.
‘ ASP.NET makes for easy deployment. There is no need to register components because the configuration information is built-in.
‘ The Web server continuously monitors the pages, components and applications running on it. If it notices memory leaks, infinite loops, other illegal software or activities, it seamlessly kills those activities and restarts itself.
‘ ASP.NET validates information (validation controls) entered by the user without writing a single line of code.
‘ ASP.NET applications run fatter and counter large volumes of users without performance problems.

1.5.3. HTML
HTML was originated by Tim Burners-Lee.. HTML is a computer language devised to allow website creation. HTML is Hyper Text Markup Language. It consists of series of short codes typed into a text-file by the site author-these are tags. The text is then saved as a HTML files, and viewed through a browser, like Internet Explorer or Mozilla Firefox.
These browsers read the file and translate the text into visible form.HTML document file extension is ‘html’ or ‘htm’.

1.5.4. CSS
‘ CSS stands for Cascading Style Sheets
‘ Styles define how to display HTML elements
‘ Styles were added to HTML 4.0 to solve a problem
‘ External Style Sheets can save a lot of work
‘ External Style Sheets are stored in CSS files

1.5.5. JAVA SCRIPT
JavaScript is an interpreter, object-based scripting language. Although it has fewer capabilities than full-fledged object-oriented language like C, C++ and java, JavaScript is more that sufficiently powerful for its intended purpose.
JavaScript is not cut-down version of any other language (it is only distantly and indirectly related to java), and it is not a simplification of anything. It is, however, limited. You can’t write standalone application in it, for example, and it has little capability for reading or writing files. Moreover, JavaScript scripts can run only in the presence of an interpreter, either in web browser.
1.5.6. Jquery
JQuery is free, open source software, dual-licensed under the MIT License or the GNU General Public License, Version 2. JQuery’s syntax is designed to make it easier to navigate a document, select DOM elements, create animations, handle events, and develop Ajax applications. JQuery also provides capabilities for developers to create plug-ins on top of the JavaScript library. This enables developers to create abstractions for low-level interaction and animation, advanced effects and high-level, theme-able widgets. The modular approach to the JQuery library allows the creation of powerful dynamic web pages and web applications. A fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development.

1.5.7. Ajax
AJAX = Asynchronous JavaScript and XML.
AJAX is a technique for creating fast and dynamic web pages.
AJAX allows web pages to be updated asynchronously by exchanging small amounts of data with the server behind the scenes. This means that it is possible to update parts of a web page, without reloading the whole page.
Classic web pages, (which do not use AJAX) must reload the entire page if the content should change.
AJAX is based on internet standards, and uses a combination of:
‘ XMLHttpRequest object (to exchange data asynchronously with a server)
‘ JavaScript/DOM (to display/interact with the information
‘ CSS (to style the data)
‘ XML (often used as the format for transferring data)

1.5.8. Microsoft SQL Server 2008
‘ Microsoft SQL Server 2008 is a strong backbone database system to manage all the inserted data. SQL Server 2008 is also used to manipulate the query to find and retrieve data based on our SQL statements. When connecting to an instance of SQL Server, your connection is associated with a particular database on the server.
‘ SQL Server 2008 introduced “MARS” (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes.
What’s new in Microsoft SQL Server 2008’? Microsoft SQL Server 2008 extends the performance, reliability, qualified and ease-to-use of Microsoft SQL Server version 7.0 Microsoft SQL Server 2008includes several new features that make it an excellent database platform for large-scale transaction processing (OLTP),data warehousing , and e-commerce applications.
‘ The OLAP services feature available in SQL server version 7.0 is now called SQL server 2008 analysis Service .the term OLAP Service has been replaced with the term Analysis Services. Analysis Services also includes a new data mining component.

2.PROJECT MANAGEMENT
Software Project Management is an umbrella activity within software engineering. This chapter provides how to plan, track and estimates this application by managing various phases. It encompasses Project Development Approach’s justification, Schedules, risk analysis, cost and effort estimation.
2.1 PROJECT PLANNING
The successful project development is the well-planned strategy for the best and optimal use of resources available. Project management begins with a set of activities that are collectively called project planning. Effective management of a software project depends on thoroughly planning the progress of the project.
A well-planned strategy leads to the best and optimal use of the resources available and ensures completion of project on time. Project plan sets out the resources available to the project, the work breakdown and a schedule for carrying out the work. The project needs a lot of research and thus scheduling was a difficult task as there was a need for carrying out a lot of study about various algorithms and techniques and testing them at various stages, thus maintaining the schedule was also difficult.
2.1.1 Project Development Approach and Justification
Software Process model is an abstract representation of a software process. Each process model represents a process from a particular perspective so only provides partial information about that process. These generic models are not definitive descriptions of software processes. Rather, they are useful abstractions, which can be used to explain different approaches to software developments. For many large systems, of course, there is no single software process that is used. Different processes are used to develop different parts of the system. Development approach of any project depends on many factors. They are like resources, clear-cut information available in the form of requirements, process maturity, tool maturity, manpower with skills, time duration to develop, complexity and criticality of the project.
2.1.2 Project Plan
‘ Planning is the most important project management activity.
‘ A well-planned strategy leads to the best and optimal use of the resources available and ensures completion of project on time.
‘ The overall goal of project planning is to establish a sensible strategy for controlling, tracking and monitoring a project.
‘ Project plan sets out the resources available to the project, the work breakdown and a schedule for carrying out the work.
‘ Planning provides estimates for resource, cost and schedule (i.e. time duration to complete project).

2.1.3 Milestones and Deliverables
Table 1. Milestones and deliverables
Milestones Deliverables
Studying various modules of Steganography& its problems. Project Planning. Have started collecting the Requirements.

SPMP
Still continue with requirements of organization with regards to user of the system to be included.
Gathering the requirements of the project using different fact finding techniques. Progress Report
Understanding the project in depth and doing the requirement analysis by studying process of hiding information like text using bitmap image or wave sound.

SRS
Requirement Classification & Feasibility Study. Time, Cost, Risk & Work Analysis. Model specification.

Creating Custom UML design based on analysis. Progress Report
Started System Flow Diagram.

2.1.4 Roles and Responsibilities
Table 2. Roles and Responsibilities
ACTIVITY MEMBERS DESCRIPTION
ANALYSIS Member1 Detailed Analysis was carried out by both members.
DESIGN& CODING Member1 Detailed Design was carried out by both members.

2.2 PROJECT SCHEDULING
Work Breakdown Structure

Fig. 1 Work Breakdown Structure
Time Line Chart

Fig. 2 Time line chart

2.3 RISK MANAGEMENT
‘ Risk can be defined as the exposure to injury or loss.

‘ Risk management is an area in which the negative effect on cost, schedule and quality
Of the project can be minimized.

‘ During the risk management, commonly occurring unexpected events are handled.

‘ In Risk management, the effect of risk is minimized.

2.3.1. Risk Identification
Risk identification can be defined as the efforts taken to specify threats to the projectplan. Risk identification can be done by identifying the known and predictable risks. The risk items can be identified using following known and predictable component.

Product size- The risk items based on the overall size of the software product is identified.
Customer characteristics – Risks associated with customer-developer communicationCan be identified.

Development environment – The risks associated with the technology and tool being for developing the project.

2.3.2. Risk Analysis
Requirements Changes:-
As project work proceeds may requirements changes. Users may change theirrequirements.

Project time line non completion:-
In event of not being able to complete project in provided time, it would be difficult to face clients of the project. Also, financial problems can arise from project being delayed.

Project Risk:-
This type of risk can threaten the project plan. That is, if project risks become real, it is likely that project schedule, personnel, and requirement problems and their Impact on a software project.

Technical Risk:-
This type of risk can threaten the quality and timeliness of the software to be produced. If a technical risk becomes a reality, implementation may become difficult or impossible.

Increased complexity risk:-
In event of project becoming too complex for uses to understand, it would be difficult to implement it. It is prime required that project should be easy and effective enough for anybody to understand.

Business risk:-
This type of risk can threaten the viability of the software to be built. Business riskOften jeopardizes the project or the product.

2.3.3. Risk Planning
Accept risk:-
Simply take the chance that the negative impact will be incurred.

Avoid risk:-
Changing plans in order to prevent the problem from arising.

Mitigate risk:-
Lessening its impact through intermediate steps.

Transfer risk:-
Outsource risk to a capable third party that can manage the outcome.

2.4ESTIMATION
2.4.1. Effort Estimation
Table 3. Effort Estimation
COUNT Average
No. Of External Inputs 7 4 28
No. Of External Outputs 4 5 20
No. Of External Inquiries 2 4 8
No. Of Internal Logical Files 4 10 40
No. Of External Interface Files 0 7 0
Count = Total 96.00

Justification:
1) No of External Input
1. Set of parameters that generate account code
2. Set of parameters that generate group
3. Set of parameters that generate ledger
4. Set of parameters that generate unit
5. Set of parameters that generate stock group
6. Set of parameters that generate item
7. Set of parameters that generate accounting voucher

2) No of External Output
1. Account Creation
2. Inventory Creation
3. Balance sheet
4. Profit and Loss Report

3) No of External Inquiries
‘ Both reports generated by this system can be asked for decision making purpose as well as to judge overall performance of the enterprise.

4) No of Internal Logical Files
1. User File-Stores information regarding all user of the enterprise
2. Account File-Stores information regarding all available ledgers, accounts on which transaction can be performed, of the enterprise
3. Inventory File-Stores information regarding all available items of the enterprise
4. Accounting Voucher File-Stores information regarding all different accounting vouchers of the enterprise
5. No of External Interface Files
‘ As now this system is not integrated with any external system so right now no input from this system is going to be store to the data base of other system.

Table 4. Complexity adjustment values
Reliable Backup & recovery 3
Data communication required 5
Distributed processing functions 0
Performance criticality 3
Existing operational environment 0
On-line data entry 0
Input transaction over multiple screens 1
Updating of master files 4
Complexity of inputs ,outputs, files or inquiries 3
Complexity of internal processing 4
Reusability 3
Conversion/installation in design 3
Multiple installations 3
Application designed for change 2
‘(Fi) = 34

Function Point value = Count Total * [0.65 + 0.01 * sum of (Fi)]
= 96 * [0.65 + 0.01 * 34]
= 95.04
Fi is the sum of the weights assigned to the functions as per its importance in the software.

2.4.2. Cost Analysis
LOC = FP * Programming Language (Object Oriented =30)
= 95.04* 30
= 2851.2
Table 5.Cost Analysis
Project Type ab bb cb db
Organic 1.8 1.01 1.7 0.25

Effort (E) =ab (KLOC) bb
= 1.8 * 2.8512 * 1.01
= 5.18

Duration (D) = cb (E) db
= 1.7 * 5.18* 0.25
= 2.20
Avg. staffing = Effort/ Duration
= 5.18/2.20
= 2.35 persons

Avg. productivity = LOC / Duration
= 2851.2/ 2.20
= 1296 LOC/PM

3. SYSTEM REQUIREMENTS STUDY

3.1 USER CHARACTERISTICS
The system will be used for ticket booking. The administrators and online users will be the main users. Given the condition that not all the users are computer-literate. The system is also designed to be user-friendly. It uses a Graphical User Interface (GUI).

Administrators:
They all have post-secondary education relating to general business administration practices. Every administrator has basic computer training. They are responsible for all of the scheduling and updating day/night employee shifts.

Users:
The Users dose online shopping of products and need some knowledge about computer and Internet.

3.2 HARDWARE AND SOFTWARE REQUIREMENT
Hardware
‘ Processor : Computer that has a 1.6GHz or faster processor
‘ Ram : 1 GB(32 bit) or 2 GB (64 bit) RAM
(Add 512 MB if running in virtual machine)
‘ Hard Disk Space : 3 GB
Software
‘ Operating System : – Windows XP (x86 & x64)
– Windows Vista (x86 & x64)
– Windows 7 (x86 & x64)
‘ Front-End Tools : – Microsoft Visual Studio-2010
‘ Back-End Tools : – SQL Server 2008

3.3 CONSTRAINTS
3.3.1. User Interface
The user interface for software shall be compatible to user which can access to the system. The user interface shall be implemented using any tool or software package like servlet, asp, jsp etc.

3.3.2. Communication Interface

The System will perform the following functions:

‘ Sophisticated and user friendly interface for all passengers.

‘ Individual account or profile for each user related to the system.

‘ Sophisticated interfaces for all people who related to the system.

‘ Implement bus, passenger, driver and staff database systems.

‘ Implement Account System for managing invoices.

‘ Each passenger needs only one barcode i. e. PIN and username for walking through every step.

‘ Keep secret for all of passenger profiles. Each division can see only necessary data of each passenger for analyzing.

‘ Internet connection to work on with the system.

‘ Emergency help system in case of any accident and any other technical or non-technical problem or risk.

‘ Functional Requirements

3.3.3. Hardware Interface

We would need the Intel Core2Duo system and 1 GB of Memory at the minimum for the client. The corporate server needs to be a server class machine with at least 2 GB and Intel Xeon system per rack and 15 TB of storage at the minimum. And also have the
Dedicated links between the server and clients.

3.3.4. Software Interface

The client machines require Microsoft Windows XP or better. The corporate server requires Red Hat Enterprise Linux AS 5 (RHEL 5) and Oracle Database 11g Enterprise Edition to hold on to all archives. Also both the client and server computer must have internet browser to work online.

3.4 ASSUMPTIONS AND DEPENDENCIES

‘ It is assumed that one hundred IBM compatible computers will be available before the system is installed and tested.

‘ It is assumed that the agency will have enough trained staff to take care of the system

‘ The system uses licensed third party software products.

‘ The system is volatile. If the electric power is lost. The PMS system will go do.

4.SYSTEM ANALYSIS

4.1 STUDY OF CURRENT SYSTEM
The phase of system analysis process deals with problems which are affecting in the current manual system. The problems are those which are affecting the organization in it daily routine work.
As the growing trend in InfoTech World of computers need of accuracy, perfect ness, speed and high memory data storage is a must. Each and every problem must be solved with a least amount of time and energy.
The problems faced by Current system are described as below:
‘ Difficulty in Maintenance of Records.
‘ Time Consuming.
‘ Editing of data becomes a tedious job.
‘ No Security of Data.
‘ Mistakes Occurring in long Calculations [Bill Calculations, Fine Charges, etc.]
‘ Proper Generation of Daily Sheet (i.e. Daily Sheet)
‘ Lack of Efficiency and Man Power.
‘ High Data Redundancy.
‘ Data Inconsistency.

4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM

‘ During the 10s days work in company so problem in the company work in manually work and all process is register and file.
‘ The problem in work in to the manual so company efficiency is low and time is consuming.
‘ The maintain several registry in the stock purches report, customer purches report, supplier report, sales purches report, purches inquiry detail report, details of the item of supplier report and customer details, item bill amount report, item purches report ,company report etc all this process time was very lost.
‘ It provides a number of analytical reports that will help for Online E- Shopping system to analyze the performance. We are providing reports on details in stock, perches, supplier, billing, customer details report.
‘ This system developed in ASP.net for create web application and the purpose of networked application. You have to create login criteria for admin and other user. Also generate the report like stock report, purchase report, sells report. User can insert, edit, delete and searching the data according to their requirement. By the use of this system we can save a time and accuracy the system is the very give the answer accuracy.
‘ This system is use to we can reduce the time and speed is increased compare the manual system. A computerized system generates the automatic calculation and manages all the System in one system so you require more meant to manage your system.
‘ The system you have to manage of the item. Generate the purchase bill and sales bill and maintain stock according to purchase item and selling item. The computerized system is very easy to use manual system.

4.3 REQUIREMENTS OF NEW SYSTEM

4.3.1. Functional Requirement Specification
(1) Guest
‘ Create new account (Register)
‘ Browse Products
‘ View Product Details
‘ View static pages
(2) Registered User
‘ Login
‘ My Orders
‘ Browse Products
‘ View Product Details
‘ Give Rating for Particular product(Optional)
‘ Buy Product (Checkout)
‘ Logout

(3) Admin
‘ Login
‘ Dashboard
‘ Site Member(Customer) Management
‘ Product Category Management
‘ Order Management
‘ Location Management(Country, State, City, Locality)
‘ Logout
4.3.2. Non-Functional Requirement Specification
(1) Usability Requirement
‘ Color what we use in this website design are must be attractive.
‘ Fonts that use for user interface design are must be in uniform.
‘ Easy navigation are preferable to do any task.
‘ Home page should be centralized system to go to any feature and to get any result.
‘ The facility to return to home page from any page should available.
‘ Lables of all objects in the entire system must be in understandable form.

(2) Performance Requirement
‘ It has to load, within the industry standard time.
‘ Respond time should be 2 seconds.

(3) Compatibility Requirement
‘ It should support all type of Hardware versions, Operating systems, and Browsers.

4.4 FEASIBILITY STUDY

An important outcome of the preliminary investigation is the determination that the system is feasible or not. The main aim of the feasibility study activity is to determine whether it would be financially and technically feasible to develop a project .The feasibility study activity involves the analysis of the problem and collection of all relevant information relating to the product such as the different data items which would be input to the system, the processing required to be carried out on these data, the output required to be produced by the system as well as the various constraints on the behavior of the system.

4.4.1. Techanical Feasibility

We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All theresources needed for the development of the software as well as the maintenance of thesame is available in the organization here we are utilizing the resources which are available already.

4.4.2. Economical Feasibility

Development of this application is highly economically feasible .The organization needednot spend much m one for the development of t he system already available. The only thing isto be done is making an environment for the development with an effective supervision. Ifwe are doing so , we can attain the maximum usability of the corresponding resources .Evenafter the development , the organization will not be in a condition to invest more in the organization .Therefore, the system is economically feasible.

4.4.3. Operational Feasibility

It is a measure of how well a proposed system solves the problems, and takes advantages of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development.

‘ The newer system will fit to its existing system and perform more functions than manual system.
‘ The users of the system will get the information at the time when they need it.
‘ The system will work when it is developed and installed and there are no major barriers to its implementation. This accounts for the operational feasibility of the proposed system.

4.4.4. Schedule Feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this means estimating how long the system will take to develop, and if it can be completed in a given time period using some methods like payback period. Schedule feasibility is a measure of how reasonable the project timetable is.

4.5 . REQUIREMENT VALIDATION
A. INPUT/OUTPUT
‘ System shall have a form to accept the customer details.
‘ System shall have a form to accept the Plant details.
‘ System shall display transaction details.
‘ . System shall provide search facility on customer name, Order Placed, date of order, date of order dispatch, date of transaction, transaction amount, credit card no etc
‘ System should provide facility for change in address/name.
‘ System should maintain the details about placing order/dispatch or order. i.e., order status

B. PROCESSING
‘ System should automatically generate the bill.
‘ System should inform the pending order and make changes if the order is dispatched.

C. ERROR HANDLING
‘ Should report any errors on duplicate primary keys.
‘ Should report any ‘Out of Range’ values on numeric fields
‘ Should report any data type mismatches any field on the forms.
‘ Should report on any ‘Invalid dates’
‘ Should report any violation of authorization of rights
‘ Should report any Invalid Login errors

4.6 FEATURE OF NEW SYSTEM
Easy to understand.
It is easier to work well with exiting system with reference to person.
Less economical.
Exiting system does not have any compile error, accidentional error, soft ware failed, hard ware failed.
It is more protected with reference to any system.
No time consuming.
More than futures add this project.
It is very difficult to work with the proposed system with reference to the person who has list knowledge of computer.

4.7 USE CASE DIAGRAM
Customer
5

manager

Stock database

Administrator

4.8. CLASS DIAGRAM

4.9. SEQUENCE AND COLLABORATION DIAGRAM
4.10. SYSTEM ACTIVITY
4.11. MAIN MODULE OF NEW SYSTEM
ADMINISTRATOR:

In this module, maintain all the information to manage the stock for different kind of Product’s brand & their associated Models & also related different kinds of Accessories from different suppliers as a Purchase and Sales to various kinds of the customers. Also to maintain information about related stocks for the Items.

LOGIN:

In this module, the User or Company which have been already registered themselves, are allow to login in their account. The Company or User, who are login are capable to Buy & sale the Products through their account. And they can check all the details of their registration.

STOCK:

In this module, the administrator can check the stock of different types of the products. If the stock of some products is not available and the products quantity is finish to the administrative, the user or the company can’t purchase those products.

PAYMENT:

It contains the payment information of customer and the company who is registered and purchases the products. It also store the payment related information like Price, Quantity of items, and also recorded either they paid full payment or through the Check or Master Cards.

4.12 SELECTION OF HARDWARE AND SOFTWARE JUSTIFICATION
Table 9.Hardware Selection
Hardware Items Requirements Justification
CPU Intel Pentium III It processes faster during the accessing the system/application.
Memory Minimum 64 MB It’s initial memory size to run the application after development.
Disk Space Minimum 4-5 GB For the Larger storage of data.

Table 10.Software Selection
Software Items Requirements Justification
Operating System Microsoft Windows 2010/ME/XP/Vista, Linux, Solaris Because this system is connected using LAN in network and window 2000 is best for network connection.
Front End Microsoft asp.net Used for application which needs very low development and lifecycle costs and Rapid development
Back End SQL Server It’s a Free available Source.
Web Server TOMCAT5.0.19 Server It’s the current version of TOMCAT and it acts as a container to run the Servlet and jsp pages both

5. SYSTEM DESIGN
5.1 System Application Design

‘ An application design is a meaningful engineering representation of a Mobile
application that is used to be human being. A design can be needed for the
people’s requirements and can be assessed for easy to use.
Such a design should:
1. Good architectural structure
2. be modular
3. contain distinct representations of data, architecture, images, and
components (modules)
4. lead to components that exhibit dependent operation characteristics
‘ To design this application we used the UML diagram. What was the reason to
choose this method is as under’? It provides features like reuse, quality, an emphasis on modeling the real world,
resistance to change, encapsulation and abstraction etc.

1. Faster Development: This was the requirement of the application.
2. Reuse of Previous work: This was required in the application because it
is going to extend further to meet the other requirement of the
organization.
2. Increased chat: This was function requirement of the Buddy’s chat.
4. Modular Architecture: This was required the modification in the
Application.
5. Better Mapping: Only the OOD provides the mechanism.
Less complexity.
6. Problem Domain: When server is down then application work slowly or
close application but at that time application use more than one server or
high speed server so, that problem is solve. .

5.1.1 Method Pseudo Code
1). Method for Importing master data from tally
[if Has child node] check for child node.
Check for group or ledger
If it is group
Store groupledgertype= ‘G’
Else if Check for Ledger
Store groupledgertype= ‘L’
Check for parent node
If parent node present
Store parent node id with respect to ledger.
Else
Store parent node id as null.
Check for next node
Call recursively this method
2 ). Importing Trial Balance For Particular company from XML file
Read each xml node while end of file come
If xml node has child node then
Check that ledger or Group in Master table
If exist then
Store to database
Else
Add to Exception Report
End while
Recursively call this function until all xml node get refer.

5.2 Input And Output Interface Design
‘ State Diagram
State diagrams show the dynamic behavior of a system. The diagram shows
the various states that an object can get into and the transitions that occur
between the states.
Graphical Notation
‘ State:
The state object is a snapshot of an object at a particular point in its
life. A state may have an activity describing the function being performed.

‘ Initial State:
The initial state is the starting state of the object with reference to the
behavior that the diagram explains. Each state diagram should have only
one initial state.

‘ Final State:
Each final state is the ending state of the object with reference to the
behavior that the diagram explains. There may be multiple final states for an
object.

‘ Transition:
The transition link represents the relationship between different states of an
object. The transition guard is a condition which limits the cases in which a
transition can occur.

Fig 9 State diagram for order shipping

5.3 DATABASE DESIGN

5.3.1 Logical Description of Data
Table 8. Data Dictionary
Table 8.1 Register :

Description : Register is used to store username and password for data security and also store user information.
Fields Data Type Size Constraint Description
register_id Int Primary key Id of register
login_id int Foreign key Id of login user
Fname varchar MAX Not null First name of register user
Lname Varchar MAX Not null last name of register user
Gender Varchar MAX Not null Birth-date of user
Phone No. varchar MAX Not null Gender Of use
EmailId Varchar MAX Not null Email-id of register user
CityId int Foreign key Id of City Name

Table 8.2 Login :

Description : Login is used to store username and password for User.
Fields Data Type Size Constraint Description
login_id Int Primary key User_id
user_name Varchar MAX Not null Name of user name.
Password Varchar MAX Not null Password of the Admin for their security purpose.

Table 8.3 Locality :

Description : Locality is used to Area Information.
Fields Data Type Size Constraint Description
Local_id Int Primary key Id of area
Local name Varchar MAX Not null Name of area
CityId Int Foreign key Id of city

Table 8.4 City

Description : City is used to city Information.
Fields Data Type Size Constraint Description
city_id Int Primary key Id of city
City name Varchar MAX Not null Name of city
Stated Int Foreign key Id of state

Table 8.5 State

Description : State is used to state Information.
Fields Data Type Size Constraint Description
Stated Int Primary key Id of state
State name varchar MAX not null Name of state
countryid Int Foreign key Id of country

Table 8.6 Country

Description : Country is used to country Information.
Fields Data Type Size Constraint Description
Countryid Int Primary key Id of country
Country name Varchar MAX not null Name of country

Table 8.7 Category

Description : Category is used to Product Information.
Fields DataType Size Constraint Description
CategoryId Int Primary key Id of country
Category Name Varchar MAX not null Name of country

Table 8.8 Product Type

Description : Product Type is used to store product information.
Fields Data Type Size Constraint Description
ProductTypeId Int Primary key Id of product
CategoryId Int Foreign key Id of product category.
PTName Varchar MAX Not null Name of product Type
Description Varchar MAX Not null Image of product Description

Table 8.9 SubProduct

Description : Sub Product is used to store product information.
Fields Data Type Size Constraint Description
ProductId Int Primary key Id of Subproduct
ProductName Varchar MAX Not Null Name of Subproduct
PurchasePrice Float Not null PurchasePriceofSub product
SalesPrice Float Not null SalesPrice of Subproduct
BrandId Int Foreign Key Id of BrandName
CategoryId Int Foreign Key Id of CategoryName
ProductTypeId Int Foreign Key Id of ProductType
Quantity Int Not null Quantity of Subproduct
Description Varchar MAX Not null Description of Subproduct
Photo Varchar MAX Not null Image of SubProduct

Table 8.10 Add to Cart

Description : AddToCart is used to buy product information.
Fields DataType Size Constraint Description
Cartid Int Primary key Id for cart
RegId Int Foreign key Id of register
ProductName Varchar MAX Foreign key Name of SubProduct
Salesprice float Not null Price of Sales
Description Varchar MAX Not null Description of SubProduct

Table 8.11 Shipping Address

Description : Shipping Address is used to store info where product ship.
Fields Data Type Size Constraint Description
ShippingAddressId Int Primary key Id for shipping address
First name Varchar MAX Not null First Name of user
Last name Varchar MAX Not null Last Name of user
Address Varchar MAX Not null Address of user
Locality_id Int Foreign key Id of Area
Zip Code Int Not null Pincode of city area
Mobile Varchar MAX Not null Mobile No Of User
EmailId Varchar MAX Not null Email Of user

Table 8.13 CheckOut

Description : CheckOut is used to store user Purchase Product Information.
Fields Data Type Size Constraint Description
Checked Int Primary key Id of Check-out
cartId Int Foreign Key Id of AddToCart
Unitprice Float Not null Unit Price of Sub Product
Quantity Float Not null Quantity of Sub Product
Totalprice Float Not null Total Price of All Sub Product
ShippingAddressId Int Foreign Key Id of Shipping Address

5.3.2 Table and Relationship

Fig. 10 Table And Relationship

6. IMPLEMENTATION
6.1. Implementation Environment
‘ This system is web Base application. Implements in any network area which is in LAN or WAN So, any person can use this online e-shopping application.
‘ These are just a few Reports which could be further enhanced according to the
requirement,
‘ Better Backup facility can be developed in the future.

‘ Various searching record techniques can be implemented according to the need
For the betterment of the project
6.2. Security Feature
This system is provided with authentication, without this user can pass. So only the legitimate users are allowed to use the application. If the legitimate users share the authentication information then the system is open to outsiders.

6.3. Coding Standard

7.TESTING
7.1. Testing plan
Testing is the process of running a system with the intention of finding errors. Testing aims at detecting error-prone areas. The implementation is the final and important phase. It involves user-training, system testing in order to ensure successful running of the proposed system. The user tests the system and changes are made according to their needs. The testing involves the testing of the developed system using various kinds of data. While testing, errors are noted and correctness is the mode.

7.2. Testing Strategy
‘ Testing is a process of executing a program with the intent of finding errors.

‘ A Successful test case is one that uncovers an as- yet-undiscovered error.
System testing is a stage of implementation, which is aimed at ensuring that the system works accurately and efficiently as per the user need, before the live operation commences. As stated before, testing is vital to the success of a system. System testing makes a logical assumption that if all parts of the as system are correct, the goal will be successfully achieved. A series of tests are performed before the system is ready for the user acceptance test.

7.3. Testing Method
‘ Unit Testing

Unit testing focuses efforts on the smallest unit of software design. This is known as module testing. The modules are tested separately. The test is carried out during programming stage itself. In this step, each module is found to be working satisfactory as regards to the expected output from the module.

‘ Integration Testing

Data can be lost across an interface. One module can have an adverse effect on another, sub functions, when combined, may not be linked in desired manner in major functions. Integration testing is a systematic approach for constructing the program structure, while at the same time conducting test to uncover errors associated within the interface. The objective is to take unit tested modules and builds program structure. All the modules are combined and tested as a whole.

‘ Validation

At the culmination of the integration testing, Software is completely assembled as a package. Interfacing errors have been uncovered and corrected and a final series of software test begin in validation testing. Validation testing can be defined in many ways, but a simple definition is that the validation succeeds when the software functions in a manner that is expected by the customer. After Online shopping project report validation test has been conducted, one of the three possible conditions exists.
a) The function or performance characteristics confirm to specification and are accepted.
b) A deviation from specification is uncovered and a deficiency lists is created.
c) Proposed system under consideration has been tested by using validation test and found to be working satisfactory.

‘ Output Testing

After performing the validation testing, the next step is output testing of the proposed system, since no system could be useful if it does not produce the required output in a specific format. The output format on the screen is found to be correct. The format was designed in the system design time according to the user needs. For the hard copy also the output comes as per the specified requirements by the user. Hence output testing did not result in any correction for the system.

‘ User Acceptance Testing

User acceptance of a system is the key factor for the success of any system. The system under consideration is tested for the user acceptance by constantly keeping in touch with the prospective system users at the time of developing and making changes whenever required.
This is done in regard to the following point:
a) Input Screen Design
b) Output Screen Design
c) Format of reports and other outputs.

‘ Security mechanisms

This system is provided with authentication, without this user can pass. So only the legitimate users are allowed to use the application. If the legitimate users share the authentication information then the system is open to outsiders.

7.4. Test Cases
Exhaustive testing of almost any non-trivial system is impractical due to the fact that domain of input values to most practical software systems is either extremely large or infinite. Therefore we must design an optimal test suite that is of reasonable size and can uncover as many errors in system as possible. The test cases to consider in the project are
‘ Separate authentication for both the front end as well as back end.
‘ Inclusion of all eligible data and modules to be tested.
‘ Testing individual module according to requirement.
‘ Privacy to the admin as well as the user who becomes the part of the website.
‘ Updating of the information from time to time.

7.4.1. Purpose
The purpose of the test cases is to test the various input and see whether the output produces any error or not. There are different test cases according to the system. A correct system must accomplish the following:
‘ Compute correct results.
‘ Operate safely, and cause the system containing the software to operate safely.
‘ Perform the tasks required by the system containing the software, as explained in the software applications.
‘ Achieve these goals for all inputs
7.4.2. User Test Cases
Test Case Id : 1
Module: Registration
Test case Description Expected Output Actual Output Test Status
On click Register Open registration page Open registration page Pass
Unfilled data and submit Display Message- <* fields> required. Message is displayed :
<* Fields> required Pass
Unfilled data and cancel Redirect to Home Page Redirected to Home Page Pass
Fill invalid data and click on submit Message :- Invalid should be displayed. Message :- Invalid is displayed Pass
Fill valid/invalid data and click on cancel Redirect to Home Page. Redirected to Home Page. Pass

Test Case Id : 2
Module: Login Page
Test case Description Expected Output Actual Output Test Status
Enter Invalid Username Message will display “Invalid User Name”.
Message display “Invalid User Name” Pass
Enter invalid invalid password.
Message will display “Invalid Password”. Message display “Invalid Password”. Pass
Login with the valid username and Password
Register User login successfully and page must be redirect “Home page”.
Register User login successfully and page is redirected to “Home Page”. Pass

Test Case Id: 3
Module: Add to Cart
Test case Description Expected Output Actual Output Test Status
Add Product in Cart as a User User selects a product and clicks add to cart button Product is added to the shopping cart Pass
Add Product in Cart as a Guest Guest selects a Product and
clicks add to cart button and then checkout process Guest should create an account. Pass

Test Case Id : 4
Module: Edit Cart
Test case Description Expected Output Actual Output Test Status
Change Quantity User changes the Quantity
Quantity and total cost of Cart should be updated Pass
Delete Product from cart User deletes a product from shopping Cart Product and total cost of Cart should be updated Pass
Add Product In Cart User selects a new product to shopping Cart Add Product and total cost of Cart should be updated Pass

7.4.3. Admin Test cases
Test Case Id: 1
Module: Login Page
Test case Description Expected Output Actual Output Test Status
Admin Login Page It should open Admin Login Page. It opens Admin Login Page. Pass
Enter Proper Username password It will redirect to the Admin home page or related page It redirect to the Admin home page or related page. Pass
Enter valid/invalid username and valid/invalid password.
Validation will be fired- Message ‘Invalid username or Password”
Validation is fired- Message ‘Invalid Invalid username or Password’ Pass
Login with the valid username and Password
Admin user login successfully and page must be redirect “Home” page.
Admin user login successful and page is redirected to ‘Home Page ‘ Pass

Test Case Id: 2
Module: Home Page
Test case Description Expected Output Actual Output Test Status
Check that all the menu item display properly Proper display Proper display Pass

Test Case Id: 3
Module: Add and Delete Product from Product Category
Test case Description Expected Output Actual Output Test Status
Add Product from Category Admin add a new Product to Category Product should be
updated in database Pass
Delete Product from Category Admin delete a Product
from Category Product should be deleted in database Pass

Test Case Id: 4
Module: Add and Delete Product Category
Test case Description Expected Output Actual Output Test Status
Add New Category Admin Add a new Category Category should be updated to system Pass
Delete New Category Admin deletes a Category Category should be
deleted from system Pass

Test Case Id: 5
Module: Manage Order
Test case Description Expected Output Actual Output Test Status
Manage Order Admin accepts an order Order is processed Pass
Delete Order Admin delete an order Order is not processed Pass

Test Case Id: 6
Module: Manage Users
Test case Description Expected Output Actual Output Test Status
Manage User Admin accepts User as a member User is accepted Pass
Manage User Admin delete User User is not accepted Pass

8. SNAP SHOTS

8.1. USER PAGE

8.1.1 Home Page :

Fig.10 Home Page

8.1.2 Login Page :

8.1.3 About us :

8.1.4 Contact us:

8.1.5 Register Form :

8.1.6 Sitemap Form :

8.2. ADMIN PAGE

8.2.1 Country Form :

8.2.2 Brand Form :

8.2.3 Category Form :

8.2.4 Register Form :

8.2.5 Product Type :

9. LIMITATIONS AND FUTURE ENHANCEMENTS
9.1. Limitations
The system only provides authentication and authorization level security, not the other security aspects of higher level. Hence, a professional hacker may hack it. So it is not highly secured.
Due to the network traffic, the interaction between the client and server will reduce the performance.

9.2. Future Enhancements
Payment methods such as pay pal or credit cards will be available on this online shopping site.
We will Support E-mails and SMS alerts.
We can publish the discount to the regular Customer of the shop as well as the Time of the Festival.

10. CONCLUSION
10.1. Conclusion
The project entitled ‘E-commerce site for Webyep’ is developed using ASP.Net as front end and SQL Server 2008 database in back end to computerize the process of online selling of computer and it’s related parts. This project covers only the basic features required.
However a lot of features are already incorporated in this project. The main beneficiaries are both customers as well as ADMIN who consume more time while dealing with computer and it’s related parts. Moreover extra features can be identified and incorporated in the future.
In order to accommodate additional features it will take longer time and effort to understand the requirement and converting it into computerized system.

11. CANVAS SHEET
11.1 Observation Canvas :

Fig. 22 Observation canvas sheet

Observation Matrix Report:
Observation :
“E-commerce site WebYep” is a web based application that provide facility to user to purchase products online on WebYeb.
The objective of “E-commerce site for WebYep” is the simplify the process of online purchase system.
In these e-commerce system the user is able to online purchase product from selected area in Ahmadabad city, India.
Admin may manage products, orders, etc. Members can view and purchase products online and guest user can view product and create an account.
Scouted Challenges :
‘ The system is capable of maintaining details of various customers, products and storing all the day-to-day transactions such as generation of shipment address bill, handling customers and updating of stores.
Problems:
‘ The system only provides authentication and authorization level security, not the other security aspects of higher level. Hence, a professional hacker may hack it. So it is not highly secured.

‘ Due to the network traffic, the interaction between the client and server will reduce the performance.

‘ The current system of selling is time consuming and expensive.

‘ In the current system there are greater chances to avoidance of shopping by customer.
Final Problem :
‘ Payment methods such as pay pal or credit cards will be available on this online shopping site. We will Support SMS alerts.

11.2 Identical Canvas :

Fig.23 Idential canvas sheet

Identical Canvas Report :
People:
Admin, User, Student, Doctor, Teacher, Men, Women, Childrens.
Activity :
Online Payment, Rating, Data Feedback, Offers.
Situation/Context/Location:
Mall, Shopping Center, Exhibitions.
Props/Possible Solution:
Online Payment, Time Saving, Alert message, Update Customer.

11.3 PRODUCT DEVLOPMENT CANVAS :

Fig .24 Product Devlopment canvas sheet

Product Development Report :
Purpose :
Fast Accessibility.
People:
Admin, User, Student, Doctor, Teacher, Men, Women, Childrens.
Product Experience:
User Friendly Work, Proper Navigation.
Product Functions:
Manage User, Add Product, Update Product.
Product Features:
Efficient Execution, Save Money, Save Time.
Component:
Reliable Net Support, Visual Studio 2010, Router, Computer System
Customer Revalidation:
Admin Functionality : Block Users, Unblock user
Use Of Tags
Reject, Redirecting, Retain:
Way to Extract More Users.

11.4 IDENTIAL CANVAS 2:

Fig. 25 Idential canvas 2 sheet

Ideation Canvas 2 Report:
People:
Visitors, Admin, Users, Admin, User, Student, Doctor, Teacher.
Activities:
Add Product, Search Product, Online Payment, Rating, Data Feedback, Offers.
Problems:
Can Not See Product Live, Direct Adaptation Product is not possible.
Situation/Context:
Online, Laptop, Shopping Site, General User.
Props/Solution:
Higher Profit To User, Online Payment, Time Saving, Alert message.
Inputs:
Product Name, End Date, Image, New User, Search Topic .
Revenues:
Publish, Profit.

11.5 BUSINESS MODEL CANVAS :

Fig. 26 Business Model Canvas sheet

Business Model Canvas Report

‘ Key Partner : Publishers

‘ Cost Structure :
Technologies, Warehouses, Deep discount

‘ Key Activities :
Supply chain optimization, Delivery optimization, SEO,Auto recommendation

‘ Key Resource :Delivery stall

‘ Value Proposition :
Convenience, Wide selection,Cheaper, Tract (CD)

‘ Revenue Streams :Book sales

‘ Customer Relationship :
Through email, Online chat, Database marketing

‘ Channels : Web

‘ Customer Segment :
Urban Indian book lover
Internet lover people who have no credit cards
First time online shopper

Source: Essay UK - http://doghouse.net/essays/information-technology/essay-online-shopping-system/


Not what you're looking for?

Search our thousands of essays:

Search:


About this resource

This Information Technology essay was submitted to us by a student in order to help you with your studies.



Word count:

This page has approximately words.


Share:


Cite:

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay UK, Essay: Online shopping system. Available from: <http://doghouse.net/essays/information-technology/essay-online-shopping-system/> [21-02-19].


More information:

If you are the original author of this content and no longer wish to have it published on our website then please click on the link below to request removal:


Essay and dissertation help


Latest essays in this category:


Our free essays:

badges