srs

Manpower Planning - SRS

July 20

2012 Software Requirements specifications for Manpower Planning System to be employed at the organization.

Centre for Development of TelematicsMandi Road, Mehrauli, New Delhi 110030, India

Manpower Planning - SRS2012

Approval Block

Organizational responsibility Name Signature Date

Participation

This document has been created by

2


1 Arushi Paliwal

2 Divyansh Gupta

3 Tripteesh Kaur

Under the guidance of

1 Mr Raj Kumar

2 Mr Nitin Sagar

3


Table of Contents

INTRODUCTION.....................................................................................................................................6

Objective and Background.................................................................................................................6

Scope.................................................................................................................................................6

References.........................................................................................................................................6

Definitions, acronyms and terminology.............................................................................................6

OVERALL DESCRIPTION..........................................................................................................................7

Product Perspective...........................................................................................................................7

Product Functions..............................................................................................................................7

Assumptions and Dependencies........................................................................................................7

SPECIFIC REQUIREMENTS......................................................................................................................9

Division of Users................................................................................................................................9

Description and priority.................................................................................................................9

Functional requirements................................................................................................................9

Display Details..................................................................................................................................10

Description and Priority...............................................................................................................10

Functional requirements..............................................................................................................10

Add Details.......................................................................................................................................11


Functional Requirements.............................................................................................................11

Edit details.......................................................................................................................................11



Mapping...........................................................................................................................................12

Description and priority...............................................................................................................12


Changing password..........................................................................................................................13



EXTERNAL INTERFACES........................................................................................................................14

4


User interfaces.................................................................................................................................14

Hardware Interfaces........................................................................................................................15

Software interfaces..........................................................................................................................15

NON FUNCTIONAL REQUIREMENTS.....................................................................................................17

Performance requirement...............................................................................................................17

Safety requirements.........................................................................................................................17

Software Quality attributes..............................................................................................................17

Objective and Background ................................................................................................................. 5

Scope ................................................................................................................................................. 5

References ......................................................................................................................................... 5

Definitions, acronyms and terminology ............................................................................................. 5

OVERALL DESCRIPTION .......................................................................................................................... 6

Product Perspective ........................................................................................................................... 6

Product Functions .............................................................................................................................. 6

Assumptions and Dependencies ........................................................................................................ 6

SPECIFIC REQUIREMENTS ...................................................................................................................... 8

Division of Users ................................................................................................................................ 8

Description and priority ................................................................................................................. 8

Functional requirements ................................................................................................................ 8

Display Details .................................................................................................................................... 9

Description and Priority ................................................................................................................. 9

Functional requirements ................................................................................................................ 9

Add Details ....................................................................................................................................... 10

Description and Priority ............................................................................................................... 10

Functional Requirements ............................................................................................................. 10

Edit details ....................................................................................................................................... 10


Functional requirements .............................................................................................................. 11

Mapping ........................................................................................................................................... 11

Description and priority ............................................................................................................... 11


Changing password .......................................................................................................................... 12


5



EXTERNAL INTERFACES ........................................................................................................................ 13

User interfaces ................................................................................................................................. 13

Hardware Interfaces ........................................................................................................................ 14

Software interfaces .......................................................................................................................... 14

NON FUNCTIONAL REQUIREMENTS ..................................................................................................... 16

Performance requirement ............................................................................................................... 16

Safety requirements ......................................................................................................................... 16

Software Quality attributes .............................................................................................................. 16

6


INTRODUCTION

Objective and Background

The objective of this document is to list the requirements specifications for the Manpower Planning software system. The functional requirements have been categorized into a set of

features to be provided by Manpower Planning software system.

Scope

The document shall be applicable to the manpower planning Software system.

There are 3 users: Master user, admin, and Reader (employee).

The software incorporates the display of various projects and groups (and their details), skills currently active in the organisation.

It displays the contribution of each group in any project and also the contribution of an employee within the group.

The software allows adding new projects and groups as needed.

There is also a module present: Edit – which allows to delete / modify the project/group/skills details.

References

Definitions, acronyms and terminology

7


OVERALL DESCRIPTION

Product Perspective

The product allows the company officials and employees to view various projects undergoing in the company and various groups also along with the contribution of each employee in his/her respective group.

This will allow the officials to re-allocate manpower i.e. resources from one project/group to another according to their skills if they appear to be present uselessly in the group.

This software helps to efficiently analyze and utilize the manpower.

Product Functions

Manpower planning software system is broadly responsible for the following functions:

Division of users: There must be 3 possible users viz. Master user, Admin (for each group), and reader (employee).

Display details: The software must have a module for displaying details of various designations in company, employees, projects, groups and skills present in the organisation.

Add details: The module must be able to add new entries in all of the aforesaid fields.

Edit details: The module must be able to edit the employee details, projects, groups, skills and designations.

Mapping: The module must be able to map a given group to a given project.

Password Changing: Only the master user has the liberty to change the passwords for various logins.

8


Assumptions and Dependencies

No change is supposed to be done in the hardware of systems in the organization i.e. retained as it is.

9


SPECIFIC REQUIREMENTS

The Manpower Planning software functionality can be divided into following set of requirements:

Division of users

Display Details

Add Details

Edit details

Mapping

Password Changing

NOTE: all the functional requirements marked with a special character ‘*’ are planned for 1st phase of implementation of RTI- Helpdesk subsystem.

Division of Users

Description and priority

This module divides the types of users into 3 categories:

Master user

Admin(for each group)

User Reader(employee)

It is a high priority module.

Functional requirementsFR 1 ‘*’: Master User: The Master user has the liberty to view and edit every single entity present in the software.

10


FR 2 ‘*’: Admin: The Admin has liberty to view and edit only his own group/project details and cannot modify others.

FR 3 ‘*’: User Reader (employee): The reader is any employee who can only view the various details and cannot edit/modify/add anything.

Display Details

Description and Priority

A high priority module visible to all 3 users. It displays various details of projects, groups, skills, employees and designation present in the organisation.

Functional requirements

FR 4 ‘*’: Display Designation Details:It displays all the designations available in the organisation and the corresponding name of the employee.

FR 5 ‘*’: Display Employee details:shows the names of all the employees against their staff number.

FR 6 ‘*’: Display Group Details:Displays the details of all the groups present in

Bangalore

Delhi

It shows the employees in the corresponding group and their contributions in various fields.

FR 7 ‘*’: Display Project Details:Displays the details of all the projects present in

11


Bangalore

Delhi

It shows the groups in the corresponding project and their contributions in various fields.

FR 8 ‘*’: Display skills:It shows the various skills present against their ID’s.

Add Details


The module allows adding new employee/project/group/skill details.A high priority module necessary to update the database. This module can be accessed by Master user and the admin only.

Functional Requirements

FR 9 ‘*’:Add Employee Contribution:Allows to add the contribution of an employee to a given group and a given project where group, project and employee name are all selected from a drop down menu.

FR 10 ‘*’: Add New Designation:Allows to add new designation against the designation ID.

FR 11 ‘*’:Add new employee:this module has entries staff no. , employee name, group name and designation name.

FR 12 ‘*’: Add new group:adds any new group entry(name) and the group ID.

FR 13 ‘*’: Add new project:adds any new project name, project ID and Director name.

12


FR 14 ‘*’: Add new skill:Adds new skill name and skill details.

Edit details


This module allows us to modify the employee details/project/group/skills details. This module can be accessed by master user and the admin only.


FR 15: Edit employee contribution:edits the contribution of an employee in a given group corresponding to a given project.

FR 16: Edit designation details:edits the designation name for corresponding designation Id and sets the flag accordingly.

FR 17:Edit employee details:allows to edit all the details including name, staff no., group name, designation and sets the flag accordingly.

FR 18:Edit group details:Edit the group ID and the Group Name, and the flag.

FR 19:Edits project details:Edit the Project details and the project ID with the flag.

FR 20:Edit skill details:allows to edit the skill detail descriptively corresponding to the skill name.

Mapping

13


Description and priority

It allows various groups to be mapped to their respective projects.Each group can map to different numerous projects.Accessed by master user and the admin.


FR 21 ‘*’:Add mapping:Asks for the project name and the group name for the mapping to be done. The names appear in a drop down menu.

Changing password


This module can be accessed by only Master User. The master user is allowed to view and modify the passwords for all the 3 categories of users.


FR 22 ‘*’:Change Password:Asks for the user category name, current password and the new password. Accessed by master user only.

14


EXTERNAL INTERFACES

User interfaces

The interface between the software product and the master user may appear somewhat as shown:

Login page

15


Home Screen

Add Module

16


Mapping Page

Edit Page

17


Changing Password

18


Hardware Interfaces<Describe the supported device types, nature of data & control interactions between the software and the hardware.>

Software interfaces<Describe the connections between this product and other specific software components (name, version etc.), including databases, operating system, tools, libraries & integrated commercial components. >

19


NON FUNCTIONAL REQUIREMENTS

Performance requirement

It is a soft real time system.

It must perform efficiently, at acceptable speed for all operating systems (windows/ Linux / Mac)

Safety requirements

It must be handled by a single master user, admin,user and must ask for a password every time they log in.

Software Quality attributes

Maintainable and updated regularly.

Efficient and easy to use.

20

srs

Documents

srs 2012software

high priority

master user

14 functional

functional

10 functional

11 functional

12 functional