Smart Internet Cafe

SOFTWARE REQUIREMENTS SPECIFICATION

Contents:

1. Introduction.

1.1. Purpose of Requirements Document

1.2. Intended audience

1.3. Scope of development project

1.4. Definitions, Acronyms, and Abbreviations

1.5. References

1.6. Document overview

2. Overall Descriptions.

2.1. Product Perspective.

2.2. User classes and Characteristics

2.3. Operating environment

2.4. Design and Implementation constraints

3. External interface requirements

3.1. User interface

3.2. Hardware interfaces

3.3. Software interfaces

3.4. Communication interfaces

4. System features

4.1. System features

4.1.1. Description

4.1.2. Functional requirements

5. Other requirements

5.1. Performance requirements

5.2. Safety requirements

5.3. Security requirements

5.4. Software quality attributes

5.5. Business rules

5.6. Installation
1. Introduction.

1.1. Purpose of Requirements Document

The purpose of this Software Requirements Specifications (SRS) is to fully document the
specifications and requirements for the OSMS Online Shopping Mall System, so as to serve as a guide
to the developers on one hand and a software validation document for the prospective client on the
other. The application is intended to provide complete solutions for vendors as well as customers
through a single gateway i.e. internet. It will enable a shopping mall to setup its own online
application, customers to browse through and purchase items online without having to visit the shop
physically. The administration module will enable a system administrator to approve and reject
requests for new items and category.

1.2. Intended audience and reading suggestions

Clients: The users of the system will get a clear idea of the software and hardware requirements to
be engaged.

Lab Technicians: They will be in a position to attain the various features that are enabled in the
software there by inducing a new definition for security.

Developers: Project developers have an advantage of quickly understanding the methodology

Students: The project shows an infinite path in the field of security in Internet labs. There is always a
perspective of development.

The authors would suggest clients to go through the requirement section thoroughly before
installing the software. The lab technicians are expected to have certain knowledge in the terms
used and hence can go for the security issues directly. Students and Developers can utilize the
documentation as a resource in developing the project to a new product.

1.3. Scope of development project

The objective of this project is to create and implement a website for the Shopping Mall. The
website will be used primarily by customers of mall. The website will allow users to create and
maintain individual secured accounts, search the Shopping mall database for desired items and
make secured online credit card and on delivery purchases. Users will also be able to contact site
administrators. The website makes purchasing desired items quicker, easier, and more convenient.

1.4. Definitions, Acronyms, and Abbreviations

SRS: Software Requirement Specification2)

OSMS: Online Shopping Management System

Client/User: Internet user at the Internet access point4)

Server: A system that runs in Linux always monitoring the actions.5)

SQL: Structured Query Language7)

HTTP: Hyper Text Transfer Protocol8)

Use rid: Unique username issued to each user on login9)

Password: Unique word given to each user as a secret code.

1.5. References

Websites:

• https://srs-onlineshopping.blogspot.com/

•https://docuri.com_online-project.pdf
•http:// sampleSRS

1.6. Document overview

The first section of SRS builds a brief idea what the proposed System of OSMS is and what is the
need behind having it. Along with this background information it also provides the reference
information for further study, design and implementation. The second section shows the way to
overall description of application, functions, perspective, operating environment, design and
implementation constraints, data inputs required. The third section explores the various descriptions
of external interfaces such as user interface, hardware interface, communication interface and
software interface. The fourth section is written with a goal to show the various system features in
detail. The subsections give an elaborate description of individual features. The fifth section focuses
on details of non-functional requirements such as security requirements, safety requirements etc.
2. Overall Descriptions.

2.1. Product Perspective

The client will be given Internet access only by the knowledge of the server. When a client is
accessing Internet the server will be tracking the username and the account details of the user
logged in. There is also an option for the user to view the account details of the user.

2.2. User classes and Characteristics

 Customers:They will login at user level and will access to account to buy desired items and to
cancel or return item.

 Administrator: They are the core users and are able to add new users and item to the system
and permit them to buy items.

2.3. Operating environment

Particulars Client System Server System

2.4. Design and Implementation constraints

Each user must keep their password as confidential. More over the user must have individual ID for
creating a login in the OSM system. Only Administrator can control items addition and deletion in
the OSM system.

3. External interface requirements

3.1. User interface

2. Registration Form:This is for new users to create their account.

3. There will be a screen displaying information about product that the shop having.

4. If the customers select the buy button then another screen of shopping cart will be opened.

5. After ordering for the product,the system will sent one copyof the bill to the customer’s
Email-Address.

6. User Login (Client Side): The user has to give a username and password bywhich he or she
can access the Internet.

7. User Account: This enables the user to view the account status of their account.

3.2. Hardware interfaces

The server is directly connected to the client systems. Also the client has the access to the database
for accessing the account details and storing the logintime.The client access to the database in the
server is only read only.

3.3. Software interfaces

It uses java servlets as the front end programming tool and SQL as the backend application tool.

OSMS is multi-user application where any number of user can acess the site and buy desired items.
It uses java toolkit

3.4. Communication interfaces

The SIC uses java servlets and hence require HTTP for transmission of data. More over this allows
easy interact5ion between the various clients and the server.

4. System features

4.1. Authentication

4.1.1. Description

The system offers access to Internet at client level and access to server resources at server level only
by validating the user with the unique username and password.

4.1.2. Functional requirements

All system should have the client for program running. The server should identify individual systems
by their name.
Input: User name and password, Account number

Output: Access to Internet, Available balance, Account Details.

4.2. Monitoring

4.2.1. Description

This utility is used to monitor the user status of the various users using the system. Moreover it
provides real time reporting.

4.2.2. Functional requirements

All system should have the client for program running. The server should identify individual systems
by their name.

Input: User name and password, Account number

Output: Available balance, Account Details, Real time users.

4.3. Accountability

4.3.1. Description

This module is designed to support the user accounts in the SIC software. Only the administrators
could access this.

4.3.2. Functional requirements

All system should have the client for program running. The server should identify individual systems
by their name.

Input: User name and password, Account number

Output: Available balance, Account Details, Report.

5. Other requirements

5.1. Performance requirements

The important aspects of SIC software is time constrain. SIC software system is real time and hence
should be performed in minimumrequirements. The accountability is a vital feature and this could
only be assuredif the system is working in full capability. So uninterrupted power supply is needed.

5.2. Safety requirements

The data handled in the SIC system is very vital. The server should always be confirmed to run
properly and the data are saved to the database at consecutive intervals. Power is a significant
feature and the power supply should be always taken care of. An Uninterrupted Power Supply is
always recommended.

5.3. Security requirements

The security system features from having a login for all the users to access the software. The login
details will be used in the system also. So the chances of the software getting intruded are very less.
5.4. Software quality attributes

The source code of the product is going to be open as this is going to be open source software. It will
be free for further modifications and improvements.

5.5. Business rules

Illegal duplication of the reports should be strictly dealt with. The administrator should have full
details of the user while a user is getting registered to the system.

5.6. Installation

A conducive environment for the efficient running of the SIC is always recommended. The server
should be handled with great care and all unauthorised access should be restricted.