Description

This book is for database designers and database administrators using Visio, which is the database component of Microsoft's Visual Studio .NET for Enterprise Architects suite, also included in MSDN subscriptions. This is the only guide to this product that tells DBAs how to get their job done. Although primarily focused on tool features, the book also provides an introduction to data modeling, and includes practical advice on managing database projects. The principal author was the program manager of VEA's database modeling solutions.

Key Features

· Explains how to model databases with Microsoft® Visio for Enterprise Architects (VEA), focusing on tool features. · Provides a platform-independent introduction to data modeling using both Object Role Modeling (ORM) and Entity Relationship Modeling (ERM), and includes practical advice on managing database projects. · Additional ORM models, course notes, and add-ins available online.

Readership

data modelers, database modelers, and DBAs working with Visual Studio .NET for Enterprise Architects and subscribers to Microsoft Developer Network (MSDN); upper division undergraduate and graduate students in Computer Science and Information Science; professional courses in database modeling, business rules, Microsoft course in Visual Studio .NET and SQL Server

Table of Contents

Foreword Preface Part 1 Overview of Database Modeling and the Database Modeling Tool 1 Introduction 1.1 Why Read This Book? 1.2 What Can You Do with Visio for Enterprise Architects? 1.3 What Can You Do with the Database Modeling Solution? 1.4 How Can You Best Use This Book? 1.5 Format Conventions 2 Database Modeling 2.1 Four Information Levels 2.2 Designing Databases at the Logical level 2.3 Designing Databases at the Conceptual Level 2.4 The Database Life Cycle 3 Getting Started 3.1 Product Editions and Versions 3.2 Installation 3.3 The Visio Interface 3.4 Using Help 3.5 Pagination and Layers 3.6 Simple Examples of Forward Engineering Part 2 The Conceptual Modeling Solution (ORM) 4 Object Types, Predicates, and Basic Constraints 4.1 Object Types 4.2 Fact Types 4.3 Adding Basic Constraints in the Fact Editor 4.4 Populating Fact Types with Examples 4.5 Saving a Model 4.6 Verbalization and Hyphenation 4.7 Objectifying an Association (Nesting) 4.8 Model Error Checks 4.9 Derived Fact Types 4.10 Data Types 5 ORM Constraints 5.1 Value Constraints 5.2 Internal and External Uniqueness Constraints 5.3 Simple and Disjunctive Mandatory Constraints 5.4 Constraint Editing and Deletion 5.5 Set-Comparison Constraints 5.6 Subtyping 5.7 Frequency Constraints 5.8 Ring Constraints 5.9 Indexes 5.10 Constraint Layers 6 Configuring, Manipulating, and Reusing ORM Models 6.1 Configuring ORM Preferences 6.2 Showing Relationships for Object Types 6.3 Redisplaying Model Elements 6.4 Cloning

Details

No. of pages:
425
Language:
English
Copyright:
© 2003
Published:
Imprint:
Morgan Kaufmann
Electronic ISBN:
9780080491035
Print ISBN:
9781558609198

About the authors

Terry Halpin

Dr. Terry Halpin is a professor at Northface University. He has led database research teams at several companies including Visio Corporation and Microsoft Corporation, where he worked on the conceptual and logical database modeling technology in Microsoft Visio for Enterprise Architects. His publications include over 100 technical papers and five books.

Ken Evans

Ken Evans has taught and applied ORM in English and French for 10 years. His know-how in data and process modeling and complex systems management comes from over 30 years in industry, including international jobs with IBM, EDS, Honeywell Controls, and Plessy and clients among the Fortune 500.

Pat Hallock

Patrick Hallock, M.S., is the founder of InConcept, a consulting firm, and teaches object modeling throughout the United States. He has been in the industry for 30 years, focusing on database design, with an emphasis on ORM.

Bill Maclean

Bill MacLean, CPA, is an independent consultant and teacher who has worked with relational databases for over 15 years, and consulted in database design for the last 9. He believes that the purpose of a data model is to turn business requirements into buildable specifications.