Shift Scheduling

8/18/2019 Shift Scheduling

1/24

Shift Scheduler

Software Design Specication

Draft Version 1.0

Prof. Akila Victor

Page 1 of 24


2/24

Contents

1. Introduction.........................................................................................................4

2. Purpose...............................................................................................................4

3. Scope...................................................................................................................4

4. Denitions, cron!"s and ##re$iations............................................................4

%. &eferences...........................................................................................................%

'. ($erall Description..............................................................................................%

). *+ternal Interface &euire"ents.........................................................................)

-. unctional &euire"ents.....................................................................................-

/. on unctional &euire"ents............................................................................11

/.1 sa#ilit!.......................................................................................................11

/.2 Securit!........................................................................................................11

/.3 Perfor"ance.................................................................................................12

/.4 apacit!.......................................................................................................12

/.% &eco$er!......................................................................................................12

/.' $aila#ilit!...................................................................................................13

/.) &elia#ilit!.....................................................................................................13

/.- aintaina#ilit!.............................................................................................13

/./ Porta#ilit!.....................................................................................................13

/.10 Pri$ac!......................................................................................................... 13

10. Process odel

. 22

Page 2 of 24


3/24

Revision History

Name Date Reason For Changes Version

dit!a &ola 0)50351

'

irst docu"entation of the S&S docu"ent

for Shift Scheduler

Version 1.0

Page of 24


4/24

1. !ntro"#ction

Shift Scheduler is a shift "anage"ent s!ste" for "aintaining and "anaging the

schedules and related details a#out the e"plo!ees wor6ing on di7erent pro8ects

and in di7erent shifts. 9he calculation and "aintenance of co"prehensi$e shift:

related allowances of the e"plo!ees can #e done s!ste"aticall!. 9he Pro8ect

in$ol$es a transfor"ation of current platfor" dependent s!ste" to a ;e# ena#led

s!ste" with increased eation?s goals into consideration at di7erent ti"e schedules that can #e

"onthl!, wee6l! or uarterl!. oreo$er, it is an i"portant co"ponent of pro8ect

wor6force "anage"ent.

2. P#r$ose

9he purpose of this Software &euire"ents Specication @S&SA docu"ent is to

descri#e the o$erall #eha$ior of Shift Scheduler. 9his S&S denes and descri#es

the operations, perfor"ance, and ualit! assurance reuire"ents of the ShiftScheduler that is to #e de$eloped. 9his docu"ent also descri#es the nonfunctional

reuire"ents. It also descri#es the design constraints and technologies that are

to #e considered when the s!ste" is to #e designed, and other factors

necessar! to pro$ide a co"plete description of the reuire"ents for the s!ste".

9his Software &euire"ents Specication @S&SA captures the co"plete

software reuire"ents for the s!ste". &euire"ents descri#ed in this docu"ent

will #e used as guidelines to de$elop the Shift Scheduler.

.%co$e

Shift Scheduler software ai"s to pro$ide the following ad$antages B

• uto"ation of shift scheduling and pa!roll calculation.

• e7ecti$el! change the e"plo!ee wor6ing hours to ensure that Pro8ect

de$elop"ent is not paused due to e"plo!ee una$aila#ilit!.

Page 4 of 24


5/24

• *


6/24

auto"aticall! assign di7erent roles and their shifts which auto"ates the process

of pa!roll calculation. 9he S!ste" d"inistrator will assign the Pro8ect anager

their roles which will then assign tea" lead5pro8ect lead role and the! will

respecti$el! assign the e"plo!ees to the pro8ect and later assign the"

respecti$e shift. 9his gi$es 24 + ) pro8ect support reuires sta7 presence at an!

ti"e of the da!, aintenance of pro8ect with di7erent criticalit! and *


7/24

Pro$ision of e"plo!ee #ac6up in case an e"plo!ee not turning up.

ECelp leF pertaining to di7erent possi#le ueries.

9he s!ste" runs on an! platfor".

*"plo!ee can $iew his5her schedule in calendar for".

uto"atic llowances generation.

3. Constraints

'.4.1 igration of all the co"plete e"plo!ee and pro8ect data#ase with

e+isting schedule.

'.4.2 o e"plo!ee can #e gi$en two shifts sa"e ti"e.'.4.3 (nl! ad"in can "anage e"plo!ee details and position #ut cannot

assign schedule.

3.4 Ass#m$tions an" "e$en"encies

'.%.1 9he Shift ssigned to a particular e"plo!ee the e"plo!ee is free at

that ti"e and an! change is inti"idated #efore to the tea" lead.

. -5ternal !nterface Re6#irements

.1 7ser !nterfaces

1 9he s!ste" will pro$ide GI for the users.

2 essage displa! when we clic6 on #utton.

3 Standard #uttons, functions, or na$igation lin6s that will appear on

e$er! screen, such as a help #utton.

.2 Har"8are !nterfaces

).2.1 9o use SSS, !ou will need a P @regardless of its operating s!ste", it

can #e ;indows, Hinu+A or ac. 9he s!ste" reuire"ents are1. PB 2 + Intel ore 2 @2.'' Gh>, 12- cacheA2. &B 2G=3. ini"u" data#ase spaceB 40G=

Page of 24


8/24

).2.2 If s!ste" doesn?t ha$e touch input, a 6e!#oard will also #e reuired #!

the user to pro$ide input.

. %oft8are !nterfaces

1 9he s!ste" will ha$e an interface with Data#ase Software SJH ser$er

and windows we# deplo!"ent IIS.

.4 Comm#nications !nterfaces

1 9he s!ste" will use clic6 once deplo!"ent technolog! of the

windows .net fra"ewor6 where in windows for" #ased applications

can #e accessed through http o$er the internet. 9he we# =rowsers

include

Internet *+plorer 10, 11 K *dge

irefo+ @recent $ersionsA.

hro"e, Safari, ;e#6it @recent $ersionsA.

Page 9 of 24


9/24


10/24

Pro


11/24

Fig 1.

!eam "eader User case Diagram

Page 11 of 24


12/24

9.2 7se Case %cenario Descri$tion

7se Case !D 1

7se CaseName

Hog In Page

Su""ar!ad"in will ha$e their log in IDs. login page will #e

pro$ided. ;here the! can enter their user na"e and

password for user $erication. 9he Progra" can

auto"aticall! detect the role of the e"plo!ee in the

na"el! d"inistrator

Pro8ect anager

9ea" Head

*"plo!ee

fter choosing the user t!pe the! will #e redirected

to second page. ;hich consists of following

*nter serna"e te+t eld

*nter Password

orgot Password

fter the user enters the details their userna"e and

password will #e $eried fro" data#ase. In case the user

forgets his password. 9hen on clic6ing the Eforgot

passwordF lin6 the password will #e sent to his registered

*"ail ID.

Preconditions ser "ust ha$e his credentials in the data#ase.

Success *nd Lou ha$e logged in Successfull! essage is displa!ed to

Page 12 of 24


13/24

ondition the user.

ailed *nd

ondition

If ser could not pro$ide his right details.

Pri"ar!,Secondar!ctors

ad"in who will enter the details for $erication.

9rigger :

Description Step

ction

1 9he *nd user opens the rst login Page.

2 ser will enter the user na"e and password for$erication.

3 If the user na"e and password get $eried E!ouha$e logged in successfull!F "essage will #edispla!ed and user will #e redirected to appropriatepage depending on his role.

4 In case the user forgets his userna"e. Ce will clic6on the Eforgot passwordF lin6. Password will #e sentto his registered *"ail ID.

9a#le 1.1 se ase ID 1

Page 1 of 24


14/24

7se Case !D 2

se ase na"e dding5re"o$ing5assigning Pro8ects

Page 14 of 24


15/24

Su""ar! fter Hoggin in as the s!ste" ad"inistrator or Pro8ect anager

the user can add or re"o$e or assign pro8ects to e"plo!ees in

the "ain data#ase hence 6eeping a trac6 of all the e"plo!ees

wor6ing on pro8ects in the organi>ation.

;hen ad"inistrator decides to go in pro8ect he has the following

option a$aila#le

1. Assign Project.

9he following options will #e ena#led.

# Drop Down Men$% allows the ad"in to select the

desired pro8ect

# Drop Down Men$% allows the ad"in to select the

e"plo!ee to assign the pro8ect.

2. Add Project.

9he following options will #e ena#led.

# DA!& 'A"&(DA)% 9he F)OM and !O date should #e

selected fro" date pic6er and the pro8ect start and end

ti"e can #e selected.

# !&*!% 9he Pro8ect na"e along with pro8ect id to #e input

and allowances for $arious shifts

# !+M&% 9he $arious shift ti"ings of the pro8ect.

3. &dit Project.

# &dit B 9he user can edit an! pro8ect detail #! 8ust choosing

the correct pro8ect id.

. De,ete Project B 9he user delete an! pro8ect #! selecting

the correct pro8ect id.

Page 1) of 24


16/24

Preconditions • 9he d"in or Pro8ect anager "ust #e authori>ed and

logged in.

Success *ndondition Successful operation on the concerned pro8ect.

ailed *ndondition

ailed (peration "essage on the concerned Pro8ect


d"in, Pro8ect anager

9rigger 9his use case is initiated when user clic6s on MPro8ect enu?.

D-%CR!P+!*N%te$

Action

1 9he ser Selects the pro8ect "enu to do the reuiredaction

2

2a

2#

2c2d

9he user chooses an operation to #e done on pro8ect

@(nl! one option can #e selected fro" the four options

a$aila#le.AIf the user selects, Assign Pro


17/24

' 9he user can delete the reuired pro8ect #! selecting thecorrect pro8ect id.


7se Case !D 3

se ase na"e dding5*diting5&e"o$ing *"plo!ee

Su""ar! 9he user when logged in as ad"inistrator an add5delete and"odif! an! e"plo!ee record to "aintain wor6ing nu"#er of

e"plo!ees in the organi>ation and scheduling tas6 eas! for the

tea" leads and Pro8ect anager

Preconditions • 9he d"in "ust #e authori>ed and logged in.

Success *nd

ondition

9he *"plo!ee &ecord can #e successfull! "odied, added or

deleted fro" the data#ase

ailed *ndondition

9he *"plo!ee &ecord cannot #e successfull! "odied, added ordeleted fro" the data#ase


d"in

9rigger 9his use case is initiated when user clic6s on M*"plo!ee?.

D-%CR!P+!*N%te$

Action

1

9he ser selects the *"plo!ee fro" the na$igation #ar.

Ce can select an! of the following option a$aila#le andproceed.

Page 1 of 24

http://requirmentengineeringsrs.blogspot.in/http://requirmentengineeringsrs.blogspot.in/


18/24

2

2a2#

2c

9he user chooses an operation to #e done on e"plo!ee

@(nl! one option can #e selected fro" the three optionsa$aila#le.A

If the user selects, A"" -m$loyee' follow step 3

*lse If the user selects, -"it -m$loyee' follow step 4

*lse If the user selects, Delete -m$loyee' follow step %

3 9he option allows the ad"in to add the e"plo!ee details inthe "ain data#ase

4 9he option allows the user to edit the e"plo!ee details inthe "ain data#ase.

% 9he (ption allows the user to Delete the e"plo!ee details.


7se Case !D 4

7se Case

name

&eport View

Su""ar! 9he entire perspecti$e of the pro8ect is to "aintain an e


19/24

Success *ndondition

9he &eport will #e generated for all the e"plo!ees.

ailed *ndondition 9he &eport generation will gi$e #lan6 page.


Pro8ect anager, 9ea" Header and a s!ste" ad"inistrator.

9rigger 9his use case is initiated when ser clic6s on M&eport?.

D-%CR!P+!*N %te$

Action

1 9he user selects the report option.

2

3

9he user clic6s on the Generate report.

9he entire su""ar! of the s!ste" is displa!ed to theuser.

% 9he report download is a$aila#le in PD for"at


7se Case !D %

7se Case Shift Scheduling

Page 1; of 24

http://requirmentengineeringsrs.blogspot.in/http://requirmentengineeringsrs.blogspot.in/


20/24

name

Su""ar! 9he Pro8ect anager along with the tea" leader is responsi#le

for this tas6. 9he $ar! "ain and core function of the s!ste" theshift scheduling part where the tea" "anager or pro8ect

"anager can assign specic pro8ect and shifts to the e"plo!ee

lso gi$es the user the ad$antage to change the dut! to

"aintain the e of 24

http://requirmentengineeringsrs.blogspot.in/http://requirmentengineeringsrs.blogspot.in/http://requirmentengineeringsrs.blogspot.in/


21/24

3

9he user chooses an operation to #e done on pro8ect

@(nl! one option can #e selected fro" the three optionsa$aila#le.A

If the user selects, Assign %hift' follow step 4

*lse If the user selects, Delete shift' follow step %*lse If the user selects, -"it %hift' follow step '

4 9he user has the option to select the concerned pro8ectalong with the e"plo!ee to assign the pro8ect and shift to.

% 9he user has the option to select the concerned pro8ectalong with the e"plo!ee to re"o$e the pro8ect and shiftto.

' 9he user has the option to select the concerned pro8ectalong with the e"plo!ee to edit the pro8ect and shiftalread! assigned.

9a#le 1.% se ase ID %

;. Non F#nctional Re6#irements

9his section descri#es in detail all the non:functional reuire"ents

;.1 7sa(ility/.1.1 9he s!ste" shall allow the users to access the s!ste" fro" the

Internet.

/.1.2 online help will #e a$aila#le for the s!ste"

/.1.3 9he end users will #e a#le to a#le to adapt to the s!ste" with a

"ini"u" training of 2 hours

/.1.4 e! #oard short cuts will #e a$aila#le for all functions of the s!ste"

;.2 %ec#rity

/.2.1 Hogin reuire"ents :

/.2.1.1 9he d"inistrators will #e pro$ided access to the s!ste" after

the! are registered into the data#ase.

Page 21 of 24


22/24

/.2.1.2 ;hile logging in the s!ste" for the rst ti"e, the d"inistrator,

Pro8ect anager, 9ea" Head and *"plo!ee will #e pro$ided an ID and

a password.

/.2.1.3 (n logging in, the! can set a new password

;.2.2Password reuire"ents

/.2.2.1 Password will #e case:sensiti$e./.2.2.2 Password "ust ha$e at least ' characters,/.2.2.3 Password should #e changed if the sa"e password is alread!

ta6en #! other user.

/.2.3 Inacti$it! ti"eouts

/.2.3.1 S!ste" should ti"eout when there is no acti$it! for 10

"inutes.

;. Performance/.3.1 &esponse ti"e

/.3.1.1 9he response ti"e will #e less than % seconds for al"ost all the

processes perfor"ed in the s!ste".

;.4 Ca$acity

/.4.1 Storage

/.4.1.1 Card dis6 space N

10 G= N ontent

30 G= N 9ransaction Hogs

;.) Recovery

/.%.1 &eco$er! ti"e scales

/.%.1.1 9he s!ste" will #e reco$ered within 2 hours fro" the down

ti"e

/.%.2 =ac6up reuencies

/.%.2.1 Details of all the d"inistrator, pro8ect "anager, tea" lead,e"plo!ee will #e stored in the #ac6:up tapes along with schedules and

pro8ects.

/.%.2.2 ll the #ac6:up tapes will #e pro$ided to the Pro8ect

d"inistrator.

/.%.2.3 9he #ac6:up data will #e updated e$er! 10 da!s.

Page 22 of 24


23/24

;.3 Availa(ility

/.'.1 Cours of operation

/.'.1.1 9he s!ste" will #e a$aila#le on all da!s 24O)

;. Relia(ility/.).1 ean 9i"e #etween ailures

/.).1.1 9he "ean ti"e #etween failures for the s!ste" will #e /0da!s

;.9 =aintaina(ility

/.-.1 ean 9i"e to &eco$er!

/.-.1.1 9he ean 9i"e 9o &eco$er! @99&A shall not e+ceed one da!.

;.; Porta(ility

/./.1 (S reuire"ents

9he s!ste" will run on windows P 5 Vista 5 ) 5 - 5 -.1 5 10 and on (S

and on HI.

/./.2=rowser reuire"ents

9he s!ste" will run on Internet *+plorer, Internet *dge, o>illa irefo+,

Google hro"e, Safari and #rowser.

;.1> Privacy/.10.1 &eports cannot #e accessed #! end users who are not gi$en access to

the reports

/.10.2o two users would #e a#le to see their schedule.

/.10.3*$er! Person registered #! would ha$e uniue id.

1>. Process =o"el

9he process "odel that we are using is waterfall "odel. It follows the principle of

dene #efore design. ;e clearl! dene each phase #efore designing it. 9he ne+t

phase is not started without co"pletel! i"ple"enting the pre$ious step. 9his

Page 2 of 24


24/24

"odel is considered suita#le #ecause the reuire"ents are $er! well 6nown and

product denition is sta#le.

9he following are the steps in$ol$ed in the "odelB:

Page 24 of 24

Shift Scheduling

Documents