The course book (available from the home page of the site) and the slides available below (uploaded after the end of the class)
You can assess your learning with this quiz, which you should be able to answer correctly at the end of the class.
Cooking, again
Revise the cooking example of the previous chapters by using advanced task types where appropriate.
Application evaluation
We have seen the application evaluation process throughout the book. Let's change it a bit now.
What we are looking forward now is to implement a process that work like this: applications are not processed as they are received. This would be too time consuming and it would require too many meetings. Instead, once the application deadline has expired, the admin personnel collects the applications and prepares a file with all the information on all applicants, and schedules a committee meeting. During the meeting, the committee evaluates each application, defines a final ranking, and then notify the top 10 that they have been selected, while the rest is notified with a rejection.
Application evaluation without ranking
As a variation on the above, assume now that there is no ranking and no threshold: the committee examines each application and decides if it is to be accepted or not. As soon as the evaluation of each application is completed, the candidate is notified.
Conference organization
Model the following conference organization process
Setup
A conference organizer (called General Chair, or GC) wants to organize a conference.
to do so, they select the Venue and dates, and select and invite two persons (the program chairs, or PC chairs) that will be in charge of the conference program. At this point the initial conference setup is done.
The PC chairs first decide on who to invite as part of the conference paper selection committee (called PC members) and select a system to be used to manage committee invitations and paper submissions/review.
Then the PC chairs request permission to use the selected conf mgmt system (CMS). if they obtain it, they initialize it with configuration information, and load the names of the PC members. If not, they try another system.
Initially, 50 names are loaded as the wish is to have a 50-members PC. The system will take care of sending invitations and collecting replies. in case of refusal by an invited PC member, a new one is added.
At some point the PC chairs prepare and send out the announcement for the conference to mailing lists, inviting people to submit papers. This can happen either after the PC is completed, or even before if it is becoming too late (too close to the conference deadline).
At some point the PC chairs decide to open the CMS for accepting submissions of papers.
Authors can now submit papers. They can submit and modify versions of the papers until a given submission deadline. At the submission deadline, new submissions or modifications are not accepted.
Review
After the deadline, the PC chairs assign the papers to PC members for review. Each paper goes to 3 PC members.
PC members have to turn in the reviews (in the CMS) before the review deadline.
A couple of reminders are sent to the reviewers before the deadline. After the deadline, usually there are still reviews missing and reminders need to be sent to those reviewers.
Consensus and decision
At some point, the consensus phase is started. This decision is taken by the PC chairs, by opening the consensus phase on CMS. An email is sent to the reviewers to discuss the papers and reach consensus if possible. After some time the PC chairs look at the result of the discussion and take a final decision on which papers are accepted.
Authors are notified of the acceptance and of the reviewers’ comments
Authors receive instructions on how to prepare the final version of their paper. they need to upload it on CMS by the final submission deadline.
You can find tentative solutions here and here. What would you improve on these solutions?