|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/architecture-repository-in-practice/
课程评论：没有评论
**课程名称：** Sparx Enterprise Architect 作为团队的存储库 **课程概述：** 本课程旨在探讨在组织中引入和使用建模存储库的重要性，以及如何利用 Sparx Enterprise Architect 工具来构建和管理这一存储库。随着组织越来越重视建模实践的成熟度，传统的文档驱动建模方式面临诸多限制。引入建模存储库能够促进模型的重用、团队协作以及更敏捷的工作流程，从而提升建模和架构团队的效率。 Sparx Enterprise Architect 因其出色的价格与功能比而被选为本次课程的演示工具。课程将深入分析建模存储库相较于文档驱动方法的优劣势，并提供一个解决方案架构，用于指导如何在组织中成功引入存储库。你将学习到一种“吃自己的狗粮”的实践方式，即课程本身的模型便是建立在存储库之上的。 课程将详细介绍引入存储库的步骤和不同场景下的实施计划。此外，还将探讨一系列支持工作方式转变的辅助工具。需要注意的是，从文档驱动到存储库驱动的转变是一个重要的变革过程，会对架构团队和组织内外的利益相关者产生显著影响，本课程也将重点讨论这些挑战。
More and more organizations are focusing on the use of a modeling repository. A repository contributes to a more mature approach to introducing models like architectures into an organization. In the current working method, based on office automation, organizations encounter limitations when producing modeling documents. With a modeling repository reuse, cooperation in the modeling teams and a more agile approach are enablers for a modeling and architecture team.Introducing a repository is then one of the options and a promising and logical scenario. There are several platforms and tools available for modeling repositories. In this training we use Sparx Enterprise Architect as a tool for setting up a repository as a demo. The reason for choosing Sparx Enterprise Architect is the favorable price-functionality ratio compared to other products available in this segment of modeling tooling. Experience shows that the tool can provide the right support from a functional perspective. However, introducing a repository comes with a number of challenges. The transition from a document-driven to a repository-based working method should be seen as a change process that can have a significant impact. Impact on the architecture team, but also on the stakeholders of modeling and architecture within and outside your own organization.Reason for developing this training course and book in this way. We will therefore discuss the advantages and disadvantages of a modeling repository compared to the document-driven approach. We then develop a solution architecture for an introduction to a repository. Actually an "Eat your own dog food" approach, the model itself has been developed in a repository! Subsequently, a number of step-by-step plans are described which scenarios can be followed when introducing an repository. The last part is a number of tools that will support the change in working methods.
