1.

1 INTRODUCTION

This section describes the purpose of this software requirement

specification(SRS) , scope of the software system which is to be
developed , overview of the SRS , definitions,Acronyms and
Abbreviations used in SRS , and references.

1.1 DOCUMENT PURPOSE

 The purpose of this Software Requirement Specification(SRS) is to
provide a complete description and a detailed overview of Office
Management System(OMS) ,its all functionalities ,parameters , goals
and the constraints under which it must be operated.

 This document describes the intended audience of the project and the
user interface , hardware and software requirements. The intended
audience of this document is the client for whom the system is
intended to be developed and also the developer of the system who
will be responsible for the entire development of this system.

 This document will also serve as a reference for the team who will be
responsible for the testing and validation of the system after the
system has been designed.It can also be helpful for the maintainers to
have a reference about the actual requirements of the software.

 This document defines how client , team and audience see the product
and its functionality.Ultimately, it establishes the basis for agreement
between the client and the supplier on what the software product will
do.
1.2 SCOPE OF PROJECT
 This project entitled “Intranet based Office Management System” is going to
be designed towards improving the Management of Employee Information
in the field office.

 It is a LAN based application; it will be accessed simultaneously by various

employees as well as by administrator from field office.

 The project is intended for managing all the Employees data , monitoring
the empoyee’s task ,monitoring the employee payroll process, analyze and
improve all the related activities, managing the leave records of
employee,managing Seniority of employee, assigning the day to day
task to employees and other basic information of employees i.e. Employee
Data Management(EDM) .

 Various Management Information System(MIS) reports can be generated

through viz. Leave Report , Seniority List , CR Status , Salary Sleep etc.

 The Administrator of Field office are supposed to enter information of

Employee. This information is compiled and used by Admin for MIS
purposes.

 The most advantageous feature is, all the activities and their respective
summary reports are management informative for decision-making,
paperless and with least effort.

 The main purpose of the project is to develop an Employee Task

Management module, so that all communication can occurs with all
employees of organization.

 With an employee management system in place, there is better management of HR operations,

and available resources are better utilized.
  This is a web-based systems where there is easy storage and retrieval of data, including
employee details, payroll information, detailed job descriptions, employment laws, and paid
time off tracking. These applications also store information like company handbooks,
enrollment data, and emergency contact details.

 Paperwork is minimized and administrative responsibilities become streamlined.

 This project allows :

 Employee Monitoring
 Time Sheet Management
 Employee Data consolidation
 Employee Data Analysis
 Detailed Analysis and Reporting
 Centralized Employee Database

 Time sheets are created for each employee with an hour- wise break up of work. These time
sheets can be locally accessed by the employees and submitted by them online to the
supervisors. Separate attendance sheets can also be created for internal company events.
 Employee time tracking is one of the features of employee management software. It saves
on time and money, and is especially useful in cases of project performance evaluation.
 Each member has access to data based on his privileges.
 Being the LAN based application has the advantage of remote access for employees.
 There are various sections of data and the access granting authority is provided to the
central administrator.
 Employee expenses can also be handles through the application. Expense reports and
reimbursement status can be entered in to the system. Any other financial information of
the employee is also stored here, this includes loans, allowances etc.
 The specialty of employee management software is that it can make to keep note and track
of your company's workforce .

 You can easily have track of your company's employees and manage their workings.
 The usage of employee management system would ultimately reduce the overall
management costs thus ensuring greater profits and reduced burdens.

This software

manages employee time sheets, as well as the record of each employee having a role in the project
development. It provides in-depth information like time devoted by each employee to a project, work
output, their performance, and their management skills. The promotion of employees is dependant on
their work performance and output. This can be calculated effectively with employee management
software.

  Monitor employee times more efficiently

  Provide employees with a better way of tracking vacation, sick days and any time off
 Eliminate time fraud...saving the company money
 Speed up and make easier the payroll process
 Get accurate and professional time sheet reports from employees

 Send messages to other employees (meetings, company policies, personal messages,

etc.)

 Access the IN/OUT screen and view employees that are in or out of the office(Employee
attendnce)
 Make time-off requests (vacation), on-line and wait for supervisor approval (Demanding for leave)
 News and Events
 Allow employees access only to the areas designated by their supervisor (Limited Access Work)
 Access professional reports, including:
1. Daily Times
2. Monthly Times
3. Time Off
4. Access Rights
5. In/Out List
6. Vacation Requests
7. Job Postings
8. Employee Bulletin
9. And More
 With the Employee Data Management System you can take control of your Human Resources
and personnel management.

1.3 DEFINITIONS, ACRONYMS & ABBREVIATIONS

 Table 1 gives explanation of the most commonly used terms in this SRS
document.
Table 1 : Definition for most commonly used terms

TERM DEFINITION

 Table 2 gives Full Forms of the most commonly used acronyms in this
SRS document.

Table 2 : Full Forms for most commonly used acronyms

ACRONYM FULL FORM

LAN Local Area Network

SRS Software Requirement Specification
1.4 REFERENCES
 en.wikipidia.org/wiki/software_requirement_specification

 Integrated Approach to Software Engineering

-Pankaj Jalote
  Pressman: Software Engineering, A Practice [Fourth Edition McGraw
Hill Publication]

 http://www.google.com – For finding out the complete IEEE SRS

standard format and specification

 Various SRS Examples

1.6 DEVLOPERS’ RESPONSIBILITIES

The developers are responsible for under given tasks :

 Development of the complete system.

 Deploy the application on the client’s hardware.

 Conducting any user training that might be needed for using the
system.

 Maintaing the system for a period of time after installation.

1.5 DOCUMENT OVERVIEW

 The remaining sections of this document provide a general description,
including characteristics of the users of this project, the product's hardware,
and the functional and data requirements of the product.
 The second section i.e. overall description section ,of this document gives an
overview of the functionality and General description of the project. This
section gives the functional requirements, data requirements and constraints
and assumptions made while designing the multi-utility system. It also gives
the user viewpoint of product use.It describes the informal requirements and
is used to establish a context for the technical requirements specification in
the next section.

 The third Section , Requirements specification section is written primarily

for the developers and it describes in technical terms the specific

requirements of the product and the details of functionality of product.

Section 3.0 also discusses the external interface requirements and gives

detailed description of functional requirements.

 2.0 OVERALL DESCRIPTION
This section describes the general factors that affect the product
and its requirements.Specific requirements are not mentioned ,
but a general overview is presented to make the understanding
of the specific requirements easier.

2.1 PRODUCT PERSPECTIVE

2.2 PRODUCT FUNCTIONS

2.3 USER CHARACTERISTICS

2.3.1 End Users

 No specific knowledge or skills are required from the end user.

 End user should have basic idea about computer operations and
database.

2.3.2 Administrator

 Administrator must be having good knowledge of database

management system.

 Administrator must be capable to manage user rights.

2.4 GENERAL CONSTRAINTS
 If the network connection does not work properly than our system
should not work as intended.

 Also that is assumed that the product is installed properly at web

server.

 This system will not take care of any virus problem, which might occur
either on the client or the server system. Avoiding the use of pirated
software and ensuring that floppies and other removable media are
scanned for viruses before use could minimize the possibility of viral
infection.
 Recovery of data after a system crash will be possible only if backups
are taken at regular intervals.
 Manual interfaces cannot be fully avoided. Documented proofs like
data entry of employees etc. will have to be verified by the concerned
management staff before entering it into the computerized system.

2.5 ASSUMTIONS AND DEPENDANCIES

 It is assumed that the user is familiar with the basic computer
fundamentals.
 Timely backup of data should be taken to avoid data loss in case of
system crash.
 The use of pirated software should be avoided as it may lead to data
loss and system crashes due to viral infections.
  Floppies and other removable media should be scanned for viruses
before use.
 Proper configuration of the client, database server and network is
necessary for the system to function as intended.
 It is assumed that the maintenance of the database will be assigned to
the authorized person only.
 Only authorized persons will be allowed inside the server room.

3.0 SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACE REQUIREMENTS

This subsection specifies all the interactions of the software with
end users , hardware and other software.
3.1.1 User Interface:

 The system will be having user friendly interface.The end user can login to
the system through privileges based login and will be provided with
priveledges based menu through which they can access the system.

 User will have to select the options form the given menu.

 The system will be entering the information into the database to generate
reports.

 The forms will be designed to enter the data.

 Buttons will be used to insert, retrieve or modify the data.

 Links will be provided to shift from one form to another.

 3.1.2 Hardware Interface:

3.1.2.1 Server Side

1Processor Pentium IV or Higher
RAM 512 MB or Higher
HDD 80 GB or Higher
Cache 1 MB or Higher
Monitor 14” Monitor with
256+ Colours

3.1.2.2 Client Side

Pentium IV
Processor
or Higher
RAM 256 MB or Higher
HDD 80 GB or Higher
Cache 1 MB or Higher
Monitor 14” Monitor with 256+Colors
Connection Intranet , LAN

3.1.3 Software Interfaces

3.1.4.1 Server Side:

 Operating System :
 Windows 98/2000/XP/NT/Vista flavours/Window 7 or
any O.S. that supports Visual Studio .NET 2005

 ASP.NET 2.0
 C#.NET

3.1.4.2 Client Side

 Operating System:
Windows 98/2000/XP/NT/Vista/Window 7 or any O.S.
with browser.

 Browser:
Internet Explorer, Netscape Navigator, Mozilla

3.1.4 Communication Interfaces

 LAN connection