27.07.2013 Views

The Doctor Rostering Problem - Asser Fahrenholz

The Doctor Rostering Problem - Asser Fahrenholz

The Doctor Rostering Problem - Asser Fahrenholz

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6. <strong>The</strong> DRP Program 41<br />

schedules be taken into account in future versions of the program, the total time required<br />

to produce schedules would drop even more.<br />

Not unlike this program, PLANE (Burke et al. [3]) seeks to please the nurses on a per-<br />

sonal level and treats all nurses equally. PLANE is commended by the users for having<br />

high personal preference satisfaction and a low degree of constraint violation.<br />

6.4 From prototype to release candidate<br />

For this product to be commercialised, several things are needed:<br />

Past schedules should be considere. <strong>The</strong> assignment of unpopular shifts, such as on<br />

new years eve, new years day, christmas day etc., should be divided equally over<br />

several schedules.<br />

<strong>The</strong> data structure needs to be optimised for faster computations. <strong>The</strong> implementa-<br />

tion as it is now, does not fully exploit the object reference advantages.<br />

More dynamic coding is needed. <strong>The</strong> constraints need to be implemented into some<br />

easily editable form. <strong>The</strong> doctor-objects could also be coded in a more dynamic<br />

sense, letting the user specify fields for the doctors, and afterwards filling them in.<br />

But for the product to be sold, the buyer must be gaining a savings, i.e. if the doctor<br />

planning the roster is paid to do so, then it could save the medical practice money. If,<br />

on the other hand, the doctor is planning the roster for free, then no savings come from<br />

buying the DRP Program.

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

Saved successfully!

Ooh no, something went wrong!