Does a Conceptual Data Model contain Attributes?

Friday, November 3, 2017 | Likes: 0 | Comments: 0

Mark Paauwe

Sales Director

Dragon1 Inc

Does a Conceptual Data Model contain Attributes?

“DATA is the new age, trend and hype”

Can a Conceptual Data Model Contain Attributes?

I think the answer is yes, of course.

A Conceptual Data Diagram can be defined as a coherent set of related conceptual entities. Entities have attributes, even conceptual entities.

Why is this question of importance?

Well, many people who try to model and capture the business and IT of an organization are stuck with how detailed they should go about creating a data model of the organization.

But if a conceptual data model contains attributes, people will capture them, for example, during a workshop. And if a conceptual data model, by definition, does not contain attributes, they won’t or shouldn't capture them.

It makes sense to have good discussions about the key attributes for the important concepts of the business and IT in the model.

With the age of Data arriving and data scientists popping up in every organization, conceptual data models are becoming very popular. The better you understand the data concepts in the organization, the better you can analyze and get something sensible out of your Data Lake and fire off some value-added artificial intelligence.

What is a Conceptual Entity?

An entity can be defined as something that can be identified apart from its environment or surroundings. An entity can be modeled as a set of attributes/properties, operations, and functions. An entity is often tied to a real-world concept like “customer” or “company”. Entities are often used to map a real-world object and a database table. Entities hold information about a system, and every business domain of any company contains many entities.

A conceptual entity can be defined as an entity abstracted from implementation aspects. An example of a conceptual entity would be a car. 'Car' as a conceptual entity can have attributes. Even the archetype of a car. Because then we recognize it or know it as a car. A car has wheels, a car has a color, a car has a carbon footprint, and a car has an owner. Even at a conceptual level, it might be interesting to work with a car's color or carbon footprint as attributes.

Maybe it is most important to remark that any entity should be included in the conceptual model if it has meaning for the people of the business. If it does not have meaning for the business. The CDM will fail to realize its function.

The Function of a Conceptual Data Model

If the business stakeholders of an organization, like managers and staff, want to understand how their business works, want to support IT and Data, and want to support people to build the best IT support for their business, more and more often a conceptual data model is created.

A conceptual data model captures the essential concepts that are present or should be present in the organization. One can create an AS-IS CDM and TO-BE CDM.

Suppose an insurance company wants to start a digital transformation. A good understanding of the concepts of Customer-Centric, Self Service, and Insurance Product Formulas is important. A conceptual data model usually describes a complete enterprise or business with only 30 to 50 concepts (or conceptual entities). Every concept is defined,d and every concept is related to one or more other concepts.

ANSI 1975 on Conceptual Data Models

Next to people in workshops creating conceptual data models, there are also institutes and professors busy with conceptual data models, but more on the definition side of it.

According to ANSI (ANSI/X3/SPARC Study Group on Data Base Management Systems, back in 1975; Interim Report), a Conceptual Data model can be defined as follows: A conceptual data model describes the semantics of a domain, being the scope of the model.

As an example, it may be a model of the interest area of an organization or industry. This model would consist of entity classes representing things of significance in the domain and relationship assertions about associations between pairs of entity classes.

A conceptual schema specifies the kinds of facts or propositions that can be expressed using the model. In that sense, it defines the allowed expressions in an artificial 'language' with a scope that is limited by the scope of the model.

The ISO TR9007 defines a conceptual schema next to a conceptual model example. These two are closely related. For some, they are even the same. Like a conceptual model, a conceptual schema is a map of concepts and their relationships. A conceptual schema typically contains main concepts and main relationships.

Writing Good Definitions

Definitions are fundamental. If you have the wrong definitions for terms you use, misunderstandings, disinvestments, and failures are just around the corner. Words like “business capability”, “application function” and “business service” are often used, but many different meanings are attached to them. If one would create a list of occurrences of these three entity classes, anyone would create a unique list.

So when we are talking about a conceptual data model, it is also crucial to define what is a conceptual data model. And if someone asks: does a conceptual data model have attributes? Then that question is also fundamental to ensure we do not waste valuable time, money, and resources doing the wrong things.

In the Dragon1 open EA Method, we maintain three criteria for writing good definitions:

Are all the words used in a definition predefined?
Does the definition of quality and quantity? In other words, does it clarify the term's scope and border?
Are there any counter-examples? Can you provide an example that does not fit the definition?

These three criteria do not guarantee the creation of the only correct definition for a term, but they help improve any definition.

So all the definitions in the Dragon1 method and the definition for a conceptual data model comply with these three criteria. If someone can provide evidence that a Dragon1 definition does not match these three criteria, the definition will be revised.

The current definition for Conceptual Data Model in the Dragon1 method is:

A conceptual data model is a coherent set of related conceptual entities with attributes.

An Example Conceptual Data Model

Although this picture is somewhat vintage, it is still great. It shows a graphical representation of a conceptual data model. This model recognizes organization, party, address, person, customer, broker, underwriter, policy, contract, and transaction. These are all essential business concepts for an insurance company.

The conceptual data model relates these concepts. People can now communicate with the business on IT and data and build modern IT support for the business or perform a digital transformation necessary to ensure the insurance company will survive the age of data.

For many people, this diagram may contain too many technical details as in the modeling language notation is used. However, the essence of the diagram will be evident to anyone who works in the insurance business.

Today's version of such a conceptual data model would contain conceptual entities like Insurance Fraud, Customer Interest, Identity, and Claim Behavior.

With such a modern diagram version of a conceptual data model, any insurance organization can focus on what the most important data is for the business and for what data to make an effort for data visualization or artificial intelligence.

Because of the new age of Data, data modeling is back more than ever. We now need experts in data modeling, sound definitions, and good tools. And discuss attributes of conceptual entities in workshops.

Happy data modeling!