Name: The Conceptual Data Model (Part 2)
Brand: salesforceempress.com
SKU: salesforceempress-com-1
Availability: OnlineOnly

critic

The Conceptual Data Model (Part 2)

preview

Understanding the relationships between objects is critical to building a great data model. One way to easily formulate these relationships is to create a syntax formula.
Describe the business association between 2&nbsp;Objects
Define a “Business Rule” of the business area
Read the business rules in a clockwise direction, using the following syntax:
Each
Object A (Opportunity)
Relationship name (is assigned to)
Cardinality
Zero to One
Zero to Many
One and Only One
One or more
Object B (Account)
The minimum cardinality represents the minimum number of records that can be related to the other object in the relationship. For example, each opportunity is assigned to a minimum of one account. In other words, an opportunity must be assigned an account.
The maximum cardinality represents the maximum number of one record that can be related to the other object. For example, each account enables many opportunities. In other words, an account may enable one or more opportunities.
When modeling a relationship, make sure to consider if you are modeling a “point in time” or a “period of time”. For example: An Account may only be allowed to have one open opportunity at a time.
This can be modeled using “Audit Trails” or “Snapshots”. Audit trails capture changes to the initial state. Snapshots capture values prior to the current state.
A recursive relationship exists when an entity is related to itself. This is sometimes called a “self-referencing relationship” It is usually optional at both ends.
Not every relationship is necessary to include in your data model. If the relationship can be inferred based on other details, then it doesn’t need to be included in your data model. For example, if you have a relationship between the account and opportunity and between the opportunity and opportunity line items, you don’t need to draw a relationship between the account and the opportunity line items.
A conceptual data model can be used for a number of purposes, including
&nbsp;

Understanding the relationships between objects is critical to building a great data model. One way to easily formulate these relationships is to create a syntax formula.
Describe the business association between 2&nbsp;Objects
Define a “Business Rule” of the business area
Read the business rules in a clockwise direction, using the following syntax:
Each
Object A (Opportunity)
Relationship name (is assigned to)
Cardinality
Zero to One
Zero to Many
One and Only One
One or more
Object B (Account)
The minimum cardinality represents the minimum number of records that can be related to the other...

public

All posts

salesforceempress.com

Credible

Speculation

Anecdotal Evidence

Generalization

Stacking the Deck

Appeal to Authority

Straw Man

Slippery Slope

Emotional Appeal

Red Herring

False Dilemma

Illogical

Moral Equivalency

Ad Hominem

Correlation w/o Causation

Semantics

Begging the Question

Faulty Analogy

Non Sequitur

Bandwagon

Dogmatism

Failing Occam's Razor

Biased

Pure Opinion

Hit Piece

Racial Bias

National Bias

Religious Bias

Financial Incentive

Political Agenda

Gender Bias

Misused Image/Video

Study Misinterpreted

Mistake

Misused Term

Science Misrepresented

Factual Error

Satire

Surface Level

Lack of Reliable Sources

Sensational

Not Credible

Investigative

Balanced

Well Sourced

Great Context

sports

entertainment

U.S.

international

business

technology

science

culture

politics

media

health

The Conceptual Data Model (Part 2)

No article scores yet.

CRITIC REVIEWS

PUBLIC REVIEWS