UPN Shapes Library for draw.io
UPN (Universal Process Notation) is a modeling methodology used to create simple diagrams that effectively represent business processes. It provides a high-level view while also allowing for a certain level of detail.
The symbols and shapes in UPN are designed to be easy to understand. This notation is a comprehensive tool based on the following questions:
- Who needs to do what?
- When?
- Why?
- How?
About This Library
I have created this library to address the lack of UPN shapes in draw.io and to help those who do not have access to paid tools use this notation.
This library aims to provide a partial solution by making UPN shapes accessible and usable in draw.io.
There was an earlier attempt to implement UPN shapes from the draw.io team but it was paused due to insufficient contributions. Therefore, I decided to develop this library using native shapes, save them in the scratchpad tool and share them in a file.
This library is not a native implementation in draw.io, so it has some limitations, which I will explain later.
While this is a very simple implementation, it can save you a few hours of work. []~(￣▽￣)~*
How to Use
- Download the XML file from either of the following sources:
- GitHub: UPN_Library_draw_io_jaredcsv.xml
- Google Drive: UPN_Library_draw_io_jaredcsv.xml
Note: Google Drive may flag the file as dangerous, but it is safe to download.
2. Open draw.io. and click the ✏️ icon to edit your scratchpad.
4. Click on the Import button.
5. Upload the file and click the Save button.
If you upload the file and the shapes does not appear just reload the site and try again.
Now you can use them to build your business process maps.
Library Content
Content Overview:
- Activity Boxes
- Resource Boxes
- RACI Indicators
Activity boxes
Activity Box:
This is a basic representation of a task or activity within the process. It does not contain detailed sub-steps.
Activity Box with Attachment:
Similar to the basic Activity Box, but includes an attachment symbol to signify additional information or documentation related to the task.
Lower-Level Activity Box:
Please note that these shapes represent tasks at a lower level of the process hierarchy and serve as indicators for further detail without direct expansion capabilities.
These boxes resemble Activity Boxes but indicate tasks at a lower level of detail or granularity within the process. While they do not directly expand to reveal sub-steps, they signify that there are further detailed actions associated with the task.
Lower-Level Activity Box with Attachment:
Like the Lower-Level Activity Box, but also includes an attachment symbol for additional information.
Resource Box
This box represents the resources, such as people, equipment, or materials, required to complete an activity.
There is a red version of each of these boxes to highlight or accentuate specific tasks in your process mapping.
RACI tags (responsible, accountable, consulted, and informed)
These tags indicate the roles of individuals or groups in a process, using the RACI (Responsible, Accountable, Consulted, Informed) model:
- Responsible: The person or people who perform the task.
- Accountable: The person who is ultimately answerable for the task’s completion.
- Consulted: The people who provide input and advice about the task.
- Informed: The people who need to be kept updated on the task’s progress and outcomes.
Disadvantages:
1. Shape Distortion:
Shapes may become distorted because they are groups of native shapes, which can affect the appearance and accuracy of diagrams.
2. Unexpected Behaviors:
Unexpected behaviors may occur, such as triggering unwanted actions like adding arrows or separating elements from the group, leading to confusion and errors in diagram creation.
3. Limited Customization:
There are limitations in customization; for example, if you want to change colors, you must do so individually for each element within the group, which can be time-consuming.
4. Lack of Automation:
The lack of automation can be a limitation, such as the absence of automatic numbering for cards, requiring manual numbering and increasing the risk of errors.
5. Lower Fidelity than Native Implementation:
There is lower fidelity compared to a native implementation; for example, cards do not behave the same as in other tools like Lucidchart or Elements.cloud, affecting user experience and diagram accuracy.
These disadvantages may impact the efficiency and quality of diagrams created using the UPN shapes library in draw.io but I hope you find it useful.
For More Information on UPN
To learn how to build with UPN, refer to the following resources:
Thank you for being here!
Share it with your friends and colleagues! (❁´◡`❁)
For further questions or if you need additional shapes, feel free to contact me or leave a comment.
