GA001-185-8

EA精灵开模练习报告

班级：18软件5班   组员：    李海鹏     、    黄奕琛
                 学号： 1814080902510    1814080902508

1. Two Level Component Composition Hierarchy

1.1 概述

    The Two Level Component Composition Hierarchy pattern creates a number of Components and a Class diagram that describes the structural hierarchy of a Component. Role names and multiplicities describe the role each Component plays in the hierarchy and the number of allowed instances of each Component
    两级组件复合层次结构模式创建了许多组件和描述组件结构层次结构的类图。角色名称和多重性描述了每个组件在层次结构中所扮演的角色以及每个组件的允许实例的数量。

1.2 EA开模过程

Figure 1. Shows a Class diagram that contains a hierarchy of Components. Role name and multiplicities adorn the association ends on the part end of the relationships.
图1.显示了一个类图，其中包含组件的层次结构。 角色名称和多重性修饰在关联的结束部分

1.3 讨论

    该模式的目的是允许工程师、架构师和实现分析员对组件及其组成的组件进行建模。生成的层次结构允许他们和其他人可视化系统。当描述和可视化系统组件变得很重要时，它通常用于计划的设计或实现阶段。

    下面列出了使用此模式时可能需要执行的一些操作：

• 更改关系图的名称以及组件和角色的名称以适合该方案。
• 添加或删除层次结构中的组件以适应计划。
• 更改关联端的多重性以反映基数。

    以下是应用该模式时的一些后续步骤的列表：

• 如果需要，可以将层次结构扩展到另一个级别。
• 可以创建一个复合结构图来显示组件如何相互作用。
• 定义跟踪关系，显示组件如何与向上流程元素（如用户情景、用例和需求）和向下流程元素（如工件和数据库表）相关。
• 创建从模型自动生成的高质量文档。有用的工作空间布局核心|核心建模，宽视野

2. Component Interfaces with XML Payload

2.1 概述

    The Component Interfaces with XML Payload pattern describes how two Components, representing logical parts of a system, communicate via Ports and Interfaces. The Information Flow allows the payload to be modeled and specified as one or more information items that flow across the connector.
    带XML有效负载模式的组件接口是系统的逻辑部分，描述了两个组件如何通过端口和接口进行通信。信息流允许将有效负载建模并指定为流经连接器的一个或多个信息项。

2.2 EA开模过程

Figure 1. Shows two Components communicating via Ports and Interfaces. The XML payload is defined as an information flow, allowing a user to drill-down to the modeled payload elements.
图1显示了通过端口和接口进行通信的两个组件。XML有效载荷被定义为一个信息流，允许用户深入到建模的有效载荷元素。

Figure 2. Shows two Components communicating with Ports and Interfaces collapsed in the diagram to hide the detail from non-technical audiences.
图2显示了与图中折叠的端口和接口通信的两个组件，以向非技术受众隐藏详细信息。

2.3 讨论

    其目的是描述两个组件如何通过端口和接口进行通信，并显示两个接口之间的信息流。传递的信息项（有效载荷）也被建模，并且可以作为模型中的元素找到。
    该模式通常用于计划的设计或实现阶段，设计师或架构师需要描述系统组件之间如何通信。正式描述接口（包括接口提供的方法或服务）也很有用。

    下面列出了使用此模式时可能需要执行的一些操作：

• 更改组件、端口和接口的名称以适合您的计划。
• 更改接口操作的名称以适合您的计划。
• 更改信息流所传递的名称或元素，以适合您的计划。

    下面列出了使用此模式时可能需要执行的一些操作：

• 创建描述系统重要逻辑部分的附加组件和接口。
• 向接口添加操作以描述接口提供的方法或服务。
• 创建序列图，直观地记录按时间顺序调用消息。

3. Component Interfaces with JSON Payload

3.1 概述

3.2 EA开模过程

Figure 1. Shows two Components communicating via Ports and Interfaces. The JSON payload is defined as an information flow, allowing a user to drill-down to the modeled payload elements.
图1显示了通过端口和接口进行通信的两个组件。JSON负载被定义为一个信息流，允许用户深入到建模的有效负载元素。

Figure 2. Shows two Components communicating with Ports and Interfaces collapsed in the diagram to hide the detail from non-technical audiences.
图2显示了与图中折叠的端口和接口进行通信的两个组件，从而向非技术受众隐藏详细信息。

Figure 3. Shows a Sequence diagram with two Components communicating with Ports and Interfaces. The diagram allows the time ordered message flow to be visualized.
图3显示了一个序列图，其中有两个组件与端口和接口通信。该图允许可视化按时间排序的消息流。

3.3 讨论

    其目的是描述两个组件如何通过端口和接口进行通信，并显示两个接口之间的信息流。传递的信息项（有效载荷）也被建模，并且可以作为模型中的元素找到。
    该模式通常用于计划的设计或实现阶段，设计师或架构师需要描述系统组件之间如何通信。正式描述接口（包括接口提供的方法或服务）也很有用。

下面列出了使用此模式时可能需要执行的一些操作：

• 更改组件、端口和接口的名称以适合您的计划。
• 更改接口操作的名称以适合您的计划。
• 更改信息流所传递的名称或元素，以适合您的计划。

下面列出了使用此模式时可能需要执行的一些操作：

• 创建描述系统重要逻辑部分的附加组件和接口。
• 向接口添加操作以描述接口提供的方法或服务。
• 创建序列图，直观地记录按时间顺序调用消息。

4. 参考资料(Reference)

The following help topics will assist you learn about how to work with this pattern.

• Component Diagram
• Information Flow
• Convey Information on a Flow
• Diagram Properties

The following are some of the tools that will be helpful when working with this pattern.

• Traceability Window

The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window help topic.

• Relationship Matrix

The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix help topic.

• Specification View

The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.

• Hand Drawn and Whiteboard Diagrams

The Hand Drawn and Whiteboard Mode are display options available for any diagram that changes a system-drawn diagram to appear as though it was drawn by hand and, optionally, hand drawn on a whiteboard. It is a powerful device to engage an audience by presenting the diagram in a rough and more immediate style giving the impression that it is just a sketch that can be changed. For more details see the Hand Drawn and Whiteboard Mode help topic.

• Diagram Layout

The Diagram Layout tool allows you to layout an entire diagram, selected elements or sections of a diagram to make it more visually appealing or meaningful to a particular audience. There are a wide range of layout types to choose from and some types have filters that can be applied. For more details see the Diagram Layout help topic.

• Pan and Zoom

The Pan and Zoom facility is one of the tools that can be used to navigate around a large diagram. Often the resolution of a diagram must be reduced to ensure it is wholly visible but by using the Pan and Zoom window you can leave the diagram at a readable resolution and pan around to areas of interest zooming in when necessary. For more details see the Pan and Zoom help topic.

• Alternate and Images for Diagram Elements

Most standard elements allow an alternate image to be defined for an element that will be used in place of the graphical notation for the element either on a selected diagram or as a default on all diagrams. For more details see the Using the Image Manager help topic.

• Document Generator

The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.

© 2000 - 2018 Sparx Systems Pty Ltd. All rights Reserved.