Open Halpfrog opened 2 years ago
The text above shows an overview of the implementation of the command. The sequence diagram shows a more detailed version. There is no value in describing every aspect of the implementation in words when it can be more concisely shown ("comprehensible and not comprehensive").
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: [replace this with your explanation]
Implementation step 2 jumps from logicmanager straight to editRoleCommandParser and ignores CommandListParser. Implementation is meant to make the reader understand how your software deals with this specific user input. By skipping steps but showing them in the UML diagram it adds additional confusion to the reader who now has to go through your code to figure out what exactly you meant.