DOCSLIB.ORG

CA Erwin Data Modeler Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

CA ERwin® Data Modeler Release Notes r7.3 r7.3.8 SP2 Edition This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be used or disclosed by you except as may be permitted in a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright © 2009 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. CA Product References This document references the following CA products: ■ CA ERwin® Data Modeler ■ CA ERwin® Model Manager Contact CA Contact Technical Support For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/support, you can access the following: ■ Online and telephone contact information for technical assistance and customer services ■ Information about user communities and forums ■ Product and documentation downloads ■ CA Support policies and guidelines ■ Other helpful resources appropriate for your product Provide Feedback If you have comments or questions about CA product documentation, you can send a message to [email protected]. If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs. Documentation Changes This Release Notes document is cumulative - it is updated as features are added or changed during the patch and Service Pack releases.The following list summarizes the documentation updates that have been made since the initial release (r7.3 GA) of CA ERwin Data Modeler: Chapter 1: New Features and Enhancements ■ Macro Added (r7.3.5)—Addition of the macro DatabaseConnection to the Forward Engineering Template macros. ■ Metadata Integration Bridges Updated (r7.3.2, r7.3.4 SP1, and r7.3.8 SP2)—List of Import/Export bridges added, removed, and renamed. ■ Enhancement made to Rename Column Dialog (r7.3.4 SP1). ■ Allow Special DBMS Characters check box added to the Derive Wizard, Naming Standards pane (r7.3.8 SP2). Chapter 2: System Information ■ Operating System Support - Note added regarding requirement that Administrative privileges are needed when installing, updating, or removing the software. ■ r7.3.8 SP2 includes certification on Microsoft Windows 7, and Microsoft Windows XP (SP3). Chapter 3: Installation Considerations ■ Silent Install for CA ERwin Data Modeler and Crystal Reports (r7.3.6) - Overview and examples for performing a silent install of CA ERwin Data Modeler and Crystal Reports. Chapter 5: Known Issues ■ Known Issue With Meta Integration Bridges for Microsoft Office Excel (r7.3.8 SP2) - Import and Export issues when working with the Microsoft Office Excel bridges. ■ The silent install is not supported on the Windows 7 operating system. Contents Chapter 1: New Features and Enhancements 7 Support for Teradata 2.6/12 .................................................................... 8 Model Validation Enhancements for Teradata .................................................... 9 Integrated SQL Query Tool ..................................................................... 9 ODBC-Based Metadata Access ................................................................. 10 Crystal Reports 2008 Included with CA ERwin DM ............................................... 10 Enhancements to Complete Compare .......................................................... 11 Features Added to Improve Complete Compare Performance with CA ERwin Model Manager ... 11 Advanced Options ......................................................................... 12 Type Resolution Wizard .................................................................... 13 Change to Type Selection Filtering ......................................................... 13 Demand Loading Enhancement ............................................................ 13 Demand Loading and DB Sync ............................................................. 14 Object Selection Enhancement ............................................................. 14 Range Selection Enhancement ............................................................. 14 "Explain" Button Added .................................................................... 14 Template Editor for Forward Engineering Template Files ......................................... 15 Macro Enhancements ......................................................................... 15 Macro Added (r7.3.5) ..................................................................... 16 Universal File Close Dialog ..................................................................... 17 Enhancements to Open or Save a Model in XML Format ......................................... 17 Enhancements to Triggers ..................................................................... 18 Customize Model Explorer Display.............................................................. 19 Metadata Integration Bridges Updated (r7.3 Initial Release) ..................................... 20 Import Bridges Added/Removed ........................................................... 20 Export Bridges Added/Removed ............................................................ 20 Bridges Renamed ......................................................................... 20 Metadata Integration Bridges Updated (r7.3.2) ................................................. 22 Import Bridges Added/Removed ........................................................... 22 Export Bridges Added/Removed ............................................................ 22 Bridges Renamed ......................................................................... 22 Metadata Integration Bridges Updated (r7.3.8 SP2) ............................................. 24 Import Bridges Added/Removed ........................................................... 24 Export Bridges Added/Removed ............................................................ 24 Bridges Renamed ......................................................................... 25 Enhancement to Rename Column Dialog (r7.3.4 SP1) ........................................... 27 Allow Special Characters During Derive (r7.3.8 SP2) ............................................ 27 Database Support Update ..................................................................... 28 Contents 5 Databases Removed ...................................................................... 28 Databases Added ......................................................................... 28 User Interface Changes for Selected Databases ............................................. 28 Operating System Support Update ............................................................. 29 Integration With Microsoft Visual Studio Team System 2008 Database Edition .................... 29 Metamodel Reference Documentation .......................................................... 29 Compiled HTML Online Help ................................................................... 30 Documentation Bookshelf ..................................................................... 30 Feature-Specific Training Videos ............................................................... 31 Chapter 2: System Information 33 Operating System Support .................................................................... 33 System
Recommended publications
  • Powerdesigner 16.6 Data Modeling

    Powerdesigner 16.6 Data Modeling

    SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82
  • Integration Definition for Function Modeling (IDEF0)

    Integration Definition for Function Modeling (IDEF0)

    NIST U.S. DEPARTMENT OF COMMERCE PUBLICATIONS £ Technology Administration National Institute of Standards and Technology FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) » Category: Software Standard SUBCATEGORY: MODELING TECHNIQUES 1993 December 21 183 PUB FIPS JK- 45C .AS A3 //I S3 IS 93 FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) Category: Software Standard Subcategory: Modeling Techniques Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Issued December 21, 1993 U.S. Department of Commerce Ronald H. Brown, Secretary Technology Administration Mary L. Good, Under Secretary for Technology National Institute of Standards and Technology Arati Prabhakar, Director Foreword The Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official publication relating to standards and guidelines adopted and promulgated under the provisions of Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235. These mandates have given the Secretary of Commerce and NIST important responsibilities for improving the utilization and management of computer and related telecommunications systems in the Federal Government. The NIST, through its Computer Systems Laboratory, provides leadership, technical guidance,
  • Metamodeling and Method Engineering with Conceptbase”

    Metamodeling and Method Engineering with Conceptbase”

    This is a pre-print of the book chapter M. Jeusfeld: “Metamodeling and method engineering with ConceptBase” . In Jeusfeld, M.A., Jarke, M., Mylopoulos, J. (eds): Metamodeling for Method Engineering, pp. 89-168. The MIT Press., 2009; the original book is available from MIT Press http://mitpress.mit.edu/node/192290 This pre-print may only be used for scholar, non-commercial purposes. Most of the sources for the examples in this chapter are available via http://merkur.informatik.rwth-aachen.de/pub/bscw.cgi/3782591 for download. They require ConceptBase 7.0 or later available from http://conceptbase.cc. Metamodeling and Method Engineering with ConceptBase Manfred Jeusfeld Abstract. This chapter provides a practical guide on how to use the meta data repository ConceptBase to design information modeling methods by using meta- modeling. After motivating the abstraction principles behind meta-modeling, the language Telos as realized in ConceptBase is presented. First, a standard factual representation of statements at any IRDS abstraction level is defined. Then, the foundation of Telos as a logical theory is elaborated yielding simple fixpoint semantics. The principles for object naming, instantiation, attribution, and specialization are reflected by roughly 30 logical axioms. After the language axiomatization, user-defined rules, constraints and queries are introduced. The first part is concluded by a description of active rules that allows the specification of reactions of ConceptBase to external events. The second part applies the language features of the first part to a full-fledged information modeling method: The Yourdan method for Modern Structured Analysis. The notations of the Yourdan method are designed along the IRDS framework.
  • Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes

    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes

    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes “The Business Driven Application Lifecycle” Bob Sherman Procter & Gamble Pharmaceuticals [email protected] Michael Sutherland Galactic Solutions Group, LLC [email protected] Prepared for the Telelogic 2005 User Group Conference, Americas & Asia/Pacific http://www.telelogic.com/news/usergroup/us2005/index.cfm 24 October 2005 Abstract: The fact that most Information Technology (IT) projects fail as a result of requirements management problems is common knowledge. What is not commonly recognized is that the widely haled “use case” and Object Oriented Analysis and Design (OOAD) phenomenon have resulted in little (if any) abatement of IT project failures. In fact, ten years after the advent of these methods, every major IT industry research group remains aligned on the fact that these projects are still failing at an alarming rate (less than a 30% success rate). Ironically, the popularity of use case and OOAD (e.g. UML) methods may be doing more harm than good by diverting our attention away from addressing the real root cause of IT project failures (when you have a new hammer, everything looks like a nail). This paper asserts that, the real root cause of IT project failures centers around the failure to map requirements to an accurate, precise, comprehensive, optimized business model. This argument will be supported by a using a brief recap of the history of use case and OOAD methods to identify differences between the problems these methods were intended to address and the challenges of today’s IT projects.
  • Metamodeling the Enhanced Entity-Relationship Model

    Metamodeling the Enhanced Entity-Relationship Model

    Metamodeling the Enhanced Entity-Relationship Model Robson N. Fidalgo1, Edson Alves1, Sergio España2, Jaelson Castro1, Oscar Pastor2 1 Center for Informatics, Federal University of Pernambuco, Recife(PE), Brazil {rdnf, eas4, jbc}@cin.ufpe.br 2 Centro de Investigación ProS, Universitat Politècnica de València, València, España {sergio.espana,opastor}@pros.upv.es Abstract. A metamodel provides an abstract syntax to distinguish between valid and invalid models. That is, a metamodel is as useful for a modeling language as a grammar is for a programming language. In this context, although the Enhanced Entity-Relationship (EER) Model is the ”de facto” standard modeling language for database conceptual design, to the best of our knowledge, there are only two proposals of EER metamodels, which do not provide a full support to Chen’s notation. Furthermore, neither a discussion about the engineering used for specifying these metamodels is presented nor a comparative analysis among them is made. With the aim at overcoming these drawbacks, we show a detailed and practical view of how to formalize the EER Model by means of a metamodel that (i) covers all elements of the Chen’s notation, (ii) defines well-formedness rules needed for creating syntactically correct EER schemas, and (iii) can be used as a starting point to create Computer Aided Software Engineering (CASE) tools for EER modeling, interchange metadata among these tools, perform automatic SQL/DDL code generation, and/or extend (or reuse part of) the EER Model. In order to show the feasibility, expressiveness, and usefulness of our metamodel (named EERMM), we have developed a CASE tool (named EERCASE), which has been tested with a practical example that covers all EER constructors, confirming that our metamodel is feasible, useful, more expressive than related ones and correctly defined.
  • The Importance of Data Models in Enterprise Metadata Management

    The Importance of Data Models in Enterprise Metadata Management

    THE IMPORTANCE OF DATA MODELS IN ENTERPRISE METADATA MANAGEMENT October 19, 2017 © 2016 ASG Technologies Group, Inc. All rights reserved HAPPINESS IS… SOURCE: 10/18/2017 TODAY SHOW – “THE BLUE ZONE OF HAPPINESS” – DAN BUETTNER • 3 Close Friends • Get a Dog • Good Light • Get Religion • Get Married…. Stay Married • Volunteer • “Money will buy you Happiness… well, it’s more about Financial Security” • “Our Data Models are now incorporated within our corporate metadata repository” © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable 2. Data Models can in be incorporated into your corporate metadata repository © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable 2. Data Models can in be incorporated into your corporate metadata repository 3. ASG Technologies can provide an overall solution with services to accomplish #2 above and more for your company. © 2016 ASG Technologies Group, Inc. All rights reserved AGENDA Data model imports to the metadata collection View and search capabilities Traceability of physical and logical
  • CA Erwin Data Modeler Release Notes

    CA Erwin Data Modeler Release Notes

    CA ERwin® Data Modeler Release Notes Release 9.5.1 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
  • 1. Enterprise Data Planning

    1. Enterprise Data Planning

    1. Enterprise Data Planning Introduction: Enterprise data planning is a strategy for CMS business-focused data standardization. Its objective is to strengthen the agency’s ability to manage and share data and information. NOTE: There are references within this section that refer the reader to the Operating Procedures and Guidelines section. Please download the Operating Procedures and Guidelines section to view these references. The major Enterprise Data Planning products are: Enterprise data objects in the form of Subject Areas and Enterprise Data Entities (Supertypes); and Enterprise Attributes (Data Elements); and Information Security Category settings that establish the controls for appropriate use of CMS data resources. The Enterprise Data Planning process diagram depicts the milestones, control points, and deliverables as they occur during the following steps: Initiate Enterprise Data Planning Define Enterprise Subject Areas Model Enterprise Data Assign Information Security Categories Create the EDM Metadata Repository Publish the Enterprise Data Model Activities in this process are directed by the CMS Enterprise Data Architecture Approach. Key Deliverables: The Enterprise Data Planning process creates the following deliverables: Business Process Model Enterprise Subject Area Definitions, Subject Area Create Read Update Delete Archive (CRUDA) Matrix, Enterprise Data Model, Enterprise Metadata Repository, Business Terms, Enterprise Data Architecture for Repository update. Exhibit 1. Enterprise Data Planning process
  • The Layman's Guide to Reading Data Models

    The Layman's Guide to Reading Data Models

    Data Architecture & Engineering Services The Layman’s Guide to Reading Data Models A data model shows a data asset’s structure, including the relationships and constraints that determine how data will be stored and accessed. 1. Common Types of Data Models Conceptual Data Model A conceptual data model defines high-level relationships between real-world entities in a particular domain. Entities are typically depicted in boxes, while lines or arrows map the relationships between entities (as shown in Figure 1). Figure 1: Conceptual Data Model Logical Data Model A logical data model defines how a data model should be implemented, with as much detail as possible, without regard for its physical implementation in a database. Within a logical data model, an entity’s box contains a list of the entity’s attributes. One or more attributes is designated as a primary key, whose value uniquely specifies an instance of that entity. A primary key may be referred to in another entity as a foreign key. In the Figure 2 example, each Employee works for only one Employer. Each Employer may have zero or more Employees. This is indicated via the model’s line notation (refer to the Describing Relationships section). Figure 2: Logical Data Model Last Updated: 03/30/2021 OIT|EADG|DEA|DAES 1 The Layman’s Guide to Reading Data Models Physical Data Model A physical data model describes the implementation of a data model in a database (as shown in Figure 3). Entities are described as tables, Attributes are translated to table column, and Each column’s data type is specified.
  • Meta-Modeling and Modeling Languages

    Meta-Modeling and Modeling Languages

    member of Meta-Modeling and Modeling Languages Prof. Dr. Knut Hinkelmann Prof. Dr. Knut Hinkelmann Models and Modelling Model A reproduction of the part of reality which contains the essential aspects to be investigated. Modelling Describing and Representing all relevant aspects of a domain in a defined language. Result of modelling is a model. Prof. Dr. Knut Hinkelmann Metamodel and Modeling2 Languages Model in Architecture real object model house architect’s drawing (plan) Prof. Dr. Knut Hinkelmann Metamodel and Modeling Languages 3 Model and Modeling Language in Architecture real object model modeling language (concrete syntax) object types: wall door window house architect’s drawing (plan) Prof. Dr. Knut Hinkelmann Metamodel and Modeling Languages 4 Modelling Language ■ A modelling "language" specifies the building blocks (elements) from which a model can be made. ■ There can be different types of created with Modelling Model modelling languages, depending Language on the kind of model indirect model of ♦ graphical model Reality ♦ textual description ♦ mathematical model ♦ conceptual model ♦ physical model Metamodel and Modeling Languages Prof. Dr. Knut Hinkelmann 5 Modeling Model Language Prof. Dr. Knut Hinkelmann Metamodel and Modeling Languages 6 Model and Meta-Model in Architecture real object model modeling language meta-model (concrete syntax) (abstract syntax) object types: object types: • wall wall • door • window door rules: • a door is adjacent to window a wall on both sides • Windows are on outer walls. house architect’s drawing (plan) Prof. Dr. Knut Hinkelmann Metamodel and Modeling Languages 7 Meta-model A meta-model defines the semantics of the modelling language, i.e. the building blocks that can be used to Meta-model make a model.
  • A Study on Traditional and Evolutionary Software Development Models

    A Study on Traditional and Evolutionary Software Development Models

    INTERNATIONAL JOURNAL OF SCIENTIFIC & TECHNOLOGY RESEARCH VOLUME 6, ISSUE 07, JULY 2017 ISSN 2277-8616 A Study On Traditional And Evolutionary Software Development Models Kamran Rasheed, Muhammad Imran, Muhammad Noman, Muhammad Iqbal Abstract: Today, Computing technologies are becoming the pioneers of the organizations, and helpful in individual functionality i.e. added to computing device we need to add softwares. Set of instruction or computer program is known as software. The development of software is done through some traditional or some new or evolutionary models. Software development is becoming a key and a successful business nowadays. Without software, all hardware is useless. Some collective steps that are performed in the development of these are known as Software development life cycle (SDLC). There are some adaptive and predictive models for developing software. Predictive mean “already known” like WATERFALL, Spiral, Prototype and V-shaped models while Adaptive model include agile (Scrum). All methodologies of both adaptive and predictive have their own procedure and steps. Predictive are Static and Adaptive are dynamic mean change cannot be made to the predictive while adaptive have the capability of changing. The purpose of this study is to get familiar with all these and discuss their uses and steps of development. This discussion will be helpful in deciding which model they should use in which circumstance and what are the development step including in each model. Keywords: Adaptive vs. Predictive; Software development methodologies; Agile vs. Conventional models; Adaptive and Predictive methodologies; SDLC ———————————————————— I. INTRODUCTION While adaptive models are models that are not fixed or Computing Technology has created so much ease for the bounded by the specific development steps and also it says human that is why changes are occuring with enormous “Welcome Changes’ whenever requires.
  • Appendix A: a Practical Guide to Entity-Relationship Modeling

    Appendix A: a Practical Guide to Entity-Relationship Modeling

    Appendix A: A Practical Guide to Entity-Relationship Modeling A Practical Guide to Entity-Relationship Modeling Il-Yeol Song and Kristin Froehlich College of Information Science and Technology Drexel University Philadelphia, PA 19104 Abstract The Entity-Relationship (ER) model and its accompanying ER diagrams are widely used for database design and Systems Analysis. Many books and articles just provide a definition of each modeling component and give examples of pre-built ER diagrams. Beginners in data modeling have a great deal of difficulty learning how to approach a given problem, what questions to ask in order to build a model, what rules to use while constructing an ER diagram, and why one diagram is better than another. In this paper, therefore, we present step-by-step guidelines, a set of decision rules proven to be useful in building ER diagrams, and a case study problem with a preferred answer as well as a set of incorrect diagrams for the problem. The guidelines and decision rules have been successfully used in our beginning Database Management Systems course for the last eight years. The case study will provide readers with a detailed approach to the modeling process and a deeper understanding of data modeling. Introduction Entity relationship diagrams (ERD) are widely used in database design and systems analysis to represent systems or problem domains. The ERD was introduced by Chen (1976) in early 1976. Teorey, Yang, and Fry (1986) present an extended ER model for relational database design. The ERD models a given problem in terms of its essential elements and the interactions between those elements in a problem domain.