Home > Articles > Programming

  • Print
  • + Share This
This chapter is from the book

The Requirements Analysis Deliverable—Column One

Entity Types and Relationships, with Narrative

A data model is a major product of the requirements analysis process. At the very least, this should be an architect's version, showing the conceptual structures of the company's data. Where appropriate, user views of the data can be included, with the linkages appropriately documented.

The data model can be an object role model, a conceptual entity/relationship diagram, or an object model showing business-oriented classes. If an entity/relationship diagram is used, it should be in either Barker or information engineering notation, to ensure readability. If a UML business class model is produced, it must be with a stripped-down version of UML. It can show only classes, associations, and sub-types. Relationship roles must be labeled in both directions.

Regardless of notations, the relationships should be named as described in this chapter, to ensure that they can be converted into conventional English. Note that each entity type name must be a common natural language term. No abbreviations, acronyms, or references to computer terms are permitted.

In the CASE tool supporting your efforts, each entity type must be described by its name and definition. Optionally, estimates of the number of occurrences, synonyms, and other information may also be included. (See Chapter 2 for a description of how this information can be used to estimate the data capacity required.)

A narrative should accompany the model: Strictly speaking, this is a collection of definitions and relationship sentences, but this structure can be camouflaged, making the narrative look like paragraphs of normal text. The idea is that anyone could read the text and understand it, without necessarily understanding the model graphics.

Also included as documentation of the model should be the business rules (captured for Column Six) that constrain it. At the basic level, this includes rules associated with the data model configuration, such as “no loops in a recursive structure”, or the requirement that if there are two paths between two entities, the occurrences at each end of the paths must be the same (or they must be different). In addition, there will be many rules which originate in the business itself.


In the course of developing a model, the entity types and relationships are defined first, with perhaps a few attributes defined for each entity type, to clarify its meaning. By the end of the requirements project, however, all known attributes must be specified, with each defined by its name and description, format, optionality, and validation rules.

In assigning attributes, be sure to recognize that some things that appear to be attributes are really relationships to other entity types. Bob Schmidt [Schmidt, 1999] points out that what an entity type really has are predicates. A predicate is a piece of information about an entity type. It may be an attribute or a relationship to another entity type. The important thing at the beginning of the effort is to identify the predicates. Once they have all been laid out, which are attributes and which are in fact relationships to other entity types?

This is the approach also taken by object role modeling.

Ask, does this attribute itself have attributes? If so, you have a relationship to a new entity type.

In fact, you should have relatively few attributes for each entity type. You may have a surrogate key, a name or description, and possibly some cost or date data. Nearly every other attribute you may imagine is probably a relationship to another entity type.

As with entity types, each attribute must be a common natural language term. If the UML is used and attributes are shown on the model, show the attribute name only. Be sure to describe attribute characteristics behind the scenes.


It is a good practice to assign a domain to every attribute. A domain is a validation rule for an attribute. It establishes a context. It may consist of a list of values, a range, or an expression of some kind. A domain may also be used to specify a standard format. This is convenient, because once a validation rule has been defined, it can be applied easily to many attributes. It also adds discipline to the attribution process, because it requires the analyst to analyze carefully just what the attribute means.

In addition, many domains are actually specified as …TYPE entity types. While defining these as entity types/tables adds flexibility and robustness to the final system, the values should be determined up front. WORK ORDER TYPE, REPORTING RELATIONSHIP TYPE, and so forth are effectively domains, and it is the analyst's job to provide at least an initial set of values for these.

Unique Identifiers

As shown above, a data model cannot be validated without knowledge of each entity type's unique identifiers. For this reason, it is important to be sure that the attributes and relationships identifying each entity type be properly identified.

Referential Integrity

Most CASE tools do not permit this annotation, but examine the data model, and for every relationship, note on the “one” end the referential integrity rule for that relationship. Is it cascade delete, meaning that if the parent is deleted, all of that parent's children will also be deleted? Is it restricted, meaning that the parent cannot be deleted if it has children? Or is it nullify, meaning that the relationship from children to parent is optional, and deleting the parent means that the value of the relationship for each remaining child is reset to “null”?

  • + Share This
  • 🔖 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.


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.


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.


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.


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


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


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.


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.


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