 |
.. (לתיקייה המכילה) | |
I saw in IBM's site that it is possible to download a 30-days trial version of Rhapsody 7.5.1. Can I use this version to solve the homework? | |
| Your submitted assignments will be checked using Rhapsody 7.2. You can use the 7.5 version BUT it is your responsibility that your statechart model will be compatible with the 7.2 version (i.e., to make sure that it runs also in the PC farm). |
I found a link where Rhapsody 7.2 may be downloaded without a time limit: http://www-01.ibm.com/support/docview.wss?uid=swg21380564. Could you tell the other students? p.s. note that it is called Telelogical Rhapsody and not Rational Rhapsody. | |
| Thanks, but I would like to make it clear that the official environment supported by the course is the one installed in the farm. Projects defined in any other environment including the above-mentioned Rhapsody 7.2 should be checked also in the PC farm. |
It is written that if the robot goes to sleep while conducting a task, in the day after it should continue in the previous execution point. What does it mean? | |
| As written, when a robot gets a task, it first analyzes it (for 5 seconds) and then performs it (for 10 seconds). When we say that it should continue in the same point it means that it should return to the beginning of the last active stage (i.e., if the robot went to sleep while being analyzing, it should start again with the analysis stage). |
How do I use timing syntax in Rhapsody Java? | |
| You write tm(X) above the edge. X is in milliseconds. E.g., tm(3000) means that a transition will occur after 3 seconds. |
It is written that upon heavy rain the Robot goes inside. What happens when it is inside and the rain gets weaker? | |
| In such a case the Robot goes outside and behaves according to its specification in weak rain (no deep sleep). |
How do we know what time is it? is there any built-in clock that we can use? | |
| There is no such clock. You should implement something (hint 1: by "implement" we do not mean Java code. hint 2: do not define a clock for the whole day, just one relevant for the specification). |
Is it possible to assume that when the sun sets (and the Robot goes to sleep) there is no rain? | |
| Yes. |
You said that we should implement a clock. Should it simulate a real clock? how? | |
| There is no need to implement a real clock, i.e., one that ticks and has an hour/minutes format. Define one that moves between the significant events as defined in the assignment (e.g., sunset, sunrise). Moreover, it is acceptable to have the clock driven by external signals and not by internal time events. |
Should we have a queue of tasks (remember how many tasks are pending) - for the case when tasks arrive during the night, or tasks arriving when the robot is already processing a task? | |
| No need for a queue. You may assume that no tasks are arriving while handling a task. |
What kind of documentation should we provide for the test scenarios? in which format? | |
|
It should be a textual documentation in natural language. It should include the steps that you did in order to test the system, the expected result, and the actual system's behavior. For instance: "send a signal B and then wait 10 seconds. Expected: the system should enter state A. Actual: As expected." Of course, you should arrange it in a readable format (probably in a table). |
What happens if there is heavy rain during daytime? what should the robot do? | |
| During daytime you (and the robot) should ignore the weather. |