Northern Trails Outfitters (NTO) is ready to start the next phase of its Salesforce implementation. A consultant recommends using Universal Process Notation (UPN) to document the business process maps NTO will use as its guide.
As NIO maps out its processes, which two key principals of UPN should the team keep in mind? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D.BD
Universal Process Notation (UPN) is a graphical notation used to document business processes. When mapping out processes using UPN, there are two key principles that the team should keep in mind:
Keep version control and change history at the diagram level (Option C): Version control and change history are essential for managing the evolution of process maps. By keeping version control at the diagram level, the team can easily track changes and revisions made to the process maps over time. This helps in maintaining an accurate and up-to-date representation of the business processes. Additionally, having a change history allows the team to review and understand the modifications made, ensuring transparency and accountability in the process.
Attach supporting information at the detail level (Option D): When documenting business processes, it's important to provide additional context and supporting information to enhance clarity and understanding. Attaching supporting information at the detail level allows the team to provide more in-depth explanations, guidelines, or references related to specific activities or steps in the process. This can include detailed instructions, business rules, system requirements, or other relevant documentation. By incorporating this information, the process maps become more comprehensive and serve as a valuable resource for users.
While the other options may have their own relevance in certain situations, they are not specifically related to the key principles of UPN:
A. Limit the number of activity boxes on the screen to 8 to 10: This option suggests limiting the number of activity boxes displayed on the screen. While it may be a useful practice to avoid overwhelming the viewer with too much information, it is not a key principle of UPN. The number of activity boxes required would depend on the complexity and granularity of the business processes being documented.
B. Use symbols of different colors, arrows, and swim lanes for clarity: Using symbols of different colors, arrows, and swim lanes can indeed enhance the clarity and visual representation of process maps. However, this is not a key principle of UPN. These visual elements are more associated with process modeling and diagramming best practices in general, rather than specific principles of UPN.
In summary, when mapping out processes using UPN, the team should focus on maintaining version control and change history at the diagram level and attaching supporting information at the detail level to ensure accurate and comprehensive documentation of the business processes.