In the lecture we discussed the differences between Checked and Unchecked Exceptions. Go through the following list of conditions and decide whether this information should be represented as Checked Exception, Unchecked Exception, or as regular element of the program flow (typically return values of type boolean or of an enumeration type). Give for each decision an argument (one sentence). In case your answer depends on a context, explain which context you are assuming.

1. File can not be opened because no file with the given file name is found at the specified location.
2. File can not be opened for write access because another user has locked it for write access.
3. The user decides that he doesn't want to save the content of the file that he just edited.
4. While saving the content of a large file the file system reports that it can't complete the write process.
5. The user wants to send a file via Bluetooth, but he turned of the Bluetooth capability previously.
6. A variable can't be read because of a memory malfunction.
7. The connection to a remote server is lost during communication.
8. The component that provides the basic user interface functionality can not be loaded.

After our discussion in Task 24 we decided to develop the component that allows to find Bike Rental Outlets nearby as a server component. The component gives a list of the 5 closest BROs if you pass the GPS coordinates as parameters. In the following you will discuss the availability of this component.

a) In the lecture we discussed two strategies to detect whether a component is available or not. Discuss which one is appropriate here. (2-4 sentences should be enough. Of course you can use as well the predefined format from the recent tasks.)

b) We mentioned the following tactics to handle failures. Discuss which one is appropriate here. (2-3 sentences per tactic should be enough. Of course the predefined format from the recent tasks could be especially helpful here as well.)

1. Client-sided switch to alternative component
2. Active Redundancy, Bridge
3. Active Redundancy, Voting
4. Handling failure of non-redundant components

c) Finally we describe one error handling strategy in detail.

Assume that due to cost restrictions

1. it will NOT be possible to have redundant components.
2. the server might be unavailable three days a month on average.

We decided to deploy a list of BROs by PLZ (Postal Code) on the mobile device. In case the mobile device is not able to get the list of closest BROs, it will offer to find the BRO by PLZ.

Draw a sequence diagram that illustrates the case of a failure and how it will be handled by the mobile device.

The sequence diagram should contain at least one or a few objects as part of the client, the stub representing the server object on the client, the server object, and one or more objects representing the middleware framework. (You might want to have a look at the fourth slides of chapter 8).

In the lecture we discussed some modifiability tactics. From the aspect of localizing change (by reducing the consequences of a change and by reducing the cost of a change) the heuristics we gave you in Task 18 are very important. Explain for each of the following principles (in 1 or 2 sentences) how it improves modifiability:

1. A Subsystem is characterized by the services it provides to other subsystems.
2. The Release-Reuse Equivalency Principle
3. The Common Reuse Principle
4. The Common Closure Principle
5. Dependency Principle: Depend on abstract elements
6. Dependency Principle: Depend on stable elements
7. Dependency Principle: Avoid dependency cycles
8. Entities must never depend on Boundaries or Controllers

Find a RMI tutorial on the web and implement a client object and a server object and get it up and running. Deployment on the same machine is ok. Distribution over two machines is of course more fun.

You should be able to explain your code and to show client and server running and interacting.