Handnote(a simplified e version)

T-Form ER DataModeling

HandNote (a Simplifier Version)

SYSTEMS DESIGN Co.,Ltd

S.Toriyabe

NOTATION

T-Form ER Data Modeling

2015 Copyright, All rights reserved. SYSTEMS DESIG Co.,Ltd 2

Notation


T-form ER Data Modeling incorplated the notation of the Superset/Subsets.

Superset

Header

Details

Notation


Header and Details

Superset

(Entity Name here)

Header

Details

Notation


Superset

Subset

Subset

Superset / Subset

Superset

Classificatio

n

Subset

Subset

The Superset subsets of Diference

The Superset Subset of isomorphicC

lassification

Notation


ENTITY RECURSIVE

Recursive

Notation


RESOURCE RESOURCE

QUASI-EVENT

Quasi Event

Notation


EVENT EVENT

MAPPING LIST

Mapping List

Notation


RESOURCE VIRTUAL ENTITY

EVENT VIRTUAL ENTITY

Virtual Entity

Notation


RESOURCE ENTITY ROLE

EVENT ENTITY ROLE

Entity Role

Notation


0 or 1 From１ to Many

Cardinality Constraints

The Symbols of cardinality Constraints

Notation


Entity Name

Identifier

Reuse_1(R)

Reuse_2(R)

・・・Reuse_n(R)

Attribute_1

Attribute_2

・・・Attribute_n

En

tity T

yp

e

The position of denotes

Notation


E: EVENT

R: RESOURCE

VE: VURTUAL ENTITY

ER: ENTITY ROLE

TS: QUASI ENTITY

ML: MAPPING LIST

Credit Check

CreditCheckRequestNo.

CustomerNo.(R)

Customer_Name

Request_Date

Credit_Limit_AMT

・・・

E

The position of the denotes

Notation


Identifier

Among the data items that

are included in an

observation entities , which

corresponds to the identifie

Reuse(R)

Individual

indicator(Identifier) of other

entities is equivalent to this .

Reuse is inserted by the

occurrence of Relationship.

Identifier and Reuse

Entity Name

Identifier

Reuse_1(R)

Reuse_2(R)

・・・Reuse_n(R)

Attribute_1

Attribute_2

・・・Attribute_n

En

tity T

yp

e

Notation


Attrributes

Which corresponds to the

data items that are included

in an observation target

entity

Date and Timestamp

Text and description

Value

Derivation

Boolean

Binary Data

Others and Copy from

other Entities

Credit Check

CreditCheckRequestNo.

CustomerNo.(R)

Customer_Name

Request_Date

Credit_Limit_AMT

・・・

E

The Attributes

A Examples of “QUASI EVENT”


Pref.ID. Pref_Name CityID. City_Name Ward_ID Ward_Name

Pref City Ward

Pref・City・Ward・QE

PrefID(R)

CityID(R)

WardID(R)

Pref_Name(d)

City_Name(d)

Ward_Name(d)

Pref・City・QE

PrefID(R)

CityID(R)

City・Ward・QE

CityID(R)

WardID(R)

R R R

TS TS

TS

A Examples of “QUASI EVENT”_(cont.)


Pref.ID. Pref_Name CityID. City_Name Ward_ID Ward_Name

Pref City Ward

Pref・City・Ward・QE

PrefID(R)

CityID(R)

WardID(R)

Pref_Name(d)

City_Name(d)

Ward_Name(d)

Pref・City・QE

PrefID(R)

CityID(R)

R R R

TS

TS

商談DTL

A Example of Entities


商談

商談HDR

商談No.

H_Rev.No.

リードNo.(R)

商談日予算

案件化予定日

要望総額（D)

対応時間

商談明細No

D_Rev.No...

商談No.(R)

H_revNo.(R)

品番(R)

商談詳細メモ

要望金額要望数量希望納期

リード

リードNo. 氏名職位

所属部署(d)

商談品目

品番商談許可期日

品名説明

提供価格決定方式メモ

R

R

E

E

The Notation rules for Event -based Entity

1. The Event -based Entity inherit the identifier of the Resource

-based Entity by the Relationship as Reuse.

2. When a relationship is drawn to the event from the event ,

inheritance destination is to inherit the identifier of the

original side

3. However , if the relationship of the original side of the

cardinality constraint of "n", the new correspondence table

“Mapping List” is generated .


The Notation rules for Event -based Entity

1. It’s not an Event -based Entity to Entity

The Entities other than the Event -based Entity that has the Identifier

is a Resource -based Entities

2. The relationships between Resource -based Entity , the

Quasi-Event occurs.

It ‘s not affected by the cardinality constraint.


Date post:	09-Aug-2015
Category:	Technology
Upload:	-
View:	67 times
Download:	1 times

Handnote(a simplified e version)

Technology