5SHY3545L0010 3BHB013088R0001 高压变频器IGCT可控硅

5SHY3545L0010 3BHB013088R0001 高压变频器IGCT可控硅 

建筑描述。体系结构描述的两个子类型被调用-
AV-1和清单-由于它们在发现和交换中的重要性，
分别地注意，AV-1信息也可以以结构化的方式提供
使用项目数据组描述架构项目的目标，
时间线、活动、资源、产品、规则、措施等
在开发项目中，体系结构描述将越来越详细，
约翰·扎克曼称之为“物化水平”。
应该注意的是，所有方法，即使是哲学和方法，都涉及
获取企业流程、遗留信息保存系统的一些记录，
以及对其认为处理的类型的描述。在收集此原始数据时
数据，其中的术语是：
a、 确定。这是通过记录重复出现或关键术语来实现的。
b、 理解。寻求和研究术语的定义。在大多数情况下，有
多个权威定义。所选定义应适用于
在企业活动中使用该术语的上下文。
c、 整理和关联。这是通过将看似相似或相关的术语分组来实现的。
d、 和谐。在此步骤中，将识别别名、近别名和复合项。A.
共识定义是根据权威来源定义制定的。经常
超级子类型和整体-部分关系开始出现。
下一步是关联协调术语。一些关系隐含在
定义和这些定义可能有助于关系描述。此时，
形式可能会有所不同。正式的本体论方法将所有关系类型化为
基本概念，如整体、部分和超子类型。然而，有很多
这种方法的形而上学挑战，对许多人来说是不必要的
应用。这构成了建模、定义和相关术语的概念层面，
现在被认为是概念，因为定义和关系赋予
条款。概念模型应该为任何了解
企业超亚型和整体-部分关系可以提供认知经济。
概念模型可以以实体、关系或UML类模型样式完成，尽管有
记录定义和关系的格式在功能上是等效的。请注意
53
DM2-信息和数据
http://cio-nii.defense.gov/sites/dodaf20/info_data.html[2011年3月3日下午3:43:12]
UML中的子类型概念通常导致子类从
超类型：在实体关系（E-R）建模中，仅继承标识键
直接地其他超类型属性在联接操作后可用。
在逻辑级别，关系可能具有基数或添加的其他规则，指示
某事物的一个实例中有多少与另一事物的实例相关
这种关系的必要性，等等。这些概念也可以归因于
例如，眼睛的概念具有颜色的概念。
通常在逻辑层面上，关系被具体化或变得具体或明确。在
逻辑层面，这是在需要说明其他内容的情况下完成的
关系，例如，某物某部分的数量或分类
相关信息，其可能不同于单个元素的分类。
还可能需要考虑规范化，这意味着数据库结构是
为通用查询而修改，并且没有某些不希望的特征
在可能导致数据完整性丢失的插入、更新和删除操作期间。
规范化的好处是发现可能存在的其他业务规则
忽略了标准化的分析严谨性，并确保捕获
业务逻辑。逻辑模型虽然具有比概念模型更多的部分，
企业专家仍然可以理解。在逻辑层面上
通常使用建模样式，如实体关系或UML类建模

5SHY3545L0010 3BHB013088R0001 高压变频器IGCT可控硅 

5SHY3545L0010 3BHB013088R0001 高压变频器IGCT可控硅 

an Architectural Description. Two subtypes of Architectural Description are called out -
the AV-1 and the Manifest - because of their importance in discovery and exchange,
respectively. Note that the AV-1 information can also be provided in a structured
manner, using the Project data group to describe the architecture project's goals,
timeline, activities, resources, productions, rules, measures, etc. In a typical
development project, the architecture descriptions will be at increasing levels of detail,
what John Zachman calls "levels of reification".
It should be noted that all methods, even the most philosophical and methodical, involve the
ingestion of some record of the enterprise's processes, legacy information-keeping systems,
and descriptions of what types of things it thinks it deals with. Upon collection of this raw
data, terms within it are then:
a. Identified. This is done by noting recurring or key terms.
b. Understood. Definitions of terms are sought and researched. In most cases, there are
multiple authoritative definitions. Definitions selected should be appropriate for the
context of use of the term within the enterprise activities.
c. Collated and correlated. This is done by grouping seemingly similar or related terms.
d. Harmonized. In this step, aliases, near-aliases, and composite terms are identified. A
consensus definition is formulated from the authoritative source definitions. Often
super-subtype and whole-part relationships begin to emerge.
The next step is to relate the harmonized terms. Some of the relationships are implicit in the
definitions and these definitions may contribute to the relationship description. At this point,
the formality can vary. A formal ontological approach will type all relationships to
foundational concepts such as whole-part and super-subtype. However, there are many
metaphysical challenges with such an approach and it is not necessary for many
applications. This constitutes the conceptual-level of modeling, defined and related terms,
now considered concepts because the definitions and relationships lend a meaning to the
terms. The conceptual model should be understandable by anyone knowledgeable about the
enterprise. Super-subtype and whole-part relationships can provide cognitive economy.
Conceptual models can be done in Entity-Relationship or UML Class model style although any
format that documents definitions and relationships is functionally equivalent. Note that the
53
DM2 - Information and Data
http://cio-nii.defense.gov/sites/dodaf20/info_data.html[3/3/2011 3:43:12 PM]
subtype concept in UML generally results in the subclass inheriting properties from the
supertype while in Entity-Relationship (E-R) modeling only the identifying keys are inherited
directly; the other supertype properties are available after a join operation.
At the logical-level, relationships may have cardinalities or other rules added that indicate
how many of one instance of something relates to an instance of something else, the
necessity of such relations, and so on. The concepts may also be attributed, meaning they
will be said to have some other concept, e.g., the concept of eye has the concept of color.
Often at the logical-level, the relationships are reified or made concrete or explicit. At the
logical-level, this is done in case there is something additional that needs to be stated about
the relationship, e.g., the quantity of some part of something or the classification of the
related information, which may be different from the classification of the individual elements.
There may also be considerations of normalization, meaning that the database structure is
modified for general-purpose querying and is free of certain undesirable characteristics
during insertion, update, and deletion operations that could lead to a loss of data integrity.
The benefits of normalization are to uncover additional business rules that might have been
overlooked without the analytical rigor of normalization and ensure the precise capture of
business logic. The logical model, though having more parts than the conceptual model,
should still be understandable by enterprise experts. At the logical-level, some sort of
modeling style is normally used such as Entity-Relationship or UML Class modelin