1

1. Introduction

1.1 Purpose:
Sales Analyzer & Projector is intended at enabling sales persons todetermine the
extent to which a sales Iorce has met its sales objectives within the speciIied
time Irame. This soItware can be eIIiciently used as a sales management tool
in various sales-oriented Iorum.
This document is meant to delineate the Ieatures oI SAP, so as to serve as a
guide to the developers on one hand and a soItware validation document Ior
the prospective client on the other.

1.2 Scope:
e describe what Ieatures are in the scope oI the soItware and what are not in
the scope oI the soItware to be developed.

IN SCOPE:

a. &ser Authentication.
b. Managing sales oI a product in a sales Iorum which would include
maintaining the inIormation oI the product, adding new product and
viewing updates oI the particular product.
c. Managing the details oI the customers buying the products.
d. Computation oI Total Expenditure and Net ProIit earned through the sales
oI a particular product in a month.
e. &pdating the data oI the products in the database.

OUT OF SCOPE:

a. isplaying graphical representation oI sales made by any customer.

1.3 Glossary (Acronyms, abbreviations):

Acronyms and Abbreviations.
a. SAP: Sales Analyzer and Projector.
b. SRS: SoItware Requirement SpeciIication.
c. : orld ide eb.

1.4 Overview:
The rest oI this SRS is organized as Iollows: Section 2 gives an overall
description oI the soItware. It gives what level oI proIiciency is expected Irom
the user, some general constraints while making the soItware and some
assumptions and dependencies that are assumed. Section 3 gives speciIic
requirements which the soItware is expected to deliver. Functional
requirements are given by various use cases.




2

2. Overall Description:

2.1 Product Perspective: SAP is aimed towards providing aid to the sales Iorum
which has considerable amount oI sales oI a product, and so needs soItware
assistance Ior book-keeping and computations regarding the sales made. SAP
should be user-Iriendly, quick to learn and reliable soItware Ior the above
purpose.
SAP is intended to be a stand-alone product and should not depend on the
availability oI other soItware.

2.2 Functional Requirement Specifications:
SAP should support the Iollowing use cases:

S.No Class of use cases Use Cases Description of use
cases
1. &se cases related to
system authorization
Login Login into SAP
Change Password Change SAP password
2. &se cases related to
InIormation display
isplay items isplay inIormation
about the given items
isplay customers isplay inIormation oI
all the customers
isplay Sales
employee
isplay inIormation oI
all the sales employees
3. &se cases related to
transactions
Add Transactions Add Transactions to
the database
Edit Transactions &pdate into and edit
the existing
transactions
elete Transactions elete existing
transactions
4. &se cases related to
computations
Compute Total
Expenditure
Compute Total
Expenditure oI the
given item
Compute net proIit Compute Net ProIit
earned in the given
month
5. &se cases related to
items prices
Get the current item
price
&pdate the item price
Irom the sales manager
Edit the price Edit the price oI item
already present in the
list

2.3 User Characteristics:

a. The manager should be Iamiliar with the sales management related
terminology like Security/Transactions.
b. The manager should know the details oI a transaction.

3


2.4 Principal Actors:

The two principal actors in SAP are 'manager and 'system.

3. Specific Requirements:

3.1 Functional Requirements:
e describe the Iunctional requirements by giving various use cases:

Use case related to the System Authorization:

Use Case 1: Login
!rimary Actor. Sales Manager
Main Scenario.
1. Start the application. Manger prompted Ior login and password.
2. Manager gives the login and password.
3. System does authentication.
4. Main screen is displayed.

Alternative Scenario.
4(a). Authorization Iails
4(a)1. Prompt the user that he typed the wrong password.
4(a)2. Allow him to re-enter the password. Give him 3 chances.





Provide login
Provide password


II Iails, re-enter again

Sales Manager
SYSTEM AUTHORIZATION

Use Case 2: Change Password

!rimary Actor. Manager
Main Scenario.
1. &ser initiates the password change command.
2. &ser is prompted Ior old password, new password and conIirm new password.
3. &ser gives the old password, new password and conIirm new password.
@,
4

4. System does authentication
5. New password is registered with the system.

Alternative Scenario.
4(a). Authorization Iails
4(a)1. Prompt the user that he typed the wrong password.
4(a)2. Allow him to re-enter the password. Give him 3 chances.



ld password

New password

Authenticates him
Sales Manager
Password change command


Use case related to the Information display:

Use Case 1: Create Customers accounts
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'create accounts Iunctionality.
2. System asks Ior the customer`s name.
3. Manager enters the customer`s name.
4. An empty account is created.

Alternative Scenario.
4(a). Customer with the same name exists.
4(a)1. Manager assigns unique codes to every customer.
4(a)2. An empty account is created.




Create account
Empty account created


Assigns unique codes

Sales Manager
Create Customers Account
@,
@,
3


Use Case 2: isplay Customers inIormation
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'customers Iunctionality.
2. InIormation oI all the customers is displayed.
3. System provides the customer code, name, annual total, sales amount.


Alternative Scenario.
4(a). Customer whose name supposed to be displayed does not exist.
4(a)1. isplaying Iails, the error message is displayed.



Customer`s account

isplays name, code, total amt, sales amt.

II not exist, error message displayed

Sales Manager
Displays Customer`s Details


Use Case 3: Create Items account
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'create items accounts Iunctionality.
2. System asks Ior the items name.
3. Manager enters the items name.
4. An empty account is created.
Alternative Scenario.
4(a). Item with the same name exists.
4(a)1. Manager enters the quantity, unique item no, item description.
4(a)2. An empty account is created.


Create account
Empty account created


Enter quantity, item no, description
Sales Manager Create Item`s Accounts
@,
@,
6



Use Case 4: isplay Items inIormation
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'items Iunctionality.
2. InIormation oI all the items is displayed.
3. System provides the quantity, unique item no, item description, total
sale

Alternative Scenario.
4(a). Item whose name supposed to be displayed does not exist.
4(a)1. isplaying Iails, the error message is displayed.


Item`s inIormation

isplays quantity, unique item no, total sale

II not exist, error message displayed

Sales Manager Displays Item Details


Use Case 5: Create Sales employees account
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'create employees accounts Iunctionality.
2. System asks Ior the employee name.
3. Manager enters the employee name.
4. An empty account is created.
Alternative Scenario.
4(a). Employee with the same name exists.
4(a)1. Manager enters the unique id code Ior each employee.
4(a)2. An empty account is created.


Create employee`s account
Empty account created


Enter unique id code

Sales Manager
Create employee`s Accounts
@,
@,
7


Use Case 4: isplay employee`s inIormation
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'manager Iunctionality.
2. InIormation oI all the employees is displayed.
3. System provides the unique id code, name, total sale made.

Alternative Scenario.
4(a). Employees whose name supposed to be displayed does not exist.
4(a)1. isplaying Iails, the error message is displayed.



employees inIormation

isplays unique id code, name, total sale made.

II not exist, error message displayed

Sales Manager
Displays Employee`s Details


Use case related to the transactions:

Use Case 1: &pdating by adding new items.
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'add items Iunctionality.
2. System prompts the manager Ior the Iollowing details:-
I. item name,
II. id,
III. quantity.
3. Manager enters all the item`s description
4. The account is updated.

Alternative Scenario.
4(a). Invalid attribute value is entered.
4(a)1. Manager is shown the error message and prompted to enter the
incorrect Iields again.




@,
8



Add new item s
Enters name, id, quantity


II invalid entry, enter it again

Sales Manager
Updating Item`s Account


Use Case 2: &pdating by deleting existing items.
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the 'delete items Iunctionality.
2. Manager enters the item`s description.
3. The details are deleted.


Enter details oI item to be deleted

elete the item



Sales Manager
Deleting Item`s details


Use case related to the computations:

Use Case 1: Compute total expenditure.
!rimary Actor. System
!re Condition. Manager logged in & item id, quantity, expenditure/ pc and
various costs incurred is speciIied .
Main Scenario.
1. System computes total expenditure oI the item.(Appendix A shows the
detailed method Ior computing the total expenditure.)


Use Case 1: Compute Net ProIit earned in a given month..
!rimary Actor. System
!re Condition. Manager logged in & item id, capital, sale is speciIied.

@,
@,
9

Main Scenario.
1. System computes net proIit oI the item.(Appendix A shows the detailed
method Ior computing the net proIit.)


Use case related to the updating the item prices:

Use Case 2: &pdating price oI item by manager
!rimary Actor. Manager
!re Condition. Manager logged in.
Main Scenario.
1. Manager initiates the '&pdating price Iunctionality.
2. Manager enters the item`s description to be updated.
3. The price oI that item is updated depending upon market`s demand.


3.2 Performance Requirements:

(a). Should run on 500 MHz, 64 MB machine.
(b). 90 oI the responses would be within 2 sec.

3.3 Design Constraints:

(a). Security. The Iiles containing the inIormation oI items, customers and employees
should be secured against malicious deIormations.

(b). Fault tolerance. ata should not become corrupted in case oI system crash or power
Iailure.


4. Appendix:

4.1 Appendix A:
Formula for the calculation of total expenditure of items.

Suppose that, given is the item name.
Quantity oI item n
Expenditure/pc m
Total variable and Iixed cost p

Then, TTAL EXPENIT&RE (n*m)p





10


4.2 Appendix B:
Formula for the calculation of Net !rofit of a item in specified month.

Suppose that, given is the item name.
Total capital oI the item r
Sales made oI item s

Then, NET PRFIT earned (s-r)