如何在Sparx Enterprise Architect(EA)中对软件组件进行版本控制? [英] How can I version software components in Sparx Enterprise Architect (EA)?

问题描述

我正在使用Sparx Enterprise Architect 13对软件系统进行建模.该系统包含不同版本的软件组件.当我们发布软件组件的新版本时，我们通常会添加服务和/或API.

I am working at modelling a software system using Sparx Enterprise Architect 13. This system contains different versions of software components. We typically add services and/or APIs when we release a new version of a software component.

当前，为了反映组件ServiceV1公开接口A而ServiceV2公开接口A(与ServiceV1相同)和B的事实，我使ServiceV2扩展了ServiceV1.但这并不简单:

Currently, to reflect the fact that component ServiceV1 exposes an interface A and ServiceV2 exposes interfaces A (the same as ServiceV1) and B, I make ServiceV2 extend ServiceV1. But that is not straightforward:

• 组件之间的图中通用链接不可用，因此我必须使用高级">父级...".
• 它缺乏灵活性，因为我无法用接口的较新版本覆盖接口A

是否有更好的方法? 维护同一组件的多个版本的标准方法是什么?

Is there a better way to do so? What is the standard way of maintaining several versions of the same component?

谢谢！

推荐答案

我不认为这是某些标准组织所标准化的，但是我建议引入两个抽象级别:未版本化的组件级别和版本化的组件级别.

I don't think this is standardized by some standards body, but I would recommend to introduce two levels of abstraction: the unversioned component level and the versioned component level.

• 在未版本控制的组件级别上，项目存储库中每个组件只有一个元素(而不是每个组件版本).
• 在版本化的组件级别，对于每个组件的每个版本，项目存储库中都有一个元素 .

每个版本化的组件，例如MyComponentV2对未版本控制的版本具有``trace''依赖关系，例如MyComponent.

Each versioned component, e.g. MyComponentV2 has a ≪trace≫ dependency to the unversioned one, e.g. MyComponent.

为避免不必要的设计工作，您可以决定仅在版本化的组件元素之间，而不在未版本化的组件元素之间或仅反之亦然之间绘制不同组件之间的关系.但这取决于组织的需求.

To prevent unnecessary design work, you may decide to draw relationships between different components only between versioned component elements, not between unversioned component elements, or only vice versa. But this depends on the needs of your organization.

创建组件的新版本时，请将组件的所有最新版本(包括Mytrace≫-dependency)复制到未版本化的组件(MyComponent)，并将其所有连接复制到该组件的正确版本中(MyComponentV3).

When you create a new version of a component, you copy the most recent version of the component (MyComponentV2) with all its connections, including the ≪trace≫-dependency to the unversioned component (MyComponent) and give it the right name (MyComponentV3).

我已经在一个大型项目中应用了它.

I have applied this in a large project.

这篇关于如何在Sparx Enterprise Architect(EA)中对软件组件进行版本控制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！