Open rageqqq opened 3 years ago
We believe there is no requirement to put a class diagram for every component. In this case, we deemed it unnecessary as both components only contain a single class each. The user can refer to the architecture diagram to find out how these 2 components interact with the other components.
Team chose [response.Rejected
]
Reason for disagreement: Editor component has 2 classes? Why not create a diagram for that includes both text editor and command components
The UI, Editor and Parser components do not have a class diagram to describe their architecture while the Model, Storage and Command components have class diagrams. Might be useful to have some form of consistency in providing diagrams for components