Development Cycles
  Home arrow Development Cycles arrow Page 12 - 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 - The Database Analysis Team - A Teamwork


    (Page 12 of 21 )

    The importance of a professional database analysis team cannot be overstated. The complexity and degree of computer involvement in the business is constantly growing. No wonder; each 18th month, we can buy hardware with twice the performance at the same price. We are therefore able to put more demands on our software, until we reach some limit. However, it only takes another 18 months; then we can buy new hardware without these limits... and so on.

    There is also a good reason for it: We may very well rely on a standard system for our accounting or payroll routines, we can use market standards in word processing and spreadsheets, and so on. What separates a high-performing business from a failure is the way the CUSTOMER is reached for, and how he is treated.

    That is customer marketing and customer care. The customer is always the business. If you do not have customers, you do not have a business. If such a business exists, however, please let me know.

    Such systems, systems that give the business an advance compared to its competitors, we may call strategic systems. If two businesses buy the same strategic system from the shelf, then they do not gain any system advantage towards each other.

    On the other hand, the business that is fastest to respond, and deliver, and at the same time is competitive, will definitely have an advantage. In a world with rising competition and globalization, this will grow more and more important. Good news for the software industry and the analysis team...

    In the analysis stage, we need an analysis team of both business experts as well as experienced system analysts. In addition, we need tools that can help us see the overall picture, as well as help us in the future. Top business experience is required in the analysis team in order to get in-depth understanding of the business itself.

    Remember: Our model, at this stage in development, must reflect the business, not some constraints given by any tool or personal preferences. This happens all too often and usually with not-too-good results.

    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 5 Hosted by Hostway
    Stay green...Green IT