SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 118 of 365 Next >

Database Design - Adjusting the Model

In this tutorial, we'll refine the data model that we created in the last few sections. In the last article, we turned the business requirements into entities, attributes and relationships on an Entity Relationship Diagram (ERD). To be more specific, we created a logical model.

This time, we'll examine the model closer, to ensure that our database design accurately reflects the application's business requirements. Once we've completed that step, we'll show this plan to the design team, which includes a representation from the business community. Without their input, even the entities are suspect (not to mention the attributes they contain). One primary factor in poorly received systems is the failure to include the end users in all phases of the design process.

You'll recall that we've gathered the business requirements from the business community. This is often presented in the form of a fairly lengthy narrative, checked and re-checked against current or proposed business processes. The next phase of the design process is to take that narrative and break it into single-concept sentences. Both of these steps might be done by a DBA, but in larger shops this falls within the purview of the Business Analyst.

We got to this step in an earlier article, and the final narrative looked like this:

Here at BuckSoft Consulting, consultants work on projects for clients. Consultants have individual expertise and work in teams for each project, for a set period of time, and are billed out by the hour on a predetermined rate.

This set of statements is quite simple, to be sure, but it will serve for our tutorial purposes. Data Modeling is quite exponential, in that adding one more level to the requirements would explode the diagram into something that wouldn't fit on one screen!

We derived the entities and attributes from the nouns in the sentence. Here's another statement written from the one above regarding a project:

Projects are created for a client. Projects have a name. A project has phases, which are bounded units of work. Projects have a lifecycle, consisting of the request and initiation, planning, execution, control, and close. Projects have a budget. Projects are measured by the man-hour per work. Projects have a success or failure state. Projects have several stakeholders, such as various members of the client's staff and various members of BuckSoft consulting.

From the verbs in the first set of statements and all subsequent descriptions, we derived our relationships.

With all this information, we arrived at the following logical Entity Relationship Diagram:

Figure 81

We now come to the purpose of this tutorial, the design review. It is important to understand that the model is a tool – it assists us in the design, and is not the final outcome of the design. This is an important distinction; I have seen groups of professionals that feel once a design has reached the "on paper" stage that it is sacrosanct and cannot be tampered with. Nothing should be further from the truth. This graphical design should flush out any design flaws.

I mentioned in the last article that this design may have had a few errors in it. Let's examine the various entities, attributes and relationships to see if the errors rear themselves.

We'll begin with the entities. Do they capture all that is related in the business requirements? The stated goal for this project is to capture all efforts from an hours-standpoint on a given project. To do that, we need to house information for three main entities: Projects, Clients and Consultants.

Let's begin with the Clients entity. Does it contain all the information regarding a client?

We've got attributes in the Clients entity that you might expect such as name, address, and phone, but we also have another attribute, called Start Date, that you may not have considered. Since the requirements don't call for this information, why did we include it?

A start date on the Clients entity will help us determine when we signed the client to the first activities that we perform on a project for that client.

Now we move on to the Projects entity. Does it contain all relevant project information?

The model includes the attributes of name, phase, budget and state, in accordance with the business requirements. To be sure, there are several other attributes that we could have added but didn't. One glaring exception might be the lack of a start or end date for the project. Shouldn't that be a key entity here? Actually, the only part about the project that we're interested in is the work our consultants do on the project. Since that information will be stored in the Hours entity, there's no need to track it twice.

And, finally, we consider the consultants, or Staff Members entity. Does it capture what we need to know about the consultants working on the project?

Just in case we have two people with the same name, I've included a code to uniquely identify each staff member. The model also includes the consultant's name, so we can track who does the work. Notice that the model shows that the years of service as an attribute of the staff member entity. There is only one value for both name and years on staff.

Each consultant, however, may have more than one skill. To keep each entity separate, I've included a Skills entity to track not only the name, but the classification and level the consultant has for that skill. While this isn't technically included in the business requirements, we may need this information to adequately determine if we have the proper staff on the project.

We haven't included things like address, social security number, phone, and so forth for the Staff Member entity. The business requirements don't state that we need to store this information, so in this case we won't.

Using the same logic regarding consultant skills, I've attached the Hours entity to the Staff Members entity. Staff Members work hours, and we can see that relationship here.

I mentioned in the last article that there were entities which came into play only when relationships were considered. Referring back to our diagram, you can see I've created one such entity, called ProjectStaff. This entity stores the relating attributes between Projects and Staff Members. The logic that used for that decision was that staff members worked on projects.

While this is true, is this in fact the best way to model this relationship? The difficulty lies in the Hours entity. Do hours actually belong to staff members? At first glance, it might seem so. But when we re-read the business requirements, we see that from some perspectives, the hours are owned not by the consultant who works them, but the project and the staff member. For us to present hours for a given project using our current model, we would need to join the Projects entity to the Staff Members entity, and then derive the hours from there. This is a rather cumbersome method, considering the business requirements we were presented several articles ago.

Consider this revised model:

Figure 82

Notice that I've removed the ProjectStaff entity and moved the Hours entity into its place. I did this to show that hours are not independent of any other entity, and that they aren't really owned by the project or the staff members. It is the intersection of a project and a staff member that causes an hour to materialize.

Does this model more accurately represent the relationship? I believe that it does. Is this the only way to model that relationship? Certainly not! Just as in the Roman era, many roads lead to the same result. Often, the database design is considered from only one perspective.

In our next tutorial, we'll develop this logical model to a physical Entity Relationship Diagram. Again, we may discover an issue or two with the design. That's OK! We'll fix it and move on.

Note that I've left a couple of glaring issues here. Hint: Where do we track what the consultant did during his or her hours? For that matter, what were the hours? Stay tuned!

Online Resources

An article on refining a data model can be found here.

Here's another article on refining data models.

Here are some good design articles for various entities.

InformIT Articles and Sample Chapters

Object-Oriented Design Heuristics by Arthur J. Riel

< Back Page 118 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address