Resouce management system1

Resource Management System

Software Requirement System


Table of Content :

1 Introduction 1.1 purpose1.2 scope1.3 Definitions, Acronyms, and Abbreviations1.4 Reference1.5 Overview

2 overall Description 2.1 Product perspective2.2 productfunction

2.3 User characteristic2.4 Constraints2.5 Assumptions and Dependencies 2.6 Apportioning of requirement

3 Specification Requirement 3.1 External Interface 3.2 Function3.3 Performance Requirement3.4 Logical Databases requirement 3 . 5 Design Constraints 3.6 Software System Attribute

Revision History:

Version Created by Submitted to Remarks Date

1 Gunikhan sonowal Dr Salman Abdul Moize 30/08/2013

2 Gunikhan sonowal Dr Salman Abdul Moize 2/10/2013



1 INTRODUCTION

The resource management system is the resource of a organization which is used by organization when they needed .This is the initial release of the SRS document. This project can be used by any enterprise for managing their Resource.

1.1 Purpose

This document is aimed at developing an online resource management system and will provide the need of the various Independent Business Units (IBU) of an organization and a basis of validation and verification .

1.2 ScopeThis document required for controlling the authentication mechanization and managing the

resources . Basically RMS have databases where difference user such as normal user , super user and power user manipulate the data. Super user provide authentication mechanization and normal user should login their username and password .

1.3 Definitions, Acronyms, and Abbreviations SRS – Software requirement specifications. ORMS – Online resource management system. IBU – Independent business units. S U – Super User. N U – Normal User. UML – Unified Modeling Language PHP – Hypertext Pre Processor SQL – Structured Query Language DB – Database

1.4 References

An Integrated Approach to software engineering by Pankaj Jalote IEEE std 830 – 1998 : IEEE recommended Practice for software requiremen. Software Technology & Management Lecture by Dr Salman Abdul Moize. W3School for software developing .



1.5 Overview

This document have block diagrams to visualize the solution of difference problem of RMS and specific requirement , interface requirement and constraints will help to developing the software. This document is written in such a way that any user can easily understand and use the RMS .

2. The Overall Description

The overall Description start with a password mechanism to safely accomplish tasks mentioned above.

2.1 Product perspective

Two types of peoples are using RMS. One is Super User and another are Normal Users. There are one authentication page where every normal users have to login to access the resource for difference project . If password accept then they can access the Resource . Super user allocate resource in system for difference project.



2.2Product Function

RMS have some major-function in achieved to requirement task. Normal user after successfully done the authentication page then he have two option one is he can change the password or another one is to access the resource . After he done his task then he should logout his profile. Super user also have some task such as reset the password if someone forget , allocate resource for normal user and change employee name, no etc if required. Power user can view the records of all employee, and he can able to edit the current location, ibu, project code of all employee.

2.3 User Characteristics :



The Super User should expert about the system means he should able maintain the personal database where employee record are stored, allocate or update the resource if required and normal user also have knowledge to authenticated and able to change their password or access the resource .

2.4 Constraints:

2.4.1 Regulatory Policies :

Each Normal Users has a account and authenticated by Super User. He cannot change some field like name, numbers etc.

2.4.2 Hardware Limitation:

Normal user access the system at any inter net browsers and the databases will work on a server the need to be always online.

2.5 Assumptions and dependencies :It is assumed that the project development team has sufficient knowledge to undertake and

complete the project Through RMS is software so it dependencies on Operating system(Linux) and Internet .

2.6 Apportioning of requirements

3 Specific requirements :

The software we use for RMS are php , mysql , html etc . For interfaces we can use html and php use for coding the authentication and mysql use for save database.



3.1 External Interfaces

Main page : All the user see same interfaces when they open the RMS where normal user have to write his user name and password .

After successfully login this authentication page then it will ask whether you want to change your password or not.



If press yes then it appear password change page.

If no then it will appear final page where you can access resource and after you successfully access resource then you have to log out .



3.2 FunctionRMS provide various fundamental action that may took place in the project

3.2.1 Use case diagram

Login :

Actor Normal user , Super user

Precondition Normal user enters user name and password

Normal flow Verify the password in login page, if yes login successful otherwise A-1

Alternative flow A-1 : if no then enter again password or A-2A-2 : if three times entered wrong password block his account until super user reset his password or A-3A-3 : if normal user belong to his company reset his password otherwise terminate.

Postcondition Login successfully done and he can change his password.

Other Log out and terminate

Edit employee :



Actor Super user

Precondition Super user enter the employee id

Normal flow Verify the id if yes then he can edit his profile as required otherwise A-2

Alternative flow A-2 : invalid employee id and terminate

Postcondition Edit successful

Other termina

Actor Super user

Precondition Super user enter employee id

Normal flow Verify the employee id If yes he can edit the profile of employee otherwise A-1

Alternative flow A-1 : invalid id and terminate

Postcondition Edit successfully done

Access resource :

Actor Normal user



Precondition The normal user should successfully login

Normal flow Verify the availability if yes access the resource otherwise A-1

Alternative flow A-1 : Ask Super user to allocate the resource for project

Postcondition Access successfully

Normal flow Ask for log out if yes terminate otherwise A-2

Alternative flow A-2 : go to access interface

Other Terminate

Allocate resource :

Actor Super userPrecondition Super user open the resource storeNormal flow Verify the availability for project if yes

then he allocate the resource otherwise A-1

Alternative flow A-1 : ask for otherPostcondition Successfully allocated Normal flow check for other project if yes then allocate

the resource other wise A-2Alternative flow A-2: terminate

Edit project :



Actor Power user

precondition Employee should belong to at least one project

Normal flow Verify the project if yes edit the project of all employee otherwise A-1

Alternative flow A-1 remain same

Postcondition verified successfully

View record :

Actor Power user

Precondition Power user enter the employee id

Normal flow Verify the employee id if yes he can view all record of all employee otherwise A-1

Alternative flow

A-1 invalid id goto employee profile

Postcondition View record successfully



3.2.2 Activity diagram

Activity diagram provide how each function done sequentially with help of activities. Login :

Edit employee profile:



Access resource :

Allocate resource :



Edit project :

View record :



3.3 Performance Requirement :

There are no restriction for normal user to access the resource and the power user to add new employee .

3.4 Logical Db Requirement

3.4.1 Sequence Diagram :

Login :



Edit employee profile :

Access resource :



Allocate resource :

edit project :



3.5Design constraints:

3.6 Software system attribute:

Reliability RMS The system should be able to work as needed without worry of it breaking such aspects include accuracy, and recoverability.

Availability This software is available for all employee who include the organization . Normal user can access the resource for 24 hours per day.

Security Highly protected. Password is provided .

Maintainability The system must be easily maintainable by the users so changes made in the real system that will affect the application can easily be changed in the application to match.

Portability It works in any environment . There no restriction foraccess resource .

Usability To ensure that the system can be used by users with little knowledge of computers and can be trained easily to use the system.

Testability The system should be easy to test to see if there are any problems with it. And if a problem is found it must be easy to narrow down where the problem.



THANK YOU


Resouce management system1

Education

Transcript of Resouce management system1