4 SRS Jalote
4 SRS Jalote
4 SRS Jalote
Requirement
Specification
For
Software
Requirements
Newspaper Agency System
Specification
for
Table of Contents
1. Introduction
1.1
Purpose..
1.2
Scope..
1.4
Reference..
1.5
Overview .
2. Overall Description:
2.1 Product Perspective
2.4
General Constraints .
3. Specific Requirements
3.1
Functional Requirements
3.2
Performance Requirements .
3.3
Design Constraints
4.
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.
3.
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.
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.
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