Database Design for Smarties: Using UML for Data Modeling

Chapter 2: System Architecture and Design

Works of art, in my opinion, are the only objects in the material universe to possess internal order, and that is why, though I don't believe that only art matters, I do believe in Art for Art's Sake.

E. M Forster, Art for Art's Sake

Overview

Is there a difference between the verbs "to design" and "to architect"? Many people think that "to architect" is one of those bastard words that become verbs by way of misguided efforts to activate nouns. Not so, in this case: the verb "to architect" has a long and distinguished history reaching back to the sixteenth century. But is there a difference?

In the modern world of databases, often it seems there is little difference in theory but much difference in practice. Database administrators and data architects "design" databases and systems, and application developers "architect" the systems that use them. You can easily distinguish the tools of database design from the tools of system architecture.

The main thesis of this book is that there is no difference. Designing a database using the methods in this book merges indistinguishably with architecting the overall system of which the database is a part. Architecture is multidimensional, but these dimensions interact as a complex system rather than being completely separate and distinct. Database design, like most architecture, is art, not science.

That art pursues a very practical goal: to make information available to clients of the software system. Databases have been around since Sumerians and Egyptians first...

UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Category: Data Warehousing Software
Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.