Home arrow Development Cycles arrow Page 2 - Entity Relationship Modeling
DEVELOPMENT CYCLES

Entity Relationship Modeling


Entity Relationship Modeling (ER modeling) is by far the most common way to express the analytical result of an early stage in the construction of a new database. In this ebook, Alf Pedersen describes the principles for ER modeling, as well as the most important terms used in modeling a new database.

Author Info:
By: Alf A. Pedersen
Rating: 4 stars4 stars4 stars4 stars4 stars / 89
April 05, 2004
TABLE OF CONTENTS:
  1. · Entity Relationship Modeling
  2. · The Entity
  3. · Other Business Contacts
  4. · Attributes in entities
  5. · Business Rules
  6. · Three types of relationships
  7. · Supplier Entity
  8. · A Weak Relation
  9. · A Useful Relation
  10. · Involuted (or recursive) relationships
  11. · Many-to-Many
  12. · The Database Analysis Team - A Teamwork
  13. · Level of Knowledge
  14. · Experience vs. Inexperience
  15. · Complete Model?
  16. · Building Queries
  17. · Other Common Errors in ER Modeling
  18. · Second Normal Violation
  19. · More Specific
  20. · Generic or Specific Models?
  21. · Analysts Experience

print this article
SEARCH DEVARTICLES

Entity Relationship Modeling - The Entity
(Page 2 of 21 )

The single entity-As we define different entities, we find that we are digging deeper and deeper into the problem domain of the business we are modeling. The more we, as system analysts, interact with the business we are modeling with, the more information we find belong in different entities. This is how the process works. 

You should not be afraid to create new entities, if so just as placeholders for ideas. In the analysis phase we need not be concerned about it; the analysis phase is where we test out ideas, new questions, and eventually evolve towards a solution which is sound, correct, and shows the business as it really is (or as we would like it to be).

It is also a good idea to create attributes as they are coming up. Again, they can be evaluated and thrown away later if we really do not need them. With a good ER modeling tool, your ER diagram may be thought of as a sketchbook, especially in an early phase of analysis.

Single entities are relatively easy to spot: An account is something different from transactions or balances, and a customer is something different from an order. However, customers and orders are related to each other through relationships, as well as accounts are related to transactions and balances. Sometimes we may enter a dilemma, when two or more entities actually look very similar: What is really the difference between a customer and a supplier?

Both entities have some form of identification; they both have a name, address, telephones, contact persons etc. We may even have a discount system for our customers, and our suppliers also give us some discount mechanisms. The two are really quite like.

In our analysis work, we have two mechanisms for dealing with such uncertainties.

The super-entity and the sub-entity-If we first draw an entity we call BUSINESS CONTACT, and then draw two or more entities inside the BUSINESS CONTACT entity, then BUSINESS CONTACT becomes a super-entity, and the others become sub-entities of BUSINESS CONTACT. The purpose of this is to verify if we really are talking about different kinds of contacts:

entity relationship

As we add attributes into this model, we must ask ourselves: The attribute I am about to create; is it valid for all the sub-entities, or is it specific to only one (or two...) of the sub-entities? If the attribute is valid for all sub-entities, we place it in the super-entity in stead.


blog comments powered by Disqus
DEVELOPMENT CYCLES ARTICLES

- Division of Large Numbers
- Branch and Bound Algorithm Technique
- Dynamic Programming Algorithm Technique
- Genetic Algorithm Techniques
- Greedy Strategy as an Algorithm Technique
- Divide and Conquer Algorithm Technique
- The Backtracking Algorithm Technique
- More Pattern Matching Algorithms: B-M
- Pattern Matching Algorithms Demystified: KMP
- Coding Standards
- A Peek into the Future: Transactional Memory
- Learning About the Graph Construct using Gam...
- Learning About the Graph Construct using Gam...
- Learning About the Graph Construct using Gam...
- How to Strike a Match

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 
Support 

Developer Shed Affiliates

 




© 2003-2017 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials