You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With reference to issue #707 and the image above, the tester agues that using the new keyword in calls to constructor is inaccurate and the new keyword should be omitted from the sequence diagram e.g. CommandResult(..., uiCommand) instead of new CommandResult(..., uiCommand). The tester has assigned this as a medium severity bug.
Is not omitting the new keyword considered a bug and is this part of the module's UML standard? I would argue that there is no loss of information and a reader's understanding is not hindered by the new keyword and therefore not a bug. However, I also think it would be reasonable to accept this bug (at a lower severity level) if this was part of the module's UML standard as some examples in the textbook do omit it, although I am unable to find a definitive source for this in the textbook.
The text was updated successfully, but these errors were encountered:
With reference to issue #707 and the image above, the tester agues that using the new keyword in calls to constructor is inaccurate and the new keyword should be omitted from the sequence diagram e.g.
CommandResult(..., uiCommand)
instead ofnew CommandResult(..., uiCommand)
. The tester has assigned this as a medium severity bug.Is not omitting the new keyword considered a bug and is this part of the module's UML standard? I would argue that there is no loss of information and a reader's understanding is not hindered by the new keyword and therefore not a bug. However, I also think it would be reasonable to accept this bug (at a lower severity level) if this was part of the module's UML standard as some examples in the textbook do omit it, although I am unable to find a definitive source for this in the textbook.
The text was updated successfully, but these errors were encountered: