GA007-185-8

EA精灵开模练习报告

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

1. 活动图（ActivityDiagram）

1.1 概述

    A SysML Activity diagram is an extension of the UML Activity diagram. The Activity diagram is a powerful tool for representing the sequence of Actions that describe the behavior of a Block or other structural element; the sequence is defined using Control Flows. Actions can contain Input and Output Pins that act as buffers for items that flow from one Action to another as the task carried out by the Action either consumes or produces them. The items can be physical materials, energy, power, data, information, or anything else that can be produced, conveyed or consumed, depending on the system and the activity being described. Activity Diagrams can be used to define situations where parallel processing occurs in the execution of some activities. Activity diagrams are useful for engineering modeling, where they detail the processes involved in system activities. This is an example of an Activity diagram.

简单理解：

活动图可以表示各式各样的活动，甚至可以描述最复杂的行为，活动图擅长通过行为表示事件或数据的流动，关注系统操作时，对象是如何在行为的执行过程中被修改的。

活动图的优势是可读性强，是有效的分析工具，一般情况下是首先要创建的行为图，可以使用活动图与利益相关者或项目成员沟通。

复杂系统设计过程中，工程师需要撰写文档，由于文字的不易理解和二义性，都会绘制流程图、组成图进行辅助说明，每个人的绘制方式都不同，沟通时需要向对方解释自己的图形，互相也很难理解，而且容易产生歧义。而采用了SysML语言之后，你用活动图描述你的，我用活动图描述我的，同样的元素类型和规则，理解起来非常容易，为沟通带来极大的便利，同样的表述方式也利于系统的合并和分解。

1.2 EA开模过程

1.3 讨论

    选择商品购买，可以选择直接购买或者加入购物车后再购买，支付之后可以在发货之前取消订单。发货后经过运输的过程，用户收货，订单完成。

2. 商业动机模型（Business Motivation Model）

2.1 概述

    A SysML Package diagram provides a means of visualizing the organization of a complex model into recognizable containers, which helps you to group the structures of the model and define high level relationships between these groupings. The structures can include name-spaces and their sub-Packages, and other less formally defined groups of elements. The basis of allocating structures to Packages could be, for example, access control, configuration Management, ease of navigation, or dependency level.

简单理解：

包图是现实系统模型的组织方式时所创建的图。系统模型的组织方式由包的层级关系决定。系统模型没有唯一的正确结构，不同的方法会有不同的模型结构，项目的目标不同，模型结构产生的效果也不同。

包图会传达关于模型本身结构的信息，一旦确定了项目有效的模型结构，创建包图会很有用，可以为利益相关者提供一种针对结构容易理解的视图。

除了描述系统的静态结构，SysML模型提供了活动图、序列图、状态机图用于描述系统的动态行为。

2.2 EA开模过程

2.3 讨论

    我们的项目分为数个packge，数据存储在服务器中。而客户端下包含着商品，订单，店铺等。商品包含店铺，销量，评价。而各个packge中还可以再细分。

3. 用例图（use case diagram）

3.1 概述

    A SysML Use Case diagram is used to define and view Use Cases and the Actors that derive value from the system. The Use Case diagram describes the relationship between the Actors and the Use Cases. Enclosing the Use Case within a Boundary defines the border of the system; the Actors by definition lie outside the boundary. (All elements are internal to the SysML diagram frame.) While the Use Case diagram can appear simplistic, it is a powerful communication device that describes the value or goals that external roles achieve from interacting with the system. Each Use Case can be detailed, with descriptions, constraints and any number of scenarios that contain sets of steps performed alternately by Actor and system to achieve the desired goal.

简单理解：

对于系统工程师来说，指定系统用例是一种常见的设计活动，通过用例来替代系统的功能需求，那么什么是用例呢？

简单来说，用例是特定的一系列动作，系统可以通过用例与外部角色来交互，以提供服务。从实践的角度，用例要定义系统边界，边界内是系统，边界外是外部角色，再按照某种规则（如时间、业务逻辑、组成单元等）对系统进行划分，形成用例。用例图包括系统边界、用例、外部角色和关联关系。

3.2 EA开模过程

3.3 讨论

    商户注册店铺之后，可以进行上新产品，发布活动等行为。最终是为了销售，获得销售毛利和被平台抽成。在用户方面，可以在平台上进行，登录，购买以及加入购物车等一系列操作

4. 需求图（Requirement Diagram）

4.1 概述

    Requirements engineering is a fundamental aspect of a systems engineering model. The discipline focuses on eliciting, analyzing and managing customer requirements early in the process. Once the requirements are understood, trade studies
can be conducted to formally assess design options, typically using weighted choices. The requirements are managed as
first class citizens and are formally allocated to development items and verification methods. Enterprise Architect has extensive functionality to assist the modeler with every aspect of the requirements engineering
discipline, including elicitation, modeling, management and testing. High quality engineering documentation can be
generated out-of-the-box using a wide range of built-in templates, carefully crafted to extract the information in the
models and present it in visually compelling and high quality documentation in a wide range of formats, including
DOCX, PDF and HTML. The documentation engine is highly configurable, and documentation to match any engineering
or organizational standard can be generated by creating templates and setting generation options. The SysML Requirements Model provides the system requirements, the expected abstract behavior and the operating
constraints that the designed system must conform to. This diagram shows an example requirements model for a Portable
Audio Player.

简单理解：

对一个系统进行全新开发，首先要获取涉众需求，即利益相关方的需要和需求，利益相关方可能包括供应商、客户、开发者、验证方、确认方，还可能包括法律法规等，只有全面识别出所有利益相关方，并了解清楚各方的关注点（或关切），捕获的需求才能完整。

捕获到利益相关方的需求后，需要对需求进行分析，形成系统需求，再依据需求进行相应的开发，需求一般分为功能性需求和非功能性需求。此时，获得的系统需求是基于文字的需求。

需求图是一种重要的SysML图。建模者可以使用六种关系来确定需求之间的可追踪性，以及从需求到系统模型中的结构和行为的可追踪性。需求图是SysML的主要媒介，可以向利益相关者传达这类信息。

基于文字的需求是系统工程中的重要产品，在SysML中，通过创建用例来替代基于文字的功能性需求，创建约束表达式来替代基于文字的非功能性需求。然而，如果项目没有创建基于文字的需求，而需要显示需求及需求与其他模型元素之间关系的时候，可以创建需求图。

需求图是非常有价值的图，可以直观的显示需求，并展示需求与其他模型元素之间的关系，可以建立需求之间，需求与包、用例、模块、约束模块之间的关系。在需求图中可以建立的需求关系包括：包含、跟踪、继承、改善、满足、验证。

4.2 EA开模过程

4.3 讨论

    电子商城系统需要考虑到法律需求，性能需求以及功能需求。法律则首先需要保证用户隐私，然后是注意销售的相关法律。性能则要考虑到事物间的并发处理，以及服务器的性能等。功能需求则需要考虑到用户登录才能进行操作，商品的推荐以及购买，商家入驻和商品的评价等。

5. 模块定义图（Block Definition Diagram）

5.1 概述

    A Block defines a collection of features used to describe a system, subsystem, component or other engineering object of interest. These features can include both structural and behavioral features, such as properties, operations and receptions, that represent the state of the system and the behavior that the system might exhibit.

简单理解：

模块定义图（BDD）是最常见的SysML图，可以在BDD中显示不同类型的模型元素和关系。在BDD中显示的模型元素包括模块、角色、值类型、约束模块、接口等，都是其他模型元素的类型，它们会出现在其他8种SysML图中。

模块（Block）是SysML结构的基本单元，可以使用模块为系统中或者系统外部环境中任意一种感兴趣的实体类型创建模型。

那么，何时创建BDD呢？答案是经常创建，应该经常创建BDD，BDD并不会与系统生命周期的特定阶段或者设计等级绑定，在执行不同系统工程活动时，如利益相关者需求分析、需求定义、架构设计、性能分析、测试案例开发、集成，通常会和其他SysML图一起创建BDD，从而为所关注系统的一个方面提供完整的视图。

5.2 EA开模过程

5.3 讨论

    我们的项目是一个父系统——电子商城系统，下面包含支付、智能搜索，平台活动、商品管理以及登录子系统。

6. 参考资料(Reference)

百度百科：https://baike.baidu.com/

火龙果软件网：http://www.uml.org.cn/index2.htm

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.