(20 points) Design document includes design class diagram (DCD) with types and attributes/functions of all classes and files, and a link to commentable (and preferably editable e.g. with Miro or other tool) version of the diagram
The DCD needs to represent the team’s app. If it doesn’t reasonably agree with the project’s current source code or doesn’t show how the design patterns will be used, -5 points each.
The DCD should show classes with their attributes, associations, and methods, and types, and functions and parameters, that fit your team’s app i.e. user stories, use cases. The DCD should match/build on the names, types, etc and domain model.
For every mistake or mismatch, deduct -2 points.
As an example for “matching”/corresponding to domain model for domain objects (not React components), see
(20 points) Design document includes design class diagram (DCD) with types and attributes/functions of all classes and files, and a link to commentable (and preferably editable e.g. with Miro or other tool) version of the diagram
The DCD needs to represent the team’s app. If it doesn’t reasonably agree with the project’s current source code or doesn’t show how the design patterns will be used, -5 points each.
The DCD should show classes with their attributes, associations, and methods, and types, and functions and parameters, that fit your team’s app i.e. user stories, use cases. The DCD should match/build on the names, types, etc and domain model.
For every mistake or mismatch, deduct -2 points.
As an example for “matching”/corresponding to domain model for domain objects (not React components), see
Example 1
Design class diagram in two parts at end and design patterns
(domain model that the above design class diagram was based on)