Module 3-Database Development Process

Module 3: Database
Development Process
Enterprise Data Modeling
 Data modeling is a process for conceptualizing the

relationships between different types of information in
an organization, independent of the organization’s
structure, processes, people, or domains.
 Datamodels are a representation of data objects and
the relationships between those objects which helps
users across disciplines store and interact with data
more effectively for a variety of use cases.
 IT professionals design data model structures based on
the actual ways in which IT entities, personnel,
and business capabilities interface with one another.
Such objects become the main categories, or boxes, in
the model.
 These objects are all interconnected, and the

connections (or relationships) between the items are
used to visualize data and guide policies governing this
data.
Why should you use data modeling?
• Users can take advantage of having this information neatly structured to
identify technical and functional overlap, foster business intelligence, and
optimize how data are organized.
• Controlling how and where data interact in either a server or cloud

environment is vital for implementing systems that equally benefit business
and IT professionals.
• A data model can be used to validate the technical and functional benefits of
current and future data objects while also revealing if databases are correctly
represented.
Benefits of data modeling
1. Ensure that data objects in an IT landscape are correctly
represented.
2. This information can then be utilized to define connections
between primary and foreign keys, tables, and procedures.
3. A data model can then be used to build a physical
database if sufficiently detailed.
4. Data models can also be leveraged to communicate to
business stakeholders throughout organizations.
5. Locating accurate sources of data to auto-fill the model.
Challenges of data modeling
1. The creator should have a firm understanding of the
characteristics of the data that is already physically stored.
2. A data model is also a system that can result in complex

application development, thereby making these processes
difficult to manage as well.
3. All changes to the data model, both large and small,

require developers to modify the entire application system.
Types of enterprise data models
1. Conceptual data models
Conceptual models reflect high-level and static business structures.
This model is commonly used by data architects and stakeholders.
2. Logical data models

Logical data models focus on data attributes, IT entity types, and
relationships between the entities. A logical data model is useful for
understanding the nature and compositions of data but not its actual
implementation.
They are commonly used by business analysts and data architects to
help develop a database management system, a technical map of
structures, and rules for the model.
3. Physical data models
Physical data modes cover aspects related to the design
and implementation of databases. These cover the
structure of databases, including all relational databases
and objects.
They are typically employed by developers and database

analysts to show the execution of a structure with the use
of a database management system.
Enterprise data modeling
techniques
1. An Entity Relationship Diagram (ERD) is the default
technique for data modeling and works especially well when
modeling tabular data. This technique involves making graphical
representations of data objects alongside their attributes and
relationships.
ERDs are very useful when designing traditional and Excel-based

databases. They are also ideal for securing clear visuals of
database schemas, along with top-level data.
2. Unified Modeling Language encompasses a
series of notations for designing and modeling
information structures. Used by many as a
general-purpose software notation, UMLs reflect
either the behavior or structure of data objects
and employ different diagram types for doing so.
One of these diagrams is a class diagram, which

relates to defining the classes, methods, and
attributes of databases.
3. Data dictionaries are based on a tabular
definition of data assets. This is a grouping of
tables and data sets with an accompanying list
of attributes and columns.
Other optional sections of a data dictionary are

item descriptions, additional constraints, and
relationships between columns and tables.
Enterprise data modeling best
practices
1. Don’t create redundancies: Good data objects do not overlap; they are mutually exclusive.
A good test is to check whether you can assign Level 2 data objects without any ambiguity.
2. Rely on business capabilities: It is very easy to find which data objects exist once you have
mapped your business capabilities. This is why we recommend first creating a business
capability map.
3. Long-term stability: Properly defined data objects are fairly stable over time, persisting
throughout any organizational changes. Only major business changes should affect them.
4. Cross-organizational: Don’t get too specific. Data objects should remain the same,
independent of any changes that might happen to the organizational structure.
4. Use existing data models: Many applications (e.g., SAP) will
already have existing data object models. Familiarize yourself with
these when creating your own map.
5. Breadth rather than depth: While more levels can help to get
a better structure, it comes at the cost of increased complexity. Go
for breadth and build your map with no more than three levels.
6. Involve relevant parties: Leverage insights from

representatives throughout the business. Those responsible for
different parts of the business are likely to have the best overviews
of data objects. Consider using surveys to collect information.

Module 3-Database Development Process

Uploaded by

Module 3-Database Development Process

Uploaded by

Module 3: Database

 Data modeling is a process for conceptualizing the

 These objects are all interconnected, and the

• Controlling how and where data interact in either a server or cloud

2. A data model is also a system that can result in complex

3. All changes to the data model, both large and small,

2. Logical data models

They are typically employed by developers and database

ERDs are very useful when designing traditional and Excel-based

One of these diagrams is a class diagram, which

Other optional sections of a data dictionary are

6. Involve relevant parties: Leverage insights from

You might also like