E-Commerce Online Shopping Web Application Is A Lifestyle, Which Retails Various

[E-COMMERCE SHOPPING WEB APP] 2018-19
Abstract
E-commerce Online Shopping web application is a lifestyle, which retails various
fashion and lifestyle products (Currently Men’s Wear). This project allows viewing
various products available enables registered users to purchase desired products
instantly using PayPal payment processor (Instant Pay) and also can place order by
using Cash on Delivery (Pay Later) option.
The E-commerce Online Shopping is a web based application intended for online
retailers. The main objective of this application is to make it interactive and its ease of
use. It would make Searching, viewing and selection of a product easier.It contains a
sophisticated search engine for users to search for products specific to their needs. The
search engine provides an easy and convenient way to search for products where a
user can Search for a product interactively and the search engine would refine the
products available based on the user’s input. The user can then view the complete
specification of each product. Online Shopping provide sales and service to customer
by interaction with customer. The success of a company is mainly based on its
satisfied customers, which in turn gives huge
[DEPT OF COMPUTER PROGRAMME,BUB] Page 1

CHAPTER-01
INTRODUCTION
2.1 Project Description
The objective of project “E-COMMERCE ONLINE SHOPPING WEB

APPLICATIONS” It is an Ecommerce portal which allows formal and informal
merchants to advertise and sell their The Online Shopping is a web based application
intended for online retailers. The main objective of this application is to make it
interactive and its ease of use. It would make Searching, viewing and selection of a
product easier.It contains a sophisticated search engine for users to search for products
specific to their needs. The search engine provides an easy and convenient way to
search for products where a user can Search for a product interactively and the search
engine would refine the products available based on the user’s input. The user can then
view the complete specification of each product.
They can also view the product reviews and also write their own reviews. The
application also provides a drag and drop feature so that a user can add a product to the
shopping cart by dragging the item in to the shopping cart. The main emphasis lies in
providing a user friendly search engine for effectively showing the desired results and
its drag and drop behavious Goods on the internet. This would permit western
categorizing to manyoutlets formats for retailing food, personal care, fashion,
electronics and daily useable products to make available to the rest of the world
through internet. Online shopping store for. The website has a combination of Indian
and international products and it also has its own range of quality and standards. It is
an online shopping store for western fashion, catering to women’s wear,Men’s wear,
footwear, accessories, jewelry and beauty products. E-commerce, also known as
electronic commerce or e-business, is simply the buying and selling of goods and services
via an electronic medium, mainly the internet. The usage of electronic commerce has been
increasing rapidly in the last decades since its inception, prompting the majority of
businesses to have an online platform. It is now essential for companies to do their
business online, as virtually any kind of goods and services can be sold or purchased

through the internet. Online Shopping provide sales and service to customer by
interaction with customer. The success of a company is mainly based on its satisfied
customers, which in turn gives huge profits.
Retaining existing customers is also an important job of a company. Online Shopping

concentrates on the retention of customers by collecting all data from every
interaction, every customer makes with a company from 'all' access points whether
they are phone, mail, web or field. The company can them use this data for specific
business purposes viz., marketing, service, support or sales
Online Shopping is basically the collection and distribution of "all" data to "all" areas
of business. The data can then help market the company, help up sell to existing
customer, understand customers better so that customers can be given better service
and allows them to interact with the company by whatever means they wish.
2.2 Objectives
The objective of the Shopping systems is to increase the point of customer choice,
reduce time used in shopping and efficiency in buying product.
 It allows user to buy the various products.
 It allows user to track the ordered products.
 It allows delivery time seeing allocations.
 It allows user to buy the products through online payments
 To develop an easy way to use web based interface where users can search for
product view the details of the product and order it without going to market.
 The searching product can be done by product category, manufacturer as well
as latest product, view it purchase it become a convenient way for customer.
 Customer can add product to cart to purchase, delete the product from cart
before selecting the final submission.
 A user can view the complete specification of the product with various images
and also view the customer review the product.
 It minimize the shopping time of customer, increase the point of choice

 To provide information about various Electronics Products in different

category online.
 Customer can purchase Products Online.
 Customer can login and get various information about product and can
purchase the suitable product.
 Customer can pay online, so security is must therefore Online Shopping
provide secure transactions.
 After sale Online Shopping also provide after sales service in which customer
problem is solved.
 Data security is maintained to relatively high level by implementing it at
Database level, so as to ensure that only authorized users have access to
confidential client information

CHAPTER-02
COMPANY PROFILE
2.1 COMPANY PROFILE
CorporateProfile
FLAGROOT TECHNOLOGIES PRIVATE LIMITED
Introduction to Flagroot Technologies Pvt. Ltd.
We are a company focused on software testing. We provide software testing services

and build software to aid in testing. We provide world class functionality,
performance, security and agile testing services. Flagroot Technologies Private
Limited is a Private incorporated on 27 November 2015. It is classified as Non-govt
company and is registered at Registrar of Companies, Bangalore. Its authorized share
capital is Rs. 100,000 and its paid up capital is Rs. 100,000. It is inolved in Software
publishing, consultancy and supply [Software publishing includes production, supply
and documentation of ready-made (non-customized) software, operating systems

software, business & other applications software, computer games software for all
platforms. Consultancy includes providing the best solution in the form of custom
software after analyzing the user?s needs and problems. Custom software also includes
made-to-order software based on orders from specific users. Also, included are writing
of software of any kind following directives of the users; software maintenance, web-
page design].
Flagroot Technologies Private Limited's Annual General Meeting (AGM) was last
held on 29 September 2018 and as per records from Ministry of Corporate Affairs
(MCA), its balance sheet was last filed on 31 March 2018.Directors of Flagroot
Technologies Private Limited are Sowmya Bekkalale Chikkalingaiah and Girish.
Flagroot Technologies Private Limited's Corporate Identification Number is (CIN)
U72200KA2015PTC084378 and its registration number is 84378.Its Email address is
contactcpk@gmail.com and its registered address is No.88, 3rd Floor, Brigade
Chambers Gandhi Bazar, Basavanagudi Bangalore KA 560004 IN ,Current status of
Flagroot Technologies Private Limited is - Active.
Services
 Testing Services
 Managed Testing Services
 Mobile Testing
 Test Automation Solutions
 Testing Centers of Excellence
Platform
 Mobile App Testing

 Web App Testing
Contact us
Flagroot Technologies Pvt Ltd
Address: #88, Brigade Chambers, 3rd Floor, Gandhi Bazaar Main Road,
Basavanagudi, Bangalore - 560004

 +91 80 26607676
 contactus@flagroot.com
Business Models
Project Development
We have a dedicated development team and testing team of software engineers to

undertake projects in the following areas:
 Mobile App Testing
 Web application Testing
CHAPTER-3
LITERATURE SURVEY
3.1 Existing and Proposed System

3.1.1 Existing system
 When a person wants to buy a book he first have to drive to the books store
then walk throughout the store until he locates the book he need .After finding
the product if he wants to purchase ,he may often need to stand in long queue
at cash counter for long time.
 The online shopping is the best and convience way for shopping .
Online shopping helps consumer avoid this disadvantage.
With the help of online shopping consumer can buy a variety of items from
the online store .With the online shopping consumer can purchase just
above any things from companies that provide online household appliances ,
books , clothing ,toys , hardware,software and many moreproducts .
Limitations
 It takes more man power.

 It takes more time and space for manual process.
 Needs manual service.
 All service work done by manually.
3.1.2Proposed system
When a person wants to buy a book he first have to drive to the book store then walk
throughout the store until he locates the book he need .After finding the product if he
wants to purchase ,he may often need to stand in long queue at cash counter for long
time.The online shopping is the best and convience way for shopping .Online
shopping helps consumer avoid this disadvantage.With the help of online shopping
consumer can buy a variety of items from the online store .With the online shopping
consumer can purchase just above any things from companies that provide online
household appliances books,clothing,toys, hardware,software and many more products
Advantages of proposed system
 This android app takes less human support.

 No complexity.
 Faster and Exact information.
 Higher efficiency.
 Provides better service.
 User friendly and easy to access.
3.2 Feasibility Study
The problem to be automated is analyzed in sufficient details to ensure that all

aspects of feasibility are evaluated. Five tests of feasibility –all equally important are
studied:
 legal feasibility
 Technical feasibility
 Economic feasibility
 operational feasibility
 political feasibility
3.2.1 Legal Feasibility
Deal with analyzing whether the proposed system is legally feasible with
respect to law, copyright acts, licenses etc.
3.2.2 Technical Feasibility
In this study, whether software is technically feasible is analyzed by seeking

alternatives for hardware, software and general technical design approach to be
available, appropriate and functional.
3.2.3 Economical Feasibility
This analysis elaborates costs of special hardware, software, personal, office

space etc. for each implementation alternative. Before, building the project you have to

think about the project economic condition. Clients are satisfied with this economic
condition or not and then to implement the project.
3.2.4Operational Feasibility
First known about the peoples are able to interact with the system or not. And
also peoples are known about the android and web system working process and
installation process.
3.2.5 Political Feasibility
Deal with the extent of managerial support for changes to the present system.
The developed project get the political support or not and projectwants to support from
the political peoples are help for the hosting of project in society.
3.3 About Tools and Technologies
CHAPTER-04
Hardware Requirements and Software Requirement
3.4.1 Hardware Requirements

• CPU : Intel 2.1 GHZ
• Memory : 500MB
• Disk : 40 GB
• Display : 15 inch color monitor
• Mobile Phone : Android Smart phone
3.4.2 Software Requirements

• Platform Browser, oppermini,mozila,Google chrome, web app
• Dev. Tool : Acti time,BUG ZERO
• Data base : MySQL
• OS : Windows
• Android GUI : XML
4. SOFTWARE REQUIREMENTS SPECIFICATION
Software requirements specification (SRS) is the specification of the project

system. It should include both a specification of requirements and a definition. As far
as possible, it should set of what the system should do rather than how it should do it.
These are theways to represent specifications in a consistent format.

3.2Functional Requirements:
Each capability can be achieved with the help of more than one function need
to be done in a particular sequence. The software should have the E-commerce
package to allow manage to without difficulty of IT service company problems.
The E-commerce support workflow automata has following parts

1] Web App
2] Mobile App
3.2.1 Web App

Admin Module: Sets user name and password to login for service provider
and Add client. Admin can view the work order from client and assign the task to
service provider, he can view the work order status means assigned work completed or
not.
3.2.2 Mobile App:
The android app is downloaded by from the website & it is authorized by the
admin.By using the android app the Client can view the service or work order details
which is raised by him or he make work order based on the requirement, he can
provide the feedback for the existing work orders.
By using the android app the service provider can view the work requested
raised by the clients, he can work on the order and update the status through the
android app, he can request for the billing to admin. With respect to work or service
provided by him.
Modules:
Module Description:
This project work consists of applications web page development. The software contains
different modules such as
 My account
 Login
 Customer
 Sign up

 My cart
 Search
 Men’s add product
 Women add product
 The edit
 View order
 Track order
 Contacts
 Admin Module: Sets user name and password to login for service
provider and Add client. Admin can view the work order from client
and assign the task to service provider, he can view the work order
status means assigned work completed or not.
 My account
To check the login via valid Email Id

To check the login via valid Facebook credentials
To check the login via valid Google credentials
 Track order
To check order text field using valid order number and E-mail id
.To check Login via Email-id
.To check Login via valid Google credentials
 Search
To check whether search text box accepts search by Top categories
To check whether search text box accepts search by gender

male/female
To check whether search text box accepts search by colour
 The edit
To check if ALL link is clickable or not
To check if WOMEN link is clickable or not

To check if MEN link is clickable or not

To check if KOOVS TV link is clickable or not
 Customer Module: customer can sign up the e-commerce web

application create a account and serach the product
 Add Product Module: The form on this page is displayed when the
link for adding products on the products page is clicked. Every input
on this form is checked for null and empty values. The edit product
form is basically the same as the product form, except that it contains
editable data in its fields
 Search product Module: user can login the account and add the
product in cart
Affer user search the product from list of the cart
 Payments Module:The page is accessed by filling and submitting the

paymen report form correctly. The page displays a list of all payment
transactions in accordance with the start and end dates entered,user
can order the product finally next step is payment method
3.3 NoN-Functional Requirements:
Non-practical prerequisites May be more discriminating than useful necessities.
The non-functional keys are.
 Security:This application to be secure and safety system. This software is not

misuse.
 Performance: The system is high level of interaction and process of the user
request.
 Safety: This system is safety of the design, development, and deployment and
maintains the software.
 Portab ility : It can be executed in any platform depend upon client

requirement. Which sufficient to the user that one developer can do.

 C orrectn es s : it took after an all-around characterized plan of practice and

principles to process furthermore thorough testing is performed to affirm the
rightness of the information.
 Modularity: the complete item is separated into two modules and all around
characterized interfaces are created to investigate the advantage of flexibility of
the item.
 Re-usability: as whole itemsare being developed in small chunks, it gives a
scope for reusing these chunks for the similar requirements. This feature
drastically reduces the development costs.
 Understandability: the efficiency of a product relies mostly on user

satisfaction, which can be achieved through a well-designed front-end and
well-performing backend. The user interface is being designed in a way that all
the functions are easily understood and even a novice user can use this
interface with much ease.
4. SYSTEM DESIGN
This is containing the details of system perspective, architecture design and the
context design of our project. It primarily says how to design system and how to
interact with internal and external system.
4.1: System Perspective
System models are an inherent part of structured methods. System

modeling is the interdisciplinary; studies on the use of models for
conceptualizing and building systems. The model system analyst helps for
understand the modelof the project system and how the models are communicate
with client.

Figure 4.2: architectural design.
Description: web application and android application can be communicated and

the android means client and service provider information will be stored in the
web application database and view the data from the database.
4.2 Context Models:

Shopping
cart
Figure 4.2: Context Diagram
Description:the communication between the models is admin, client, provider

and work order with the system. The diagram shows the system that may interact
with all admin, client and provider models. The Objectives of the project system
context diagram are to focus attention on external models and events.
4.2.1 Data Flow Model:
The flow of project data running in the system, most project systems is driven
by the data. The project models are controlled by the dataappends to the system with
small models event processing. E-commerce is needed to represent the behavior of the
project systems.

A data flow models, which shows the steps involved in e-commerce support workflow
automata
Figure4.1 Data Flow Diagram.
Description: the data can be flow as show in the above figure, first admin can login
and enter his window and he manage the client, service provider, work order, and
service type. Second client can login and manage his details and service provider as
also same.
Context Level Diagram:

Context level diagram just show the task happening in the whole system, its actually
shows the input what is the ourput for the input.
First Level DFD:
First level DFD shows the major steps that have to complete to buy a product. Initially
customer visit the website, search the product by category, manufacturer and top
selling, show the details of the product, select payment method, finally the product
delivered by the company agent

Second Level DFD:

Second level DFD shows the whole fact that happen in the system and it’s given
below:

5. DETAILED DESIGN
This is the last process before design implementation design.In this case we can design
the blue print of required project in manually design, and then get idea about your
project develop to start coding part. We can design the models and their event of our
required project. Then we get the idea of sequential flow of events, collaboration,
activity and database designs of our required project.

5.1Usecase Diagram:
Figure 5.1.3 use case diagram of Customer.
Description: In this diagram client is the actor and request of order, send feedback,
and status these are the client actions.

5.2SequenceDiagram:

The sequence diagram represents sequence flow of project; the sequence flow
is from left side to the right side. In the bellow sequence diagram shows admin to
service provider and provider to client sequentially flowed.
Sequence diagrams are used during subsystem design, but they are applicable
to dynamic modeling equallyduring analysis, system design and event capture
requirements. The client can be request the work order to the admin, after the request
admin has to be assign the work to the provider and he has been complete the
requirement to fulfill the clients queries.
5.3Activity Diagram

It is a diagrammatical representation of movement outlines of service processes

of step by step activities and exercises with backing for decision, concurrency and
emphasis.Brought together in the dialect displaying, action outlines are planned
toshow both computational and authoritative procedures. In activity diagram shows the
project activity how to work and validates the user request. If the user input
requirement is valid you can entered into the next step of process, otherwise get back
to outside of the requirement.
Figure 5.3movement stream of the project.
Description: above diagram shows the flow of the project.

5.4 E-R DIAGRAM
E-R DIAGRAM tool is utilized as a part of examination to portray the

prerequisites information and presumptions in the framework from a top-down point
of view. There are three essential components in e-r models:
Shopping
app

5.4.1 Table structure
1. Table Name: ADMIN
Sl. No Fields Data Types
1 admin_id Int
2 admin_name Varchar(5)
admin_email_addre Varchar(6)
3
ss
4 admin_password Int (10)
2. Table Name: Login
1 User name Varchar(4)
2 Password Int
3. Table Name: customer details
1 customer_id Int (10)
2 first_name Varchar (30)
3 last_name Varchar (20)
4 email_address Varchar (10)

5 password int (10)
6 address Varchar (10)
4. Table Name: product details
1 product_id Int
2 product_name Varchar(7)
3 product_code Int
4 category_id Int
5 manufacturer_id Int
6 product_price Int
7 product_quantity Int
publication_statu Varchar(10)
8
s
Varchar(18)
9
deletion_status
product_long_descriptio Varchar(13)
10
n
5. Table Name: track order
1 Order name varchar (10)
2 Order id int

3 Transcation id Int
6. IMPLEMENTATION
A good shopping cart design must be accompanied with user-friendly shopping cart
application logic. It should be convenient for the customer to view the contents of their
cart and to be able to remove or add items to their cart. The shopping cart application
described in this project provides a number of features that are designed to make the
customer more comfortable. This project helps in understanding the creation of an
interactive web page and the technologies used to implement it. The design of the
project which includes Data Model and Process Model illustrates how the database is
built with different tables, how the data is accessed and processed from the tables. The
building of the project has given me a precise knowledge about how to access the data
and how the data and web pages are modified to provide the user with ashopping cart
application.
6.1 Screenshots
 HOME PAGE

Figure 6.1: In this web page admin can be login with help email id and his personal
passwordto login
 MY ACCOUNT
 SIGN UP

 LOGIN PAGE
 MY WISHLIST

 TRACK ORDER
 MY BAG

 MEN ADD PRODUCT
 SEARCH PRODUCT

 THE EDIT
 CONTACT

 FOOTER
 ABOUT US
7.SOFTWARE TESTING

The test program is the program subject to a set of test inputs and observing
whether the program behaves as expected, then a fault occurs under conditions seen
for debugging and subsequent correction.
1 It is a process of finding or identifying defects in s/w is called s/w testing.

2. It is verifying the functionality (behavior) of the application(s/w) against
requirements specification.
3. It is the execution of the s/w with the intention of finding defects.
4. It is checking whether the s/w works according to the requirements.
7.1.1Testing Objective
 Testing is aprocess of executing aprogram with the intent of finding an

error.
 A good test case is one that has a high probability of finding an as-yet
Undiscovered error.
 A successful test is that uncovers an as-yet-un discovered error
7.1.2Testing Principle
 All tests should be traceable to customer requriments

 Test should be planed long before testing begins
 Exhaustive testing is not possible
 To be most effective, an independent third party should be conducting
testing
There are 2 types of s/w testing, namely,

1) White box testing – also called unit testing or structural testing or glass box
testing or transparent testing or open-box testing
2) Black box testing – also called as functional testing or behavioral testing
7.1.3 WHITE BOX TESTING (WBT)

Entire WBT is done by developers. It is the testing of each and every line of code in the
program. Developers do WBT, sends the s/w to testing team. The testing team does black box
testing and checks the s/w against requirements and finds any defects and sends it to the
developer. The developers fixes the defect and does WBT and sends it to the testing team.
Fixing defect means the defect is removed and the feature is working fine
7.1.4 BLACK BOX TESTING (BBT)
It is verifying the functionality (behavior) against requirement specifications
Types of Black Box Testing
 FUNCTIONAL TESTING
Also a called component testing. Testing each and every component thoroughly
(rigorously) against requirement specifications is known as functional testing.
 INTEGRATION TESTING
Testing the data flow or interface between two features is known as integration testing
 SYSTEM TESTING
It is end-to-end testing wherein testing environment is similar to the production
environment.Here, we navigate through all the features of the software and
test if the end business / end feature works. We just test the end feature
and don’t check for data flow or do functional testing and all
 ACCEPTANCE TESTING.
Testing to verify a product meets customer specified
requirements. A customer usually does this type of testing on a product that is
developed externally.
 COMPATIBILITY TESTING.
Testing to ensure compatibility of an application or Web site with different
browsers, OSs, and hardware platforms. Compatibility testing can be performed
manually or can be driven by an automated functional or regression test suite.

 CONFORMANCE TESTING. Verifying implementation conformance to

industry standards. Producing tests for the behavior of an implementation to be
sure it provides the portability, interoperability, and/or compatibility a standard
defines.
 PERFORMANCE TESTING.
Performance testing can be applied to understand your application or WWW site's
scalability, or to benchmark the performance in an environment of third party products
such as servers and middleware for potential purchase. This sort of testing is
particularly useful to identify performance bottlenecks in high use applications.
Performance testing generally involves an automated test suite as this allows easy
simulation of a variety of normal, peak, and exceptional load conditions
 REGRESSION TESTING.
Similar in scope to a functional test, a regression test allows a consistent, repeatable
validation of each new release of a product or Web site. Such testing ensures reported
product defects have been corrected for each new release and that no new quality
problems were introduced in the maintenance process. Though regression testing can
be performed manually an automated test suite is often used to reduce the time and
resources needed to perform the required testing.
 SMOKE TESTING.
A quick-and-dirty test that the major functions of a piece of software work without
bothering with finer details. Originated in the hardware testing practice of turning on a
new piece of hardware for the first time and considering it a success if it does not catch
on fire.
 UNIT TESTING
This testing is activity in individual ways to control module structure to guarantee

complete scope and most extreme slip location. This test spotlights on every module
Independently, Guaranteeing that it legitimately as a unit Capacities. Subsequently, the
unit naming is trying. Amid east testing, every module is tried separately and the
module interfaces are checked for consistency with the outline determination.

Exceptionally handling vital ways are tried for the usual results. All lapses Taking
Care of ways are additionally tested.
 INTEGRATION TESTING
This testing address connected the issues with the double issues of project
development and confirmation. The product have been incorporated resource of higher
request tests are directed. In integration testing procedure is to receive unit tried
modules and constructs a system fabricate that have-been directed by outline.
 VALIDATION TESTING
The validation testing is to test the user given input is right or wrong, it is to be test
input value as per the particular values as like email, password and so on.
 STRESS TESTING.
Testing conducted to evaluate a system or component at or beyond the limits of its

specified requirements to determine the load under which it fails and how.a graceful
degradation under load leading to non-catastrophic failure is the desired result. Often
Stress Testing is performed using the same process as Performance Testing but
employing a very high level of simulated load.

TEST CASES
Test case is a document which covers all possible scenarios to test all the feature(s).
It is a set of input parameters for which the s/w will be tested. The SRS are numbered
so that developers and testing team will not miss out on any feature.
When do we write test cases?
Customer gives requirements – developer start developing and they say they need
about 4 months to develop this product – during this time, testing team start writing
test cases – once it is done, they send it to test lead who reviews it and adds some
more scenarios – developers finish developing the product and the product is given
for testing – the test engineer then looks at the test cases and starts testing the product
– the TE never looks at the requirements while testing the product – thus testing is
consistent and does not depend on the mood and quality of the test engineer.
Why we write test cases?

 To have better test coverage – cover all possible scenarios and document it,
so that we need not remember all the scenarios
 To have consistency in test case execution – seeing the test case and testing
the product
 To avoid training every new engineer on the product – when an engineer
leaves, he leaves with lot of knowledge and scenarios. Those scenarios should
be documented, so that new engineer can test with the given scenarios and also
write new scenarios.
 To depend on process rather than on a person
TEST PLAN

Test plan is a document which drives all future testing activities. Test plan is prepared
by Test manager(20%), Test Engineer(20%) and by Test Lead(60%).
There are 15 sections in a test plan. We will look at each one of them below
 OBJECTIVE :-
It gives the aim of preparing test plan i.e, why are we preparing this test plan.
 SCOPE :-
Features to be tested
For ex, Compose mail
Inbox
Sent Items
Drafts
Features not to be tested

For ex, Help
…
…
…
…
i.e, In the planning stage, we decide which feature to test and which not to test due to
the limited time available for the project.
 TESTING METHODOLOGIES (Types of Testing)

Depending upon the application, we decide what type of testing we do for the various
features of the application. We should also define and describe each type of testing we
mention in the testing methodologies so that everybody (dev team, management,
testing team) can understand, because testing terminologies are not universal.
 APPROACH
The way we go about testing the product in future,
a) By writing high level scenarios
b) By writing flow graphs
 ASSUMPTIONS
When writing test plans, certain assumptions would be made like technology,
resources etc.
 RISKS : If the assumptions fail, risks are involved

 CONTINGENCY PLAN OR MITIGATION PLAN OR BACK-UP PLAN

To overcome the risks, a contingency plan has to be made. Atleast to reduce the
percentage from 100% to 20% Let us consider an example for 5, 6, 7
In the project, the assumption we have made is that all the 3 test engineers will
be there till the completion of the project and each are assigned modules A, B,
C respectively. The risk is one of the engineers may leave the project mid-way.
Thus, the mitigation plan would be to allocate a primary and secondary owner
to each feature. Thus, one engineer quits – the secondary owner takes over that
particular feature and helps the new engineer to understand their respective
modules.
Always assumptions, risks, mitigation plan are specific to the project.
The different types of risks involved are,
Resource point of view
Technical point of view
Customer point of view
 ROLES AND RESPONSIBILITIES
Test Manager
Test Lead
Senior Test Engineer Junior Test Engineer Fresher
When a Big project comes, it’s the Test Manager who writes the test plan.
If there are 3small projects, then Test Manager allocates each project to each
Test lead. The Test lead writes the test plan for the project which he is
allocated.
 DEFECT TRACKING
In this section, we mention – how to communicate the defects found during
testing to the development team and also how development team should respond to
it. We should also mention the priority of the defect – high, medium, low.
 TRACEABILITY MATRIX
We have learnt about TM earlier. Once the missing requirements are identified
– we write the test cases for the requirements which we have missed – review it
and get it approved – and then store the test cases in the repository and then fill
in the name of the test case for which the requirements have been missed.

Traceability Matrix is a document which has got the mapping between

requirements and test cases. We write TM to make sure that every requirement
has got atleast 1 test case.
 TEST STRATEGY
It is a document which captures the approach on how we go about testing the
product.
The approach can be from ,
a) resource point of view
b) automation or not
..
..
Like this from many points of view, we capture the approach.
After Test Strategy, only then we start writing the detailed Test Plan and
continue further.
The Test Strategy is reviewed by development team and after changes are
made, it is approved
 TEST EXECUTION
Here, we test the product. We test repeatedly for 40 – 60 cycles. We do all
types of testing on the application. Test Execution is the phase where we spend
80% of our time on the project. Only 20% is spent on the remaining stages.
 TEMPLATES
This section contains all the templates for the documents which will be used in the project.
Only these templates will be used by all the test engineers in the project so as to provide
uniformity to the entire project. The various documents which will be covered in the Template
section are,
 Test Case
 Traceability Matrix
 Test Execution Report
 Defect Report
 Test Case Review Template
DEFECT TRACKING
Defect : If a feature is not working according to the requirement, it is called a defect.

Deviation from requirement specification is called as defect.
A bug occurs only because of the following reasons,
Wrong implementation :- Here, wrong implementations means coding. For ex, in an

application – when you click on “SALES” link – it goes to “PURCHASE” page – this
occurs because of wrong coding. Thus, this is a bug.
Missing implementation :- We may not have developed the code only for that
feature. For ex, open the application – “SALES” link is not there only – that means
feature has not been developed only – this is a bug.
Extra implementation :- The developer develops extra feature which is not needed
and not there in the requirements also. For ex, consider the below application
In the above application – requirements say only to develop “submit” and “cancel”
button – but the developer also develops “help” button which is not there in the
requirements.
 If we develop extra features not there in the requirements, it leads to unnecessary
extra effort
 Chances are there that adding extra features might affect other features.
In this section, we mention – how to communicate the defects found during testing to
the development team and also how development team should respond to it. We
should also mention the priority of the defect – high, medium, low
DEFECT LIFE CYCLE

DEFECT REPORT
Defect ID – it is an unique number given to the defect

Test Case Name – whenever we find a defect, we send the defect report and not the
test case to the developer. For defect tracking, we only track the defect report and not
the test case. Test case is only for reference for the TE. We always only send the
defect report whenever we catch a bug.
When we are doing ad-hoc testing – no test case is written for ad-hoc testing because
they are “out of the box” testing scenarios – if we find a critical bug – then we convert
that ad-hoc scenario into a test case and send it to development team.
DEFECT ID : BugID _ 1578

RELEASE NAME : Tiger

BUILD ID : B03
MODULE NAME : Sent Items
STATUS : Open
Assigned
Fixed
Closed
Duplicate
… etc etc
SEVERITY : Blocker OR Showstopper
Critical
Major
Minor
PRIORITY : High P1
Medium P2
Low P3
P4
TEST DATA : username = abc123 , password = xyz123
TEST ENVIRONMENT : In Windows XP, Internet Explorer 7.0
TEST CASE NAME : Yahoo _ SI _ mail list
FOUND BY :
BRIEF DESCRIPTION : Sent mails are not there in the Sent Items page
DETAILED DESCRIPTION : Following are the steps to reproduce the defect
1. Open the browser and enter the test URL
2. Login with valid username and password
3. Click on “compose” link
4. Enter valid data into all fields and click on Submit button
5. Click on Sent Items link
EXPECTED RESULT : Sent mail should be listed in Sent Items page

ACTUAL RESULT : Sent mail is not there in the Sent Items page.
DEFECT REPORT IN OUR E-COMMERCE PROJECT


BUILD ID : B03
MODULE NAME : MY WISH LIST
STATUS : Open
Assigned
SEVERITY : Blocker
PRIORITY : High P1
TEST CASE NAME : to check my wish list
FOUND BY :
BRIEF DESCRIPTION : my adding product ore are not there in the my wish list
3. Click on “my wish list” link
5. Click on my wish list link
EXPECTED RESULT : add bag should be listed in my wish list

ACTUAL RESULT : add bag is not there in my wish list

BUILD ID : B03
STATUS : Open
Assigned
SEVERITY : Blocker
PRIORITY : High P1
FOUND BY :



BUILD ID : B03
STATUS : Open
Assigned
SEVERITY : Blocker
PRIORITY : High P1
FOUND BY :

BUILD ID : B03
STATUS : Open
Assigned
SEVERITY : Blocker
PRIORITY : High P1
FOUND BY :

Test case 1: admin functionality test cases:

name of the test test case for admin login
test description A test for the valid username and password is entered.
sample input Enter username and password.
expected output The system will check for the validity of the admin and
display the admin windows.
actual result/remarks As expected.
Passed (?) Yes
Test case table 1: admin functionality test cases.
Test case 2: USER functionality test cases:
name of the test test case for user
test description Enter the user details.
sample input user details (e.g. name, address and email etc.).
expected output Client details are stored in database.
actual result/remarks As expected.
Passed (?) yes
Test case table 2: user functionality test cases.
Test case 3: my account functionality test cases:
My Account Login 1.To check the login via valid Email Id
2.To check the login via valid Facebook credentails

3.To check the login via valid Google credentials



1.To check the Sign up via valid Email Id
Sign Up 2.To check the Sign up via valid Facebook

credentials
3.To check the Sign up via valid Google

credentials
Test case 4: Track order functionality test cases
1.To check order text field using valid order number

Track order Enter your order
and
number and e-
mail address E-mail id
1.To check Login via Email-id
Login 2.To check Login via valid Facebook credentials
3.To check Login via valid Google credentials
Test case 5: search functionality test cases
To check whether search text box accepts search by

Search Top Categories
Top
Categories
Brands
Brands
Gender To check whether search text box accepts search by
gender male/female
Colour
colour
Trending Searches
Trending searches
Recent Searches
Recent searches
Test case 6: THE EDIT OR ADD functionality test cases
THE
EDI WOMEN
T .To check if WOMEN link is clickable or not
MEN To check if MEN link is clickable or not

KOOVS TV .To check if KOOVS TV link is clickable or not

Magazine To check if Magazine link is clickable or not
YOUR HOTLIST
.To check if YOUR HOTLIST link is clickable
or not
Test case :7 Register Module,Login Module and Logout Module is Integrate
Sr Test Case Input Expected Observed Test

Behavior
No Description behavior Result
1 Is new User Login ID User should User named Succes

be created
created? +personal ID is
And created.
Information
personal
Information
should be
Stored in
Database
2 Is Database Connection Connection No error Succes
Connection Object is establishes during
establishing? Created connection
was found
3 Match Login Id Proper Matching Success

matching
Login ID& +Password done
Password
4 Does status of Logout cmd Statuss No change No change

hould in in
User changes to
change

'Logout status’? status Status
TEST CASE :8 Add Record Module,Delete Record Module,Update Record

Module,Search Record Module is Integrated
Sl Test Case Input Expected Observed Test

no behavior
Description Behavior Result
1 Is new Record Item Records Records Succes

Name/Auth should be should be
Added in
or
Added and Added and
database?
Name/Editio
displayed displayed
n
on the view on the view
Etc page page
2 Existing Item Records Records Succes

Record deleted
or Added and
Added and
From data base?
Name/Editio displayed
displayed
n on the
on the view
Etc view page page
3 existing Item Records Records Succes

Record deleted
or Added and
Added and
From data base?
Name/Editio Displayed
displayed
n on the
on the view
Etc View page page
3 On search item Records Records Succes


Criteria names or Added and Added and
Should be correct. Name/Editio Displayed displayed

n on the View on the view
page page
Etc
8. CONCLUSION
The proposed project titled“ E-commerce shopping web applications” The main
objective of this thesis work was to develop an e-commerce web application for a small
retail store where the store owner manages products, customers, and orders, while the
customers make orders and pay for products. The application was developed with the
above-mentioned features.
One of the biggest challenges faced during the development of this software project was
how to implement JPA for the application. A lot of time and effort were invested in
learning and implementing JPA for this e-commerce application. Another challenge faced
was how to integrate PayPal Express Checkout NVP API operations for the project.
PayPal has a poor API integration documentation, especially API integration for the Java
programming language. This actually affected the flow of the application development
process as much time was used to learn and understand the NVP API integration for Java.
With these challenges and others not mentioned here, a lot of new experience has been
gained during the development process of this application.
Although all the requirements set out for the e-commerce web application have
been met, there are still areas to improve on. A mobile version can be developed for the
application so that users can have a better access to the application. Also, other online
payment methods like credit/debit card and bank payment methods can be implemented
for the application.

9. FUTURE ENHANCEMENT
There are some limitations for the current system to which solutions can be
Provided as a future development:
1. The system is not configured formulti-users at this time.The concept of

Transaction can be used to achieve this.
2. The Website is not accessible to everyone.It can be deployed on a web
Server so that every body who is connected to the Internet can use it.
3. Credit Card validation is not done.Third party proprietary software can be Used for
validation check
As for other future developments ,the following can be done:
1. The Administrator of the website can be given more functionalities,

Like looking at a specific customer’s profile ,the books that have to be
Re ordered,etc.
2.Multiple Shopping carts can be allowed.

10.BIBLIOGRAPHY
REFERENCE BOOKS:
Anne Boehm, Joel Murach, Murach’s ASP.NET 4 Web Programming with C# 2010,
4th
Edition, Murach, 2010.
2. Bryan Syverson, Joel Murach, Murach’s SQL Server 2012 for developers, Murach,
2012.
3. http://www.w3schools.com/
4. http://msdn.microsoft.com/
5. http://agilemodeling.com/
6. http://csharp-video-tutorials.blogspot.co.uk/p/free-dot-net-video-tutorials-for.html
7. http://csharp-video-tutorials.blogspot.com/p/free-aspnet-video-tutorial.html
8. http://csharp-video-tutorials.blogspot.com/p/free-adonet-video-tutorial.html
WEB REFERENCES:
 www.google.co.in
 www.tutorialspoint.com
 www.mkyong.com
 www.acadgild.com

B. USER MANUAL

E-Commerce Online Shopping Web Application Is A Lifestyle, Which Retails Various

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Commerce Online Shopping Web Application Is A Lifestyle, Which Retails Various

Uploaded by

Copyright:

Available Formats

[E-COMMERCE SHOPPING WEB APP] 2018-19

[DEPT OF COMPUTER PROGRAMME,BUB] Page 1

2.1 Project Description

The objective of project “E-COMMERCE ONLINE SHOPPING WEB

[DEPT OF COMPUTER PROGRAMME,BUB] Page 2

Retaining existing customers is also an important job of a company. Online Shopping

[DEPT OF COMPUTER PROGRAMME,BUB] Page 3

 To provide information about various Electronics Products in different

[DEPT OF COMPUTER PROGRAMME,BUB] Page 4

2.1 COMPANY PROFILE

FLAGROOT TECHNOLOGIES PRIVATE LIMITED

Introduction to Flagroot Technologies Pvt. Ltd.

We are a company focused on software testing. We provide software testing services

[DEPT OF COMPUTER PROGRAMME,BUB] Page 5

 Mobile App Testing

Flagroot Technologies Pvt Ltd

[DEPT OF COMPUTER PROGRAMME,BUB] Page 6

We have a dedicated development team and testing team of software engineers to

 Mobile App Testing

 Web application Testing

3.1 Existing and Proposed System

[DEPT OF COMPUTER PROGRAMME,BUB] Page 7

3.1.1 Existing system

 It takes more man power.

Advantages of proposed system

 This android app takes less human support.

[DEPT OF COMPUTER PROGRAMME,BUB] Page 8

3.2 Feasibility Study

The problem to be automated is analyzed in sufficient details to ensure that all

3.2.1 Legal Feasibility

3.2.2 Technical Feasibility

In this study, whether software is technically feasible is analyzed by seeking

3.2.3 Economical Feasibility

This analysis elaborates costs of special hardware, software, personal, office

[DEPT OF COMPUTER PROGRAMME,BUB] Page 9

3.2.5 Political Feasibility

3.3 About Tools and Technologies

Hardware Requirements and Software Requirement

3.4.1 Hardware Requirements

[DEPT OF COMPUTER PROGRAMME,BUB] Page 10

• CPU : Intel 2.1 GHZ

• Display : 15 inch color monitor

• Mobile Phone : Android Smart phone

3.4.2 Software Requirements

• Dev. Tool : Acti time,BUG ZERO

• Data base : MySQL

• Android GUI : XML

4. SOFTWARE REQUIREMENTS SPECIFICATION

Software requirements specification (SRS) is the specification of the project

[DEPT OF COMPUTER PROGRAMME,BUB] Page 11

The E-commerce support workflow automata has following parts

3.2.1 Web App

[DEPT OF COMPUTER PROGRAMME,BUB] Page 12

To check the login via valid Email Id

To check the login via valid Google credentials

To check whether search text box accepts search by gender

To check whether search text box accepts search by colour

[DEPT OF COMPUTER PROGRAMME,BUB] Page 13

To check if MEN link is clickable or not

 Customer Module: customer can sign up the e-commerce web

 Payments Module:The page is accessed by filling and submitting the

3.3 NoN-Functional Requirements:

Non-practical prerequisites May be more discriminating than useful necessities.