User:Xavery Lisinski/sandbox

= Universal Process Notation = Universal Process Notation is a streamlined approach to business process modelling that emphasizes clarity and simplicity. UPN is designed to be easily understood by all stakeholders, from business analysts to end-users, fostering better communication and more effective process improvement.

Universal Process Notation has been used successfully both in wide-scale staff training at large organizations and in business analysis and system solution design.

UPN notation
UPN notation is based on IDEF0 notation and was first documented as a specification at Nimbus Partners in early 2000s. It became part of the public domain in 2007 when Ian Gotts, CEO of Nimbus Partners, published 'Common Approach, Uncommon results'.

UPN methodology shifts focus in business process modelling from multitude of different shapes to detailed text descriptions on boxes and lines. As such, UPN notation relies on using a single building block that is compromised of following elements:


 * Verb-based activity (What? happens)
 * Flowlines
 * Input (When? does it happen)
 * Outcome (Why? does it happen)
 * Resources
 * Human (Who? is responsible or involved)
 * Systems (With what? is the activity executed)

A UPN diagram is only composed of those building blocks, so the diagram always follows a sequence of rectangular boxes and lines.

Verifiable outcomes in UPN
One of the distinct features of UPN is its focus on verifiable outcomes. Each process step must be followed by clear, distinct, and verifiable outcome. The outcome must provide business rationale for performing the step in the first place as well as specify what asset, system status, or document is produced that proves the step was performed.

In order to achieve distinct, verifiable outcomes following rules are prescribed as best practice:


 * This outcome provides the rationale for the activity and signals its completion.
 * The outcome also acts as a catalyst or requirement for the following activity
 * Outcome must provide clear, unique, verifiable set of conditions for completing the task

Verb-based activities in UPN
fggfg

Hierarchical diagramming in UPN
Another unique aspect of UPN is the built-in hierarchical modelling. In UPN, each diagram is meant to remain fairly small (with no more than 8 to 12 activity boxes) to remain easy and simple to consume by the audience.

supports hierarchical diagramming, allowing complex processes to be broken down into manageable sub-processes. This hierarchical structure enables users to drill down into details as needed, without losing sight of the overall process flow. It provides a clear visual representation of how different parts of the process interact and contribute to the overall objective.

UPN vs BPMN
While Business Process Model and Notation (BPMN) is a widely used standard for process modeling, it can be complex and difficult for non-experts to understand. Especially since the latest BPMN specification is 532 pages long.

UPN, on the other hand, prioritizes simplicity and ease of use, making it more accessible for all stakeholders. BPMN uses various symbols to represent different types of activities and events, which can be overwhelming. In contrast, UPN's use of straightforward verb-based boxes reduces complexity and enhances clarity.

UPN tools
Due to unique nature of Universal Process Notation, specifically the hierarchical diagramming, this modelling technique requires a specialized software. There are three purpose-built platforms that support Universal Process Notation as of June 2024:


 * Elements.cloud
 * Skore
 * Tibco Nimbus

UPN certification
As of June 2024, there isn't a formal certification one can get in Universal Process Notation. However, UPN has become part of the larger Salesforce Business Analyst certification.