‘’ONLINE SHOPPING STORE’’

Submitted By
Aroos Fatima 15MIT2664
Jawaria Shahid 15MIT2668
Rumana Noor 15MIT2673
Samina Safdar 15MIT2669
Supervised By:
Sir Shehzad Rafique
 Acknowledgement
Our first and foremost acknowledgement is to Allah Almighty for his entire blessings, which He
shower upon us. He gave us strength and enough courage and made us take the courageous
steps towards our destination, so that today we able to rise.
Secondly, we extend our sincere and heartfelt thanks to our esteemed guide and Supervisor
Mr. Shezad Rafique for providing us with the right guidance and advice at the crucial junctures
and for showing us the right way, as well as for allowing us to use the facilities available to
achieve our goal .We are also grateful to all other faculty members for being there for us all the
time.
Last but not the least we would like to express our deep sense of gratitude and convey thanks
to our parents for the support and encouragement they have given us during the course of our
work and to everyone who helped us and support us during the completion of this project.
Chapter 1: Final Project Proposal

• Abstract
Online Shopping also known as electronic commerce or ecommerce is a type of industry or a
provided platform where buying and selling is conducted over an electronic system or
medium such as internet. This website is for online shopping. The main objective of this
website is to provide easy assistance to both the customer and merchant to interact with each
other for business purpose through a platform. It provides a system which controls the selling of
items and user can buy items sitting anywhere and anytime. It is a 365/24 service. All the data is
store in database and avoids any miscalculations.

• Introduction
“Shopping Triangle” is an online shopping website. This Online shopping website is to facilitate
the customers to buy products online with ease of “Click N Buy”. It’s a process of
implementing all the activities of the Shopping in an electronic and computerized automated way
to fasten the performance with ease.
It is known globally that, in today’s market it is extremely difficult to start a new business and
its maintenance is more difficult with competition from the already existed and well-
established and settled brands in market.
Most often, if the quality of the product is really good but due to a lack of advertisement or
running a new small scale business, it just becomes another problem for owner that the
product does not reach a larger group of customers. With the help of an online shopping
platform a seller can overcome this problem by selling his products globally.
In fast paced life of today when everyone is squeezed for time, the majority of people become
lazy and finicky when it comes to doing physical shopping. So if we think logistically here,
customers find more interesting and attractive products when they find it on the website of a
retailer directly and are able to see item’s details online. The customers of today are not only
attracted because online shopping is very convenient there are much more reasons for
preferring online shopping because they have broader selections of a product with highly
competitive prices in market and better information about the product including the feature of
other people’s reviews and extremely simplified navigation for searching regarding the desired
product.
Moreover, business owners often offer online shopping options at low rates with attractive
offers because the overhead expenses in opening and running a physical store are higher.
Further, with online shopping, their products have access to a worldwide market, which
increases the number of customers from all over the world.

• Project Title
“SHOPPING TRIANGLE AN ONLINE SHOPPING STORE”
• Project Overview Statement
The website is developed to allow the customer to shop virtually and customers can buy the
products of their desire from the store. The information of related products is stores on a DBMS
at the server side. The details of the items are brought forward from the database for the
customer view, based on the selection through the menu and the database of all the products
are updated at the end of each transaction.
The system after careful analysis has been identified to be presented with the following
modules and roles. The modules involved are:
• Administrator
• User

Project Title: Shopping Triangle An Online Shopping Store

Project Manager: Shezad Rafique
Project Members:
Name Registration # Email Address Signature
Aroos Fatima

Jawaria Shahid

Samina Saffdar

Romana Noor

Project Goal:
We want to develop a successful system that will fulfill the customer requirements by giving the
concept of ‘Click N Buy’ and ease of online shopping.
Objectives:
Sr.#

1 Facilitates easy shopping online from anywhere.

2
Provides information about the products in categories.
3
Customer can Mange and view items in cart.
4 The customers register with their details and get authentication
5 Administrator has full authority of check and balance with control on managing the entire
tasks related to website.
Project Success criteria:
A project success criterion depends on the successful operational modules.
Organization Address: Punjab College for Women Jhelum

Type of project: Research Development

Target End users: Customers

Development Technology: Object Oriented Structured

Platform: Web based Distributed
Desktop based Setup Configurations
Other_____________________
Approved By: Project Coordinator
Date:
• High Level System Components
We are going to present information about the main functional units of the entire system. High
level system components are a set of modules assembled together to deliver a solution to a
present problem. Our high level components are:
• ADMINISTRATOR:
The administrator is the super user of the system as a controller. Only admin have access into
this admin page. The administrator has all the information about all the users, their accounts,
orders and information about all products and available stock.
This module is divided into different sub-modules:
• Mange Products:
• Add Products
• Delete Product
• Mange Order
• View Order
• Delete Order
• Mange User:
• View User
• Add User
• Delete or Block User

2. UERS:
User is the customer who visits website for shopping. These users are anyone with shopping
experience and the know-how to browse through a shopping website. They must have basic
understandings about computers and the internet. This module is futher divided into sub-
modules:
• Registration:
A new user will have to register in the system by providing essential details in order to
place an order or to buy a product.
• View Products:
 User can view the list of products based on their names after successful login. A detailed
description of a particular product with product name, products details, product image and
price can be viewed by users.
• Search Product:

Users can search for a particular product in the list by name.

• Add To Cart:
The user can add the desired product into his cart by clicking add to cart option on the
product. User can even view his cart by clicking on the cart button. All products added by
cart can be viewed in the cart. User can remove an item from the cart by clicking remove.
• Submit Cart:
After confirming the items in the cart the user can submit the cart by providing a delivery
address. On successful submitting the cart will become empty.
• Edit Cart:
The user can view and edit his cart.
• Sustainability
Sustainability is ensured through demonstrating how good project design leads to good project
implementation. This will encourage all us to attach greater priority to the requirement and
project design phases and should improve development.
• Assumptions
For every business type whatever your requirements are, our experts can combine the right
software, and hardware to give you a reliable solution you need to boost productivity and
efficiency of the business.
• Project Plan
• Management
It is a section where you can find the product, user and user’s log time. Where we can add,
delete and retrieve the data. An area where you can find the detailed products companies
with sales transactions and transaction log.
• Deliverables
Provide a list and a brief description of all the tangible project deliverables.
• Application Architecture

Admin

Online Shopping Website

Users

Database

• Gantt Chart
ID TASK NAME START FINISH DURATI marc apr ma jun jul Ag se
h il y e y u p
 ON
1. A:Preliminary 3/1/201 4/8/2017 5w 4d
investigation
7
2. B:System 4/1/201 4/22/201 3w 1d
Analysis
7 7
3. C:Project 4/5/201 5/13/201 5w 4d
Planning 7 7
4. D: System 5/1/201 6/10/201 6w
Design 7 7
5. E:Logical 5/7/201 5/17/201 3w
Design 7 7
6. F:Physical 5/14/20 6/17/201 5w
Design 17 7
7. G:user 6/1/201 6/24/201 3w 3d
Interface 7 7
Design
8. H:Database 6/11/20 7/19/201 5w 4d
Design 17 7
9. I:Admin Login 7/1/201 7/31/201 4w 3d
Module 7 7
10 J:Insert Stock 7/9/201 8/20/201 6w 1d
. Module 7 7
11 K:Insert 8/1/201 8/17/201 2w 3d
. customer info 7 7
module
12 L:View stock 8/6/201 8/28/201 3w 2d
. module 7 7
13 M:view 8/21/20 9/12/201 3w 2d
. customer info 17 7
 14 N:Delete 9/1/201 9/30/201 4w 2d
. customer info 7 7
module
15 O:Integartion 9/10/20 10/11/20 4 w 4d
. 17 17
16 P:testing 6/20/20 10/14/20 16w 4d
. 17 17
17 Q:Implementa 7/16/20 9/16/201 9w
. tion 17 7

18 R:Mentanince 8/11/20 10/15/20 9w 3d

. 17 17

• Hardware and Software Specifications

Any hardware or software specification e.g. machine type required, operating system and other
utilities should be clearly specified for the system to be developed.
Hardware and software specification include the following:
• Hardware Specification
• Processor: Intel Pentium 4
• RAM: 512 MB
• Processor speed: 1.7 GHz
• Hard disk: 40GB
• Keyboard
• Mouse

• Software Specification
• Operating system: Window 8.1
• Documentation Tool: Microsoft Office
• Tools and Technologies used with Reasoning
• Wamp Server (localhost)
• Microsoft Visio (creating UML Diagrams)
• Star UML (creating UML Diagrams)
• Adobe Photoshop (interfaces)
• Wordpress
• Theme (Divi)
• Plugins: WooCommerce
• Plugins:MailChimp

• Cost and Risks

Discuss the expected impact of the project and its expected outcomes. Provide detail on
expected and potential costs and risks. Also, consider both one-time as well as on-going costs
and risks (i.e., maintenance and support). Wherever possible, quantify the impact of the
solution.

• In your discussion speak to the following areas of impact

• positioning to take advantage of other opportunities
• effect on business processes and workflow
• staffing (number of staff required, training, redefinition of roles)
• effect on client base/end users
• budget (i.e., incremental costs needed; potential savings
2.1 Chapter 2: First Deliverable

2.2 Introduction
Nowadays Information Technology (IT) has a great effect on the business world. With the help
of IT commercial and operating process are done during a few seconds instead of days or weeks
& this caused better servicing to the customers in comparison to the past. Electronic business has
turn to an important subject in the world of business & all organizations which are after the
improvement of efficiency & outrunning the competitors are affected by this. Electronic business
describes the new modules of avocations and includes the administration and coordination of the
main processes of avocation along with the vast usage of computers, information technology,
network technology &computerizing the data.
First deliverable is all about planning and scheduling of project. That deliverable on a
Project is the specific modules that you have to produce in order to complete the project.
It describes the modules which produced as a result of the project that is intended to be
delivered to a user.
• Project Costing
• Task Dependency Table
• Critical Path Method Analysis (CPM Analysis)
• Gantt Chart
• Introduction to team members
• Tasks and member assignment table
• Tools and Technologies
• Vision Document
• Risk List
• Product Features
2.3 Project Feasibility Report:-
When a project is started the first matter to establish is to assess the feasibility of a project or
product. Feasibility mean's the state or degree of being easily or conveniently done. Feasibility
also refers the extent to which appropriate data and information are readily available or can be
obtained with available resources such as staff, expertise, time and equipment. It is used as a
measure of how practical or beneficial the development of a software system will be to you (or
organization). Through feasibility report we assess solutions of the present problems and
determine which of these are viable for further analysis. There are many types of feasibilities:
2.4 Technical Feasibility:-
Technical feasibility assessment is based on an outline design of Electronic business (shopping
triangle) requirements, to determine whether the system has the technical knowledge to
handle completion of the project. Electronic business evaluated from the technical point of
view. An E-commerce site (shopping triangle) is developed within latest technology. Electronic
business is technically feasible for development. Different tools and technology are used for
development of this system. The site (shopping triangle) should be user friendly so that user
can easily operate it .The site’s (shopping triangle) design will be very effective. The member of
project have complete grip on tools and technologies which we use to develop for our system.

2.5 Operational Feasibility:-

Operational feasibility is a measure of how well a E-commerce site serves the user, and takes
advantage of the opportunities identified during scope definition. In the operational feasibility
we study problems and solve their problems about this system are available the user can easily
access to the E-commerce site.
2.6 Economic Feasibility:-
The purpose of the economic feasibility assessment is to determine the economic benefits to
the organization that the E-commerce site will provide. This assessment typically involves a
cost/benefits analysis. Economic feasibility determines the costs of developing and
implementing of our E-commerce system. Therefore, economic can be divided into two parts:
1: Cost estimated.
2: Benefits estimated.
Cost estimates can be further to be alienated into development or acquisition costs (one time)
and maintenance and operation costs (ongoing).
********Assume that we have 5000 lines of code********

2.7. Schedule Feasibility:-

Time is an important factor. So we keep the arrangement of time in our mind for different
tasks. A project will fail if it takes too long to be accomplished.. Some projects are initiated with
clearly defined deadlines. The deadlines and milestones are kept in our mind. Before starting
the project all the tools are installed in our system for developing this system. Firstly work on
interface than perform other activities. The assessment and evaluation of the system will be
complete with the available members and resources within the given time period. By following
the milestones and meeting the deadlines all process of the system is very scheduled.

2.8. Specification Feasibility:-

All the requirements are clearly define in the specification feasibility. All the requirments of the
system well defined by the customer. Everyone easily interact with E-commerce
Site through user interface. This system is easily can use in different devices and platforms
e.g. (Windows OS, Machantosh OS, Mobile browser)
2.9. Information Feasibility:-
E-commerce site interface is helpful and informative for all the persons who interact with it or
who want to get any information about products and buy these too. A rich variety of
information will be available on E-commerce user interface.
2.10 Motivational Feasibility:-
Valid user can use this system with identification and authentication process.
2.11. Legal and Ethical Feasibility:-
Legal/ethical feasibility describes whether the E-commerce conflicts with legal requirements,
e.g. the user entering data (id, passwords, address, banking information) will be safe. There is
no legal and ethical problem by this site. There are not any infringements or liabilities arise
from this project.
2.12 Project/Product Scope
The scope of ecommerce is very bright the reason behind is that now a days each any every
person is having their own smart phones in each and every hand they are also having many
electronic gadgets with them through which the consumers are always looking for online
shopping in which they are able to see more that 1000 brands and also able to see many
varieties under it. Consumers are also have the option of cash on delivery. Therefore they can
save their time to travel.
2.13 Project Costing

2.14 TASK DEPANDENCY TABLE

ID TASK START FINISH DURATION PREDECESSORS
1 A: Preliminary 12/7/2015 1/29/2017 8w
investigation
2 B: System analysis 1/11/2017 3/15/2017 9w 2d A
3 C: Project planning 2/1/2017 3/10/2017 5w 4d B
4 D: System design 2/25/2017 4/25/2017 8w 3d B,C
5 E: Logical design 3/28/2017 5/6/2017 8w D
6 F: Physical design 4/15/2017 5/30/2017 6w 2d D,E
7 G: User interface design 5/2/2017 6/10/2017 6w E,F
8 H: Designing pages 5/20/2017 6/24/2017 5w 1d
9 I: Admin login module 6/10/2017 7/8/2017 4w 1d H
10 J: Insert stock module 6/27/2017 7/27/2017 4w 3d I
11 K: View stock module 7/11/2017 8/11/2017 4w 4d I,J
 12 L: Insert costumer info 7/27/2017 8/26/2017 4w 3d
module
13 M: View costumer info 8/8/2017 9/8/2017 4w 4d L
module
14 N: Delete costumer info 8/22/2017 9/22/2017 4w 4d M
module
15 O: Integration 9/19/2017 10/19/2017 4w 4d I,J,K,L,M,N
16 P: Testing 6/15/2017 10/20/2017 18w 2d O
17 Q: Implementation 9/1/2017 11/2/2017 9w P
18 R: Maintenance 11/2/2017 1/6/2017 9w 3d Q

2.16 CPM-CRITICAL PATH METHOD

Further explanation will describe critical path method
2.17 Specify the individual activities
TASK
Preliminary investigation
System analysis
Project planning
System design
Logical design
Physical design
User interface design
Designing pages
Admin login module
Insert stock module
View stock module
Insert costumer info module
 View costumer info module
Delete costumer info module
Integration
Testing
Implementation
Maintenance

2.18 Determine the sequence of the activities

ACTIVITY DESCRIPTION REQUIRED DURATION
PREDECESSORS
A Preliminary investigation 8w
B System analysis A 9w 2d
C Project planning B 5w 4d
D System design B,C 8w 3d
E Logical design D 6w
F Physical design D,E 6w 2d
G User interface design E,F 6w
H Database design 5w 1d
I Admin login module H 4w 1d
J Insert stock module I 4w 3d
K View stock module I,J 4w 4d
L Insert costumer info 4w 3d
module
M View costumer info module L 4w 4d
N Delete costumer info M 4w 4d
module
O Integration I,J,K,L,M,N 4w 3d
P Testing O 18w 2d
 Q Implementation P 9w
Maintenance Q 9w 3d
R

2.19 Draw the network diagram

2.20 Critical path method diagram

ACTIVTY Immediate Predecessor DURATION

A None 8w
B A 9w 2d
C B 5w 4d
D B,C 8w 3d
 E D 6w
F D,E 6w 2d
G E,F 6w
H 5w 1d
I H 4w 1d
J I 4w 3d
K I,J 4w 4d
L 4w 3d
M L 4w 4d
N M 4w 4d
O I,J,K,L,M,N 4w 3d
P 18w 2d
Q O,P 9w
R Q 9w 3d
2.21 Gantt Chart

• Figure 2.1: Gantt Chart

2.22.Introduction to team members and their skill set

Here is a brief introduction of the team members their skill set. This skill set would especially be
representative of the tasks and activities assigned to her.
There are four team members which are included in this project.
• Aroos Fatima (M1)
 Role: Group Leader
Skill Set: Web Designing, Adobe Photoshop, Design Diagram, JavaScript
• Jawaria Shahid (M2)
Role: Group Leader
Skill Set: Web Designing, Adobe Photoshop, Design Diagram, JavaScript
• Samina Saffdar (M3)

Role: Group Member

Skill Set: Web Designing, Design Diagram, JavaScript
• Romana Noor (M4)
Role: Group Member
Skill Set: Web Designing, Design Diagram, JavaScript

2.23Task and member assignment table

TASK DURATION DEPENDENCIES
T1 8w M1,M3
T2 9w 2d M2.M3
T3 5w 4d M1,M4
T4 8w 3d M1,M2,M3
T5 6w M4
T6 6w 2d M2,M4
 T7 6w M1
T8 5w 1d M1,M3
T9 4w 1d M2
T10 4w 3d M1
T11 4w 4d M4
T12 4w 3d M2
T13 4w 4d M1
T14 4w 4d M2
T15 4w 3d M3,M4
T16 18w 2d M1,M2,M3.M4
T17 9w M1,M2,M3.M4
T18 9w 3d M1,M2,M3.M4

2.24 .Tools and technologies with reasoning

2.25 .Wordpress
WordPress is an online, open source website creation tool written in PHP. But in non-geek
speak, it’s probably the easiest and most powerful blogging and website content management
system (or CMS) in existence today.
2.25 . Notepad++

Notepad++ is a text editor and source code editor for use with Microsoft Windows. It supports
tabbed editing, which allows working with multiple open files in a single window. Notepad++ is
one of the most popular source code editors in the world, and supports syntax highlighting and
code folding for over 50 programming, scripting, and markup languages. Matching tag
highlighting (for HTML and XML tags).
2.26 Wamp server
Wamp is a regularly updated to the latest releases of Apache, MariaDB, PHP and Perl .It also
come with the number of other modules. Wampalso provide support for creating and
manipulating database.
2.27 Microsoft Visio
Microsoft Visio is software designed to translate complex information from text and table into
diagrams.

2.28 Vision Documents

Introduction
A vision document defines the scope and purpose of the project. It is a clear statement of the
problem for which we find the solution. It also includes the complete statement of the solution.
Purpose
The purpose of this document is to define the high level requirement of our project.
Scope
This vision document applies to an E-commerce site which facilitates the user to shop online
with ease from anywhere without travelling the physical markets, developed by IT department.
Definitions, Acronyms and Abbreviations
This is a comprehensive list of all terms used in this vision document.
E-commerce (electronic commerce or EC):
E-commerce is the buying and selling of goods and services, or the transmitting of funds or
data, over an electronic network, primarily the internet. These business transactions occur
either as business-to-business, business-to-consumer, consumer-to-consumer or consumer-to-
business.
Vendor:
A company/person who is in the business of selling products and goods to Businesses.
Inventory:
A detailed list of goods and materials that are in stock.
User:
A person who can interact with the software – can be an employee or end user (Customer).
Sales:
The overall money transaction during a specified time interval.
Transaction:
The exchange of goods or services for legal tender.
References
None.
2.29 Product Features
Ease of use:
The product must be easy to use. Simplicity should be a goal in good design. Focus on the user
experience by providing shopping categories, filters, and comparison capabilities. Consider
easy-to-find customer reviews and FAQ information to help buyers make decisions more
quickly.
High resolution pictures:
Images sell, not text. E-commerce websites should display multiple photos per product. The
photos need to be high-resolution and optimized for page load.
Transactions
The product must be able to interface the sales registers with the database in order to update
the total count of each product available in the E-commerce store at a given time.
2.30 Quality Ranges
Reliability
The system shall be designed to be robust and be able to handle a large amount of traffic. The
system must be able to handle improper user input. The system shall be designed in a manner
that is free of security flaws.
Usability
The system shall enable the users to navigate and perform operations in an intuitive and easy
manner. The user interface must allow the user to search for the books in a timely manner.
Also, vendors must access the system in a secure manner and the product information.
However, they should have this capability during the business day but not affect the business
operations of our website.
Supportability
The system shall be designed for easy maintenance and upgradability. The system must
continue operating at a constant pace with a maximum load.
Functionality
The system shall be designed such that a user can get information of products in the E-
commerce store for the buying the clothes, shoes, beauty and health products etc . The system
shall be designed in a manner that user can navigate easily throughout the website.
Performance
The system shall be designed to handle a large amount of traffic.
2.31 RISK LIST
The possibility of suffering harm or loss in terms of danger is called risk.
Risk may be related to the failure of hardware or software.
Data can be destroyed.
Unauthorized access.
If there is any mistake in typing records it can easily recovered and updated.
2.32 PROJECT FEATURES
Followings are the project features:
Admin Login:
Admin Login module is used by admin to secure the system by unauthorized access.
Insert Stock:
This module provides stock management for E-commerce store. The module uses rules for
implementation of the stock insertion.
View Stock:
This module provides information about all products that are available in store.
Mange User:
This part specifies to admin through which admin of site is able to mange user or customer of
store who register, login or place the order.

Costumer Registration :
Costumer (User) login module is used by costumer himself to gain access to his account on the
E-Commerce store. By accessing his account he can check his orders, order list, place new
orders. Costumer (User) login Security module improves the security options in the “E-
commerce store (shopping triangle)”.
2.33 The search bar:
The search bar in our store will gain access to costumer to search the specific item he is looking
for this makes it easy to use and more reliable.

2.34 Product Categories:

Every item in the store is categorized and there are different modules for those items. So
the costumer will only see those products that are related to that module or
category.
Chapter 3: Second Deliverable for Object Oriented Approach

3.1 Introduction:
Nowadays Information Technology (IT) has a great effect on the business world. With the help
of IT commercial and operating process are done during a few seconds instead of days or weeks
& this caused better servicing to the customers in comparison to the past. Electronic business has
turn to an important subject in the world of business & all organizations which are after the
improvement of efficiency & outrunning the competitors are affected by this. Electronic business
describes the new modules of avocations and includes the administration and coordination of the
main processes of avocation along with the vast usage of computers, information technology,
network technology &computerizing the data.
First deliverable is all about planning and scheduling of project. That deliverable on a
Project is the specific modules that you have to produce in order to complete the project.
It describes the modules which produced as a result of the project that is intended to be
delivered to a user.
Project Costing
Task Dependency Table
Critical Path Method Analysis (CPM Analysis)
Gantt Chart
Introduction to team members
Tasks and member assignment table
Tools and Technologies
Vision Document
Risk List
Product Features
3.1.1. Systems Specifications
It is the process of collecting the requirements of a system from users, customers and other
stakeholders for creating E-commerce store.

3.1.2. Requirements analysis and negotiation

Requirements negotiation and analysis is the most crucial process in requirements engineering
for creating E-commerce store. All the stakeholders have a common goal to build a system.
They do have their own perspectives and perceptions.

3.1.3. Requirements specification

Is a formal description for creating E-commerce store application?

3.1.4. System modeling

A system model represents aspects of a system and its environment. Systems modeling or
system modeling is the interdisciplinary study of Creating “E-commerce site”.

3.1.5. Requirements validation

Requirements and specifications and that fulfill its purpose. Requirement validation procedures
are used for checking the system that meets.

3.1.6. Requirements management

Requirements management process for documenting, analyzing on requirements and then
controlling change and communicating to relevant stakeholders. It is a continuous process for
“E-commerce site”.

3.17. System specification

The following are the clauses that must be included while describing the system specifications.
3.1.7.1Introduction
Electronic commerce (ecommerce) is a type of business model, or segment of a larger business
model, that enables a firm or individual to conduct business over an electronic network,
typically the internet. Also sometimes written as "e-commerce" or "ecommerce".
 3.1.7.2Existing system
There are numbers of disadvantages of existing system in retail shop. The existing system has
several modules. All modules currently run manually. It is very difficult to manage huge stock of
products. Now online stores became essential thing for time saving and making the purchasing
and buying products easily.
3.1.7.3. Scope of the system
The scope of ecommerce is very bright the reason behind is that now a days each any every
person is having their own smart phones in each and every hand they are also having many
electronic gadgets with them through which the consumers are always looking for online
shopping in which they are able to see more that 1000 brands and also able to see many
varieties under it. Consumers are also having the option of cash on delivery and online payment
option also. Therefore they can save their time to travel

3.2. Context level data flow diagram

3.3. Capture "shall" Statements

Para# Initial Requirements
 1.0 Admin “shall” log in to admin account.
1.0 Admin “shall” enter the new stock in database.
1.0 Admin “shall” view and manage stock.
1.0 Admin “shall” view and manage the product detail in stock.
1.0 Admin “shall” enter new product record in database.
1.0 Admin “shall” view and manage product record on user side interface.
1.0 Admin “shall” delete stock.
2.0 Admin “shall” get payment.
2.0 User “shall” start new buying process.
2.0 User “shall” check order detail of products.
3.0 Customer “shall” order for products.
3.0 Customer “shall” get receipts.
3.0 Customer “shall” pay for products.
4.0 System “shall” check the validity of Customer.
4.0 System “shall” calculate bill.
4.0 System “shall” generate total bill.

3.4. Allocate Requirements

Para# Initial Requirements USE CASE
1.0 Admin “shall” log in to admin account. UC_ admin_ login
1.0 Admin “shall” enter the new stock in database. UC_ enter_ stock
1.0 Admin “shall” view and manage stock. UC_ View_ manage_
stock
1.0 Admin “shall” view and manage the product detail in UC_ View_ manage_
stock. products
1.0 Admin “shall” view and manage employee record. UC_ manage_
employee_ record
 1.0 Admin “shall” delete stock. UC _delete _stock
2.0 Customer “shall” start new sale process. UC _process _sale
2.0 Customer “shall” check order detail of products. UC _check _order
3.0 Customer “shall” request for item. UC _request _for _item
3.0 Customer “shall” pay for products. UC _pay _payment
4.0 System “shall” check the validity of Customer. UC _check _validity
4.0 System “shall” calculate bill. UC _calculate_ bill
4.0 System “shall” generate total bill. UC _generate _receipt

Chapter 4: Third Deliverable For Object Oriented Approach

4.1 Introduction:
Third deliverable is all about the software design. In the previous deliverable, analysis of the
system is completed. So we understand the current situation of the problem domain. Now we
are ready to strive for a solution for the problem domain by using object-oriented approach.
Following artifacts must be included in the 3rd deliverable.

• Domain Model
• System Sequence Diagram
• Sequence Diagram
• Activity Diagram
• Collaboration Diagram
• Operation Contracts
• Design Class Diagram
 • State Transition Diagram
• Data Model
• Package Diagram
• Component Diagram

Now we discuss these artifacts one by one as follows:

Domain Model Of “ONLINE STORE” System:
4.2 SEQUENCE DIAGRAM

4.2.1 System Sequence Diagram of “ONLINE STORE”:

4.2.2 Sequence Diagram of(Admin Login):
4.2.3 Sequence Diagram of(Insert Stock):

4.2.4.State diagram for buying of an item:

4.2.5 UML ACTIVITY DIAGRAM FOR CUSTOMER ORDERING SYSTEM :
 4.3. Collaboration diagrams:

4.3.1. Collaboration Diagram of (Inserts Stock):

• Operation Contracts:
A UML Operation contract identifies system state changes when an operation happens.
Effectively, it will define what each system operation does. An operation is taken from a system
sequence diagram. It is a single event from that diagram. A domain model can be used to help
generate an operation contract.
 Use case Sign up
name
Scope E-commerce store
Level System functionality
Primary actor Admin
Secondary Customer
actor
Preconditions Enter name and password
Post Press sign up button for sign up.
conditions
Main success 1: enters name and password in to specific space.
scenario 2: wants quick response from system.
Special System, operating system
requirements
Alternative If he enter wrong ID then he roll back to interface of sign up.
scenario
Frequency of It depends on admin or customer.
occurrence
Stakeholder Admin or Customer: Both enters the Name and Password.
and interest System: System checks the validity of the both.

4.4.1 Use case of sign up:

Use case Log in
name
Scope E-commerce Application
Level User goal
Primary actor Administrator, Customer
Secondary System
actor
Preconditions Sign up
Post Successful login
conditions
Main success Admin enter his sign up information then log in.
scenario
Stakeholders Admin or Customer wants quick response from system.
& their
interest
Frequency of Depends on occurrence of system response.
occurrence
Alternate If the system hangs he will bought another system and replace to it.
Scenario

4.4.1 Use case of log in:

Use case Insert stock

name
Scope E-commerce website
Level System functionality
Primary actor System
Secondary Admin
actor
Preconditions Get request from customer
Post Update stock
conditions
Main success 1: System take the stock information.
scenario 2: System save the stock information in to Database.
Special System
requirements
 Alternative If system has any error to insert of stock then system will check the
scenario error.
Frequency of It depends on system performance.
occurrence
Stakeholder Cashier: Cashier wants quick and accurate response from the
and interest system.
System: System wants valid information from the cashier .

4.4.2 Use case of Insert stock:

Use case Generate Total bill

name
Scope E-commerce
Level System functionality
Primary actor System
Secondary Admin
actor
Preconditions Check basket
Post Calculate total bill
conditions
Main success System calculate bill according to purchased items and generates
scenario total bill.
Special System, operating system.
requirements
Alternative If system has any error to generate bill system will check the error.
scenario
Frequency of It depends on system performance.
occurrence
Stakeholder Quick and accurate response from the system.
and interest
4.4.3 Use case of Generate receipt:

Use case Update stock

name
Scope E-commerce
Level System functionality
Primary actor Administrator
Secondary System
actor
Preconditions Process sale
Post Generate bill
conditions
Main success System calculate total bill and generate total bill.
scenario
Special System, operating system
requirements
Alternative None
scenario
Frequency of It depends on admin and system.
occurrence
Stakeholder Admin enters accurate information into system and wants accurate
and interest information from system.
System: System checks the validity of the Customer.

4.4.4 Use case of update stock:

Use case Get payment
name
Scope E-commerce
Level System functionality
Primary actor Customer
Secondary Admin
actor
Preconditions Process sale
Post Give bill
conditions
Main success 1: System calculate total bill and generate the total bill.
scenario 2: Customer pays the bill on delivery .
Special System, operating system
requirements
Alternative None
scenario
Frequency of It depends on system.
occurrence
Stakeholder Customer enters accurate information into system and wants
and interest accurate information from system.
System checks the validity of the Customer and wants accurate data.

4.4 .5 Use case of payment :

Use case View customer info
name
Scope E-commerce
Level System functionality
Primary actor Administrator
Secondary Customer
actor
Preconditions Successful login.
Post Get info from system
conditions
Main success System check and update modify the information of customer.
scenario
Special System, operating system
requirements
Alternative None
scenario
Frequency of It depends on Administrator and system.
occurrence
Stakeholder Customer enters accurate information into system
and interest system checks the accurate information of customer.

4.4.6 Use case of View customer info:

Use case Process of purchase

name
 Scope E-commerce
Level System functionality
Primary actor Customer
Secondary System
actor
Preconditions Customer subscription
Post Successful subscription, authentication of customer and search
conditions products.
Make purchases.
Main success Customer subscription to the website.
scenario System doing process.
Special System, operating system
requirements
Alternative None
scenario
Frequency of It depends on customer and system.
occurrence
Stakeholder Customer enters accurate information into system
and interest

4.4.7Process of Purchase
CHAPTER 5: 4TH DELIVERABLE (USER INTERFACE DESIGN)

5.1 Introduction
“Shopping Triangle” is an online shopping website. This Online shopping website is to
facilitate the customers to buy products online with ease of “Click N Buy”. It’s a process of
implementing all the activities of the Shopping in an electronic and computerized
automated way to fasten the performance with ease.
It is known globally that, in today’s market it is extremely difficult to start a new business
and its maintenance is more difficult with competition from the already existed and well-
established and settled brands in market.
Most often, if the quality of the product is really good but due to a lack of advertisement
or running a new small scale business, it just becomes another problem for owner that the
product does not reach a larger group of customers. With the help of an online shopping
platform a seller can overcome this problem by selling his products globally.
In fast paced life of today when everyone is squeezed for time, the majority of people
become lazy and finicky when it comes to doing physical shopping. So if we think
logistically here, customers find more interesting and attractive products when they find it
on the website of a retailer directly and are able to see item’s details online.

5. 2 Site Map for Administrator:

System Modules

Insert Stock

View Stock

Login
Delete Stock

Main page

Add/Delete User

Manage Products

View Order
5. 3 Site Map for customer:
 Chapter6: 5th DELIVERABLE (Software Testing)

6.1 Introduction
Online shopping is a form of electronic commerce which allows customer to directly buy goods
or services form a seller over the internet using a web browser. Consumer find a product of
internet by visiting the website of the retailer directly or by searching among alternative
vendors using a shopping search engine.
6.2 Test Plan:
6.3 Purpose:
Online shopping is a form of electronic commerce which allows consumers to directly buy
goods or service form a seller over the internet using a web browser…online stores typically
enable shoppers to use ‘search’ features to find specific models brands or items.
6.4 Outline:
A test plan shall have the following structure:
• Test plan identifier

• Introduction

• Test items

• Features to be tested

• Features not to be tested

• Approach
 • Item pass/fail criteria

• Suspension criteria and resumption requirements

• Test deliverables

• Testing tasks

• Environmental needs

• Responsibilities

• Staffing and training needs

• Schedule

• Risks and contingencies

• Approvals

6.5 Test Plan Identifiers:

A software Test Plan is a document describing the testing scop and activities.it is the basis
formally testing any software product in a project.A document describing the scop approach
resource and schedule of intended test activities.
6.6 Introduction:
This document\ is intended to give a complete planning of a systematic strategy for online
shopping.
6.7 Test Items:

• Mange profile
• Mange stock
• Mange categories
• Mange bill
• Mange sale
• Mange purchase product
• Mange employee info
 • Report Generate

In this section we will provide a list of all those components that has been identified as test
items. All of the items that constitute the "online shopping" will be tested during the system
test to insure that they work together to implement the user's requirements.

The basic performance test:

The most critical performance measures to test are:
• Response time for Admin login.

• Response time for updating information.

• Response time for requested records.

6.8 Features To Be Tested:

The following is the list of features to be tested:
Features Priority Description
Add profile 1 Create profile for admin
Add stock 1 All stock record in the system
Add categories 2 All detail about the product
Add bill 3 Detail about the bill recorded in
the system
Add sale 1 Detail about the sale product
Add purchase product 1 Info about the purchase product
Add employee info 1 Add employee record in the
system
Login 1 Login as authenticate user

Logout 1 Logout from the system

Technological Feature
Database 1 Access to data
base is frequently
needed operation.
So this technical
feature should be
tightly in control
for ONLINE
SHOPPING for shoe
retail store system.
 6.9 Approach:
We are following these test approaches which are given here under as:
6.10 (1)White Box Testing :
In white box testing, the UI is bypassed. Inputs and outputs are tested directly at the code level
and the results are compared against specifications.
6.11(2) Black Box Testing:
Black box testing typically involves running through every possible input to verify that it results
in the right outputs using the software as an end-user would. We have decided to perform
Equivalence Partitioning and Boundary Value Analysis testing for the website.
6.12 (1)Equivalence Class Partitioning :
In considering the inputs for our equivalence testing, the following types will be used:
• Legal input values (Valid Input)–Test values with in boundaries of the specification
equivalence classes.

• Illegal input values (Invalid Input)–Test equivalence classes outside the boundaries of
the specification.

Using these Valid and Invalid classes testing engineer will generate test cases.

6.13 (3)Boundary Value Analysis:

The acceptable range of values for this application was set by the development team. At the
time of testing developer will define the boundary value and generate test case for performing
the boundary value analysis.

• Integration Testing

Integration tests exercise an entire subsystem and ensure that as set of components play nicely
together.
• System Testing

The goals of system testing are to detect faults that can only be exposed by testing the entire
integrated system or some major part of it. Generally, system testing is mainly concerned with
areas such as performance, security, validation, load, and configuration sensitivity. But in our
case we well focus only on Performance and load testing.

6.14 .(a)Performance Testing :

This test will be conducted to evaluate the fulfillment of a system with specified performance
requirements. It will be done using black-box testing method. And this will be performed by:
• Storing the maximum data in the file and trying to insert, and observe how the
application will perform when it is out of boundary.

• Deleting data and check if it follows the right sorting algorithm to sort the resulting data
or output.

6.15 (b)Load Testing:

The test will perform after executing a performance test. This will help to develop the loading
quality of the website. Tester will perform the test using visual studio and generate a
performance graph.
6.16 User Interface Testing:
User Interface (UI) testing verifies a user’s interaction with the software. The goal of UI testing
is to ensure that the UI provides the user with the appropriate access and navigation through
the function soft he target-of-test. In addition, UI testing ensures that the objects within the UI
function as expected and conform to corporate or industry standards.
6.17 Item pass/fail criteria:
The criteria's for each phase of testing must be met before then next phase can commence.
Now the criteria’s for pass and failure given below.
• According to the given scenario the expected result need to take place then the scenario
will be considered as pass otherwise that criteria should be failed.

• If an item tested 10 times, 9 times perfectly worked and single time do not work
properly then it will consider as fail case.

• System crash will be considered as fail case.

 • After submitting a query in the system, if expected page won’t appear then it will be
considered as fail case.

6.18 Test deliverables:

The following documents will be generated as a result of these testing activities:
• Test plan (this document)

• Test Design Specifications

• Test case specifications

• Test procedure specifications

• Test Item transmittal reports

• Test logs

• Test incident report.

• Test summary reports

6.19Testing tasks:
TASK ASSIGNED TO
Create Acceptance Test Plan Jawaria , samina
Create Integration Test Plan Samina , rumana
Define Unit Test rules and Procedures Rumana , aroos
Define Turn over procedures for each level Jawaria, aroos
Verify prototypes of Screens Aroos , Jawaria , Rumana , Samina

6.20 Environmental needs:

The following elements are required to support the overall testing effort at all levels within the
“E-commerce store” project:
• Access to the online store (desktop system).
• Access to the database.
• Access to the environments used by the Admin.
• Systems functional structure created by Mind map.
 • Use visual studio for performance and load testing.
6.21 Responsibilities:
Identify groups responsible for managing, designing, preparing, executing, witnessing, checking
and resolving that will help the whole team to deliver a quality full desktop system.
6.22 Staffing and training needs:
This section outlines show to approach staffing and training the test roles for the project.
Staffing is fixed for the duration of this project. It is likely most of the staff will assume some
testing role.
The following roles are identified:
• Project Manager: Responsible form and aging the total implementation of the Website.
• Test Manager: Responsible for developing the master test plan, reviewing the test
deliverables, managing the test cycles, collecting metrics and reporting status to the
Project Manager, and recommending when testing is complete.
• Test Engineer: Responsible for designing the tests, creating the test procedures, creating
the test data, executing tests, preparing incident reports, analyzing incidents, writing
automated test procedures, and reporting metrics to the test manager.
• The test manager and test engineers should be familiar with the system development
life cycle methodology.

6.23Risks and contingencies:

Serial Risk List Contingencies Plan

No

1 Data can be destroy Data can recover thorough the

software.
2 Unauthorized access Use the security process to make
the system secure
3 Hardware can be destroy Use affecting protections to secure
the hardware
 4 System might be slow Use boost up clears for the fast
speed

6.24 Approvals:
The test plan will be approved by the whole team.
Signature: _______________________
Date: _______________________
Print Name: _______________________
Title: _____________________
Role: _____________________

Signature: _______________________
Date: _______________________
Print Name: _______________________
Title: _______________________
Role: _______________________

Signature: _______________________
Date: _______________________
Print Name: _______________________
Title: _______________________
Role: _______________________

_________________________________________

Signature: _______________________
Date: _______________________
Print Name: _______________________
Title: _______________________
Role: _______________________

_________________________________________