Development Cycles
  Home arrow Development Cycles arrow Page 4 - Entity Relationship Modeling
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
DEVELOPMENT CYCLES

Entity Relationship Modeling
By: Alf A. Pedersen
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 53
    2004-04-05

    Table of Contents:
  • Entity Relationship Modeling
  • The Entity
  • Other Business Contacts
  • Attributes in entities
  • Business Rules
  • Three types of relationships
  • Supplier Entity
  • A Weak Relation
  • A Useful Relation
  • Involuted (or recursive) relationships
  • Many-to-Many
  • The Database Analysis Team - A Teamwork
  • Level of Knowledge
  • Experience vs. Inexperience
  • Complete Model?
  • Building Queries
  • Other Common Errors in ER Modeling
  • Second Normal Violation
  • More Specific
  • Generic or Specific Models?
  • Analysts Experience

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Entity Relationship Modeling - Attributes in entities


    (Page 4 of 21 )


    Most common metadata on attributes-
    We take for granted, that doing a major analysis study in a given field, you use tools that are appropriate. As for the choice of a modeling tool, I give no concrete recommendations: I have used Oracle Designer (formerly Oracle CASE*Method) for the last 15 years, and I have found it to be a powerful and rich system, which delivers in many more areas than I have needed to use it for. I am probably a little biased here.

    However, a toolset should include reusable objects: The results from the analysis phase should be the basis for generating tables and all other database objects for use in the design phase, as well as functions should be used for generating candidate modules.

    Furthermore, the database objects and candidate modules should be used to generate the DDL (Data Definition Language) scripts for physically building all the elements of the database, as well as the candidate modules should be used to generate running program modules. Not that I expect a system to be 100% generated – far from it.

    However, with such functionality you could show a prototype, which illustrated the resulting, needed functionality, but without the last finishing touch, or the most advanced business constraints built into it.

    As you enter attributes, it is important that you can define their descriptions, optionality, data format and –length restrictions for later use in design. Here is what I would recommend you to: If at all possible, place each and every attribute in a domain.

    A domain is a container that holds general descriptions, as well as data types and length, and in certain circumstances also can keep legal values or legal ranges for a domain. By relating every attribute to a domain definition, you ensure that if you change the domain, the change is reflected for all attributes that belong to that domain. A short example, taken from Oracle Designer:

    Oracle Designer

    We see that the domain MONEY has a legal range between 0.01 and 999,999.99. It sounds fair: Money must have some minimum value. How about maximum? This domain was created for use in transactions, and we have a rule in the business saying that no transaction larger than a million is allowed, for security reasons.

    More Development Cycles Articles
    More By Alf A. Pedersen


     

    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







    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 3 Hosted by Hostway
    Stay green...Green IT