mini_Project_SRS

<Online Ordering Web Application>
Software Requirements Specification
<Version 1.0>
<30.04.2015>
<H.V Tamari>
Trainee Software Engineer
Prepared for
Internship task 01

< Online Ordering Web Application >
Software Requirements Specification Page ii
Table of Contents
1. INTRODUCTION ...................................................................................................................................................1
1.1 PURPOSE ..............................................................................................................................................................1
1.2 SCOPE ..................................................................................................................................................................1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ................................................................................................2
1.4 REFERENCES........................................................................................................................................................2
1.5 OVERVIEW...........................................................................................................................................................3
2. GENERAL DESCRIPTION...................................................................................................................................3
2.1 PRODUCT PERSPECTIVE .......................................................................................................................................3
2.2 PRODUCT FUNCTIONS ..........................................................................................................................................3
2.3 FUNCTIONAL REQUIRMENT ..........................................................................ERROR! BOOKMARK NOT DEFINED.
3. SPECIFIC REQUIREMENTS...............................................................................................................................5
3.1 EXTERNAL INTERFACE REQUIREMENTS...............................................................................................................5
3.1.1 User Interfaces............................................................................................................................................5
3.1.2 Hardware Interfaces ...................................................................................................................................9
3.1.3 Software Interfaces....................................................................................................................................10
3.1.4 Communications Interfaces.......................................................................................................................10
3.5 NON-FUNCTIONAL REQUIREMENTS ...................................................................................................................10
3.5.1 Performance..............................................................................................................................................10
3.5.4 Security .....................................................................................................................................................10
3.8 LOGICAL DATABASE REQUIREMENTS................................................................................................................11

Software Requirements Specification Page 1
1. Introduction
The purpose of this document is to present a detailed description of the Online Ordering Web
Application. It will explain the purpose and features of the system, the interfaces of the system,
what the system will do, the constraints under which it must operate and how the system will
react to external stimuli.
1.1 Purpose
Using OOP concepts and MVC design architecture (Model View Controller) implement an
effective and efficient web application. This document is intended for both the stakeholders and
the developers of the system.
1.2 Scope
This software system will be an Online Ordering Web Application for business to customer
model in the e-commerce. This system will be designed to manage the products and easily
review the client’s orders. By maximizing the admin’s work efficiency and facilitate efficient
order system to the client.
More specifically, this application is designed to allow an admin to manage and contact with a
clients and facilitating ordering facilitate to the client. The software will facilitate
communication between Admin and client via web application. In this project not contain the
stock management task. The application also contains a relational database.

1.3Definitions, Acronyms, and Abbreviations
Short name description
1 OOP Object Oriented Programming is a programming
language model organized around objects rather than
“action” and data rather than logic
2 MVC MVC is one of three ASP.NET programming
models. MVC is a framework for building web
applications using a MVC (Model View Controller)
design
3 Relational Database A relational database is a collection of data items
organized as a set of formally-described tables from
which data can be accessed or reassembled in many
different ways without having to reorganize the
database tables.
4 Software Requirements
Specification
A document that completely describes all of the
functions of a proposed system and the constraints
under which it must operate. For example, this
document.
5 OOWA Online Ordering Web Application
1.4References
[1] IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications. IEEE Computer Society, 1998.
[2] Marc Plotz (2014) 'Principles of MVC for PHP Developers'.

1.5 Overview
The next chapter, the Overall Description section, of this document gives an overview of the
functionality of the product. It describes the requirements and is used to establish a context for
the technical requirements specification in the next chapter. The third chapter, Requirements
Specification section, of this document is written primarily for the developers and describes in
technical terms the details of the functionality of the product. Both sections of the document
describe the same software product in its entirety, but are intended for different audiences.
2. General Description
2.1 Product Perspective
This product is mainly related with the online shopping cart systems but the difference is this
product only deal with the clients and Administrator. In this project not handle stock
management side.
Manage & review Order
Administrator Clients
2.2 Functional Requirements
There are 2 sub modules in this phase.
 Administrator module
 Client module
The major functions that are available to the Administrator are:
 The administrator has the full-fledged rights over the OOWA.
 Can create/delete a product.
Web Application

 Insert/delete/edit the products information of available on OOWA.
 Can view the orders.
 Can change the password.
The major functions that are available to the Client are:
 Facilitate to ordering a products.
 Client have facility to manage his /her cart.
 Facilitate to review the current number of products items.

3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
Here include the relevant interfaces
01. Administrator Login
02. Home page

03. Administrator’s product managing page
04. Add product item form

05. Order review page

06. Client’ selection page

07. Client profile
08. Client ordering page
3.1.2 Hardware Interfaces
Server Side:
 Operating System: Windows 8.1 pro
 Processor: Intel (R) Core(TM)i3 CPU
 RAM: 8.00 GB

Client side:
 Operating System: Windows 9x or above
 Processor: Pentium III or 2.0 GHz or higher.
 RAM: 256 Mb or more
3.1.3 Software Interfaces
 Client Side: HTML, Web Browser, Windows
 Web Server: HTML, Windows
3.1.4 Communications Interfaces
The Customer must connect to the Internet to access the Website:
 Dialup Modem of 52 kbps
 Broadband Internet
 Dialup or Broadband Connection with an Internet Provider.
3.2 Non-Functional Requirements
3.2.1 Performance
Some Performance requirements identified is listed below:
 The application should support to multiple users at a time.
 Display the available quantity at a time.
3.2.2 Security
Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below. Keep specific log or
history data sets
 Assign certain functions to different modules
 Restrict communications between some areas of the program

3.3 Logical Database Requirements

mini_Project_SRS

More Related Content

What's hot (20)

Similar to mini_Project_SRS (20)

mini_Project_SRS