The Doctor Rostering Problem - Asser Fahrenholz

The Doctor Rostering Problem - Asser Fahrenholz The Doctor Rostering Problem - Asser Fahrenholz

asser.fahrenholz.dk
from asser.fahrenholz.dk More from this publisher
27.07.2013 Views

Chapter 5. Optimal solution 33 Amount Amount Amount 1 0 1 0 1 0 Results 7,1,20 8,50,13 6,50,2 6,100,8 2,1,0 1,100,4 3,1,7 7,50,2 14,1,0 31,50,0 50,100,2 52,100,1 Z(S), RCL (%), V(S) Greedy-Shift Greedy-Day GRASP-Shift GRASP-Day (a) Test 1 Results 6,1,19 5,50,16 2,50,1 8,1,0 10,100,10 1,100,4 5,1,2 6,50,5 11,1,0 33,50,0 44,100,1 56,100,0 Z(S), RCL (%), V(S) Greedy-Shift Greedy-Day GRASP-Shift GRASP-Day (b) Test 2 Results 6,1,23 10,50,18 9,50,3 6,100,11 3,100,4 4,1,0 4,1,6 2,50,3 13,1,0 19,50,0 47,100,3 62,100,0 Z(S), RCL (%), V(S) Greedy-Shift Greedy-Day GRASP-Shift GRASP-Day (c) Test 3 Figure 5.1: Comparison of heuristic performances for the GAMS problem

Chapter 6 The DRP Program Through this chapter, the reader is presented with the implementation of a graphical user interface, provided to the medical practice. The various features are described as to the allow reader to gain an insight into how the user interface connects with the concepts described in chapters 3 and 4 respectively. It should be noted that the implementation is a prototype of a software product and will most likely contain use cases that will cause the program to stop responding, fail or even crash. This is a direct consequence of the time horizon on this project. The program does enable the user to create usable schedules within minutes or even seconds. At the end of this chapter, I briefly review what program features are missing or lacking, for the program to be commercialised. The software can be found on the enclosed dvd 1 . 6.1 The user When developing an application, it is important to keep in mind who will be using the application. I recognise that the end user of the DRP program is not necessarily, on any level, good with computers or IT in general. It was a goal of this implementation to allow both experienced IT users to quickly grasp the features of the program, utilising all of the features and novice IT users to simply make use of the basic features. There is a fine line between adding features that enhance the capabilities of the software product and making it too complex for anyone outside the project to understand. This is also in line with the conclusion by Burke et al. [5], who recognise the importance of parameterless implementations. 1 Run the .jar-file, in the ”DRP/dist” folder 34

Chapter 5. Optimal solution 33<br />

Amount<br />

Amount<br />

Amount<br />

1<br />

0<br />

1<br />

0<br />

1<br />

0<br />

Results<br />

7,1,20 8,50,13 6,50,2 6,100,8 2,1,0 1,100,4 3,1,7 7,50,2 14,1,0 31,50,0 50,100,2 52,100,1<br />

Z(S), RCL (%), V(S)<br />

Greedy-Shift Greedy-Day GRASP-Shift GRASP-Day<br />

(a) Test 1<br />

Results<br />

6,1,19 5,50,16 2,50,1 8,1,0 10,100,10 1,100,4 5,1,2 6,50,5 11,1,0 33,50,0 44,100,1 56,100,0<br />

Z(S), RCL (%), V(S)<br />

Greedy-Shift Greedy-Day GRASP-Shift GRASP-Day<br />

(b) Test 2<br />

Results<br />

6,1,23 10,50,18 9,50,3 6,100,11 3,100,4 4,1,0 4,1,6 2,50,3 13,1,0 19,50,0 47,100,3 62,100,0<br />

Z(S), RCL (%), V(S)<br />

Greedy-Shift Greedy-Day GRASP-Shift GRASP-Day<br />

(c) Test 3<br />

Figure 5.1: Comparison of heuristic performances for the GAMS problem

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!