REWERSE – WG A1 – Deliverables

2007-07-31

A1-D8: Appointment scheduling system: requirements specification

In the requirements specification document for the appointment scheduling system we will include the high level requirements of the system and the technical requirements that those high level requirements impose. We shall also identify the temporal notions the geotemporal reasoning system needs to support and investigate the use of the querying mechanisms to be developed in WG I4.

A report is to be delivered.

Contact person

Hans Jürgen Ohlbach

Contributor

Heraklion , Malta , Munich

Internal cross reader

to be announced

External cross reader

to be announced

Draft Deliverable D8. Deliverable D8. Munich.

Back to Top

2008-01-31

A1-D9: Appointment Scheduling System: system design

Develop the overall system design for the appointment scheduling system. This must include: (1) the representation of the information of each participating agent (2) administrative tools for the information and queries (3) a local server for each participating agent (4) a negotiation procedure (5) a constraint reasoner for planning the appointments. Each component is to be specified in detail.

A report is to be delivered.

Contact person

Hans Jürgen Ohlbach

Contributor

Munich

Internal cross reader

to be announced

External cross reader

to be announced

Draft Deliverable D9. Deliverable D9. Edinburgh. Eindhoven. Munich.

Back to Top

2008-01-31

A1-D10: Implementation

We shall implement prototypes of the various systems: the geotemporal reasoning system, the geospatial reasoning system, the topical reasoning system and the two application systems, the appointment scheduling system and the logistics support system. Intermediate documentations of these systems shall be provided as soon as major parts are finished, but the final documentation will be delivered at the end of the project.

The final documentations and the prototypical implementations are to be delivered.

Contact person

Hans Jürgen Ohlbach

Contributor

Munich

Internal cross reader

to be announced

External cross reader

to be announced

Draft Deliverable D10. Deliverable D10. Munich.

Back to Top

Howto: Deliverable Submission & Quality Control

During the Kickoff Meeting the following procedures for submitting deliverables have been established:

Contact person:

The management office asks to be informed as soon as possible about the contact person for each deliverable of year 1, i.e., the person who is mainly involved in writing and editing the deliverable. For each Deliverable the management office distinguish "contact persons" and "responsible persons". The contact person is the person mainly involved in writing, editing and publishing the Deliverable. The responsible person is always the working group co-ordinator. In case of problems, both, contact person and responsible person have to be contacted by the management office.

Draft versions:

Drafts of the deliverables can be published on the REWERSE internal web site that is currently being set up.

Quality control / Cross-reading:

To ensure Deliverables of good quality the management office would like to ask you to stick to the following internal control procedure before the Deliverables are submitted to the management office.
Each Deliverable has to be cross-read by two independent persons determined according to the following procedure:

1. A first (internal) cross-reader must be chosen within your Working-/Activity Group. He/she should, if possible, not be an author of the Deliverable.
2. A second (external) cross-reader should be chosen from a Working-/Activity Group that is different from the group that is producing the Deliverable.

Cross-reading of both internal and external readers has to be organized as follows:

• The external cross-reader must be suggested to the Executive Committee, and -- after approval by the Executive Committee -- the cross-reader should be contacted by the Working-/Activity Group to ask whether he/she agrees to cross-reading.
• The names of both cross-readers (after they agree) should be communicated to the management office as soon as possible, e.g. at the beginning of the 6 month period at the end of which the deliverable is to be completed. This means for the first deliverable that you have to determine your cross-readers soon, ideally until March 31.
• Both cross-readers should read the Deliverable -- or at least an advanced draft of it -- before its submission to the management office. The cross-readers' names should appear on the title page of the deliverable sent to the management office.

Final version:

Each final version of a Deliverable must be sent to the management office 1 month ahead of time. The Deliverables must be sent as PDF files. The cover sheet of the Deliverables must conform to the official cover page that will be provided by the management office.

Back to Top