Software Requirements

Specifications
FOR

HOME APPLIANCE STORE MANAGEMENT

SYSTEM

Version1.0

Prepared by
Ayesha Tariq
&
Hafiz Muhammad Waqas
1st Jan, 2018
 Revision History

Version Description Author Date

First Release/ Ayesha Tariq

1.0 1st Jan, 2018
initial release Hafiz Muhammad Waqas

Second release / Ayesha Tariq

1.1 12th Jan, 2018
Some corrections Hafiz Muhammad Waqas
 HOME APPLIANCE STORE MANAGEMENT SYSTEM (HASMS)

1. Introduction
Our Home Appliance Store Management Systemis a desktop application which will be implemented in
Store, which will help maintaining the records of the Items, Customer’s details, Dealer’s detail, Sale’s
detailetc.

The previous system in use is totally manual and it is hard manage keep track of data and
to perform simple tasks it requires an immense amount of time and energy
The company wants to find a solution to reduce its operating costs. The major goal of the
system is to fulfill the client’s wishes and provide a better working environment for the staff to
work in easy and effective way so they can save time and work in more efficient way

1.1. Purpose
Our Home Appliance Store Management Systemis a desktop application which will
be implemented in Shop which will help maintaining the records of the items, customer’s
details, Dealer’s details etc
The previous system in use is totally manual and it is hard manage keep track of data
and to perform simple tasks it requires an immense amount of time and energy. The
company wants to find a solution to reduce its operating costs. The major goal of the system
is to fulfill the client’s wishes and provide a better working environment for the staff to work
in easy and effective way so they can save time and work in more efficient way

1.2. Scope
The functional scope of the system has the following main features
 To record details of Items
 To record information of the customer
 To record information of the customer selling
 To record information of the customer buying
 Recording the information of Dealers
The System has various modules as:
 Login Management Form
 Item’s Management Form
 Dealer’sManagementForm
 Customer’sManagement Form
 Sale’s Management Form

• Login ManagementModule will provide the access to the system according to the
privileges of the user. This will used to authenticate the user accessing the system
• Item’s Management Module is keeping the record of the new items, sold items,
item’s detail etc. The purpose of this module’s will be to contain the data of the items and
information about the specific item
• Dealer’s Management Module will help to manage Dealer information i.e. adding
new Dealer, updatingDealer&searchingDealer
• Customer’sManagement Module will help to manage Customer information i.e.
adding new Custom, updatingCustomer& searchingCustomer
 Sale’s Management Module will help to manage Sale’s information i.e. adding new
Sale, updating Sale & searching Sale

Term/Abbreviation Definition

HASMS Home Appliance Store Management System

GUI Graphical User Interface

RUP Rational Unified Process

C# Programming language

Visio Designing tool

DEO Data Entry Operator

UML Unified modeling language

1.3 References
Websites:
 www.msdn.microsoft.com
 www.ibm.com

Books:
 Software Requirements - Techniques By Soren Lauesen
 Applying UML and Patterns by Craig Larman 2nd Edition

1.4 Overview
This document contains the requirements of the Home Appliance Store
Management System(HASMS). All the functional Requirements are collected by the
personal visit to the “House Appliance Store”
Manager of the company Mr. Ahmed Ali provided the requirements and functionalities
by himself
1.5 System’s main features
 Login Management
 Item’s Management
 Dealer’s Management
 Customer’s Management
 Sale’s Management

2. Functional Requirements
2.1 Login Management

2.1.1 Process Login

SRS-1 Users can enter the system by entering the username and password

SRS-2 The user name should be Unique

Authentication should be provided and the suitable access of the

SRS-3
system should be given according to privileges
2.2 Item Management

2.2.1. Add New Item

SRS-4 DEO can add a new Item into the system

Item should have following attributes name, model number, color,

SRS-5
price, Company name & quantity

SRS-6 Item’s documents should be proper and legal

SRS-7 System should save this information

2.2.2. Search Item

SRS-8 Administrator and DEO can search for Item information

System should give facility of searching Item information on the

SRS-9
basis of Item model number

SRS-10 System should find the result based on search criteria

SRS-11 System should display search information

2.2.3. Update Item Information

SRS-12 The item to be updated will be searched first

The information of the Item being updated should be according to

SRS-13
the standards/parameters

SRS-14 Administrator should be able to update theItem’s information

SRS-15 System should update this information

2.2.4. Generate Item Reports
System should generate reports of the Item byColor, Model
SRS-16 Number,Price they can be viewed by the Administrator of the
HASMS on runtime

2.3. Dealer Management

2.3.1. Add New Dealer

SRS-17 New Dealer can be added into the system By DEO

Details of the Dealer i-e. Name, CNIC Number, Contact number, and
SRS-18
Company name should be entered

SRS-19 System should save this information

2.3.2. Search an Dealer

SRS-20 The item to be updated will be searched first

System should give facility of searching Dealer information on the

SRS-21
basis of Dealer’s CNIC

SRS-22 Administrator and DEO can search for an Dealer

SRS-23 System should display search information

2.3.3. Update Dealer Information

SRS-24 The updating of the Dealer should be according to his parameters

SRS-25 Administrator should be able to update the Dealer information

 SRS-26 System should update this information

2.3.4. Generate Dealer Report

System should generate reports of theDealerby Name, CNIC

SRS-27 Number, phone number, and Company name. They can be viewed
by the Administrator of the HASMS on runtime

2.4. Customer Management

2.4.1. Add New Customer

SRS-28 New Customer can be added into the system by DEO

Details of the Customer i-e. Name, CNIC Number, phone number

SRS-29
and City

SRS-30 System should save this information

2.4.2. Search Customer

System should give facility of searching Customer information the

SRS-31
basis of Customer CNIC

SRS-32 Administrator and DEO can search for a Customer

SRS-33 System should display search information

2.4.3. Update CustomerInformation

 System should give facility of searching Customer information on
SRS-34
the basis of Customer CNIC

SRS-35 The updating of the Customer should be according to his/her CNIC

SRS-36 Administrator should be able to update the Customer information

SRS-37 System should update this information

2.4.4. Generate Customer Report

System should generate report of the customer by Name, Phone

SRS-38 Number, City and CNIC, they can be viewed by the Administrator of
the HASMS
2.5. Sale Management
2.5.1. Add New Sale
SRS-39 NewSale can be added into the system by DEO

Details of the Sale i-e. ID, Salesman name, Date, Customer CNIC,Item
SRS-40
model number

SRS-41 System should save this information

2.5.2. Search Sale

System should give facility of searching Sale information the basis of

SRS-42
Sale’s ID

SRS-43 Administrator and DEO can search for a Sale

SRS-44 System should display search information

2.5.3. Update Sale Information

System should give facility of searching Sale information on the basis

SRS-45
of Sale’s ID

SRS-46 The updating of the Sale should be according to Sale ID

SRS-47 Administrator should be able to update the Sale information

SRS-48 System should update this information

2.5.4. Generate Sale Report

System should generate report of the Sale by ID, Salesman name,

SRS-49 Date, Customer CNIC, Item model number they can be viewed by
the Administrator of the HASMS
3. Non-Functional Requirements

1. Security
The system requires the users to identify themselves by using login-id and
password. Any user who uses the system shall have a login-id and a password

2. Usability
With proper guidance and use of manual the required training time for a normal
users will not be more than one week

3. Reliability
Availability The system facility will be available to its users for 24 hours

Bugs or defect rate Very little

Our system will generate appropriate exceptions and will
Robustness
handle those exceptions effectively
The system will generate accurate results and will behave
Accuracy
according to the User Requirements
Our system will be according to all the requirements
Correctness collected. All the requirements will be metto the User
Requirements

4. Performance
 The HASMS has a simple GUI, which is self-explanatory and user friendly
 The lists, reports and results generated by the system will not take more than
2-3 sec
 Responses to queries shall take no longer than 4-5 sec to load onto the screen
after the user submits the query
 The HASMS shall display confirmation messages to user within 1-2 sec after the
user submits information to the system. In other words robustness is
maintained
 Resources Required
Hardware Minimum Recommended

Processor 1 Core 2 GHz Dual Core 2+ GHz

RAM 1 GB 2 GB

Hard-drive 20 GB As Required
 Printer - -

5. Design Constraints
RUP will be used for the design purposes and UML will be used for the diagrams
in MS Visio. C# language will be used for the development and for the database side
Microsoft SQL server will be used. So, we must be familiar with these constraints

6. User Help/ manuals

Detailed System manuals are given to the system users and one week training
session will be held to ensure that the users of the system understands the system fully
and can get the maximum benefit from the system

7. External Interface Requirements

7.1. User Interfaces
The user interfaces will be friendly because they will be made after discussion
with the end users. The software will be interactive and self-explanatory

7.2. Hardware Interfaces

The system will interact with the printer if the user wants to print the reports
7.3. Software Interfaces

Software USE Version

Windows Operating System XP,7,8,10

MS Visual Studio (C#) Front End 2010+

MS SQL Server Backend Latest is Better

Microsoft Visio For Modeling 2010+

8. Licensing requirements
This system will be developed according to the business oriented nature of
HASMS, and it is licensed by Home Appliances Store