Chapter-1

Introduction
1.1 Purpose
The main objective of this document is to illustrate the requirements of Online Shop System.
This document also provides functional and nonfunctional requirement according to the
Online shop of our country. The purpose of the project is to ensure an easy and reliable
connection between customer and online shop owner where customer can make an order and
get product by sitting at home. For this reason, this document specifies all kinds of
requirements of this project.

1.2 Scope
The Online Shop System is a web-based application. It has user registration process which
will allows shop owner to save unlimited product and stock them at any time. It will also
allows customer to search any kind of products and cart products. The registered customer
can buy any kind of product. This internet based application will allows customer to access
the system from any corner of the Country.

1.3 Overview
This Software Requirement Specification (SRS) is a formal representation of a online shop
System. Shopping is not an easy task in our country. The customer has lots of different
requirement. This document includes all kinds of requirements of an online Shop system
according to our country. This requirement is written with Bangladesh perspective. This
document is going to show customer registration and login process. It will also describe how
to shopping any products. It will describe functional and nonfunctional requirement. This
includes description of the system, customer characteristic, general constraints and any
assumption of the system. This document also includes some description on security,
maintainability, portability and reliability of the system.

1.4 Product Function

The system requires most useful functionality. These can be listed as follows:

 Customer login and logout process.

 Admin, Customer

 Shop Details and Product

 Add, Delete, Update Product

 Searching Product

1
  Customer Can Cart Product

 Communication process with owner

1.5 User Characteristics

The system must support three types of users and the functionality must restrict to the guest
user. The key features of the users can be summarized as follows:

Admin:

 Can Add-Delete-Update Menu

 Can Add-Delete-Update category

 Can Add or Delete Product

 Can View Order and can delete Order

 Can Complete Order

 Can View Sale Statistics

 Owner of this system

Customer:

 Can Create Account

 Add Cart Product

 Can Update or Delete Product

 Can Complete Order

1.6 Operating Environment

As mentioned it is a web based application thus the system can be used by any type of
operating system either mobile or personal computer. This project is using PHP 5 so the
uploaded server must enable PHP 5. The system is using twitter bootstrap for responsive
purpose so it can be used by any size of mobile or tab. This online base application can be
used by Google Chrome, Mozilla Firefox, Internet Explorer(8-11), Opera etc. It should be
mentioned that the browsers must enable Java Script to get proper functionality of the system.

1.7 Constraints
Some constraints describe below:

 The user admin of this system must be computer literate and familiar with web
application uses.

2
 Requires internet connection for using this project as it is a web based application.

 Sufficient bandwidth and hosting space will be required for implementing the system.

3
 Chapter-2
Database and Tables
The database of the system using MySQL. The database is designed by applying the
normalization processes and finally BCNF is also applied. After applying all the process the
database has divided into ten tables. By using foreign keys in the tables joined in SQL queries
for producing different data results.

2.1 Schema Diagram

Figure 01: Schema diagram

4
 Chapter-3
Software Requirement Specification
The application will be cross-platform, as it will design with Twitter Bootstrap and HTML5
that will be able to be run from any web browser. The application will communicate with
server using Code Igniter while data will be stored using PHP myadmin.

3.1 Hardware Interfaces

In terms of hardware interfaces, the system should be able to function on any device with a
working web browser that supports HTML5, CSS and JavaScript. We can abstract our system
from directly communicating with the hardware and use the web browser as a means of
communication to both the backend of the system, which is a centralized server/database, and
to the device itself. The communication between the application and the backend servers will
be done through Code-igniter PHP Framework.

3.2 Software Interfaces

The application will be cross-platform, as it will design with Twitter Bootstrap and HTML5
that will be able to be run from any mobile web browser. The application will communicate
with server using Code-igniter while data will be stored using Phpmyadmin. Communications
between the employee and candidate will be based on the site itself. The contact message will
receive by email.

3.3 Communication Interfaces

A user will be able to access the product through native applications or through the device's
web browser. A login will be required to ensure only registered users may use the product as
well as to protect their content. The login process will provide encrypted password
information.

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

3.4 Functional Requirements

The system’s functional requirement can be summarized as follows:

 Customer Registration: In registrations process the user must set his/her username,
password and what types of user he/she is either Customer. Customer can login the
system using username and password.

5
 View Product: Customer can view all products anytime.

 Shopping Product: Customer can buy product anytime.

 Search Product: Filtering the shopping product.

 Product Category: Filtering the shopping category product.

3.5 Non-Functional Requirements

3.5.1 Security

This application, deals with private user information that would require greater levels of
security to ensure proper safety standards. User information will include data; such as name,
home address, phone number, and National Id no, which require proper security protocols to
prevent data from being compromised. The application must be able to safely protect each
user's data without fault.

3.5.2 Reliability

The target audience for this application includes tenants and property owner whom will store
information to a database. This creates the possible problem of information being breached
by other users of the system. The application must have well developed security standards to
ensure data from users do not unintentionally interact and cause problems for the system and
its database.

3.5.3 Availability

The system should be available at all times, meaning the user can access it using a web
browser. In case of a of a hardware failure or database corruption, a replacement page will be
shown.

3.5.4 Maintainability

A commercial database should use for maintaining the database and the application server
takes care of the site. In case of a hardware failure or database corruption, backups of the
database should be retrieved from the server and saved by the administrator. Then the service
will be restarted.

3.5.5 Portability

The application is HTML and scripting language-based. So the end-user part is fully portable
and any system using any web browser should be able to use the features of the system,
including any hardware platform that is available or will be available in the future. An end-
user can use this system on any OS. The system shall run on PC, Laptops, and PDA etc.

Chapter 4

6
 Design and Analysis
4.1 Use case diagram:

The purpose of use case diagrams can be as follows.

 Used to gather requirements of a system.

 Used to get an outside view of a system.
 Identify external and internal factors influencing the system.
 Show the interacting among the requirements are actors.

4.1.1 Use case diagram of the system with features :

Figure 02: Use case diagram of the system with features

4.1.2 Use Case diagram of Admin

7
 Figure 03: Use case diagram of admin

4.1.3 Use Case diagram of Customer

8
 Figure 04: Use Case diagram of Customer

4.2 Database Design:

9
The purpose of Design phase is to plan a solution for problem specified by the requirements.
System design aims to identify the modules that should be in the system, the specification of
those modules and how the interact with each other to produce the results. The goal of the
design process is to produce a model that can be used later to build that system. The produced
model is called design of the system.

System design is the process of defining the architecture, components, modules, interfaces
and data for a system to satisfy specified requirements.

4.3 Entity Relationship Diagram :

Figure 06: Entity Relationship Diagram

4.3 Activity Diagram.

10
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.

So the control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using
different elements like fork, join etc.

It does not show any message flow from one activity to another. Activity diagram is some
time considered as the flow chart. Although the diagrams looks like a flow chart but it is not.
It shows different flow like parallel, branched, concurrent and single.

So the purposes can be described as:

 Draw the activity flow of a system.

 Describe the sequence from one activity to another.

 Describe the parallel, branched and concurrent flow of the system.

4.3.1 Activity diagram of Sign up

Figure 07: Activity diagram of Sign up

4.3.2 Activity diagram of Login

11
 Figure 08: Activity diagram of Login

4.3.4 Activity diagram of customer order

12
 Figure 09: Activity diagram of customer order

4.3.5 Activity diagram of admin order complete

13
 Figure 10: Activity diagram of admin order complete

4.4 Data Flow Diagram: Data flow diagrams are used to specifyi ng the flow of data
between different modules. Data flow diagrams give us complete knowledge that what
happens to a particular data in a particular module and also specifies that what data are used.

14
4.4.1 Data Flow of Admin

Figure 11: Flow diagram of Admin

4.4.2 Data Flow of Customer

Figure 12: Flow diagram of Customer

15
 Chapter 5
Implementation
5.1 Implementation

Implementation is next after testing. After long explanation and building phases the system is
developed and tested. Implementation is the stage of system development life cycle. The
system is implemented into operation in real environment. A formal acceptance typically
terminates the implementation stage. After the implementation phase software development
lifecycle is the most expensive and time consuming.

There are many ways of implementation. It must be decided which way to adopt prior to
implementation. This phase required many things for consideration because a wrong
approach could bring unexpected result. The risk associate with this phase should be sorted
out. The typical advantages and disadvantages are also the important factor for
implementation.

For front desk implementation method will be parallel and the new system will run parallel to
old one. Implementation is expensive because too many people are associated with the
process, it’s also time consuming as the works are completed during implementation. Backup
should be used. Then if any problem occurs and the system would not affected badly.

5.2 Education:

It is essential for any system that the users of the system must know the context of the
organization need. User must be influenced of the benefits of a new system to them. The first
and foremost decision in education and training must be about the operator to be educated
and trained.

5.3 Implementation Schedule:

In this section, provide a schedule of activities to be accomplished during implementation.
Show the required tasks (described in Section 2.3, Major Tasks) in chronological order, with
the beginning and end dates of each task.

5.4 Security:

If appropriate for the system to be implemented, include an overview of the system security
features and requirements during the implementation.

 System Security Features.

In this section, provide an overview and discussion of the security features that will be
associated with the system when it is implemented. It should include the primary
security features associated with the system hardware and software.

 Security During Implementation.

16
 This section addresses security issues specifically related to the implementation effort,
if any. For example, if LAN servers or workstations will he installed at a site with
sensitive data preloaded on non-removable hard disk drives, address how security
would be provided for the data on these devices during shipping, transport, and
installation because theft of the devices could compromise the sensitive data.

5.5 Implementation Support:

Hardware, Software, Facilities, and Materials.

This section describes the support software, materials, equipment, and facilities required for
the implementation, as well as the personnel requirements and training necessary for the
implementation. The information provided in this section is not site-specific. If there are
additional support requirements not covered by the subsequent sections, others may be added
as needed.

5.6 Personnel.
This section describes personnel requirements and any known or proposed staffing
requirements, if appropriate. Also describe the training, if any, to be provided for the
implementation staff.

5.7 Training.

The training phase is a phase where the users of the system are train. In training the following
methods can be used:

 Observation.

 Informal Discussion.

 Computer Assisted Training.

 User Manual.

Chapter 6
User Interface
6.1 Website Front-end Interface.

17
6.1.1 Home page.

Figure 13: Home Page

6.1.2 Category Page.

18
 Figure 14: Category Page

6.1.3 Checkout Page.

Figure 15: Checkout Page

6.1.4 Sign Up Page.

19
 Figure 16: Signup page

6.1.5 Login Page.

Figure 17: Login Pag

6.1.6 Billing Page

20
 Figure 18: Billing Page

6.1.7 Shipping Page

Figure 19: Shipping Page

6.1.8 Order Confirm Page

21
 Figure 20: Order Confirm Page

6.1.9 Add Menu.

Figure 21: Menu

6.1.10 Category Page

22
 Figure 22: Category Page
6.1.11 Product Page

Figure 23: Product Page

6.1.12 Dashboard page

23
Figure 25: Dashboard Page

Chapter 7

24
 Conclusion
We have tried our best for making this system user friendly as well as usable. The system is
developed under responsive frame work and upgraded technologies so that the system can
run from any devices like PC, Tab, Laptop, Mobile etc. We have tried our best for making this
project cost-effective and flexible. During development of the software all phases have
completed carefully. A sin case of any system development process there might be few
shortcomings. So this project is still under modification. Future up gradation and
enhancement will be continued for keeping the system up to date.

Future Improvements: Our plan to convert into mobile app and also make faster so that
inserting more data, the system will not slow.

References:
 Software engineering,8th edition by Sommerville

25
  Database System Concepts ,Sixth EditionWritten by AviSilberschatz, Henry F.
Korth,S. Sudarshan . Published by McGraw-Hill ,ISBN 0-07-352332-1
 Systems Analysis and Design in a Changing World, 4th Edition written by John
W. Satzinger ,Robert B. Stephen,D. Burd,ISBN-10: 1305117204 | ISBN-13:
9781305117204
 First Course in Database Systems, Written byJeffrey D. Ullman and Jennifer
WidomISBN 0-13-861337-0
Websites:
 https://en.wikipedia.org/wiki/Software_requirements_specification

 https://www.scribd.com/

 https://www.uml.org/

Definitions, Acronyms, and Abbreviations

Admin Owner of this system

Ajax Short form of Asynchronous JavaScript and XML

26
BCNF Short form of Boyce and Codd Normal Form

Bootstrap Designing Frame work combination of HTML, CSS and

JavaScript

CSS Short form of Cascading Style Sheets

CI Code igniter is a php framework

Guest User Unregistered users

HTML Short form of Hyper Text Markup Language

MySQL Is an open-source relational database management system

(RDBMS)

PHP Is a server-side scripting language designed for web

development but also used as a general-purpose programming
language

RDBMS Short form of Relational Database Management System

SRS Short form of Software requirement specification

SQL Short form of Structured Query Language

27