USE A MODELLING TOOL
Use a modelling tool to work with your architecture and views. Maintaining views in simple diagrams is difficult to manage, and they quickly become outdated. In a modelling tool, views will automatically update as the model is updated.
When collaborating with stakeholders, the architect may need to tailor presentations from the model to meet stakeholders’ needs, using drawing or presentation tools. However, maintaining the model as the master for views is key for manageability.
PRIMARY VIEWS BEFORE COMPOSITE
When working with a view, it can be tempting to quickly move toward a composite view illustrating a solution. However, by considering primary views first, the architect creates a foundation for the architecture that serves as a reference point for both the architect and other stakeholders.
The architect can then select elements from the primary views to create multiple composite views, providing insights and potentially uncovering alternatives that might otherwise be missed.
COLLABORATE
Views are a valuable analysis tool for the architect and provide significant advantages when used in collaboration with other stakeholders. Working together with stakeholders while constructing views allows the architect to gather information from multiple perspectives.
This approach facilitates a broader understanding of the architecture and may provide insights that the architect might otherwise miss.
SIMPLICITY
Architectures can be complex, but we should avoid overcomplicating views. If a view becomes too complex with many elements or relationships, it may appear confusing to stakeholders.
Complex views can be broken down into several simpler views, making it easier for stakeholders to absorb the information. The architect can also take a step back and describe views at a higher level of context, abstracting them to make them more understandable for stakeholders.
COHESSION BETWEEN VIEWS
An architecture can contain a large number of views, and cohesion is essential to ensure that the architecture is accurately represented as a whole.
For example, when changing the relationships between a set of system components, the relationships in all views should reflect the change. Manually maintaining cohesion between views can be challenging for the architect, but using a modeling tool can significantly reduce the required effort.
RECORD YOUR ASSUMPTIONS
When constructing a view, it is common for the architect not to have all the required information available. Information is often uncovered during the development and evolution of the architecture.
Therefore, the architect is likely to make assumptions to drive the architecture forward. When constructing a view, it is highly beneficial to record any assumptions made, as these may later turn out to be requirements or constraints on the architecture, the organization, or its stakeholders.
REGULAR REVIEWS
When the architect has created a view, it is always worthwhile to obtain a second opinion. Reviewing views with peers can highlight risks or opportunities at an early stage, helping to avoid costly redesigns and facilitating an optimized and streamlined architecture.
As an architecture evolves, the architect needs to ensure that the views remain relevant. Scheduling regular reviews of architecture views helps ensure that the architecture remains accurate and up to date.
CHANGE CONTROL
When multiple architects are working with the elements and relationships in an architecture, the changes they make are likely to impact many views. To avoid overwriting the work of other architects or losing information, processes and tools are required for change control.
A change control board or reference group can be used to manage changes to the architecture, while techniques such as baselining the architecture or version control can help track and manage changes effectively.
AVOID STAGNATION
In large architecture assignments with a significant number of views, keeping everything up to date can be challenging. This can lead to the stagnation of views, meaning they no longer accurately represent the architecture.
Stagnation can incur significant costs, as architects and stakeholders may rely on these views for decision-making. Decisions made based on incorrect information can result in rework or even serious business consequences.
Architecture Mindset 