UML for Database Design

The Workflow

We are sure that a few of our readers will now give a mental sigh and say, “Finally, we're getting to the good part—building the system. All that other stuff is fluff.” We do understand that many people feel that way. After all, what we focus on shapes our perceptions. When a mail carrier is delivering the mail, he is “working.” When a carpenter is driving those nails, she is “working.” When a system architect is designing a system, he is “working.” When a coder is coding, she is “working.” So any activity that falls outside their “work” is, by default, “not working” and therefore is perceived to be not valuable or important. Given that these people chose the area in which they wanted to work, not only are these other activities ...