You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current tutorial is a chain of many steps going up to 28 steps. It is told in the form of narration from start to finish.
Problem
It becomes challenging to link each step during tracing to the sequence diagram.
Proposed
We can add headers to highlight which logic interaction is currently being traced, for example, when LogicManager passes control to AddressBookParser, we can explicitly mention this in header in whatever is the best form. It is hoped this can allow them to relate it to the introduced sequence diagram in high level overview in #16 easily
We can also highlight it in a diagram?
The text was updated successfully, but these errors were encountered:
@UdhayaShan1MarkBind's image annotations feature is likely useful here. That way, we can cite the same UML diagram (directly referred from AB3) while annotating it as necessary to fit the tutorial.
e.g.,
Feel free to submit a PR. Initially, the PR can add just 1-2 diagrams. After discussing the initial change set, it can proceed to add more.
Current:
The current tutorial is a chain of many steps going up to 28 steps. It is told in the form of narration from start to finish.
Problem
It becomes challenging to link each step during tracing to the sequence diagram.
Proposed
We can add headers to highlight which logic interaction is currently being traced, for example, when
LogicManager
passes control toAddressBookParser
, we can explicitly mention this in header in whatever is the best form. It is hoped this can allow them to relate it to the introduced sequence diagram in high level overview in #16 easilyWe can also highlight it in a diagram?
The text was updated successfully, but these errors were encountered: