A002-185-2537-翁格婉（个人期末作业）

1.作业查词说明

1.1第一次查词

1.1.1Requirements baseline（需求基线）

查找名词 Requirements baseline（需求基线）
名词解说 A baseline for a set of requirements.
查找网址 https://www.jamasoftware.com/blog/defining-requirement-baseline/
查找时间 2020/9/22
详细解释
A requirements baseline is a snapshot in time that represents an agreed-upon, reviewed, and approved set of requirements that have been committed to a specific product release.
That “release” could be a complete delivered product or any interim development increment of the product. When stakeholders “sign off” on requirements, what they’re really doing is agreeing and committing to a specific requirements baseline (whether they think of it in those terms or not).
Once the project team establishes a requirements baseline, the team should follow a pragmatic change control process to make good business and technical decisions about adding newly-requested functionality and altering or deleting existing requirements.
A change control process is not about stifling change; it’s about providing decision-makers with the information that will let them make timely and appropriate decisions to modify the planned functionality. That planned functionality is the baseline.
Typically, a baseline is also given a unique name so that all the project participants can refer to it unambiguously. And good configuration management practices allow the team to reconstruct accurately any previous baseline and all its components.
需求基线是一个及时的快照，它代表了一组已被承诺到特定产品发布的已商定的、评审的和批准的需求。
这个“发布”可以是一个完整交付的产品，也可以是产品的任何中间开发增量。当涉众在需求上“签字”时，他们真正要做的是同意并承诺一个特定的需求基线(不管他们是否以这些术语来考虑它)。
一旦项目团队建立了需求基线，团队就应该遵循一个实用的变更控制过程，以做出关于添加新请求的功能和更改或删除现有需求的良好业务和技术决策。
变更控制过程并不是要扼杀变更;它向决策者提供信息，使他们能够做出及时和适当的决定，以修改计划的功能。计划的功能就是基线。
通常，基线也被赋予唯一的名称，以便所有项目参与者都能清楚地引用它。良好的配置管理实践允许团队精确地重建任何以前的基线及其所有组件。

1.1.2Enterprise Architect（企业架构师）

查找名词 Enterprise Architect（企业架构师）
名词解说 A visual platform for designing and constructing software systems, for business process modeling, and for more generalized modeling purposes.
查找网址 https://www.sparxsystems.com/enterprise-architect/index.html
https://www.sciencedirect.com/search?qs=Enterprise%20Architect

查找时间 2020/9/22
详细解释
What is Enterprise Architect?
Enterprise Architect is a visual platform for designing and constructing software systems, for business process modeling, and for more generalized modeling purposes.

Enterprise Architect is based on the latest UML® 2.5 specification (see www.omg.org). UML defines a visual language that is used to model a particular domain or system (either proposed or existing).

Enterprise Architect is a progressive tool that covers all aspects of the development cycle, providing full traceability from the initial design phase through to deployment, maintenance, testing and change control.

What differentiates Enterprise Architect from other UML tools?
Comprehensive UML 2.5 based modeling
Built-in Requirements Management
Extensive Project Management support, including resources, tasks, project calendar and metrics
Test Management built-in: Testpoint management, model-based test execution, test case specification and support for JUnit and NUnit
Flexible documentation options: HTML and Rich-Text (RTF) report writers
Code engineering support for many languages out of the box
An integrated Visual Execution Analyzer to profile, debug and document executing applications; instantiate run-time model objects; and record sequence diagrams from a stack trace
Extensible modeling environment that can host user-defined profiles and technologies
Usability: Enterprise Architect makes it easy to get up and running quickly with UML

Speed: Enterprise Architect is a spectacularly fast performer
Scalability: Enterprise Architect can handle extremely large models and many concurrent users with ease
Price: Enterprise Architect is priced to outfit the entire team, making collaboration and team development cost effectivelity from the initial design phase through to deployment, maintenance, testing and change control.
什么是企业架构师?
Enterprise Architect是一个可视化平台，用于设计和构建软件系统、业务流程建模以及更通用的建模目的。
Enterprise Architect基于最新的UML®2.5规范(请参见www.omg.org)。UML定义了一种可视化语言，用于建模特定的领域或系统(建议的或现有的)。
Enterprise Architect是一个渐进的工具，它覆盖了开发周期的所有方面，提供了从最初的设计阶段到部署、维护、测试和变更控制的完整跟踪。
企业架构师与其他UML工具的区别是什么?
全面的基于UML 2.5的建模
内置的需求管理
广泛的项目管理支持，包括资源，任务，项目日历和指标
内置的测试管理:测试点管理，基于模型的测试执行，测试用例规范以及对JUnit和NUnit的支持
灵活的文档选项:HTML和富文本(RTF)报告编写器
代码工程支持多种语言开箱即用
一个集成的可视化执行分析器来分析、调试和记录执行应用程序;实例化运行时模型对象;并从堆栈跟踪记录序列图
可扩展的建模环境，可以托管用户定义的概要文件和技术
可用性:Enterprise Architect使得使用UML可以很容易地建立和快速运行
速度:企业架构师是一个非常快的执行者
可伸缩性:Enterprise Architect可以轻松地处理非常大的模型和许多并发用户
价格:Enterprise Architect的定价是为了满足整个团队，使得从最初设计阶段到部署、维护、测试和变更控制的协作和团队开发成本有效性。

1.1.3Unified Modeling Language（ 统一建模语言）

查找名词 Unified Modeling Language（ 统一建模语言）
名词解说 A standardized modeling language consisting of an integrated set of diagrams
查找网址 https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/
https://www.uml.org/what-is-uml.htm

查找时间 2020/9/22
详细解释
UML, short for Unified Modeling Language, is a standardized modeling language consisting of an integrated set of diagrams, developed to help system and software developers for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems. The UML represents a collection of best engineering practices that have proven successful in the modeling of large and complex systems. The UML is a very important part of developing object oriented software and the software development process. The UML uses mostly graphical notations to express the design of software projects. Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the software. In this article, we will give you detailed ideas about what is UML, the history of UML and a description of each UML diagram type, along with UML examples.
Why UML

As the strategic value of software increases for many companies, the industry looks for techniques to automate the production of software and to improve quality and reduce cost and time-to-market. These techniques include component technology, visual programming, patterns and frameworks. Businesses also seek techniques to manage the complexity of systems as they increase in scope and scale. In particular, they recognize the need to solve recurring architectural problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance. Additionally, the development for the World Wide Web, while making some things simpler, has exacerbated these architectural problems. The Unified Modeling Language (UML) was designed to respond to these needs. The primary goals in the design of the UML summarize by Page-Jones in Fundamental Object-Oriented Design in UML as follows:

Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models.
Provide extensibility and specialization mechanisms to extend the core concepts.

Be independent of particular programming languages and development processes.
Provide a formal basis for understanding the modeling language.
Encourage the growth of the OO tools market.
Support higher-level development concepts such as collaborations, frameworks, patterns and components.
Integrate best practices.
UML是统一建模语言的缩写，是一种标准化的建模语言，由一组集成的图组成，开发用于帮助系统和软件开发人员指定、可视化、构造和记录软件系统的工件，以及用于业务建模和其他非软件系统。UML代表了在大型和复杂系统的建模中被证明成功的最佳工程实践的集合。UML是面向对象软件开发和软件开发过程中非常重要的一部分。UML主要使用图形符号来表达软件项目的设计。使用UML可以帮助项目团队进行交流，探索潜在的设计，并验证软件的架构设计。在本文中，我们将详细介绍什么是UML, UML的历史和每种UML图类型的描述，以及UML示例。
为什么UML
随着许多公司对软件的战略价值的增加，业界开始寻找技术来实现软件生产的自动化，提高质量，降低成本和上市时间。这些技术包括组件技术、可视化编程、模式和框架。随着系统范围和规模的增加，企业还寻求管理系统复杂性的技术。特别是，他们认识到需要解决重复出现的架构问题，比如物理分布、并发性、复制、安全性、负载平衡和容错。此外，万维网的发展在简化一些事情的同时，也加剧了这些体系结构问题。统一建模语言(UML)就是为了响应这些需求而设计的。由Page-Jones在UML基本面向对象设计中总结的UML设计的主要目标如下:
为用户提供一种随时可用的、富有表现力的可视化建模语言，这样他们就可以开发和交换有意义的模型。
提供可扩展性和专门化机制以扩展核心概念。
独立于特定的编程语言和开发过程。
为理解建模语言提供形式化的基础。
鼓励OO工具市场的发展。
支持更高层次的开发概念，如协作、框架、模式和组件。
集成的最佳实践。

1.1.3Unified Modeling Language（ 统一建模语言）

查找名词 Unified Modeling Language（ 统一建模语言）
名词解说 A standardized modeling language consisting of an integrated set of diagrams
查找网址 https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/
https://www.uml.org/what-is-uml.htm

查找时间 2020/9/22
详细解释
UML, short for Unified Modeling Language, is a standardized modeling language consisting of an integrated set of diagrams, developed to help system and software developers for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems. The UML represents a collection of best engineering practices that have proven successful in the modeling of large and complex systems. The UML is a very important part of developing object oriented software and the software development process. The UML uses mostly graphical notations to express the design of software projects. Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the software. In this article, we will give you detailed ideas about what is UML, the history of UML and a description of each UML diagram type, along with UML examples.
Why UML

As the strategic value of software increases for many companies, the industry looks for techniques to automate the production of software and to improve quality and reduce cost and time-to-market. These techniques include component technology, visual programming, patterns and frameworks. Businesses also seek techniques to manage the complexity of systems as they increase in scope and scale. In particular, they recognize the need to solve recurring architectural problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance. Additionally, the development for the World Wide Web, while making some things simpler, has exacerbated these architectural problems. The Unified Modeling Language (UML) was designed to respond to these needs. The primary goals in the design of the UML summarize by Page-Jones in Fundamental Object-Oriented Design in UML as follows:

Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models.
Provide extensibility and specialization mechanisms to extend the core concepts.

Be independent of particular programming languages and development processes.
Provide a formal basis for understanding the modeling language.
Encourage the growth of the OO tools market.
Support higher-level development concepts such as collaborations, frameworks, patterns and components.
Integrate best practices.
UML是统一建模语言的缩写，是一种标准化的建模语言，由一组集成的图组成，开发用于帮助系统和软件开发人员指定、可视化、构造和记录软件系统的工件，以及用于业务建模和其他非软件系统。UML代表了在大型和复杂系统的建模中被证明成功的最佳工程实践的集合。UML是面向对象软件开发和软件开发过程中非常重要的一部分。UML主要使用图形符号来表达软件项目的设计。使用UML可以帮助项目团队进行交流，探索潜在的设计，并验证软件的架构设计。在本文中，我们将详细介绍什么是UML, UML的历史和每种UML图类型的描述，以及UML示例。
为什么UML
随着许多公司对软件的战略价值的增加，业界开始寻找技术来实现软件生产的自动化，提高质量，降低成本和上市时间。这些技术包括组件技术、可视化编程、模式和框架。随着系统范围和规模的增加，企业还寻求管理系统复杂性的技术。特别是，他们认识到需要解决重复出现的架构问题，比如物理分布、并发性、复制、安全性、负载平衡和容错。此外，万维网的发展在简化一些事情的同时，也加剧了这些体系结构问题。统一建模语言(UML)就是为了响应这些需求而设计的。由Page-Jones在UML基本面向对象设计中总结的UML设计的主要目标如下:
为用户提供一种随时可用的、富有表现力的可视化建模语言，这样他们就可以开发和交换有意义的模型。
提供可扩展性和专门化机制以扩展核心概念。
独立于特定的编程语言和开发过程。
为理解建模语言提供形式化的基础。
鼓励OO工具市场的发展。
支持更高层次的开发概念，如协作、框架、模式和组件。
集成的最佳实践。

1.1.5Asynchronous Processes（异步进程）

查找名词 Asynchronous Processes（异步进程）
名词解说 The caller must wait for the method call to return before continuing with the behavior
查找网址 https://trailhead.salesforce.com/en/content/learn/modules/asynchronous_apex/async_apex_introduction
https://developer.salesforce.com/forums/?id=9060G000000I6XAQA0
https://www.gnu.org/software/emacs/manual/html_node/elisp/Asynchronous-Processes.html

查找时间 2020/9/22
详细解释
An asynchronous process is controlled either via a pty (pseudo-terminal) or a pipe. The choice of pty or pipe is made when creating the process, by default based on the value of the variable process-connection-type (see below). If available, ptys are usually preferable for processes visible to the user, as in Shell mode, because they allow for job control (C-c, C-z, etc.) between the process and its children, and because interactive programs treat ptys as terminal devices, whereas pipes don’t support these features. However, for subprocesses used by Lisp programs for internal purposes (i.e., no user interaction with the subprocess is required), where significant amounts of data need to be exchanged between the subprocess and the Lisp program, it is often better to use a pipe, because pipes are more efficient. Also, the total number of ptys is limited on many systems, and it is good not to waste them unnecessarily.

An asynchronous process is job or function that doesn’t have direct interaction with user. Suppose you have implemented SFDC for a mobile company and the company has millions of customers using its services. Company decides to flag those customers as inactive that have not recharged in the last one year. For this you can create a nightly job (usually by a batch job) to do this activities. Here this job runs in the background and doesn’t have direct interaction with user.
异步进程可以通过pty(伪终端)或管道进行控制。在创建流程时选择pty或pipe，默认情况下，基于变量process-connection-type的值(参见下面)。如果可行，ptys对于用户可见的进程来说通常是更好的选择，比如在Shell模式中，因为它们允许在进程及其子进程之间进行作业控制(C-c, C-z等)，并且因为交互程序将ptys视为终端设备，而管道不支持这些特性。但是，对于Lisp程序用于内部目的的子进程(即，不需要用户与子进程交互)，在子进程和Lisp程序之间需要交换大量数据的情况下，通常使用管道更好，因为管道更有效。另外，许多系统上的ptys总数是有限的，最好不要不必要地浪费它们。
异步流程是指与用户没有直接交互的作业或功能。假设您已经为一家移动公司实现了SFDC，该公司有数百万客户使用其服务。公司决定将那些在过去一年内没有充电的客户标记为非活跃用户。为此，您可以创建一个夜间作业(通常通过批处理作业)来执行这些活动。在这里，该作业在后台运行，与用户没有直接的交互。

1.1.6association class（关联类）

查找名词 association class（关联类）
名词解说 a class that is part of an association relationship between two other classes.
查找网址 https://www.ibm.com/support/knowledgecenter/SSCLKU_7.5.5/com.ibm.xtools.modeler.doc/topics/cassnclss.html
https://www.jguru.com/faq/view.jsp?EID=100819

查找时间 2020/9/22
详细解释
In UML diagrams, an association class is a class that is part of an association relationship between two other classes.
You can attach an association class to an association relationship to provide additional information about the relationship. An association class is identical to other classes and can contain operations, attributes, as well as other associations.

For example, a class called Student represents a student and has an association with a class called Course, which represents an educational course. The Student class can enroll in a course. An association class called Enrollment further defines the relationship between the Student and Course classes by providing section, grade, and semester information related to the association relationship.

As the following figure illustrates, an association class is connected to an association by a dotted line.
在UML图中，关联类是作为其他两个类之间关联关系的一部分的类。
您可以将关联类附加到关联关系，以提供关于该关系的附加信息。关联类与其他类相同，可以包含操作、属性以及其他关联。
例如，一个名为Student的类代表一个学生，并与一个名为Course的类有关联，后者代表一个教育课程。学生班可以注册一门课程。一个名为Enrollment的关联类通过提供与关联关系相关的部分、年级和学期信息，进一步定义了学生和课程类之间的关系。
如下图所示，关联类通过虚线连接到关联。

1.1.7behavioral model aspect（行为模型方面）

查找名词 behavioral model aspect（行为模型方面）
名词解说 A model aspect that emphasizes the behavior of the
instances in a system
查找网址 https://file.scirp.org/pdf/JSEA_2013032915342168.pdf
查找时间 2020/9/22
详细解释
Aspect oriented software development is an emerging paradigm of software development. The notion of this technique is separation of concerns which means to implement each concern in a single object in object oriented programming but still there are concerns which are distributed on different objects and are called crosscutting concerns while another form is Core concerns are the core fun ctionality provided by the system but cro sscutting concerns are the concerns like logging, performance etc. Modeling of aspect oriented software is different from the normal modeling of object-ori- ented or procedural language software, because aspects don’t have the independent identity or existence and they are tightly coupled to their woven context so it is difficult to model them. The one aim of our research paper is to explore the domain of Modeling of the aspect oriented software. The goal of this research paper is to give a UML Behavioral modeling techniques in the domain of aspect oriented software development. This technique of generating UML Be-havioral Model for aspects will give better understating of separations concerns.
面向方面的软件开发是一种新兴的软件开发范式。这种技术关注点分离的概念意味着实现每一个关注点在面向对象编程中一个单独的对象,但仍有担忧,分布在不同的对象和被称为横切关注点,而另一种形式是核心关切的核心系统,但提供的乐趣ctionality cro sscutting担忧关切像日志记录、性能等。面向方面软件的建模不同于面向对象软件或过程语言软件的常规建模，因为面向方面没有独立的身份或存在性，而且它们与它们编织的上下文紧密耦合，因此很难对它们建模。本文的目的之一是探索面向方面软件的建模领域。本文的研究目标是给出面向方面软件开发领域中的UML行为建模技术。这种为方面生成UML Be-havioral模型的技术将更好地理解分离关注点。

1.1.8binary association（二元关联）

查找名词 binary association（二元关联）
名词解说 An association between two classes. A special case of an n
ary association.
查找网址 https://www.sciencedirect.com/topics/computer-science/binary-association

查找时间 2020/9/22
详细解释
Transforming the Conceptual Data Model to SQL
Toby Teorey, … H.V. Jagadish, in Database Modeling and Design (Fifth Edition), 2011

Binary Relationships
A one-to-one binary relationship between two entities is illustrated in Figure 5.1(a)–©. Note that the UML-equivalent binary association is given in Figure 5.2(a)–©.

When both entities are mandatory (Figure 5.1a), each entity becomes a table, and the key of either entity can appear in the other entity’s table as a foreign key. One of the entities in an optional relationship (see Department in Figure 5.1b) should contain the foreign key of the other entity in its transformed table. Employee, the other entity in Figure 5.1(b), could also contain a foreign key (dept_no) with nulls allowed, but this would require more storage space because of the much greater number of Employee entity instances than Department instances. When both entities are optional (Figure 5.1c), either entity can contain the embedded foreign key of the other entity, with nulls allowed in the foreign keys.

The one-to-many relationship can be shown as either mandatory or optional on the “many” side, without affecting the transformation. On the “one” side it may be either mandatory (Figure 5.1d) or optional (Figure 5.1e). In all cases the foreign key must appear on the “many” side, which represents the child entity, with nulls allowed for foreign keys only in the optional “one” case. Foreign key constraints are set according to the specific meaning of the relationship and may vary from one relationship to another.

The many-to-many relationship, shown in Figure 5.1(f) as optional for both entities, requires a new table containing the primary keys of both entities. The same transformation applies to either the optional or mandatory case, including the fact that the “not null” clause must appear for the foreign keys in both cases. Note also that an optional entity means that the SQL table derived from it may have zero rows for that particular relationship. This does not affect “null” or “not null” in the table definition.
The white diamond indicates a shared aggregation where the part may belong to different wholes at the same time. In Figure 6.20, a given Item must be part of an Order, but also may be part of a Sale.

Composite and shared aggregation are special associations and should be used with much parsimony, that is, they should be used only when the team is sure that it is the case that an object is really part of another, and not just a normal association. Even the UML specification (Object Management Group, 2011) states that the precise semantics of a shared aggregation varies between application areas and modelers.

It is common to see aggregation and composition being abused in models, when objects that are not part-whole related are linked by that kind of association. For example, a customer is not part of an order, if not for any other reason but the fact that a customer is a person and an order is not a physical thing, but a transaction. Composite and shared aggregations should unite elements of the same nature: physical with physical, and abstract with abstract. An order may be associated to a customer, but the order is not made of customers.

There are few real advantages in using aggregation in conceptual modeling. This is another reason to minimize or even abolish their use in conceptual models. Among the advantages is that composite or shared aggregation parts usually have attributes that are combined and derived in the whole. For example, the total value of an order is the sum of its items; the weight of a package is the sum of the weight of each book; when a car is sold, all its parts are sold too; and so on. However, these concerns usually appear only at design time.

将概念数据模型转换为SQL
托比Teorey,……《数据