Software Engineering

Includes requirements in contract style and use cases in Pressman style. Has to be handed in as one single PDF document.

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).

Revise requirement documents on the basis of the feedback given by lecturer.

(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

The prototype has to be demonstrated to the client no later than 2011-02-04. (You are free to set up an earlier date as you wish.) The exact use cases to be implemented and demonstrated are defined per project by Prof. Zeller and will be sent to you on or before Friday 2011-01-14.

After the demonstration, the client can request revisions to your prototype. To protect you from excessive work, these revisions (a) should stay in line with the agreed requirements, (b) should not include new functionality beyond the use cases as defined above and (c) must not exceed 10 working-hours per person. The revised prototype must be provided to the client and to us on 2011-02-25 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.

When submitting your final prototype for grading (thus, to the Software Engineering Chair), we also expect (a) a single paragraph in HTML format that describes the prototype, (b) a screencast video that repeats the demonstration, and (c) the full source code with appropriate build instructions. We will post (a) and (b) on a Web page, demonstrating your achievements (for your CV, for instance).

There are many screencasting software programs, including open source and freeware tools, available. For instance, you could use Wink (Windows and Linux), or QuickTime X (Mac OS X v10.6). Your screencast should contain audio (preferably) or subtitles and explain the main features of your prototype. If your prototype is not suited for a video at all, you are allowed to submit a series of screenshots. However, the latter only if need be. Please, ask for permission first as we will decide from case to case.

To submit your screencast video, please upload it first to a video-sharing website of your choice that allows to embed videos into other websites; for instance, Vimeo or YouTube. Finally, submit the link pointing to your video via e-mail as is usual.