GA004-185-8

EA精灵开模练习报告

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

1. Basic Dialog with Tree and List

1.1 概述

    The Basic Dialog with Tree and List pattern creates a Dialog Window with a series of controls including a Tree control and List control and three buttons that can be used to visualize the user interface of a Windows application, to generate the code to an application’s Resources file for compilation or to simulate its states with a behavioral diagram using JavaScript.

简单理解：

    带有树和列表模式的基本对话框创建一个对话框窗口，其中包含一系列控件，包括一个树控件和列表控件，以及三个可用于可视化Windows应用程序用户界面的按钮，将代码生成到应用程序的资源文件以进行编译，或使用JavaScript用行为图模拟其状态。

1.2 EA开模过程

Figure 1. Shows a Window 32 Bit User Interface diagram with a simple Dialog Window with a Tree View, List View and three buttons: OK, Cancel and Help.

1.3 讨论

    The purpose of the pattern is to allow technical Ux Designers, software engineers and other stakeholders to create and view Windows 32Bit dialog boxes that can be used to visualize a user interface and as inputs into the implementation of an application. The dialog can been designed with a Tree Control that would be typically be used as a navigation for a container node (such as a directory) that when selected would display its contents (such as files) in the List control. The buttons would be used to submit the Dialog, Cancel the Changes or Open help. The controls can all have their Win32 properties set directly in the application.

    The dialog is useful in the following situations:

• Visualize a dialog as part of a User Interface for a Win32 application.
• Get sign off and feedback from users to ensure the design meets their requirements and expectations.
• Use in conjunctions with behavioral models such as State machines to which can be used to trigger changes in the dialog using JavaScript commands.

    The following is a list of some things you may want to do when working with this pattern.

• Change the name of the Package and the diagram to suit the initiative.
• Change the name of the Dialog and the Controls to suit the initiative.
• Set the properties of the dialog and the each control using the Win32 section of the Properties window.
• Create additional controls, lay them out and set their properties.

2. AcV-2: Programme Timelines

2.1 概述

    The AcV-2: Programme Timelines pattern creates elements and a diagram that provides a starting point for the viewpoint. Element names and details can be changed and new elements and relationships can be added as required.

简单理解：

    程序时间线模式创建元素和图表，为视点提供起点。可以更改元素名称和详细信息，也可以根据需要添加新的元素和关系。
    The AcV-2 provides a time-based perspective of programmes. (MoD)

2.2 EA开模过程

Figure 1. Shows a Logical diagram that contains the elements and relationships relevant for this viewpoint.

2.3 讨论

    The purpose of the pattern is to allow Systems Engineers and other stakeholders to create and view elements and diagrams relevant to the viewpoint.The AcV-2 is primarily intended to support the acquisition process across multiple projects or programmes, including the management of dependencies between projects and the integration of all the DLODs to achieve a successfully integrated military capability.
Use of AcV-2 should support the management of capability delivery and be aligned with the StV-3, Capability Phasing. (MoD)
    The pattern is typically created when the necessary model precursors have been defined but it can be used at any subsequent point to provide an understanding of the viewpoint.
    The intended usage of the AcV-2 includes:

• Project management and control (including delivery timescales).
• Project dependencies and the identification of associated risk.
• Portfolio management.
• Through Life Management Planning (TLMP).

    The following is a list of some things you may want to do when working with this pattern.

• Change the name of the Package and diagram to suit the initiative.
• Change the name of the elements to suit the initiative.
• Create additional elements and relationships to suit the initiative.

    The following is a list of some of the next steps available when applying the pattern.

• Create a Hyperlink or an Artifact that references an external Gantt Chart.
• Create relationships between the elements in the diagram and other elements in the repository where this is specified in the process.
• Create documentation automatically with the document generator using built-in or user defined templates.
• Create drill-down from diagram elements by adding a child diagram which will make the element composite and allow a user to click-through to a more detailed or explanatory diagram.

3. Roles and Permissions Matrix

3.1 概述

    The Roles and Permissions Matrix pattern creates Activities that represent the system, functions and Classes that represent the roles and a diagram that uses relationships to associate the roles to the activities. A Relationship Matrix can be created to facilitate the visualization of the permissions and the location of gaps.

简单理解：

    角色和权限矩阵模式创建表示系统的活动、表示角色的函数和类以及使用关系将角色与活动关联的图表。可以创建一个关系矩阵来帮助可视化权限和间隙位置。

3.2 EA开模过程

Figure 1. Shows a Relationship Matrix that allows an analyst to visualize the permission that are assigned between roles and Activities.

3.3 讨论

    The purpose of the pattern is to allow Business Analysts and other stakeholders to create a model of the System Activities and the Roles that perform these Activities. The permission is represented as a relationship between the Role and the Activity.
    The pattern can be used at any point during an initiative but is more commonly used during the analysis phase when an analyst is breaking down system functions to create a set of activities and wants to ensure that there is coverage of the system functions by the set of identified Use Case and their Scenarios.

The following is a list of some things you may want to do when working with this pattern.

• Rename the diagram to suit the initiative
• Rename the Activities and Classes add Properties and Notes to describe the Activities and Roles.
• Create additional Activities and Classes to suit the initiative.

The following is a list of some of the next steps available when applying the pattern.

• Create a Relationship Matrix to visualize the permissions. Ensure the options to highlight missing column and row relationships is set.
• Create high quality documentation generated automatically from the model.
• Create Discussions and Reviews and engage in Chat to collaborate with team members, Requirement owners, Product Managers and other stakeholders.

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.