SOFTWARE REQUIREMENTS SPECIFICATION

(SRS)
FOR
THE SOFTWARE SALES DAY
This Software Requirement Specification is written accordance with the IEEE Standard 830-
1984 model.

INTRODUCTION

This SRS Document contains the complete software requirements for the software Sales Day
and describes the design decisions, architectural design and the detailed design needed to
implement the system. It provides the visibility in the design and provides information needed
for software support.

This is the software which is designed to solve the problems faced by the organization. In this
software the data has been entered in the computerized form of every entry, which will help to
save the organization from facing different problems. A heightened focus on computerization
will affect workers in these sales and related occupations. For example, increased
computerization of product-line information and systems to record transactions will lead to
greater computer use among sales personnel Grocery clerks and store shelf stockers pack
customers' purchases, price items, stock shelves with merchandise and fill mail and telephone
orders and the whole information should be stored in the database.

PURPOSE

The main purpose of this software is to design and implemented a complete computerized system
that fulfils all the requirements of the shop and will provide help to maintain the each and every
record regarding the shop. For the successful database, it is most important that it satisfies the
user requirements. Therefore the user expectations should be clearly displayed.

SCOPE

Since the existing system is completely manual so a computerized system is proposed.

Computerization means to change a manual system to a computer system. Sales day is the
process of exploring, acquiring and reifying user requirements through discussion with the
problem owners, observation of the existing system, task analysis and so on.
The software Sales day of the store will remove the above mentioned errors and will provide
help to the whole staff in managing information of their products in a better way. Due to this
software Sales day one can ask queries and can enter data easily in the forms.

1
GENERAL DESCRIPTION
PRODUCT PERSPECTIVE
Product Functions
The software Sales day will meet the objectives, especially to enhance the efficiency of the
system. For this now the best system is to computerize the system.
• Wide range of Data: -
The proposed system will provide the capability of entering a wide range of data.
• Easy assessment of reports: -
The proposed system will provide the easy assessment of reports.
• Security provide: -
The proposed system will provide security.
• Help in Calculation: -
The proposed system will provide the help in calculation (calculating mark-up).

User Characteristics

The users of the system are customers, employee and the administrators who maintain the
system. The users are assumed to have basic knowledge of the computers. The administrators of
the system to have more knowledge of the internals of the system and is able to rectify the small
problems that may arise due to disk crashes, power failures and other catastrophes to maintain
the system. The proper user interface, users manual, guide to install and maintain the system
must be sufficient to educate the users on how to use the system without any problems.

General Constraints

The information of all the users must be stored in a database that is accessible by the sales day.

Assumptions and Dependencies

The users have sufficient knowledge of computers.

The users know the English language, as the user interface will be provided in English
The product can access the customer database.

INFORMATION DESCRIPTION
This section provides a detailed description of the problem that the software must solve
.Information content flow and structure is documented.

USER INTERFACES

All pages of the system are following a consistent theme and clear structure. The occurrence of
errors should be minimized through the use of checkboxes, radio buttons and scroll down in
order to reduce the amount of text input from user.

2
HARDWARE REQUIREMENTS:

i. Computers:

• Required Pcs:
Our requirements of Pcs are recent Pentium and the number of computers are around 70.Each
pc consist of monitor, CPU, keyboard, mouse.
• Cost Of Pcs:
Each pc cost round about 45,000-50,000. From this we can illustrate 4 pcs cost range will be
from 500,000 to 750,000.
ii. Equipments:

• revolving chairs
• lights
• fans
• air conditioners
• generators
• underground wiring encapsulated wire system

SOFTWARE REQUIREMENTS:

i. Microsoft Office:
Microsoft Access is used to form our data base of employees, customer, owners etc. Microsoft
word is used to write instruction and guidelines pages. By and large we need this software for
customers as ell as for our project management.

ii. Antivirus:
Proper antivirus should be installed on every computer.
Training:
The following are the most important Essential Skills for this trade:

• Oral Communication
• Job Task Planning

The employees should be trained either by their co-workers, lectures or by workshop.

3
FUNCTIONAL DESCRIPTION

This section describes in detail all the functional requirements.

FUNCTIONALITY

Logon Capabilities
The system shall provide the users with logon capabilities.
Alerts
The system can alert the administrator in case of any problems.
Usability
• Since all users are familiar with the general usage of Microsoft Access, no specific
training is required.
• The system is user friendly and self-explanatory.

RELIABILITY
The system has to be very reliable due to the importance of data and the damages incorrect or
incomplete data can do.
Availability
The system is available 100% for the user and is used 24 hrs a day and 365 days a year.
The system shall be operational 24 hours a day and 7 days a week.
Mean Time Between Failures (MTBF)
The system will be developed in such a way that it may fail once in a year.
Mean Time to Repair (MTTR)
Even if the system fails, the system will be recovered back up within an hour or less.
Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the employees of
the shop and users of the shop use the system.
Maximum Bugs or Defect Rate
Not specified.
Access Reliability
The system shall provide 100% access reliability.

4
 PERFORMANCE
Response Time
Every user receieve an average response time not exceeding 3 sec.The system shall be
allowed to take more time when doing large processing jobs.
Administrator Response
The system shall take as less time as possible to provide service to the administrator .
Throughput
The number of transactions is directly dependent on the number of users, the users may be
the administrator, employees of the shop and also customer.
Capacity
The system is capable of handling 10 users at a time.
Resource Utilization
The resources are modified according the user requirements and also according to the
database administrator requirement .

DESIGN CONSTRAINTS
Development Tools
Will make use of the available Microsoft Office .In this we will specially use Microsoft
Access to maintain the database.

BEHAVIORAL DESCRIPTION
Operation as a result of external events and internal conditions
• System States
• Events and Actions

VALIDATION CRITERIA
A Software Testing Plan (STP) will be created to define a set of qualification methods and to
specify for each requirement in this document a method of ensuring that the requirement is
satisfied . How do we recognize a successful implementation? What classes of tests must be
conducted to validate function, performance and constraints?
• Performance bounds
• Classes of tests
• Test to be performed and expected software response
• Special considerations