peer review: Need to fix module hierarchy diagram to communicate design decisions<Promish Kandel Team 22 TeleHealth Insights> #215
Labels
peer review
To be used with different parties for review purposes
artifact under review.
Design Doc MIS.md
team number (for the team doing the review). Team 22
description of issue.
Reading through you MIS, I can see that there is some level of hierarchy that is trying to be communicated but I'm finding that this doesn't translate to your diagram. Make it a Hierarchical structure so that the flow is more natural because right now I am having to look all over the diagram to figure out what layers the modules are in. Its not easy to read the software architectural design you are trying to present, the design patterns and decisions are a bit unclear.
https://github.com/aarnphm/tinymorph/blob/main/docs/content/images/modulediagram.png
The text was updated successfully, but these errors were encountered: