Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Clarified components #6 & #7

...

Note: Color is used for highlighting the component that is being exemplified

#NameShapePart ofDefinitionExample
1

Stage

(Leap)

Image Modified


Leap Stage, with a label of either START or END, indicating Leap's initial and terminal points

Image Modified

2

Stage

(Custom)

Image Modified


Custom Stage, with a verbatim label as the name of the stage, that your form will go next to, upon user submitting the form

Note: At a bare-minimum, if your form does not go to another (custom) stage, then by default it will go to the (Leap's) terminal stage. In which case, the initial stage will be pointing to the terminal stage (i.e. Component #1 (Labeled START) pointing to Component #1 (Labeled END)

Image Modified

3[what:who]N/A - Text onlyStage component(s) (#1, #2)

This is a short way to annotate what can be done by who at/on that stage.

What can be C (Create), (Read), W (Write), D (Delete)

Who is a number which corresponds to a Role

Image Modified

4Straight Arrow

Image Modified


Arrow, with a same label as the submit button, indicating the flow from one stage (non-pointy end) to next stage (pointy-end)

Image Modified

5Curved Arrow

Image Modified


Curved arrow, with a same label as the submit button, indicating that upon submitting the form the form will "come-back" (i.e. remain within the same stage as prior to the form being submitted

Image Modified

6Role

Image Modified

Arrow component 

(#4, #5)

Role indicator, with label of Role #(s) described within Emails section below the diagram.


Only annotate the arrow with the role component, if an OPEN role user is triggering the stage/workflow progression.

Image Modified

7Email

Image Modified

Arrow component 

(#4, #5)

Email notification, sent by Leap, with label of Email #(s) described within Emails section below the diagram.


If the submit action triggers multiple emails, annotate the arrow that shows an email component per notification.

Image Modified


Draw.io is a good resource for creating UI & D (or UID) diagrams. Below is a "skeleton" (i.e. bare-bones) version of a UID diagram, in two different flavors: shadow / plain, that one can use to jump start their diagram. It is pre-filled with basic construct of the diagram and you can start from this. Be sure to change anything in red font color to tailor it to your application. Of course, you may change decide to change static parts; do so, as you see fit. Lastly, if you have no need for mentioning any notes, you may remove the third column in the footer of the diagram called "NOTES"


NamePreviewDownload

User Interaction & Design Diagram

Note: Change anything that is in red color as necessary/needed.

Image Modified

[PROJECT_NAME]_UID_Diagram.drawio

User Interaction & Design Diagram - Plain / No Shadows

Note: Change anything that is in red color as necessary/needed.

Image Modified

[PROJECT_NAME]_UID_Diagram_NS.drawio