Software

Requirement
Specification
For

News Paper Agency

Prepared byVIJAY CHAUDHARI (216CS3173)

Software Engineering lab

10/08/2016

Software
Requirements
Newspaper Agency System

Specification

for

Table of Contents
1. Introduction
1.1

Purpose..

1.2

Scope..

1.3 Definitions, Acronyms, and Abbreviations

1.4

Reference..

1.5

Overview .

2. Overall Description:
2.1 Product Perspective

2.2 Product Functions

...
2.3 User Characteristics

2.4

General Constraints .

3. Specific Requirements
3.1

Functional Requirements

3.2

Performance Requirements .

3.3

Design Constraints

4.

External Interface Requirements .........................................................

4.1
User
Interfaces.......................................................................................
4.2 Hardware Interfaces ............................................................................
4.3 Software Interfaces ..............................................................................
4.4 Communications Interfaces .................................................................
5. Appendix

Software Requirement Specification (SRS) for

Newspaper Agency System
(NPAS)
1. Introduction
1.1
Purpose:
Newspaper Agency (NPAS) is intended to help the user keep
information about his client newspaper and magazines subscription,
billing & distributor information.
This document is meant to delineate the features of NPAS, 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.
1.2
Scope:
We describe what features are in the scope of the software and
what are not in the scope of the software to be developed.
In Scope:
a. Managing subscription of user, which would include maintaining
papers and magazines information and will be able to modify his
subscription.
b. User will be able to see and print his bill and can pay the bill
online.
c. It will be able to send a message to users after the end of his
subscription.
d. Agency can see all information about users and also distributors.
e. User authentication will also be involved in this process.
Out of Scope:

a. Features for actual purchasing and selling of securities. That is,

actually buying and selling of shares/securities is done outside
PIMS.
b. Tax computations for gains/losses.
c. Any market related prediction.
1.3

Definitions, Acronyms, and Abbreviations:

Acronyms and Abbreviations:

a. NPAS: Newspaper Agency System.
b. SRS: Software Requirements Specification.
c. WWW: World Wide Web.
d. GUI: Graphical User Interface.
e. ROI: Rate of Investment.

Definitions:
a. SUBSCRIBE: It contain all the names of papers and magazines,
which user wants to be delivered to his house and already being
delivered.
b. BILL: The sum total of all the Paper and Magazines values, which
he received in the corresponding month included pending
payments.
c. ROI: The interest that user gets on a particular investment. In
NPAS, in the context of delivering the publication:
1.4
References:
Appendix A: Formula for ROI calculation for shares.

1.5
Overview:
The rest of this SRS is organized as follows: Section 2 gives an
overall description of the software. It gives what level of proficiency
is expected of the user, some general constraints while making the
software and some assumptions and dependencies that are
assumed. Section 3 gives specific requirements which the software
is expected to deliver. Functional requirements are given by various
use cases. Some performance requirements and design constraints
are also given. Section 4 gives some possible future extensions of
the system. Finally the appendices in Section 5 describe
respectively the formula for ROI calculation for shares and user
screen.
2. Overall Description:

2.1
Product Perspective:
NPAS is aimed toward the persons who sells the newspaper and
magazines.
It helps the Agency to keep all the records related to his customer
like customer name, address, subscription and bill along with that it
helps the manager to maintain the records related to all distributors
also. NAPS should be user-friendly, quick to learn and reliable
software for the above purpose.
NPAS is intended to be a stand-alone product and should not
depend on the availability of other software. It should run on both
UNIX and Windows based platform.

2.2
User Characteristics:
a. The user should be familiar with the term subscription.
b. The user should know about the details of paper and magazines.
2.3

Principal Actors:
The two principal actors in NPAS are user and system.

2.4

General Constraints:
a. For full working NAPS user you need internet connection.
b. NAPS is single-user software.

3 Specific Requirements:
3.1 Functional Requirements:
We describe the functional requirements by giving various use
cases.

Use cases related to system authorization:

Use Case 1: Login
Introduction:
User has to sign up first.
Input:
1.
Start the application. User prompted for login and
password.
2.
User gives the login and password.
5

3.

It also provides the functionality to user to change their

passwords.
Processing:
Processing will check for the unique name and password
authentication filled by the user.
Output:
Account created successfully.
Alternative:
Username already taken or password do not match. Enter again.

Use cases related to

subscription:
Use Case 2: Create subscription package:
Introduction:
This feature allows the user to choose the appropriate
subscription and
customize the subscription.
Input:
1. Choose the magazines and newspapers whatever he likes.
2. User can also modify his subscription.
3. One extra functionality has been added a remainder message,
Which will be able to send a subscription ending
message to
Automatically.
Processing:
System will check the authentication of subscription.
Output:
User subscription has been created successfully.
Alternative:
If some authenticity found by the system during
processing than ask the user to subscribe again.

Use Case 3: customer information:

Introduction:
In this phase we have to take all the important
information regarding the user.
Input:
1.
System ask the user about customer name, address
(permanent and correspondence).

2.
System ask the user about unique id information,
mobile no.
3.
Other personal information like email etc.
Processing:
System will check all the related information has been
entered by the customer in the right format.
Output:
Customer information has been updated successfully.
Alternate Scenario:
1. The user id should be unique & email also should be
unique
Otherwise Ask the user to enter different id and email.

Use cases related to manager:

Use Case 4: Manager information
Introduction:
In this phase we have to take all the important
information regarding the manager.
Input:
1. Ask the manager to enter Manager id, name, address.
2. Manager email-id, phone-no
Processing:
System will check all the related information has been entered by
the manager in the right format.
Output:
Manager information update successfully.
Alternative:
if system found some error than prompt the manager again on
details page and ask him to enter his details again.

Use cases related to Distributor:

Use Case 5: Distributor information
Introduction:
In this user case, we will take all the info related to
distributor and information related to his delivery area and all the
house no in which he
Provides his service.

Input:
1.
no.
2.

Distributor information regarding name, address, phoneInformation regarding Delivery area, no of houses.

Processing:
System will check if the information entered by the
distributor are valid
or not. In processing system will check info
related to unique id of the distributor and his delivery area (should
not be match with the others).

Output:
Distributor information has been updated successfully.

Alternative: If system will found errors, ask the distributor to

enter the details
Again.

Use Case 6: BILL:

Use Case 6: Bill information
Information:
This use case provides the information about the Bill of current
month
And all the remaining month.
It also provides us the functionality to pay the payment.
Input:
1. User/manager can check the dues details.
2. Functionality for payment through check/cash/online.
3. Check the status
Output:
User will be able to print the receipt of the paid bill.

3.2 Performance Requirements:

(a) Should run on 500 Mb, 64/32 Bit machine.
(b) 90% of the responses should be within 2 second, except for
downloading current prices for which more time is acceptable.
(c) Pentium iv with 1GB ram with at least 2GB memory
3.3 Design Constraints:
1. Security: The files in which the information regarding Fault
Tolerance: Data should not become corrupted in case of system
crash or power failure.
4. Future Extensions:
a. NAPS is intended to be a single user software. A possible future
extension would be to make it multi user.

4. External Interface Requirements

4.1 Interfaces
4.1.1 User Interfaces
The interface of the software will provide options for relatively easy data input processes
text-boxes that will be properly labeled. It will also have a user friendly view of the whole
system with simple and easy understanding of action driven processes as command
buttons are functionally labeled.
With all these target users of the software will relatively find it not difficult to use.
4.1.2 Hardware Interfaces
A network of four Pentium- III workstations, with a 4 GB RAM, serves as the cluster,
with the Linux operating system or windows operating system. For better performance
analysis, a larger number of dedicated workstations would be beneficial.500 GB of
memory.
4.1.3 Software Interfaces
It is a web based system, so it need internet connection. How-ever the system requires
minimum specifications for software interfaces to be able to use it efficiently. The
operating system required in order to use the system is at minimum Windows XP, but it
may also be Windows Vista or Windows 7, Net-beans or eclipse ide, SQL star plus server.
4.1.4
Communications
Interfaces:
communication is needed as it is a web
based system.

5.

Appendix A:
The formula for calculation of ROI for

banks:
For a banks the ROI is constant, namely the interest rate of
that bank.

S.I = P*R*T/100
P = PRINCIPLE
T = TIME
R = RATE
S.I = SIMPLE INTEREST

10