Open AlfredBeNoel opened 11 months ago
We decided to draw UML diagrams only for the new features we implemented, for example "remove team and remove dev from team". And remove developer is an old feature of AB3, in order to standardize among our we decided not to draw UML diagrams for the existing AB3 features. This bug is valid, but we did not want to complete our developer guide with so many diagrams.
Team chose [response.NotInScope
]
Reason for disagreement: Even if the functionalities existed in AB3, it should still be stated as to how the command is executed. Furthermore, even if you didn't want to clutter the DG with too many diagrams, it should have been instead stated under other UML diagrams that the functionalities are similar to that function, but this wasn't stated at all.
There is no sequence diagram that shows the calls to the different functions in the DG.