Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering
Release date: Monday, 06.06.11 - Due date: Sunday, 19.06.11, 23:59
2 points |
---|
Consider the following design goals. Indicate the candidate patterns you would consider to satisfy each goal.
6 points |
---|
The initial Java program code - the library application - can be found in the SVN (https://svn.iai.uni-bonn.de/repos/IAI_Software/se/oosc2011/group00/Assignment8/LendingLibrary.zip). The goal of this task is to enhance the given application by the use of design patterns.
3 points |
---|
2 points |
---|
Take a look at the cyclic dependency expressed in the following UML class diagram: Can you think of a way to break this cycle without loosing any functionality?
2 points |
---|
For the use case to print an email with an attached file the requirements elicitation identified the following objects:
Categorize the objects into boundary, controller and entity objects. There might be an actor as well.
6 points |
---|
0-1,5 points: +0.5 per correct answer, -0,5 per incorrect |
---|
In the Requirements Eliciation… | Yes | No |
---|---|---|
…the focus is on the description of the system goals. | ||
…a technical system specification for the developer is generated. | ||
…entities, boundaries and controllers are identified. |
0-1,5 points: +0.5 per correct answer, -0,5 per incorrect |
---|
At the end of the Requirements Analysis… | Yes | No |
---|---|---|
…for each use case there is only one domain object. | ||
…the system is structured as a set of classes that are the base for the further development. | ||
…there may be redundant requirements. |
0-1,5 points: +0.5 per correct answer, -0,5 per incorrect |
---|
During the System Design… | Yes | No |
---|---|---|
…the design goals are obtained based on the non-functional requirements. | ||
…related operations are combined to a service. | ||
…subsystems with maximal coherence and minimal coupling are defined. |
0-1,5 points: +0.5 per correct answer, -0,5 per incorrect |
---|
At the end of the Object Design… | Yes | No |
---|---|---|
…the created class diagrams are the basis for the real implementation. | ||
…the checking of the model is done by a new system design iteration. | ||
…there needs to be a 100% test coverage. |
3 points |
---|
0-1,5 points: +0.5 per correct answer, -0,5 per incorrect |
---|
The diagram is a UML structure diagram: | Yes | No |
---|---|---|
Use-case diagram | ||
Class diagram | ||
Componentdiagram |
0-1,5 points: +0.5 per correct answer, -0,5 per incorrect |
---|
The diagram is a UML behaviour diagram: | Yes | No |
---|---|---|
Deployment diagram | ||
State machine diagram | ||
Class diagram |
6 points |
---|
0-2 points: +0.5 per correct answer, -0,5 per incorrect |
---|
The “extends”-relation in use case diagrams… | Yes | No |
---|---|---|
…may be used between two actors. | ||
…may be used between two use cases. | ||
…may be used between a actor and a use case. | ||
…is not permitted. |
0-2 points: +0.5 per correct answer, -0,5 per incorrect |
---|
The “inheritance”-relation in use case diagrams… | Yes | No |
---|---|---|
…may be used between two actors. | ||
…may be used between two use cases. | ||
…may be used between a actor and a use case. | ||
…is not permitted. |
0-2 points: +0.5 per correct answer, -0,5 per incorrect |
---|
In a use case diagram an external system is represented by… | Yes | No |
---|---|---|
…a system box, similar to the modeled system. | ||
…an actor figure. | ||
…a symbol for an active class. | ||
…a normal class symbol together with an adapter. |