Open warrencxw opened 2 years ago
We admit that the second block of the parallel frame is missing. However, the explanation for the sequence diagram states that all methods from Countdown run in parallel with commands from other objects:
Since, we have explicitly stated this in the explanation right below the diagram, we believe the users would still be able to understand what is going on in the parallel frame. We have also lowered the severity level to low accordingly.
In case the term Timer
is argued to be ambiguous, we have defined the terms in the Glossary:
Team chose [response.NotInScope
]
Reason for disagreement:
According to the module website, this issue does not appear to be a valid use case for the NotInScope response. I understand that the explanation does explain what methods are run in parallel as other commands, but it does not change the fact that the sequence diagram is of invalid syntax and as such misleading and confusing.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your explanation]
The DG implies that the Timer methods are all parallel on a separate thread from the other commands, but this is not clear in the sequence diagrams, as there is no second part of the block which indicates what is running in parallel to the segment put in the parallel block, as per the text book shown below.