Contents

• Projects
• Project Groups
  • Tutors
  • Team organization
• What we expect
  • Submission Guidelines
  • Deliverables schedule
    • Requirements contracts
    • Requirements use cases
    • Interface design
    • Architecture design
    • First prototype
    • Revised prototype
• Redmine

Projects

A list of projects is available as a PDF document.

Project Groups

Log in to the course management system to view your project and your group, respectively.

Tutors

Log in to the course management system to see how to contact your tutor. You are supposed to meet your tutor once per week to discuss any issues that might occur during the project.

Team organization

Every team should appoint a team leader who will be a team representative, a group meetings' mooderator and a project manager. It is not important for us how you appoint your team leader. For such small teams as on this lecture it is recommended to make decisions mostly in a democratic way. Team leader responsibility is to make sure that any decisions at all will be made.

Team leader should also be responsible for splitting up work and assigning it to group members. The team leader should check back with other members of the group regularly to make sure that they are not blocked and are actually getting their work done.

What we expect

At the end of the course, we expect the following deliverables:

• A set of requirements: contract style, 2–4 pages;
• A set of use cases: Pressman style, 10–20 pages (see the "Safe Home" example at slides of the lecture on Requirements Engineering);
• An interface design: covering most of the use cases;
• Architectural models and data models: covering most of the use cases;
• An executable prototype: covering all must-have requirements and 5–95% of the use cases.

Please note that all numbers are negotiable depending on project.

In addition, we require from you to make extensive use of the Redmine project management system, namely its issue management and time logging capabilities.
See the Redmine section for details.

Submission Guidelines

Detailed submission guidelines will be available soon. As of now, while submitting given milestone, send it on your tutor's email.

Deliverables schedule

The milestone due dates are inclusive, meaning you may send in the deliverable as late as 23:59 of given day.

Start milestones denote when work on given deliverable officialy starts.

Tutor milestones denote hard deadlines for which the group has to handle in the required deliverable to the tutor.

Customer milestones are intermediate, suggested milestones, which should be shown to the customer and for which the client's feedback should be gathered.

Final milestones are hard deadlines, denoting final version of the deliverable handled to the tutor and the customer.

Requirements contracts

Milestone	Due date
Start	2012 April 24
Tutor	2012 May 04
Customer	2012 May 08
Final	2012 May 11

Between 2 and 4 pages. Requirements in contract style. Has to be handed in as one single PDF document.

Please note that all must-have requirements will have to be implemented in the prototype.

Requirements use cases

Milestone	Due date
Start	2012 May 02
Tutor	2012 May 18
Customer	2012 May 21
Final	2012 May 25

Between 10 and 20 pages. Use cases in Pressman style. Has to be handed in as one single PDF document.

Interface design

Milestone	Due date
Start	2012 May 21
Tutor	2012 June 01
Customer	2012 June 04
Customer	2012 June 08
Customer	2012 June 12
Final	2012 June 15

Paper prototyping is sufficient; computer-aided wireframing could be suitable as well. For command line clients, we expect a man page. Has to be handed in as one single PDF document (you can scan paper-based designs; has to be printable).

Architecture design

Milestone	Due date
Start	2012 June 01
Tutor	2012 June 08
Final	2012 June 15

(1) Comprehensive class diagram (including relationships, important attributes and methods) of the whole system,

(2) sequence diagrams that show how the main processes (or objects) operate with one another and in what order (at least three diagrams), and

(3) diagrams of one type out of the following ones (please choose one type depending on the nature of your project):

• Entity-relationship model
• Activity diagram / Flowchart
• State diagram

First prototype

Milestone	Due date
Start	2012 June 15
Final	2012 July 13

The prototype has to be demonstrated to the client no later than 2012 July 13. (You are free to set up an earlier date as you wish.) All must-have requirements have to be implemented in the protoype.

Revised prototype

Milestone	Due date
Start	2012 July 13
Final	2012 July 27

After the demonstration, the client can request revisions to your prototype. To protect you from excessive work, these revisions

• should stay in line with the agreed requirements,
• should not include new functionality beyond the use cases as defined above and
• must not exceed 10 working-hours per person.

The revised prototype must be provided to the client and to us on 2012 July 27 at the latest (firm deadline), as we have to grade it. This late deadline is set up for your convenience to accommodate exam preparation and other obligations; again, you are encouraged to submit at any time as it fits.

Redmine

The usage of the Redmine issues and time logging subsystems is mandatory.

Redmine (a project management web application) for your team is available at: https://se.st.cs.uni-saarland.de/redmine/

To log in to Redmine, please use the information you were provided in email from the chair. Please note that changes to your Redmine account (eg. changing your password) will not be reflected to the course management system.

Redmine enables you to (amongst other helpful features):

• arrange appointments,
• manage documents,
• maintain a wiki,
• use a version control system,
• track issues and tasks, and
• log time spent on issues.