Sei sulla pagina 1di 18

ONLINE SHOPPING STORE

Software Requirements Specification

Revision History

Date (DD/mm/yyyy) Version Description Author

29/02/2016 1.0 Online Shopping Store MUDASSIR JALIL


SRS | PAF-KIET (Final Year Project)

ABSTRACT
Electronic commerce, also known as ecommerce is a type of industry where buying and
selling of a product is conducted over electronic systems such as the internet. The purpose of
this application is to bring knowledge to students about ecommerce and how an interactive
ecommerce application can be designed from scratch using client-side languages, such as
JavaScript and HTML, combined with the server-side Java language through Java Server Faces.
The server side, mostly Java, contains all the implementation related to setting up the
database, creating session models for joining different user-interface (UI) pages, etc. It is
responsible for taking information from the database and making it available to the UI by
mapping the category or item ID to the respective IDs stored in the database. The client side is
responsible for showing the entire user interface, containing the CSS, HTML, and JavaScript.

ACKNOWLEDGMENTS

Page 2
SRS | PAF-KIET (Final Year Project)

I would like to express my deep sense of gratitude and convey thanks to everyone who helped
me and supported during the completion of this project and my research paper. First, I would
like to express a deep sense of gratitude to Mr. Zafar Iqbal for helping, guiding, and
supporting me throughout my master’s degree and research completion. I also convey thanks
to my all committee members for helping me from time to time and for being on my
committee. I acknowledge my department for providing the courses and a great atmosphere
that helped complete different chapters of this paper. I especially thank my supervisor for
supporting me and my concepts and for allowing me to do something the way I liked, as well
as my company, for helping me develop the skills necessary to design this application as part
of my master’s research. Last but not least, I would like to thank my family members for their
constant and unrelenting support towards my education and for their impartial love for me. I
would also like to thank my friends, without whom this project would have been impossible.

PAF-KIET

Table of Contents

1. INTRODUCTION ..................................................................................................................................................... 6
1.1 Motivation......................................................................................................................................................... 6
1.2 Aim of software............................................................................................................................................... 6

Page 3
SRS | PAF-KIET (Final Year Project)

1.3 About Project ................................................................................................................................................... 6


1.4 Scope ................................................................................................................................................................... 7
1.5 Objective ............................................................................................................................................................ 7
2. Modules..................................................................................................................................................................... 7
User/Customer Module ...................................................................................................................................... 7
Website Adminstrator Module ........................................................................................................................ 7
2.1 Entities ............................................................................................................................................................... 8
3. FUNCTIONAL REQUIREMENTS ....................................................................................................................... 8
3.1 Registration ...................................................................................................................................................... 9
3.2 Login ................................................................................................................................................................... 9
3.3 Changes to Cart ............................................................................................................................................... 9
3.4 Payment ............................................................................................................................................................. 9
3.5 Logout ................................................................................................................................................................ 9
3.6 Report Genertation ....................................................................................................................................... 9
4. WORK BREAK DOWN STRUCTURE…………………………………………………………………………………9
5. BUDGET AND COSTING ................................................................................................................................... 10
6. NON FUNCTIONAL REQUIREMENT ............................................................................................................ 16
6.1 Performance ................................................................................................................................................. 16
6.2 Hardware Limitations ............................................................................................................................... 17
6.3 Software Limitations ................................................................................................................................. 17
6.4 Reliability ....................................................................................................................................................... 17
6.5 Availability..................................................................................................................................................... 17
6.6 Security ........................................................................................................................................................... 17
6.7 Development Tool ...................................................................................................................................... 17
6.8 Database & Programming Languages ................................................................................................. 17
7. SYSTEM SPECIFICATION ................................................................................................................................ 18
Minimum Hardware Requirements ............................................................................................................ 18
Browsers ............................................................................................................................................................... 18

Page 4
SRS | PAF-KIET (Final Year Project)

List of Figures
Figure 1.1: Use case Diagram. .................................................................................................. 11-12
Figure 1.2: Sequence Diagram. ................................................................................................ 13-14
Figure 1.3: Activity Diagram. ........................................................................................................... 15
Figure 1.4: Class Diagram. ................................................................................................................ 15
Figure 1.5: ERD. .................................................................................................................................... 16

Page 5
SRS | PAF-KIET (Final Year Project)

1. INTRODUCTION

1.1 MOTIVATION

The motivation for designing this shopping-cart application came because I love online
shopping rather than spending lot of time at physical markets. Further, using the available
stores to sell the products, there is also the possibility of designing one’s own customized
shopping-cart application from scratch because custom-designed platforms are expensive.
Moreover, I value recent learning about the programming languages as well as seeing how
powerful and dynamic they are when it comes to web designing and applications. Apart from
helping computer science students understand the concepts of web-application designing, it
would be very easy to incorporate the idea of using programming techniques from the
available visuals to understand how a piece of code appears on a user interface. The
languages used to build this application are JavaScript, HTML, and Java because I found them
to be extremely useful while working on the technologies at my workplace.

1.2 AIM OF THE SOFTWARE


This software is developed to help computer science students learn about application
designing using JavaScript and HTML from their basic capabilities. This application allows the
student to understand the basics about the appearance of a first web page and how a
complete working application can be built from scratch. It allows students to understand the
concept of user-integrated graphics and how JavaScript can be embedded into HTML. Further,
it gives insight about how the client-side language interacts with the server-side language,
Java, and finally with the database. This shopping-cart application is designed, primarily, for
computer science students to learn and understand the concept of application development,
and can also be used to teach ecommerce and web-application topics. The application can be
downloaded and 3 installed on different machines, and students can view the source code for
all the different parts shown on the UI to visually understand how a particular piece of code
works. This shopping-cart application is very versatile and can be enhanced by adding more
functions and modified graphics for use with commercial purposes.

1.3 ABOUT PROJECT:


Online Shopping Store is the best online marketplace where buyers and sellers can meet
and make awesome deals thanks to the fixed pricing system. Online Shopping Store is the

Page 6
SRS | PAF-KIET (Final Year Project)

place where you can buy the cheapest items, such as clothing and garments items. All
transactions are safe and secure and you can even get to choose where and when the delivery
will take place.

1.4 SCOPE:
Purchasing the 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.

Few examples of these are


 darazpk.com
 waayclothing.pk
 kaymu.pk

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. 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)

1.5 OBJECTIVE:
The system is capalbe of maintining details of varios customers, vendors, products and
storing all the day to day trasictions such as generation of shippment adress bills, handling
constomers and product receipts, updating of stores. The central concept of the application is
allow the customer to shop virtually using the internet and allow customer to by athe items of
their desire form the sotre. the information peraining the products are store on DBMS at tha
server side (store). The server process the customers and the items are shipped to the
address submitted by them.

2. MODUELS
Online Shopping System consist on multiple section mention below.

 User/customer Module
 Website Administrator Module

The system after careful analysis has been divided into 9 modules to be presented with the
following modules:

Page 7
SRS | PAF-KIET (Final Year Project)

User/customer Module we have some more sub modules that are following:
1. Registration Module
2. Products Browse Module
3. Products Search Module
4. Shopping cart Module
5. Shipping & Billing Module
6. Payment Module

Website Administrator Module we have some more sub modules that are following:
1. Admin User Management Module
2. Admin Catalog Management Module
3. Admin Order Management Module

2.1 ENTITIES INVOLVED IN THE PROJECT:


1) Customer:
The target user of the system. A Customer is responsible for registering them to the site,
browsing site, placing orders and making payments
2) Product:
Product is the entity, a customer looking for. A Product will be sold to the customer.
3) Website Administrator:
An entity responsible for managing users, roles and roles privileges.
4) Operator:
Operator is a person (entity) responsible for managing products and orders.
5) Order:
Oder is an entity which describes the business transaction.

3. FUNCTIONAL REQUIREMENT
This section provides requirement overview of the system. Various functional modules that
can be implemented by the system will be:

1. Registration
2. Login
3. Changes to Cart
4. Payment
5. Logout

Page 8
SRS | PAF-KIET (Final Year Project)

6. Report Generation

3.1 REGISTRATION:
If customer wants to buy the product then he/she must be registered, unregistered user can’t
go to the shopping cart.
3.2 LOGIN:
Customer logins to the system by entering valid user id and password for the shopping.
3.3 CHANGES TO CART:
Changes to cart means the customer after login or registration can make order or cancel
order of the product from the shopping cart.
3.4 PAYMENT:
Customer can use secure billing will be, postpaid as after shipping the orders.
3.4 LOGOUT:
After the proceed order or surf the product the customer will logged out.
3.5 REPORT GENERATION:
After all transaction the system can generate the text file and then sent one copy to the
customer’s Email-address and another one for the system data base to calculate the monthly
transaction.

4. WORK BREAKDOWN STRUCTURE

Activity Weeks %age of time


Requirement Analysis 2 weeks 6.25%
Design 6 weeks 18.75%
Implementation 20 weeks 62.5%
Testing 2 weeks 6.25%
Evaluation 1 week 3.125%
Documentation 1 week 3.125%

Page 9
SRS | PAF-KIET (Final Year Project)

5. BUDGETING & COSTING

Page
10
SRS | PAF-KIET (Final Year Project)

Page
11
SRS | PAF-KIET (Final Year Project)

Page
12
SRS | PAF-KIET (Final Year Project)

Page
13
SRS | PAF-KIET (Final Year Project)

Page
14
SRS | PAF-KIET (Final Year Project)

Page
15
SRS | PAF-KIET (Final Year Project)

6. NON FUNCTIONAL REQUIREMENT


There are requirements which are significant to the site, these requirements are known as
non functional requirements. And these are performance, hardware/software limitations,
security, and others are the derivations of the described.

 Security and Privacy of Staff user Accounts form unauthorized acces


 Account deletion policies for Staff users and Candidate
 Performance of website
 Reliability of website
 Accuracy and Completion of Candidate progress report
 Separate dashboard for each module

6.1 PERFORMANCE
The web application should be fast enough to respond the user/customer trasictions in a
timely fashion.

Page
16
SRS | PAF-KIET (Final Year Project)

6.2 HARDWARE LIMITATIONS


The hardware limitations are defined by the limitations of its support web server and
database server.

6.3 SOFTWARE LIMITATIONS


The software limitations are defined by the limitations of its support web server and database
server.

6.4 RELIABILITY
The system should store and retrieve information accurately as provided by the candidate. In
the event a candidate’s session times out, any task which requires future dependent
information shall be cancelled.

6.5 AVAILABILITY
The system availability will be constrained by the availability of the web application server &
database server.

6.6 SECURITY
Candidate should be required to log into the system for all operations except the operations
on the login page. The system should restrict each module operation within its own module.

6.7 DEVELOPMENT TOOL

 Sublime Text Editor


 Adobephotoshop CS5

6.8 DATABASE & PROGRAMMING LANGUAGES

 HTML5
 CSS
 MSSQL Server 2008R2
 php
 Java Script
 Jquery
 Bootstrap

Page
17
SRS | PAF-KIET (Final Year Project)

7. SYSTEM SPECIFICATION

7.1 MINIMUM HARDWARE REQUIREMENTS

 Processor : Intel Pentium & later


 Speed : 2.60 GHz
 Hard Disk : 40GB & Above
 RAM : 2 GB
 Operation System : XP, Win 7 & Win8 Win10

7.2 BROWSERS

 Chrome
 Firefox
 Opera
 Safari
 Or any standard Browser

THANKS YOU 

Page
18

Potrebbero piacerti anche