GVC750BE101 3BHE009681R0101 可控硅IGCT模块

GVC750BE101 3BHE009681R0101 可控硅IGCT模块 

UML中的子类型概念通常导致子类从
超类型：在实体关系（E-R）建模中，仅继承标识键
直接地其他超类型属性在联接操作后可用。
在逻辑级别，关系可能具有基数或添加的其他规则，指示
某事物的一个实例中有多少与另一事物的实例相关
这种关系的必要性，等等。这些概念也可以归因于
例如，眼睛的概念具有颜色的概念。
通常在逻辑层面上，关系被具体化或变得具体或明确。在
逻辑层面，这是在需要说明其他内容的情况下完成的
关系，例如，某物某部分的数量或分类
相关信息，其可能不同于单个元素的分类。
还可能需要考虑规范化，这意味着数据库结构是
为通用查询而修改，并且没有某些不希望的特征
在可能导致数据完整性丢失的插入、更新和删除操作期间。
规范化的好处是发现可能存在的其他业务规则
忽略了标准化的分析严谨性，并确保捕获
业务逻辑。逻辑模型虽然具有比概念模型更多的部分，
企业专家仍然可以理解。在逻辑层面上
建模风格通常用于实体关系或UML类建模。
在物理层面上，信息交换、存储和传输的确切方式，
并确定被处理。在这个层面上，我们谈论的是数据。效率，
考虑了数据使用的可靠性和有保证的重复性。数据类型，确切的
确定存储数据的格式。数据类型需要容纳所有
允许存储或交换的数据必须有效，并且不允许以下格式：
是不允许的。为了提高效率，可以对实体进行非标准化，以便连接操作
不必执行。逻辑关联可以替换为标识符（例如
实体关系图[ERD]中的关联实体或外键或迁移键，或
类模型中的显式标识符属性或关联类）。密钥、标识符和
设置其他查找方式。索引、哈希和其他机制可以设置为
根据要求允许数据访问。物理目标可以是
以下是：
a、 数据库–关系、对象或平面文件。
b、 消息交换格式——文档（如XML）、二进制（如接口定义
语言（IDL））。
c、 控制论（人机），例如打印或屏幕格式，如表单。
核心流程中的使用
信息和数据模型的使用方式如下：
a、 核心流程之间的通用性和互操作性
1.信息模型为企业参与者具体化
对企业以及它们之间的关系非常重要。
2.信息模型可以作为术语标准化的基础
人、机器和人机的概念相互关系
通信。
3.信息模型可以为企业的
人员通过使用分类法和其他关系结构。这个可以
提高内部行动的清晰性、效率、准确性和互操作性
企业
4.信息模型记录了企业关注的范围
以允许与其他感兴趣的社区进行比较的形式显示共同点
利益。
5.COI协调和统一。
6.权威来源识别和管理。
b、 JCIDS和PPBE
54
DM2-信息和数据
http://cio-nii.defense.gov/sites/dodaf20/info_data.html[2011年3月3日下午3:43:12]
1） 数据和信息模型可用于确定

GVC750BE101 3BHE009681R0101 可控硅IGCT模块 

GVC750BE101 3BHE009681R0101 可控硅IGCT模块 

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 modeling.
At the physical-level, the exact means by which the information is to be exchanged, stored,
and processed is determined. At this level, we are talking about data. The efficiency,
reliability, and assured repeatability of the data use are considered. The datatypes, the exact
format in which the data is stored are determined. The datatype needs to accommodate all
the data that is permissible to store or exchange yet be efficient and disallow formats that
are not permissible. The entities may be de-normalized for efficiency so that join operations
don't have to be performed. Logical associations may be replaced with identifiers (e.g., as
associative entities or foreign or migrated keys in Entity Relationship Diagrams [ERDs] or
explicit identifier attributes or association classes in class models). Keys, identifiers, and
other means of lookup are setup. Indexes, hashes, and other mechanisms may be setup to
allow data access in accordance with requirements. The physical target may be any of the
following:
a. Database – relational, object, or flat file.
b. Message exchange format – document (e.g., XML), binary (e.g., Interface Definition
Language (IDL)).
c. Cybernetic (human – machine), e.g., print or screen formats, such as forms.
Usage in Core Processes
Information and Data models are used in the following ways:
a. Commonality and Interoperability between Core processes
1. Information models materialize for enterprise participants what things are
important to the enterprise and how they are related.
2. Information models can serve as a basis for standardization of terminology and
concept inter-relationships for human, machine, and human-machine
communications.
3. Information models can provide cognitive compactness for an enterprise's
personnel through the use of taxonomies and other relationship structures. This can
improve clarity, efficiency, accuracy, and interoperability of action within the
enterprise.
4. Information models document the scope of things the enterprise is concerned with
in a form that allows comparison with other communities of interest to reveal common
interests.
5. COI coordination and harmonization.
6. Authoritative sources identification and management.
b. JCIDS and PPBE
54
DM2 - Information and Data
http://cio-nii.defense.gov/sites/dodaf20/info_data.html[3/3/2011 3:43:12 PM]
1) Data and information models can be used to determ