The Design
You Want to Do What?!
After requirements definition, Angela, one of the data analysts on the team, ap proached Mike, the system's architect, and reasserted her previous concerns about the business object model for Manage Clinical Records. (Mike understood that such an apparent “back step” is not uncommon during an object-oriented development process and indeed is usually very valuable. Problems avoided increase quality and speed development. He also understood that this would be a hard sell to project management.) As you recall, during business modeling, Angela expressed concern about how the Clinical Records were being modeled (see Figure 3-18). The use of New, Old, and External in the Clinical Records entity names seemed to be trying ...
Get UML for Database Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
