Software Requirements

Specifications For
Salary Management System
(SMS)

Version 0.3

Prepared by:
 Omar Ahmed Alaa
 Omar Gamal Awd
 Mohamed Abd El Hady Fathy
Table of Contents
List of Figures................................................................................Error! Bookmark not defined.
1. Preface....................................................................................Error! Bookmark not defined.
1.1 Document Purpose..........................................................Error! Bookmark not defined.
1.2 Target Users.....................................................................Error! Bookmark not defined.
1.3 Revision History..............................................................Error! Bookmark not defined.
2. Introduction............................................................................Error! Bookmark not defined.
2.1 Purpose............................................................................Error! Bookmark not defined.
2.2 Scope...............................................................................Error! Bookmark not defined.
2.3 Overview.........................................................................Error! Bookmark not defined.
3. Glossary.................................................................................Error! Bookmark not defined.
3.1 Acronyms, definitions, and abbreviations.......................Error! Bookmark not defined.
4. System Users..........................................................................Error! Bookmark not defined.
4.1 System stakeholders........................................................Error! Bookmark not defined.
4.2 Users objectives...............................................................Error! Bookmark not defined.
5. User Requirements definitions...............................................Error! Bookmark not defined.
5.1 System Function..............................................................Error! Bookmark not defined.
5.2 Constraints.......................................................................Error! Bookmark not defined.
6. System Architecture...............................................................Error! Bookmark not defined.
7. System Functional requirements............................................Error! Bookmark not defined.
7.1 Add a new employee
7.2 Edit employee information..............................................Error! Bookmark not defined.
7.3 View employee information............................................Error! Bookmark not defined.
7.4 Track attendance
7.5 Calculate Salary
7.6 Generate Salary Report
7.7 Generate Taxes Report
7.8 Remove Employee
8. Interface requirements............................................................Error! Bookmark not defined.
8.1 User interfaces:................................................................Error! Bookmark not defined.
8.2 Software Interfaces..........................................................Error! Bookmark not defined.
9. Non-functional requirements.................................................Error! Bookmark not defined.
9.1 Preformance:...................................................................Error! Bookmark not defined.
9.2 Avalibality:......................................................................Error! Bookmark not defined.
9.3 Security:...........................................................................Error! Bookmark not defined.
9.4 Realiblity:........................................................................Error! Bookmark not defined.
10. System Models and Diagrams.............................................Error! Bookmark not defined.
11. System Evolution................................................................Error! Bookmark not defined.
12. Time Plan............................................................................Error! Bookmark not defined.
12.1 Work Breakdown Structure.........................................Error! Bookmark not defined.
12.2 Gantt chart...................................................................Error! Bookmark not defined.

1. Preface
1.1 Document Purpose
The purpose of this document is to give a detailed description of the
requirements for the “Salary Management System” (SMS) software.
This document will explain the purpose and features of the system, the
interfaces of the system, what the system will do, the constraints under
which it must operate and its interaction with other systems.

1.2 Target Users

Specify the Requirements and read

them to check that they meet their
System
needs. Customers specify changes
Customers to the requirements.

Use the requirements document to

Managers plan a bid for the system and to plan
the system development process.
 Use the requirements to understand
System Engineers what system is to be developed.

System Test Use the requirements to develop

Engineers validation tests for the system.

System Use the requirements to understand

Maintenance the system and relation between its
Engineers parts.

1.3 Revision History

Name Date Description Version
Mohamed 7/12/2018 Initial 0.1
Abd El Hady
Omar Ahmed 14/12/2018 Update 0.2
Omar Gamal 18/12/2018 Final Update 0.3

2. Introduction
2.1 Purpose
The purpose of this software is to automate the salary system, the system
will do the following:
  Access the employee’s information
 Manage the attendance of the employee’s
 Manage the employee’s salary
 Generating reports monthly
 Keep track of all the employee’s payments and if they received it or
not
 Taxes computing
 Store employee’s data and information

2.2 Scope
SMS is a software for managing salary for employee’s, it will make
everything easier on computer than using a whole bunch of papers so the
staff who are working in the salary management department will manage the
salaries easily through the system, the system can work on multiple pc’s
sharing the same database the system will show the salary of each
employee and add the taxes and bonuses.
Basically, the system is designed to help the staff working in salary
management department to calculate salary of each employee, add or
remove employee from the system and generate complete reports about the
employee’s salary monthly.
It will consist of 3 things mainly:
1. Employee Management.
2. Salary Management.
3. Generate Reports.

2.3 Overview
The document contains the following:

 First chapter contains an overview description of the system, the

purpose of the document and the target users of the system.
 Second chapter contains an overall description of the system with it is
functions and scope.
 Third chapter contains detailed description of system functional and
non-functional requirements.
 Fourth chapter contains diagrams that will help in understanding the
system.
3. Glossary
3.1 Definitions/acronyms/abbreviations
SMS: Salary Management System
SM: Salary Management Department Employee
HR: Human Resource
DA: Dearness Allowance
HRA: House Rent Allowance
MA: Miscellaneous Allowance

4. System Users
4.1 System stakeholders
System Engineer

 Responsible for requirement gathering

 Responsible for development
 Responsible for deployment and maintenance
Salary Management Department Employee

 Responsible for salary management

 Generate Reports
HR

 View Reports
 Manage Employee:
o Add Employee
o Remove Employee
o Edit Employee data
Manager of The Company

 View Employee’s Data

4.2 Users Objectives

System Engineer
  Gain experience in software development
 Gain experience on working with clients and teamwork

Salary Management Department Employee

 Avoid repeatable work

 Avoid using a lot papers
 Simplification in creating more complete reports
 Avoid employee’s salary problems

HR
 Simplification in managing employee’s data
 Avoid repeatable work
 Avoid using a lot papers

Manager of The Company

 Increase employee’s satisfaction

 Higher quality reports

5. User requirements definition

5.1 System functions
 Add new employee
 Edit employee data
 View employee data
 Remove employee
 Search for employee data by name
 Check for attendance
 Generate report
 Calculate Salary

5.2 Constraints
Company Policies: All Data should be in printable form.
Hardware limitations: Only one fingerprint scanner used.
6. System Architecture

Figure 1: System Architecture

7. System Functional Requirements

7.1 Add new employee
Only HR can add a new employee and that can be done by adding some
information.
 Personal information
- Name, Position, Birthdate, id, Gender.
 Education and certificates;
- Graduation certificate, Academic achievements, Courses and training
certificates.
 Contact information;
- Phone number, E-mail address.
7.2 Edit employee information
- HR can edit the information of any employee.

7.3 View employee information

- SM or HR can view employee information

7.4 Track attendance

- The system will be able to trace the daily attendance of each employee
using fingerprint scanner.

7.5 Calculating salary

- Main function of the system, to complete calculating the salary some data
must be added for each employee.
 Basic salary
- Each employee has a basic salary depends on his position.
 Deductions
- Taxes, Absence, Insurance.
 Allowance
- DA, HRA, MA.
Salary= (Basic salary+ Allowance) – deductions

7.6 Generate salary report

- SM generates salary report at the end of each month for all employees or
specific employee.
- It includes; Employee name, Position, Salary, allowance and deductions

7.7 Generate taxes report

-SM generates taxes report to use it to send it to government if needed.

7.8 Remove employee

- Only HR can remove employee from the system, so this employee no longer
exists in the system.
- Before completely removing an employee the system must check if this
employee gets his salary for the working days.

8. Interface Requirements
8.1 User Interfaces:
:
 Figure 2,3,4: Wireframe

8.2 Hardware Interface:

Will use fingerprint sensor that will interact with the system to check for
attendance

9. Non-Functional Requirements
9.1 Performance
The system should be fast and without any errors.

9.2 Availability
The system should be available during working hours.

9.3 Security
You must login to access the system.

9.4 Reliability
The system is stable and easy to use.

10. System Models and Diagrams

10.1 Context Diagram

 Figure 5: Context Diagram

10.2 Use Case

10.2.1 Use Case Diagram
 Figure 6: Use Case diagram

10.2.2 Use Case Scenario

Use Case Name Add New Employee

Participating Actors: HR

Extends: Manage Employee

Entry Condition: HR selects add new employee

Exit Condition: HR receives a confirmation message that a new employee has been
added to the system, or an error message

Related Add New Employee

Requirements:

Typical flow of For valid data, system adds new employee, stores his data in the
events: database and sends a confirmation message to the user

Exceptions: For invalid data, system sends a failure message to the user which
indicates the invalid data

Use Case Name Calculate Salary

Participating SM
actors:

Entry Condition: SM selects Calculate Salary

Exit Condition: SM receives a confirmation message that salaries have been

calculated and stored in the data base, or an error message.
Related Calculate Salary
Requirements:

Typical flow of System calculates salaries, stores salaries in the database and sends
events: a confirmation message to the user

10.3 UML Class Diagram

 Figure 7: UML Class diagram

10.4 Sequence Diagram

Figure 8: Sequence diagram

11. System Evolution

 The system should be able to work on different operating systems.
 It should work properly on devices with low specifications.
 The outline of the generated reports may be subjected to changes.

12. Time Plan

12.1 Work breakdown structure
 Figure 9: Work breakdown structure

12.2 Gantt chart

Figure 10: Gantt Chart