子系统和组件之间的区别
我想问一下UML意义上的子系统和组件有什么区别？
I would like to ask what is the difference between a subsystem and a component in the UML sense?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
我想问一下UML意义上的子系统和组件有什么区别？
I would like to ask what is the difference between a subsystem and a component in the UML sense?
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（4）
我必须同意 Preet 的观点，但实际上，子系统比组件更大。我将组件用于图书馆（购买的、掠夺的或构建的），并将子系统用于执行给定集成功能的整个系统的一部分。例如，在血液处理设备中，离心机驱动器和控制器将是一个组件。集成的吸血调节（包括安全机制、电机控制、用户控制和通信）将是一个子系统。
I have to agree with Preet, but practically, a subsystem is larger than a component. I use components for libraries (either bought, pillaged, or built) and subsystems for a part of the whole system that performs a given integrated function. For example, in a blood processing device, the centrifuge driver and control would be a component. The integrated blood suction regulation (which includes safety mechanisms, motor control, user control, and communications) would be a subsystem.
在 UML 2.0 之前，我可以完美地将
<> 视为设计时<> ，它最终会成为 <代码><<组件>>。 UML 1.4 将组件定义为“系统的模块化、可部署和可替换部分，它封装实现并公开一组接口。组件通常由一个或多个分类器指定（例如，实现类） ）驻留在其上，并且可以由一个或多个工件（例如，二进制文件、可执行文件或脚本文件）实现。”在前面提到的“模糊性”被引入到 UML 中（在 UML 2.0 中）之后，我更倾向于使用
<> 作为更大的<。 > ，并将它们视为系统的可替换和可重用的组成部分。Before UML 2.0 I could perfectly see a
<<subsystem>>as a design-time<<component>>, which would finally become a<<component>>. The UML 1.4 defines component as "A modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces. A component is typically specified by one or more classifiers (e.g., implementation classes) that reside on it, and may be implemented by one or more artifacts (e.g., binary, executable, or script files)."After the aforementioned "fuzziness" was introduced to the UML (in UML 2.0), I am more inclined to use
<<subsystem>>as a larger<<component>>, and see both of them as replaceable and reusable constituents of a system.来自 IBM DeveloperWorks - UML 基础知识：组件图
简而言之，没有。
From IBM developerWorks - UML basics: The component diagram
So in short none.
在 UML 模型中，子系统是一种原型组件，代表系统中独立的行为单元。子系统在类、组件和用例图中使用来表示您正在建模的系统中的大型组件。
您可以将整个系统建模为子系统的层次结构。您还可以通过指定子系统的接口以及支持这些接口的操作来定义每个子系统所代表的行为。
在图中，分区显示有关子系统的属性、操作、提供的接口、所需的接口、实现和内部结构的信息。
通常，子系统具有描述其内容和在系统中的角色的名称。
如下图所示，子系统显示为包含子系统名称的矩形。它还包含关键字“Subsystem”和子系统图标。
来自：IBM 知识中心
In UML models, subsystems are a type of stereotyped component that represent independent, behavioral units in a system. Subsystems are used in class, component, and use-case diagrams to represent large-scale components in the system that you are modeling.
You can model an entire system as a hierarchy of subsystems. You can also define the behavior that each subsystem represents by specifying interfaces to the subsystems and the operations that support the interfaces.
In diagrams, compartments display information about the attributes, operations, provided interfaces, required interfaces, realizations, and internal structure of the subsystem.
Typically, a subsystem has a name that describes its contents and role in the system.
As the following figure illustrates, a subsystem is displayed as a rectangle that contains the name of the subsystem. It also contains the keyword «Subsystem» and the subsystem icon.
From: IBM Knowledge Center