- Tips and Tricks
Release date: Monday, 21.10.13 - Due date: Sunday, 27.10.13, 23:59
Computer Science Only! Media Informatics: Please do task 01, 03, 06 and if you want 04 on Monday, 28.10.13.
Your tutor has to read through many solutions. His work is much easier, if everyone follows some conventions.
Therefore he is only allowed to accept submitted solutions, if they fulfill the following formal requirements:
In order to get everyone accustomed to each other and working with the SVN repository, do the following:
A01_T07-T09_MultiMediaMasterin your repository.
MultiMediaMaster (short: MMM) is an online shop, where users can buy movies. We are elaborating a Use Case Model for a Commenting Feature of this application. Above you see the current state. For your convenience you find the use cases description here again:
|9 = 1+1+2+1+4 points|
a) The use case diagram would be clearer if we added another actor, wouldn't it? Add the actor and the association to the use case(s).
b) The use case descriptions are lengthy, because a part of the flow of events is duplicated in two of the use cases. Mark the duplication in the text.
c) Introduce a new use case and connect it to the other, to remove this duplication.
d) Read quickly through the three scenarios below. Which is not yet represented in the use case model?
e) Create a (short!) Use Case Description for the missing Use Case and integrate the Use Case into the Use Case Diagram above. Explain in a sentence, why you connected the new Use Case to the rest in the way you did it.
Use Abbott's method to create a Domain Object Model based on the Use Case Descriptions. Name as well the boundaries mentioned in the Use Case Description. As a starting point we provide the class
Movie from the main Domain Object Model of the system:
a) Create for each of your Use Cases separately a Use Case Realization.
b) Merge your Use Case Realizations into one Analysis Object Model.