I MART

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Engineering
in
Computer Science & Engineering

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY

INDORE- 453331

2019-2020
 I MART

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Engineering
in
Computer Science & Engineering

PROJECT GUIDE SUBMITTED BY

Mr.Arjun Singh Parihar Nikita Mishra(0829cs161082)
Ritesh Kumar Mishra(0829cs161107)
Sachin Chaturvedi(0829cs161111)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE- 453331

2019-2020
SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE, 453331

CERTIFICATE
This is to certify that Nikita Mishra(0829cs161082), Ritesh Kumar
Mishra(0829cs161107), Sachin Chaturvedi(0829cs161111)
have completed their project work, titled “I MART” as per the syllabus and have
submitted a satisfactory report on this project as a part of fulfillment towards the
degree of “BACHELOR OF ENGINEERING” (Computer Science &
Engineering) from RAJIV GANDHI PROUDYOGIKI
VISHWAVIDHYALAYA, BHOPAL.

HEAD OF THE DEPARTMENT PROJECT GUIDE

DIRECTOR
SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE, 453331

CERTIFICATE
This is to certify that Nikita Mishra(0829cs161082), Ritesh Kumar
Mishra(0829cs161107), Sachin Chaturvedi(0829cs161111)
have completed their project work, titled “TITLE OF THE PROJECT” as per

the syllabus and have submitted a satisfactory report on this project as a part of

fulfillment towards the degree of “BACHELOR OF ENGINEERING”

(Computer Science & Engineering) from RAJIV GANDHI PROUDYOGIKI

VISHWAVIDHYALAYA, BHOPAL.

INTERNAL EXAMINER EXTERNAL EXAMINER

 ACKNOWLEDGEMENT

We express deep gratitude for enthusiasm and valuable suggestions that we got from our
guide Mr. Arjun Singh Parihar for successful completion of the Software Design
Specification of the project. This was not possible without the invaluable guidance of our
project guide.

We are also thankful to our project coordinator Mrs.Teena Dubey, for her technical
guidance, encouragement and support.

We are deeply indebted to Mrs. Reetu Gupta, Head of Department of Computer Science
Engineering, for providing us support and resources for successful completion of the work.

We pay deep regards to our Director Dr.N.K.Dagdee who is instrumental in setting

standards for the students to achieve.

Finally, we are thankful to all the people who are related to the project directly or indirectly.

Nikita Mishra(0829cs161082)
Ritesh Kumar Mishra(0829cs161107)
Sachin Chaturvedi(0829cs161111)
 TABLE OF CONTENTS

CHAPTER TITLE PAGE NO.

ABSTRACT iii
LIST OF TABLES xvi
LIST OF FIGURES xviii
LIST OF SYMBOLS xxvii

I. SOFTWARE REQUIREMENT SPECIFICATION

1 INTRODUCTION 1
1.1 .... ......... 2
1.1.1 General 5
1.1.2 ........... 12
1.1.1.1 General 19
1.1.1.2 . . . . . . . . . . 25
1.1.1.3 . . . . . . . . . . 29
1.1.3 ............ 30
1.2 . ....... 45
1.3 .................. 58
2 SOFTWARE REQUIREMENT ANALYSIS 59
2.1 ................. 60

II. SOFTWARE DESIGN SPECIFICATION 69

3 INTRODUCTION 70
3.1 GENERAL 75
3.1.1 .......... 99
3.2 . . . . . ……………. 100
1. Introduction

1.1. Purpose
1.2. Scope
1.3. Problem Domain
1.4. Proposed Solution

2. System Requirement Analysis

2.1 Introduction

2.1.1 Purpose
2.1.2 Document Conventions
2.1.3 Intended Audience and Reading Suggestions
2.1.4 Product Scope
2.1.5 References of SRS

2.2 Overall Description

2.2.1 Product Perspective

2.2.2 Product Functions
2.2.3 User Classes and Characteristics
2.2.4 Operating Environment
2.2.5 Design and Implementation Constraints
2.2.6 User Documentation
2.2.7 Assumptions and Dependencies

2.3 External Interface Requirements

2.3.1 User Interfaces

2.3.2 Hardware Interfaces
2.3.3 Software Interfaces
2.3.4 Communications Interfaces

2.4 Functional Requirement

2.4.1 System Feature 1

2.4.2 System Feature 2

2.5 Nonfunctional Requirements

2.5.1 Performance Requirements

2.5.2 Safety Requirements
2.5.3 Security Requirements
2.5.4 Software Quality Attributes

2.6 Project Plan

2.6.1 Team Members

 2.6.2 Division of Work
2.6.3 Time Schedule

3. Analysis

3.1. Use Case Diagram

3.2. Sequence Diagram
3.3. Dfd
3.4. Activity Diagram
3.5. Class Diagram
3.6. Er Diagram

4. Design

4.1. Component Design

4.1.1. Flow Chart
4.2. Interface Design
4.2.1. Screenshots

5. Implementation

5.1. Language and database system used for the implementation

5.2. Features of language and database used for the project
5.3. Reason for selecting language and database used.
5.4. Description of third party tools used (If any)

6. Testing (Theory of testing is not required. Only write how u have tested the system)

6.1. White Box Testing

6.2. Black Box Testing
6.3. Test Cases and results

7. Future Scope and Limitations

8. Conclusion

9. Reference (include references of the project)

 INTRODUCTION:

.1 PURPOSE
Online shopping (sometimes known as e-tail from "electronic retail" or e-shopping) is
a form of electronic commerce which allows consumers to directly buy goods or services
from a seller over the Internet using a web browser.

.2 SCOPE
This website can be implemented to any shop in the locality or to national branded shops
having retail outlet chains. This website can help the users to buy goods from any
particular store situated in their respective areas.
This will save the time of users, like for buying something we have to maintain a queue
for purchasing, so this website can rescue that problem also.

.3 PROBLEM DOMAIN

 At present, the Wholesale and Retail outlets are working under manual management. All
records related to Products, Sales, Suppliers, Orders, Payment are stored in registers. To
manage the whole data, the person maintaining records has to take great pain. Various
registers have to be maintained for each separate process.
 New Products launched in the market. Maintenance of Customers Payment Record
(including installment details). Issue Orders for more Stock. Maintenance of Suppliers
and Staff Records. Searching and answer the query asked by other users. Present
monthly, quarterly or annual Reports. All these operations will lead to continuous
modifications in the database (Here Registers).

.4 SOLUTION DOMAIN

Our project “I Mart” is an attempt to develop the already existing Shop System as a web-
based application. This project will provide more facilities to the users. This online market
makes all the transactions to be online, without any face-to-face interaction. It also provides
extra security in purchase and payment. Almost every activity in the world today is
controlled by computer driven software programs. This trend was first accommodated by
engineering applications in the past. However, as the lifestyle became more and more
complex, every area of human interactions was invaded by various software systems, such as
real time, business, simulation, embedded, web based, personal and more recently, artificial
intelligence software etc. According to the above facts, managing and maintaining a market
could also be controlled by efficient software
2. SOFTWARE REQUIREMENT SPECIFICATION

1. OVERALL DESCRIPTION

1.1 PRODUCT PERSPECTIVE:

This document contains the problem statement that the current or existing systems are
facing.
The following SRS contains the detailed product perspective from different stores. It provides
the detailed product specifications like size, price etc.
This document also includes the functional and nonfunctional requirements for the system.
This Software Requirement Specification includes the overall document on which this system is
working.

1.2 PRODUCT FUNCTION:

Authorization-
 Admin
 Users

Functions like:-
 User Registration
 User Login
 Select Product
 Add to Cart
 Cash On Delivery

1.3USER CLASS AND CHARACTERISTICS

Functional Requirements
The ADMIN should satisfy the following functional requirements.
a. There should be provision for adding and updating products.
b. There should be provision for deleting (from cart) and searching products.
c. There should be provision for searching categories.
d. There should be provision for deleting (from cart) and searching products.

The USERS should satisfy the following functional requirements.

a. End users should be registered person, people can register as user.
b. Registered users can view the products, and can purchase as well.
c. Users can select the categories of products.
d. The user should have basic understanding of the working of website.
1.4 OPERATING ENVIRONMENT

1.5 DESIGN AND IMPLEMENTATION CONSTRAINTS

a. This website is mainly developed by using php.

b. The database used in this website is Mysql.
c. This website can also be run on mobile.

1.6 USER DOCUMENTATION

No other user’s document.

1.7 ASSUMPTIONS AND DEPENDENCIES

The system is dependent availability of an xampp server.

2.2.1 USER INTERFACE

Various interfaces for the products could be:-

 Login Page
 Registration Page
 There will be a screen where user can see the products and can select the products and
add into the cart.

2.2.2 HARDWARE INTERFACE:

S No. Hardware Minimum Recommended

1. RAM 4GB 8GB

2. Hard Disk 1000GB 1000GB

2.2.3 SOFTWARE INTERFACE:

S No. Software Used

1. Operating System Windows

2. Internet Browser Microsoft Edge

4. Database Server MySQL

5. XAMPP 2.3

2.2.4 COMMUNICATION INTERFACE:

The I-Mart system shall uses the HTTP Protocol for communication over the internet and for the
intranet communication will be through TCP/IP Protocol suite.

2.4 FUUNCTIONAL REQUIREMENT:

The system must provide following functionalities-

1 .Keeping records of admission of customers.
2. Keeping the records of products.
3. Keeping the daily sell.
4. Keeping details about the product.

2.5. NON-FUNCTIONAL REQUIREMENTS:-

2.5.1 Performance Requirements:-

Response Time:-
The system shall give responses in 5 sec after user lo

Capacity:-
The system must support as many computer /mobiles available as many people at a time
2.5.1.Safety Requirements:-

All logged information, updates, user activities are securely stored in MySQL

2.5.2Security Requirements:-

Any modification for the Database shall be synchronized and done by system administrator.

2.5.3.Software Quality Attributes:-

 Software Compliance- There shall be consistency in variables within the system. The
graphical user interface shall have consistent feel and look.
 Reliability- The system is reliable; specify the factors required to establish the required
reliability of the software system at the time of delivery.
 Language- Speed up form development but does not limit functional.
 Availability- The system shall be available 24*7.

2.6. PROJECT PLAN

2.6.1 Team Members:-

1. NAME:- NIKITA MISHRA

b. EMAIL-ID:- <nikitamishrabth@gmail.com>

1. NAME:- RITESH KUMAR MISHRA

c. EMAIL-ID: <mishraritesh329@gmail.com>

1. NAME:-SACHIN CHATURVEDI
d. EMAIL-ID:-<chaturvedisachin751@gmail.com>

2.6.2 Division of work

(a) Name: - Nikita Mishra

Work: - Requirement Gathering, Analysis and Planning, Designing, Database design, entry
and testing

(b) Name: - Ritesh Kumar Mishra

Work: Planning, Coding and connecting, Database design, entry and testing
(c) Name: -Sachin chaturvedi
Work:- Planning framing, page design, Database design, entry and testing

SOFTWARE DESIGN SPECIFICATION

CHAPTER 3

ANALYSIS

3.1 Use case diagram:-

3.2 SEQUENCE DIAGRAM
3.3 ACTIVITY DIAGRAM
3.4 DATA FLOW DIAGRAM
3.5 CLASS DIAGRAM
3.6 ENTITY RELATIONSHIP DIAGRAM
DESIGN

4.1. ARCHITECTURAL DESIGN

The software architecture of a program or computing system is the structure or structures of the
system which comprise, the software components , the externally visible properties of those
components, the relationships among the components , software architectural design represents
the structure of the data and program components that are required to build a computer-based
system, an architectural design model is transferable, it can be applied to the design of other
systems , it represents a set of abstractions that enable software engineers to describe architecture
in predictable ways

4.2. DATABASE DESIGN

Database design is the process of producing a detailed data model of a database. This data model
contains all the needed logical and physical design choices and physical storage parameters
needed to generate a design in a data definition language, which can then be used to create a
database. A fully attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an overall
database system. Principally, and most correctly, it can be thought of as the logical design of the
base data structures used to store the data. In the relational model these are the tables and views.
In an object database the entities and relationships map directly to object classes and named
relationships. However, the term database design could also be used to apply to the overall
process of designing, not just the base data structures, but also the forms and queries used as part
of the overall database application within the database management system (DBMS).

i. The process of doing database design generally consists of a number of steps which will
be carried out by the database designer. Usually, the designer must:
ii. Determine the data to be stored in the database.

iii. Determine the relationships between the different data elements

iv. Superimpose a logical structure upon the data on the basis of these relationships.
4.2.1. DATA DICTIONARY

The terms data dictionary and data repository indicate a more general software utility than a
catalogue. A catalogue is closely coupled with the DBMS software. It provides the information
stored in it to the user and the DBA, but it is mainly accessed by the various software modules of
the DBMS itself, such as DDL and DML compilers, the query optimizer, the transaction
processor, report generators, and the constraint enforcer. On the other hand, a data dictionary is a
data structure that stores metadata, i.e., (structured) data about information. The software
package for a stand-alone data dictionary or data repository may interact with the software
modules of the DBMS, but it is mainly used by the designers, users and administrators of a
computer system for information resource management. These systems maintain information on
system hardware and software configuration, documentation, application and users as well as
other information relevant to system administration.

4.2.2. NORMALIZATION

Database normalization, or simply normalization, is the process of restructuring a relational

database in accordance with a series of so-called normal forms in order to reduce data
redundancy and improve data integrity. It was first proposed by Edgar F. Cod as an integral part
of his relational model.

Normalization entails organizing the columns (attributes) and tables (relations) of a database to
ensure that their dependencies are properly enforced by database integrity constraints. It is
accomplished by applying some formal rules either by a process of synthesis (creating a new
database design) or decomposition (improving an existing database design).

4.3 COMPONENT DIAGRAM

Component design is also called as component-based development (CBD), is a branch of
software engineering that emphasizes the separation of concerns with respect to the wideranging
functionality available throughout a given software system. It is a reuse-based approach to
defining, implementing and composing loosely coupled independent components into systems.
This practice aims to bring about an equally wide-ranging degree of benefits in both the short-
term and the long-term for the software itself and for organizations that sponsor such software.

Software engineering practitioners regard components as part of the starting platform for service-
orientation. Components play this role, for example, in web services, and more recently, in
service-oriented architectures (SOA), whereby a component is converted by the web service into
a service and subsequently inherits further characteristics beyond that of an ordinary component.
4.4. INTERFACE DESIGN

Interface design is the design of user interfaces for machines and software, such as computers,
home appliances, mobile devices, and other electronic devices, with the focus on maximizing
usability and the user experience. The goal of user interface design is to make the user's
interaction as simple and efficient as possible, in terms of accomplishing user goals (user-
cantered design).
Good user interface design facilitates finishing the task at hand without drawing unnecessary
attention to itself. Graphic design and typography are utilized to support its usability,

Influencing how the user performs certain interactions and improving the aesthetic appeal of the
design; design aesthetics may enhance or detract from the ability of users to use the functions of
the interface. The design process must balance technical functionality and visual elements (e.g.,
mental model) to create a system that is not only operational but also usable and adaptable to
changing user needs

4.5. SCREENSHOTS
CHAPTER 5

IMPLEMENTATION

5.1.LANGUAGE AND DATABASE SYSTEM USED FOR THE

IMPLEMENTATION

Language and database

Frontend Language Backend Database Server

HTML, CSS, JS PHP MYSQL XAMPP

5.2FEATURES OF LANGUAGE AND DATABASE USED FOR THE

PROJECT

HTML5 and CSS for the front end designing.

php as a backend development

.
MYSQL for the database.

Advantages Of PHP

The reason behind the popularity of PHP is its several advantages. PHP is most
suited for the purpose of web development. The advantages of PHP are discussed
briefly below:

1. Cross Platform.
All the PHP based applications can run on various types of platforms.PHP is supported by
majority of Operating Systems, some of which includes Solaris, UNIX, Windows and Linux. The
mentioned platforms can be used to write codes in PHP and also view web pages or run the PHP
based applications.
PHP easily interfaces with MySQL and Apache both. An effortless integration of PHP can be
done with various other technologies like Java and there is no requirement of re-development.
Therefore, saving both time and money, giving it an important advantage.

2. Easy database connection.

A programming language like PHP is widely used on the internet and needs to connect to the
database very often. Therefore, having a feature that could help PHP to connect to database
easily is mandatory. Several websites such as the ecommerce websites, require good database
management system.
PHP has a built-in module that helps it in connecting with database easily. Therefore, PHP has a
great demand in the field of web development where a data driven website needs to be
developed. PHP significantly reduces the time needed in developing the web application that
needs an efficient database management system.
3. Easy to use.
PHP is widely used because it is easy to use. In contrast with other programming languages that
are complex, PHP is simple, fluent, clean and organized, hence it is a boon for the new users.
PHP has a well-organized syntax which is logical at the same time.

PHP does not require any intensive studying or manual to use it. Command functions of PHP are
easily understood as the user can easily figure out from the name of the commands itself what it
does. A person who is new to PHP can still code because the syntax is somewhat similar to C.
A person who is new to PHP can still code because the syntax is somewhat similar to C. Hence,
if a person who knows C can easily code in PHP. Hence, it is easier to create and optimize the
application using PHP.

Speed is the primary need of web development. There are people who face the challenge of slow
internet connection and slow data speed. The high speed of PHP gives it an advantage over other
scripting languages and gives it an application in important administrations such as the server
administration and mail functionalities.
4.Open Source
One of the important advantages of PHP is that it is Open Source. Therefore, PHP is readily
available and is entirely free. In contrast to other scripting languages used for web development
which requires the user to pay for the support files, PHP is open to everyone, anytime and
anywhere.
A beginner in PHP need not worry about the support as PHP is maintained and developed by a
large group of PHP developers which helps in creating support community of PHP that helps
people in PHP implementation and manipulation.
CHAPTER 6

TESTING

WHITE BOX TESTING (BASIS PATH TESTING)

 Test Case-1
 Purpose
 To find incorrect or missing functions
 To find initialization and termination errors
 Inputs
 Manually checks of the code.
 Without login the administration login access of the each page.
 Expected Outputs & Actual Outputs
 Expected output should return to the login page if user is not logged in.
 Actual output system properly,
 each page is showing login is compulsory for the administrator to open any screen.

 Test Case-2
 Purpose
 To find interface errors
 To find behavior or performance errors
 Google Chrome.
 Internet Explorer.
 System tested with following operating system:
 Windows.
 Expected Outputs & Actual Outputs
Expectation was to work properly as platform independent web portal.
Actual output was as expected, system working on all the browsers of the all platform
mentioned above.
 Test Case-3
Purpose
To find errors in data structures or external database access
Database connectivity of the system.
Inputs
Try to access the database using different combination of the username and password.
Expected Outputs & Actual Outputs
Expected output should be no access error by the system to unauthorized user.

Database is secured with password and only the assigned administrator can access
and modify the database.
Actual output does the same.
Only an authenticated user can access the database.
  Test Case-4
 Purpose
 Privacy of the user.
 Check for the duplicity of the data for the multiple
 feedbacks from the same user in one time.
 Inputs
 Feedback has been given from the different computers and
 also from the same computer multiple times.
 Expected Outputs & Actual Outputs

6.2 BLACK BOX TESTING

6.2.1 INTERFACE TESTING

 White-box test and their results

 Control flow testing: Working as per expectation.
 Data flow testing: Working as per expectation.
 Branch testing: Working as per expectation.
 Statement coverage: Working as per expectation.
 Decision coverage: Working as per expectation.
 Modified condition/decision coverage: Working as per expectation.
 Prime path testing: Working as per expectation.
 Path testing: Working as per expectation.

CHAPTER 7

FUTURE SCOPES AND LIMITATION

FUTURE SCOPE :-

Purchasing and selling products and services over the internet without the
need of going physically to the market is what online shopping all about.
Online shopping is just like a retail store shopping that we do by going to the
market, but it is done through the internet.
Online shopping has made shopping painless and added more fun. Online
stores offer product description, pictures, comparisons, price and much
more. Few examples of these are Amazon.com, ebay.com, framt.com and
the benefits of online shopping is that by having direct access to consumer,
the online stores can offer products that cater to the needs of consumer,
cookies can be used for tracking the customer selection over the internet or
what is of their interest when they visit the site again.
Online shopping makes use of digital technology for managing the flow of
information, products, and payment between consumer, site owners and
suppliers. Online shopping can be either B2B (business to business) or B2C
(business to consumer)
Shopping cart is one of the important facility provided in online shopping,
this lets customer to browse different goods and services and once they
select an item to purchase they can place the item in shopping cart, and
continue browsing till the final selection.
Customers can even remove the items from shopping cart that were selected
earlier before they place the final order.
It reminds us of shopping basket that we carry in departmental store.

LIMITATIONS :-
In order to perform the rent a vehicle capability:
1. customer must login to their own profiles
2. guests must create their own accounts.
Unless the payment phase is completed, the system will not allow to perform the booking
and renting capabilities,
3.The system does not allow rent the same date. If such a consequences happened.
4. The system will give fatal error.
1. Delay in delivery
Though the duration of selecting, buying and paying for an onlineproduct may not take
more than 15 minutes; the delivery of the product to customer’ s doorstep takes about 1-
3 weeks.

2. Lack of significant discounts in online shops

Physical stores offer discounts to customers and attract them so this makes it difficult
for e-tailers to compete with the offline platforms.

3. Lack of touch and feel of merchandise in online shopping

Lack of touch-feel-try creates concerns over the quality of the product on offer. Online
shopping is not quite suitable for clothes as the customers cannot try them on.

4. Lack of interactivity in online shopping

Physical stores allow price negotiations between buyers and the seller. The show room
sales attendant representatives provide personal attention to customers and help them
in purchasing goods.

5. Lack of shopping experience

The traditional shopping exercise provides lot of fun in the form of show-room
atmosphere, smart sales attendants, scent and sounds that cannot be experienced
through a website.

6. Lack of close examination in online shopping

A customer has to buy a product without seeing actually how it looks like. Customers
may click some product that is not really required by them.

7. Frauds in online shopping

The rate of cyber crimes has been increasing and customers’ credit card details and bank
details have been misused which raise privacy issues.