If your organization uses viewpoints to generate insights and access data while managing large datasets, keeping these assets organized for easy accessibility is crucial. Some Ardoq users have hundreds of viewpoints, so a smart approach to managing these assets can save a lot of time for your team.
In this article, we will cover a few ideas on how to organize the storage and naming convention of viewpoints to make life easier for Ardoq users.
Use Folders
Take advantage of Ardoq's folder functionality.
To organize viewpoints in folders:
Click on "Create new" in the Asset Library.
Give your folder a name.
Allocate existing and newly created viewpoints to this folder.
Ensure that the group responsible for running Ardoq smoothly in your organization is aligned on this approach and that all users who can create or edit folders are aware of and follow it.
Approach to Creating Folders
If you follow Ardoq's recommended way of working by using Solutions (formerly Best Practice Guides), you'll see viewpoints organized in folders as part of the Solutions you download once the Reimagined Ardoq product changes are launched.
Meanwhile, there are plenty of ways you can organize viewpoints:
By Persona
By Business Unit
By User
By Domain
etc.
If you don't have many viewpoints created, you can simply create a "Viewpoints" folder and move all the viewpoints there to keep the Asset Library tidy.
Who Can See and Manage These Folders
Administrators and Writers can create, delete, and edit folders.
Readers can only view the folders.
Contributors have no access to view them..
Follow Naming Conventions
Having a naming convention for the assets you manage in Ardoq is essential. If you don't have one, you can establish and start following a naming convention as it brings significant benefits for you, other Ardoq users, and your organization.
Here are a few tips for establishing naming conventions:
Be Descriptive: Choose a name that clearly describes the purpose or focus of the viewpoint. This helps users understand what to expect from it. Avoid ambiguous or overly generic names. For example, "Application Landscape View" is more informative than just "Applications."
Be Consistent: Use consistent naming conventions across all viewpoints. This includes consistent terminology, capitalization, and formatting.
Keep It Concise: Aim for a name that is short and to the point. Avoid overly long or complex names.
Make it Layer-Specific: Indicate the architectural layer the viewpoint belongs to if relevant. For example, "Business Process View," "Application Interaction View," or "Technology Infrastructure View."
Stakeholder Focus: Consider the primary stakeholders for each viewpoint and reflect this in the name. For instance, "CIO View" or "Developer's View."
Purpose and Usage: Highlight the purpose or specific usage of the viewpoint. For example, "Risk Analysis View," "Compliance View," or "Performance Monitoring View."
Versioning and Variants: If there are different versions or variants of a viewpoint, include version numbers or differentiating details in the name. For instance, "Application Landscape View v1.0" or "Detailed Security View."
Avoid Redundancy: Ensure that the name does not include redundant information that is already implied by the context. For example, if all viewpoints are under an "Enterprise Architecture" section, there's no need to include "Enterprise" in every viewpoint name.
Use Action Words: If the viewpoint is intended to drive action or decision-making, use action-oriented words that convey its dynamic nature.
We hope these tips are helpful. If you have any questions, please reach out to us via online chat.