Open Aung-Phone-Naing opened 1 year ago
I do not think that this is a flaw. The termination simply shows that the Expense will eventually deleted and hence the activation bar extending until its deleting is rather meaningless. Also, in the platform that I used to draw this diagram I believe configuring such is impossible.
Team chose [response.IssueUnclear
]
Reason for disagreement: Firstly, I believe quoting that the platform does not allow for such configuring is not a valid reason when it comes to keeping to the correctness of documentation as developers can use a myriad of tools made available online to overcome this constrain.
Next, whether this is a flaw or not will depend on the usage of the expense class and upon closer inspection of the source code, I have realized that the "X" should not be put as destroyed at all as it clearly states in these lines of code snippets below that the instance of the expense class exists in the ArrayList
As shown below, the activation bar of Expense should be extended until its termination "X" instead.