Class Diagram for the Tunze Osmolator Universal - Report Example

Post Conditions The LED keeps on showing the updated status of the water level received from the sensors. Assumptions It is assumed that the user has switched on the button of the Tunze Osmolator and checking/viewing LED to know the level of the water.Basic Flow: 1. The user of the Tunze Osmolator switches on the machine.2. The sensor motor activates itself and detects levels of the water in the tank. 3. The sensor sends the information to the arithmetic unit to compare the sensor’s value with the lower set value of the tank. 4. Once the value has been compared, the LED would show the information about whether the water level is lower than the threshold value [A – 1]. 5. The motor starts itself to increase the level of the water until it reaches the upper limit of the tank.

Alternate Flow:A – 1. The motor would not start if the water level in the tank is higher than the required or lower threshold value of the tank. Conditions Trigging Alternate Flow: The alternate flow would only be initiated if the water level in the tank is within the prescribed threshold limits. Note: - The use case description format has been taken from the book of the R. S. Pressman. However, there are various limitations of the UML, as it focuses on software rather than hardware (Overgaard, Selic, and Bock, 2000).

In other words, there are many issues in building the UML of the real-time systems include the description of hardware elements, time constraints, communications tasks, and network modeling. Many solutions have been developed to overcome these issues and one of the solutions is to build the diagrams in three (3) tier structure of the system. In the first tier, the object building and software construction would focus on the software architecture, whereas, the system architecture would focus on the hardware and communications aspects of the system (Lou, 2000).

 The Tunze Osmolator water level controller system relates to the systems based on hardware more as compared to the software implementation. As described above, therefore, it can be stated that the implementation of the UML notation is quite difficult for the systems entirely based on hardware, time constraints, and communications tasks.