STE Report Vijaya Final
STE Report Vijaya Final
Chapter 1
Synopsis
• Project Title
Online Shopping System
• Project Option
Not sponsor
• Internal Guide
Prof.Thorat S.K.
• Technical Keyword
• Problem Statement
Chapter 2
Introduction
Online shopping is a form of electronic commerce where the buyer is directly online
to the seller's computer usually via the internet. There is no intermediatory service.
The sale and purchase transaction is completed electronically and interactively in
real-time such as Amazon.com for new books. If an intermediary is present, then
the sale and purchase transaction is called electronic commerce such as online
shopping.
Proposed System:
The development of this new system contains the following activities, which try to
develop on-line application by keeping the entire process in the view of database
integration approach.
• Browsing through the e-Mall to see the items that are there in each category of
products like Apparel, Kitchen accessories, Bath accessories, Food items etc.
• Creating a Shopping cart so that customer can Shoppe ‘n’ no. of items and checkout
finally with the entire shopping cart
• Customers should be able to mail the Shop about the items they would like to
see in the Shop
• Secured mechanism for checking out from the Shop( Credit card verification
mechanism )
• Uploading ‘Most Purchased’ Items in each category of products in the Shop like
Apparel, Kitchen accessories, Bath accessories, Food items etc.
The system after careful analysis has been identified to be presented with the
following modules:
• Customer.
• Employee.
• Admin Module.
• Security and Authentication
Chapter 3
Requirements
3.1 Software Requirements:
Processor : Pentium IV
3.4 Functions:
• Allowing customers to post queries and discuss products and sell through us.
• Allow the businessman to change the look and feel of the site with ease.
• Allow the shopkeeper to view different configuration options and update them.
Chapter 4
4.1 Introduction:
Analysis is the focus of system developing and is the stage when system designers
have to work at two levels of definition regarding the study of situational issues
and possible solutions in terms of “what to do” and “how to do”.
Analysis :
In day to day life, we will need to buy lots of goods or products from a shop. It
may be food items, electronic items, house hold items etc etc. Now a days, it is
really hard to get some time to go out and get them by ourselves due to busy life
style or lots of works. In order to solve this, B2C E-Commerce websites have
been started. Using these websites, we can buy goods or products online just by
visiting the website and ordering the item online by making payments online.
This existing system of buying goods has several disadvantages. It requires lots of
time to travel to the particular shop to buy the goods. Since everyone is leading
busy life now a days, time means a lot to everyone. Also there are expenses for
travelling from house to shop. More over the shop from where we would like to
buy some thing may not be open 24*7*365. Hence we have to adjust our time
with the shopkeeper’s time or vendor’s time.
In order to overcome these, we have e-commerce solution, i.e one place where we
can get all required goods/products online. The proposed system helps in building
a website to buy, sell products or goods online using internet connection.
Purchasing of goods online, user can choose different products based on
categories , online payments , delivery services and hence covering the
disadvantages of the
System analysis:
System Analysis is a process by which we attribute process or goals to a human
activity, determine how well those purpose are being achieved and specify the
requirements of the various tools and techniques that areto be used within the
system if the system performances are to be achieved.
System planning:
Planning for information systems has a time horizon and a focus dimension. The time
horizon dimension specifies the time range of the plan, where as the focus
dimension relates whether the primary concern is strategic, managerial, or
operational. The system i.e. The Project that we were assigned was required to
complete within 20 weeks. What we had planned is as follows:
Information gathering:
Akey part of feasibility analysis is gathering information about the present
system. The analyst must know what information to gather, where to find it, how to
collect it, and what to make of it. The proper use of tools for gathering information
is the key to successful analysis. The tools are the traditional interview,
questionnaires, and on-site observation.
Structured Analysis:
The traditional tools of data gathering have limitations. An English narrative
description is often vague and difficult for the user to grasp. System flowcharts
focus more on physical than on logical implementation of the candidate system.
Because of these drawbacks, structured tools were introduced for analysis.
Structured analysis is a set of techniques and graphical tools (DFD) that allow
the analyst to develop a new kind of system specifications that are easily
understandable to the user.
Problem Pretation:
problem is well defined very rarely. So the first task is to get more
crucial information by interviewing and meeting concerned people.
It clarifies how the problem is felt, how often it occurs, how it
affects the business and which departments are suffering with this.
This phase consists of the following tasks.
This was a preliminary investigation done with a view to have a “feel” of the working
of the proposed system. This phase has been identified the end-user directly involved
in the system who were the managers, assistant officer and database administrator,
and the development department. By understanding the working of database, its flow
and also after conducting meetings and interviews with the concerned persons of the
department, a clear idea about the working was obtained. A flexible approach is
adapted towards people who are interviewed. Short hand written notes are prepared
based on the response of the employees. Detailed investigation is done in order to
define the scope of the problem .The interview is concluded with a quick resume of
the ground covered during the interview .The Questionnaire technique is combined
with interviews to get the best result. Proper care has been taken in the design of such
questionnaires so that the persons answering these questions do not feel hesitant. An
explanatory note that serves to gain cooperation and avoid misunderstanding by
setting out the purpose of the exercise clearly accomplishes each questionnaire.
Observation technique is also used for fact finding. The work described at the time of
interview is observed personally ads it reduces the chances of misunderstanding and
omissions. Some important things observed are like the flow of information through
the system and important data transactions, the data being maintained and the
frequency of their updating.
By the end of this phase, idea as to how the information enters the system, how it is
stored, how it is processed, how information changes affects the working of the system
and finally the output format required by the end-user was collected. All the
information generated from this phase acted as an input to the next phase.
Chapter 5
Testing
the appropriate outputs.This is analogous to testing nodes in a circuit, e.g., in-circuit testing
(ICT).
While white-box testing can be applied at the unit, integration, and system levels of the
software testing process, it is usually done at the unit level. It can test paths within a unit,
paths between units during integration, and between subsystems during a system–level test.
Though this method of test design can uncover many errors or problems, it might not detect
unimplemented parts of the specification or missing requirements.
Techniques used in white-box testing include:
• API testing – testing of the application using public and private APIs (application
programming interfaces)
• Code coverage – creating tests to satisfy some criteria of code coverage
• Fault injection methods – intentionally introducing faults to gauge the efficacy of
testing strategies
• Mutation testing methods
• Static testing methods
• Black Box Testing:
Black-box testing (also known as functional testing) treats the software as a "black box,"
examining functionality without any knowledge of internal implementation, without seeing
the source code. The testers are only aware of what the software is supposed to do, not how
it does it. Black-box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, state transition tables, decision table testing, fuzz testing, model-
based testing, use case testing, exploratory testing, and specification-based testing.
Specification-based testing aims to test the functionality of software according to the
applicable requirements. This level of testing usually requires thorough test cases to be
provided to the tester, who then can simply verify that for a given input, the output value
(or behavior), either "is" or "is not" the same as the expected value specified in the test case.
Test cases are built around specifications and requirements, i.e., what the application is
supposed to do. It uses external descriptions of the software, including specifications,
requirements, and designs to derive test cases. These tests can be functional or non-
functional, though usually functional.
One advantage of the black box technique is that no programming knowledge is required.
Whatever biases the programmers may have had, the tester likely has a different set and
may emphasize different areas of functionality. On the other hand, black-box testing has
been said to be "like a walk in a dark labyrinth without a flashlight”. Because they do not
examine the source code, there are situations when a tester writes many test cases to check
something that could have been tested by only one test case or leaves some parts of the
program untested.
5.4Test Cases :
5.5Test Plan :
Introduction:
Online Shopping System consist many products like Books, Dresses, Shoes,
Baby’s product, Electronic material, Furniture, House materials, etc. This
can be for sales and anyone can buy these product by visiting these websites.
Test Items:
Login to account.
Visit the product.
Buy the product.
Return the product.
Features to be Tested:
Login form
Features to be not Tested:
Product
Approach:
In Online Shopping System internal Level testing is performed.
Item pass or fail criteria:
Pass Criteria.
Test Deliverable:
If Online Shopping login form is open successfully then output pass.
Environmental need:
Mobile phone.
Internet.
Power supply.
Computer system.
Responsibilities:
In Software product to concentrates is important.
Defect free Software product.
Schedule:
Day : Monday.
Date : 22/09/2019.
Time : 9:31pm
Risk:
Power supply.
Recharge.
Internet.
Approval:
Product:
To visit the product.
To buy a product.
Components:
Account.
Product available
Internet.
Defect Type:
Requirement testing.
Environmental:
Internet.
Computer System/Android Mobile
Database.
Steps:
• Start internet.
• Open Login page Enter id and Password.
• Click On the Login Option.
• Login page Successfully Open.
Status: New
Severity: Low
Priority: Medium
Summary:
Description:
Chapter 6
Interpretation of Result
The system has been implemented and tested successfully. It meets the information
requirements specified to the great extent. although the system has been designed keeping
the present and future requirements in mind and made very flexible.
There are limitations of the system. proper consideration has been given for a wide range
of new enhancements. The system is developed user friendly.In future , if it is required to
generate reports other than provided by the system it can be simply achieved by a separate
module to the main menu without affecting the design of the system.
6.1 Advantages
• It simplifies the operation.
• It avoids a lot of manual work.
• Every transaction is obtained and processed immediately.
• Avoids errors by avoiding the manual work.
• User friendly screen to enter the data and enquire the database tables.
• Online help messages available to the operating system.
• User can easily access the system without much experience.
• Provide hardware and software securities.
• Portable and flexible for further extensions.
Chapter 7
Conclusion
• The central concept of the application is to allow the customer to shop virtually
using the Internet and allow customers to buy the items and articles of their desire
from the store. The information pertaining to the products are stores on an RDBMS
at the server side (store).The Server process the customers and the items are shipped
to the address submitted by them.
• The application was designed into two modules first Os for the customers who
wish to buy the articles. Second is for the storekeepers who maintains and
updates the information pertaining to the articles and those of the customers.
• The end user of this product is a departmental store where the application is
hosted on the web and the administrator maintains the database. The application
which is deployed at the customer database, 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.
Chapter 8
References
8.1 Bibliography
Websites
• http://www.google.com
• http://www.microsoft.com
• http://www.programmer2programmer.net
• http://www.codeproject.com
• http://www.msdn.com.