How do you resolve conflicts in the architecture repository?

由人工智能和领英社区提供技术支持

The architecture repository is a key component of the TOGAF framework, as it stores and manages the artifacts, models, standards, and guidelines that define the enterprise architecture. However, maintaining the integrity and consistency of the repository is not always easy, as different stakeholders may have different views, expectations, and requirements for the architecture. How do you identify and resolve conflicts and issues in the architecture repository? Here are some tips and effective practices to help you.

此文章中的业界达人

由社区从 6 条内容中精选。了解更多

Antony Pinch

1 Use a governance process

One of the most important steps to avoid and resolve issues in the architecture repository is to establish and follow a governance process that defines the roles, responsibilities, and rules for creating, updating, reviewing, and approving the architecture artifacts. The governance process should also specify the criteria, methods, and tools for evaluating the quality, completeness, and alignment of the artifacts with the architecture vision and principles. By having a clear and transparent governance process, you can ensure that the architecture repository is managed in a consistent and coherent way, and that any issues or discrepancies are identified and addressed in a timely and effective manner.

添加您的观点

Antony Pinch
举报内容
Architecture governance and project/programme governance should ideally be aligned. When a project moves its status, the artefacts within the repository should be aligned also. Regular reviews should be set up to screen the repository for content that has not been updated. Schedules for this are important. If possible, align the enterprise catalogue to the live environment through the use of service management or change control people, process and technology. Seize opportunities to schedule updates or reviews of licence renewals, subscription renewals or other changes (business or technology) to evaluate whether change needs to be made and mark components due to retire or be decommissioned as such within the repository.

已翻译

赞

2 Communicate and collaborate

Another key factor is to communicate and collaborate with the relevant stakeholders, such as business users, architects, project managers, developers, and testers. By engaging them in the architecture development and maintenance process, you can ensure that their needs, expectations, and feedback are taken into account, and that they understand and agree on the purpose, scope, and content of the architecture artifacts. Communication and collaboration can also help you to identify and resolve any misunderstandings, gaps, or conflicts that may arise among the stakeholders or between the architecture artifacts and the reality of the enterprise.

添加您的观点

Antony Pinch
举报内容
In my experience, the architecture repository is not the place to talk through designs or to collaborate. I never talk about architecture to non-architect colleagues. Instead the repository is used to create designs, carry out impact assessment and identify dependences. The output from this is then published on a collaboration platform, where it can be worked through with wider teams. Architecture tools are not always the best for capturing comments, having multiple people work on the same document at the same time, etc.

已翻译

赞

3 Use a version control system

A version control system is a software tool that helps you to track and manage the changes made to the architecture artifacts in the repository. By using a version control system, you can ensure that the architecture repository is always up to date and reflects the current state of the architecture. You can also avoid losing or overwriting any important information, as you can always revert to a previous version of an artifact if needed. Moreover, a version control system can help you to identify and resolve any conflicts or issues that may occur when multiple users are working on the same artifact or when different versions of an artifact are merged.

添加您的观点

Antony Pinch
举报内容
It depends on the nature of the architecture repository and how you define an architecture repository. If your repository is a codebase, then this may work. If your company employs use of service tools and connectors between those and your repository then this also may be useful. Where these are not in place it is likely that the repository is updated manually, where again scheduled reviews are essential. Depending on the size of the architecture team, and the size of the organisation a decision may be made to only hold detail to a high level (the component) and to call for version numbers only when architecture change is required.

已翻译

赞

4 Apply standards and guidelines

Standards and guidelines are essential for ensuring the quality, consistency, and interoperability of the architecture artifacts in the repository. By applying standards and guidelines, you can ensure that the architecture artifacts follow a common structure, format, language, and notation, and that they adhere to the best practices and conventions of the architecture domain. Standards and guidelines can also help you to identify and resolve any conflicts or issues that may arise from the use of different or incompatible models, methods, or frameworks for the architecture artifacts.

添加您的观点

Antony Pinch
举报内容
This is very difficult to achieve for most organisations, particularly where there are multiple service partners, contractors, and transient stakeholders working within the repository. Having guidance or training on hand to give to those that are to use the repository is helpful. This could take the form of Wiki's or some training. Ultimately it should form part of the review to ensure that if you have for example stated that business processes are mapped using BPMN, that the diagrams within the repository reflect the notation. An opportunity will also arise for these checks during peer review. Any new notation to be used should be formally agreed and any required training completed prior to using it.

已翻译

赞

5 Perform regular reviews and audits

Regular reviews and audits are important for ensuring the validity, accuracy, and relevance of the architecture artifacts in the repository. By performing regular reviews and audits, you can verify that the architecture artifacts are aligned with the architecture vision and principles, that they meet the stakeholder requirements and expectations, and that they reflect the current and future state of the enterprise. You can also identify and resolve any conflicts or issues that may result from changes in the business environment, technology trends, or stakeholder needs. Reviews and audits can be performed by internal or external parties, depending on the scope and purpose of the evaluation.

添加您的观点

Antony Pinch
举报内容
I have mentioned these formal reviews and audits throughout this document. Not all companies carry them out and time is always a constraint for busy architecture teams but if senior management has bought in to the architecture function this should be facilitated. The reviews and audits depending on the extent to which you wish to take them can be a good health check not just for the repository but for the architecture itself.

已翻译

赞

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Antony Pinch
举报内容
The repository can be very challenging to create and manage. Done well it can be a great source of insight. Having good tools to automate impact assessments and dependencies can drastically reduce the time spent in discovery. The more value your repository provides to the company, the more investment it will attract, so try to make it useful with information that is timely, relevant and accurate.

已翻译

赞

TOGAF

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you resolve conflicts in the architecture repository?

1

2

3

4

5

6

1 Use a governance process

2 Communicate and collaborate

3 Use a version control system

4 Apply standards and guidelines

5 Perform regular reviews and audits

6 Here’s what else to consider

TOGAF

给文章评分

感谢您的反馈

更多TOGAF相关文章

更多相关阅读内容