A002-185-2502-李林

作业A002-185-2502-李林
课程名称 软件需求分析与建模
班级 18软件工程5班
教导教师 董瑞生
李林 1814080902502
日期 2020.12.15

---

目录

---

---

1、Excel查找结合项目主题说明

1.1第一次查词

1.1.1 判定表（Decision table）

https://www.techopedia.com/definition/18829/decision-table-detab

A decision table is used to represent conditional logic by creating a list of tasks depicting business level rules. Decision tables can be used when there is a consistent number of conditions that must be evaluated and assigned a specific set of actions to be used when the conditions are finally met. Decision tables are fairly similar to decision trees except for the fact that decision tables will always have the same number of conditions that need to be evaluated and actions that must be performed even if the set of branches being analyzed is resolved to true. A decision tree, on the other hand, can have one branch with more conditions that need to be evaluated than other branches on the tree.

决策表通过创建描述业务级规则的任务列表来表示条件逻辑。当有一致数量的条件必须进行评估并分配一组特定的操作，当这些条件最终满足时，可以使用决策表。决策表与决策树非常相似，只是决策表始终具有相同数量的需要评估的条件和必须执行的操作，即使所分析的分支集被解析为正确。另一方面，决策树可以有一个分支比树上的其他分支具有更多需要评估的条件。

1.1.2指导委员会（Steering committee）

https://www.reference.com/business-finance/function-steering-committee-5da

The function of a steering committee is to provide support, advocacy and enablement for the projects which they oversee. A steering committee is not designed to actually manage or run a project, and should be kept from doing so. Rather, the steering committee should facilitate the project manager’s ability to plan and direct a given project, giving advice and support along the way.Steering committees function best when the scope of their responsibilities and purposes are clearly defined. They often function as a decision-making body, determining the budgets, time lines and personnel for the projects they oversee. A steering committee should not be loaded up with members who are not needed; instead, every member on the committee should have a specific function tied to oversight, recording of decisions, budgeting or other specific skills needed depending on the project.

指导委员会的职能是为他们监督的项目提供支持、宣传和支持。指导委员会并不是为实际管理或管理一个项目而设计的，应该阻止它这样做。相反，指导委员会应该促进项目经理计划和指导一个给定项目的能力，并在整个过程中提供建议和支持方向。转向当委员会的职责范围和宗旨被明确界定时，委员会的运作最好。他们通常是一个决策机构，决定他们所监督的项目的预算、时间表和人员。指导委员会不应配备不需要的成员；相反，委员会中的每一位成员都应具有与监督、决策记录、预算编制或其他具体技能相关的具体职能，具体取决于项目。

1.1.3类（Class model）

https://www.excelsoftware.com/classmodel

A Class is a standard UML construct used to detail the pattern from which objects will be produced at run-time. A class is a specification - an object an instance of a class. Classes may be inherited from other classes (that is they inherit all the behavior and state of their parent and add new functionality of their own), have other classes as attributes, delegate responsibilities to other classes and implement abstract interfaces. The Class Model is at the core of object-oriented development and design - it expresses both the persistent state of the system and the behavior of the system. A class encapsulates state (attributes) and offers services to manipulate that state (behavior). Good object-oriented design limits direct access to class attributes and offers services which manipulate attributes on behalf of the caller. This hiding of data and exposing of services ensures data updates are only done in one place and according to specific rules - for large systems the maintenance burden of code which has direct access to data elements in many places is extremely high.

类是一个标准的UML构造，用于详细说明在运行时将从中生成对象的模式。类是一个规范-一个对象是一个类的实例。类可以从其他类继承（即继承其父类的所有行为和状态并添加自己的新功能）、将其他类作为属性、将职责委托给其他类并实现抽象接口。类模型是面向对象开发和设计的核心，它表达了系统的持久状态和系统的行为。类封装状态（属性）并提供服务来操作状态（行为）。好的面向对象设计限制了对类属性的直接访问，并提供了代表调用方操作属性的服务。这种数据隐藏和服务公开确保了数据更新只在一个地方进行，并且根据特定的规则进行——对于大型系统来说，在许多地方可以直接访问数据元素的代码的维护负担非常高。

1.1.4上下文模型（Context model）

http://ctxmodel.net/

Context Model is a divide-and-conquer method based on separation of data into subsequences by context, so that each subsequence can be approximated with a simple model (usually memoryless) while still providing a good overall precision. Most widely used CM subclass is PPM, which concentrates on a single context model due to performance considerations and switches to other contexts only if the main model fails. This allows PPM compressors to keep competitive speed at the cost of some prediction imprecision showing as redundancy. Another known subclass is Context Mixing, which linearly combines the predictions of several submodels. More complex schemes with secondary models using the primary predictions as context seem to remain anonymous. Then, there’s yet another approach which also approximates complex data with simple model but by a static data transformation (LZ, Block Sorting, Symbol Ranking). Strange as it may seem, CM too is only a speed/redundancy tradeoff stage, as an ultimate modelling method is to find a function which generates given data. There’re even some practical applications for this in the cases with known source model, then parameters can be determined by maximum likelihood.

模型是一种分而治之的方法，它将数据按上下文分解为子序列，这样每个子序列都可以用一个简单的模型（通常是无记忆的）来近似，同时仍然提供了良好的整体精度。最广泛使用的CM子类是PPM，出于性能考虑，它集中于单个上下文模型，只有在主模型失败时才会切换到其他上下文。这使得PPM压缩器能够保持具有竞争力的速度，但代价是某些预测不精确，显示为冗余。另一个已知的子类是上下文混合，它线性地组合了几个子模型的预测。更复杂的方案与次级模型使用主要预测作为上下文似乎是匿名的。然后，还有另一种方法，用简单的模型来近似复杂的数据，但是通过静态数据转换（LZ、块排序、符号排序）。奇怪的是，CM也只是一个速度/冗余的权衡阶段，因为最终的建模方法是找到一个生成给定数据的函数。在已知源模型的情况下，甚至有一些实际应用，然后用极大似然法确定参数。

1.1.5操作顺序（Action sequence）

https://wiki.pentaho.com/display/ServerDoc2x/03.+Action+Sequences

The Action Sequence is an XML document that defines the smallest complete task that the solution engine can perform. It is executed by a very lightweight process flow engine and defines the order of execution of one or more the components of the Pentaho BI Platform. We avoid calling this a process flow because it is missing many of the capabilities of a true process flow engine. It is good for sequencing small, linear, success oriented tasks like reporting and bursting. It has the ability to loop through a result set, call another Action Sequence and conditionally execute components. The Action Sequence document should have a “.xaction” suffix.

操作序列是一个XML文档，它定义了解决方案引擎可以执行的最小的完整任务。它由一个非常轻量级的流程引擎执行，并定义Pentaho BI平台的一个或多个组件的执行顺序。我们避免将其称为流程流，因为它缺少真正流程流引擎的许多功能。它有利于排序小，线性，面向成功的任务，如报告和爆破。它能够遍历一个结果集，调用另一个操作序列并有条件地执行组件。操作序列文档应具有“.xaction”后缀。

1.1.6数据流图（dataflow diagram）

https://www.lucidchart.com/pages/data-flow-diagram
https://www.visual-paradigm.com/guide/data-flow-diagram/what-is-data-flow-diagram/

A data flow diagram (DFD) maps out the flow of information for any process or system. It uses defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs, outputs, storage points and the routes between each destination. Data flowcharts can range from simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that dig progressively deeper into how the data is handled. They can be used to analyze an existing system or model a new one. Like all the best diagrams and charts, a DFD can often visually “say” things that would be hard to explain in words, and they work for both technical and nontechnical audiences, from developer to CEO. That’s why DFDs remain so popular after all these years. While they work well for data flow software and systems, they are less applicable nowadays to visualizing interactive, real-time or database-oriented software or systems.
Also known as DFD, Data flow diagrams are used to graphically represent the flow of data in a business information system. DFD describes the processes that are involved in a system to transfer data from the input to the file storage and reports generation.

Data flow diagrams can be divided into logical and physical. The logical data flow diagram describes flow of data through a system to perform certain functionality of a business. The physical data flow diagram describes the implementation of the logical data flow.
DFD graphically representing the functions, or processes, which capture, manipulate, store, and distribute data between a system and its environment and between components of a system. The visual representation makes it a good communication tool between User and System designer. Structure of DFD allows starting from a broad overview and expand it to a hierarchy of detailed diagrams. DFD has often been used due to the following reasons:
Logical information flow of the system
Determination of physical system construction requirements
Simplicity of notation
Establishment of manual and automated systems requirements

数据流图（DFD）描绘出任何过程或系统的信息流。它使用定义好的符号（如矩形、圆圈和箭头）以及短文本标签来显示数据输入、输出、存储点和每个目的地之间的路由。数据流程图可以从简单的甚至手绘的过程概览到深入挖掘数据处理方式的深入、多级DFD。它们可用于分析现有系统或为新系统建模。像所有最好的图表一样，DFD通常可以直观地“说出”难以用语言解释的事情，它们为技术和非技术受众工作，从开发人员到CEO。这就是为什么DFD在这么多年后仍然如此受欢迎。虽然它们适用于数据流软件和系统，但现在不太适用于可视化交互式、实时或面向数据库的软件或系统。
也称为DFD，数据流图用于以图形方式表示业务信息系统中的数据流。DFD描述了系统中涉及的将数据从输入传输到文件存储和生成报告的过程。
数据流图可分为逻辑流图和物理流图。逻辑数据流图描述了通过系统执行业务特定功能的数据流。物理数据流图描述了逻辑数据流的实现。
以图形方式表示功能或过程的DFD，这些功能或过程捕获、操作、存储和分发系统与其环境之间以及系统组件之间的数据。可视化表示使其成为用户与系统设计者之间的良好沟通工具。DFD的结构允许从一个广泛的概述开始，并将其扩展到一个详细的图的层次结构。由于以下原因，经常使用DFD：
系统逻辑信息流
物理系统建设要求的确定
符号的简单性
建立手动和自动系统要求

1.1.7主动类（Active class）

https://www.lucidchart.com/pages/uml-class-diagram

Class diagrams are one of the most useful types of diagrams in UML as they clearly map out the structure of a particular system by modeling its classes, attributes, operations, and relationships between objects. With our UML diagramming software, creating these diagrams is not as overwhelming as it might appear. This guide will show you how to understand, plan, and create your own class diagrams.
One of the more popular types in UML is the class diagram. Popular among software engineers to document software architecture, class diagrams are a type of structure diagram because they describe what must be present in the system being modeled. No matter your level of familiarity with UML or class diagrams, our UML software is designed to be simple and easy to use.UML was set up as a standardized model to describe an object-oriented programming approach. Since classes are the building block of objects, class diagrams are the building blocks of UML. The various components in a class diagram can represent the classes that will actually be programmed, the main objects, or the interactions between classes and objects. The class shape itself consists of a rectangle with three rows. The top row contains the name of the class, the middle row contains the attributes of the class, and the bottom section expresses the methods or operations that the class may use. Classes and subclasses are grouped together to show the static relationship between each object.

UML中比较流行的一种类型是类图。类图是一种结构图，在软件工程师中很流行，因为类图描述了被建模的系统中必须存在的内容。无论您对UML或类图的熟悉程度如何，我们的UML软件都是设计为简单和易于实现的使用.UML作为一个标准化的模型来描述面向对象的编程方法。因为类是对象的构建块，所以类图是UML的构建块。类图中的各种组件可以表示实际编程的类、主要对象或类与对象之间的交互。类形状本身由一个有三行的矩形组成。顶行包含类的名称，中间一行包含类的属性，底部部分表示类可能使用的方法或操作。类和子类被组合在一起以显示每个对象之间的静态关系。
类图是UML中最有用的图表类型之一，因为类图通过对特定系统的类、属性、操作和对象之间的关系进行建模来清晰地描绘出特定系统的结构。使用我们的UML图表软件，创建这些图表并不像看上去那么令人难以接受。本指南将向您展示如何理解、规划和创建您自己的类图。

1.1.8构件图（Component diadram）

https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-component-diagram/
https://www.tutorialspoint.com/uml/uml_component_diagram.htm

UML Component diagrams are used in modeling the physical aspects of object-oriented systems that are used for visualizing, specifying, and documenting component-based systems and also for constructing executable systems through forward and reverse engineering. Component diagrams are essentially class diagrams that focus on a system’s components that often used to model the static implementation view of a system.
Component diagrams are different in terms of nature and behavior. Component diagrams are used to model the physical aspects of a system. Now the question is, what are these physical aspects? Physical aspects are the elements such as executables, libraries, files, documents, etc. which reside in a node.
Component diagrams are used to visualize the organization and relationships among components in a system. These diagrams are also used to make executable systems.
Component diagram is a special kind of diagram in UML. The purpose is also different from all other diagrams discussed so far. It does not describe the functionality of the system but it describes the components used to make those functionalities.
Thus from that point of view, component diagrams are used to visualize the physical components in a system. These components are libraries, packages, files, etc.
Component diagrams can also be described as a static implementation view of a system. Static implementation represents the organization of the components at a particular moment.
A single component diagram cannot represent the entire system but a collection of diagrams is used to represent the whole.
The purpose of the component diagram can be summarized as −
Visualize the components of a system.
Construct executables by using forward and reverse engineering.
Describe the organization and relationships of the components.

UML组件图用于建模面向对象系统的物理方面，这些面向对象系统用于可视化、指定和记录基于组件的系统，还用于通过正向和反向工程构建可执行系统。组件图本质上是一个类图，它关注于一个系统的组件，这些组件通常用于为系统的静态实现视图建模。
组件图在性质和行为方面是不同的。组件图用于对系统的物理方面进行建模。现在的问题是，这些物理方面是什么？物理方面是诸如可执行文件、库、文件、文档等驻留在节点中的元素。
组件图用于可视化系统中组件之间的组织和关系。这些图表也被用来制作可执行系统。
组件图是UML中一种特殊的图。其目的也不同于迄今为止讨论的所有其他图表。它不描述系统的功能，但描述了用于实现这些功能的组件。
因此，从这个角度来看，组件图用于可视化系统中的物理组件。这些组件是库、包、文件等。
组件图也可以描述为系统的静态实现视图。静态实现表示组件在特定时刻的组织。
单个组件图不能代表整个系统，但是使用一组图来表示整个系统。
部件图的用途可概括为–
可视化系统的组件。
使用正向和反向工程构造可执行文件。
描述组件的组织和关系。

1.1.9复合聚合（Composite aggregation）

https://www.uml-diagrams.org/composition.html

Composite aggregation (composition) is a “strong” form of aggregation with the following characteristics:

it is binary association,
it is a whole/part relationship,
a part could be included in at most one composite (whole) at a time, and
if a composite (whole) is deleted, all of its composite parts are “normally” deleted with it.
Note, that UML does not define how, when and specific order in which parts of the composite are created. Also, in some cases a part can be removed from a composite before the composite is deleted, and so is not necessarily deleted as part of the composite.

复合聚合（composition）是一种“强”聚合形式，具有以下特点：
它是二元关联，
这是一种整体/部分关系，
一次最多可以将一个部件包括在一个组合（整体）中，并且
如果删除了一个组合（整体），则其所有组合部分都将“正常”删除。
注意，UML并没有定义如何、何时和特定的顺序来创建组合的各个部分。此外，在某些情况下，可以在删除组合之前从组合中删除零件，因此不必作为组合的一部分删除。

1.1.10具体类(concrete class)

https://www.geeksforgeeks.org/difference-between-abstract-class-and-concrete-class-in-java/

A concrete class in Java is a type of subclass, which implements all the abstract method of its super abstract class which it extends to. It also has implementations of all methods of interfaces it implements.
Java中的一个具体类是一种子类，它实现了它扩展到的超抽象类的所有抽象方法。它还实现了它实现的所有接口方法。

1.1.11基本类型(primitive type)

https://www.uml-diagrams.org/data-type.html

A primitive type is a data type which represents atomic data values, i.e. values having no parts or structure. A primitive data type may have precise semantics and operations defined outside of UML, for example, mathematically.
Standard UML primitive types include:
Boolean,Integer,Instances of primitive types do not have identity. If two instances have the same representation, then they are indistinguishable.
A primitive type has the keyword «primitive» above or before the name of the primitive type.

基元类型是表示原子数据值的数据类型，即没有部分或结构的值。一个原始数据类型可能有精确的语义和在UML之外定义的操作，例如，在数学上。
标准UML原语类型包括：
布尔值，整数等。
基元类型的实例没有标识。如果两个实例具有相同的表示，则它们无法区分。
基元类型在基元类型名称的上方或前面有关键字primitive。

1.1.12关联类(association class)

https://www.thoughtco.com/association-2034002#:~:text=The%20association%20relationship%20indicates%20that%20a%20class%20knows,is%20through%20the%20use%20of%20an%20instance%20field.

The association relationship indicates that a class knows about, and holds a reference to, another class. Associations can be described as a “has-a” relationship because the typical implementation in Java is through the use of an instance field. The relationship can be bi-directional with each class holding a reference to the other. Aggregation and composition are types of association relationships.
Associations join one or more of one thing against one or more of another thing. A professor might be associated with a college course (a one-to-one relationship) but also with each student in her class (a one-to-many relationship). The students in one section might be associated with the students in another section of the same course (a many-to-many relationship) while all the sections of the course relate to a single course (a many-to-one relationship).

关联关系表示一个类知道另一个类并持有对另一个类的引用。关联可以被描述为“has-a”关系，因为Java中的典型实现是通过使用实例字段实现的。这种关系可以是双向的，每个类都持有对另一个类的引用。聚合和组合是关联关系的类型。
关联将一个或多个事物与一个或多个另一个事物联系起来。教授可能与大学课程有关（一对一的关系），但也可能与她班上的每个学生（一对多的关系）。一个部分的学生可能与同一课程的另一个部分的学生相关联（多对多关系），而该课程的所有部分都与单个课程相关（多对一关系）。

1.1.13类图(class diagram)

https://www.guru99.com/uml-class-diagram.html#:~:text=Class%20Diagram%20defines%20the%20types%20of%20objects%20in,Methods.%20A%20class%20can%20refer%20to%20another%20class.

UML CLASS DIAGRAM gives an overview of a software system by displaying classes, attributes, operations, and their relationships. This Diagram includes the class name, attributes, and operation in separate designated compartments.
Class Diagram defines the types of objects in the system and the different types of relationships that exist among them. It gives a high-level view of an application. This modeling method can run with almost all Object-Oriented Methods. A class can refer to another class. A class can have its objects or may inherit from other classes.
Class Diagram helps construct the code for the software application development.

UML类图通过显示类、属性、操作和它们之间的关系来提供软件系统的概述。这个图包括类名、属性和操作在不同的指定分区中。
类图定义系统中对象的类型以及它们之间存在的不同类型的关系。它提供了应用程序的高级视图。这种建模方法几乎可以与所有面向对象的方法一起运行。一个类可以引用另一个类。一个类可以有它的对象，也可以从其他类继承。
类图帮助构造软件应用程序开发的代码

1.1.14非功能性需求( Non-functional requirement)

https://www.guru99.com/non-functional-requirement-type-example.html

NON-FUNCTIONAL REQUIREMENT (NFR) specifies the quality attribute of a software system. They judge the software system based on Responsiveness, Usability, Security, Portability and other non-functional standards that are critical to the success of the software system. Example of nonfunctional requirement, “how fast does the website load?” Failing to meet non-functional requirements can result in systems that fail to satisfy user needs.
Non-functional Requirements allows you to impose constraints or restrictions on the design of the system across the various agile backlogs. Example, the site should load in 3 seconds when the number of simultaneous users are > 10000. Description of non-functional requirements is just as critical as a functional requirement.

非功能需求（NFR）规定了软件系统的质量属性。他们根据响应性、可用性、安全性、可移植性和其他非功能性标准来判断软件系统，这些标准对软件系统的成功至关重要。非功能需求的例子，“网站加载速度有多快？“未能满足非功能性需求可能导致系统无法满足用户需求。
非功能性需求允许您在各种敏捷积压工作中对系统的设计施加约束或限制。例如，当并发用户数大于10000时，站点应在3秒内加载。非功能性需求的描述与功能性需求同样重要

1.1.15需求分析(Requirements analysis)

https://www.visual-paradigm.com/guide/requirements-gathering/requirement-analysis-techniques/

Requirement Analysis, also known as Requirement Engineering, is the process of defining user expectations for a new software being built or modified. In software engineering, it is sometimes referred to loosely by names such as requirements gathering or requirements capturing. Requirements analysis encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements.

需求分析，也称为需求工程，是定义用户对正在构建或修改的新软件的期望的过程。在软件工程中，它有时被松散地称为需求收集或需求捕获。需求分析包括确定满足新的或变更的产品或项目的需求或条件的任务，考虑到不同涉众的可能冲突的需求，分析、记录、验证和管理软件或系统需求。

1.1.16二元关联(binary association)

https://www.uml-diagrams.org/association-reference.html

Binary association relates two typed instances. It is normally rendered as a solid line connecting two classifiers, or a solid line connecting a single classifier to itself (the two ends are distinct). The line may consist of one or more connected segments.

二进制关联关系两个类型化实例。分类器本身就是一条连接两条线的实体线。直线可以由一个或多个连接的线段组成

1.1.17系统边界(system boundary)

https://www.sciencedirect.com/topics/agricultural-and-biological-sciences/system-boundary

The establishment of system boundaries for an analysis refers to identifying and justifying which aspects of the product life cycle are to be included in a life cycle assessment study (ISO, 2006). Since specific activities and their associated resource use and emission profiles will be of variable importance to the spectrum of potential impact indicators that might be considered in a study, system boundary decisions should, at least in part, be informed by the particular suite of sustainability impacts that are of interest. For studies focusing on potential interactions between nutritional considerations and sustainability impacts (including human health), it will be important to ensure that the system boundaries are established such that all life cycle activities having bearing on one or more of these concerns are included. For example, inclusion of even small inputs of certain pesticides applied in crop agriculture may be unimportant from the perspective of resource use or greenhouse gas emissions, but essential to include for assessment of potential human and ecosystem toxicity impacts. Here, the concept of cut-off criteria in LCA, which refers to established thresholds for exclusion of flows of marginal importance, is particularly significant.

为分析建立系统边界是指确定并证明产品生命周期的哪些方面将被纳入生命周期评估研究（ISO，2006）。由于具体活动及其相关的资源利用和排放概况对研究中可能考虑的潜在影响指标范围具有不同的重要性，因此系统边界的决定至少应部分地由感兴趣的一系列可持续性影响来决定。对于侧重于营养因素和可持续性影响（包括人类健康）之间潜在相互作用的研究，必须确保系统边界的建立，以便包括与一个或多个这些关注点有关的所有生命周期活动。例如，从资源利用或温室气体排放的角度来看，包括在作物农业中使用的某些杀虫剂的哪怕是很小的投入可能并不重要，但对于评估潜在的人类和生态系统毒性影响至关重要。在这里，生命周期评价中的截止标准的概念特别重要，它指的是排除边际重要性流量的既定阈值。