Data Modeling English
Data Modeling English
Data Modelling:
A Business-oriented Approach to
Entity-Relationship Modelling
Two day workshop by Alec Sharp
Data modelling is critical to the design of quality databases, Two points are worth emphasizing:
but is also essential to other requirements specification • This workshop is packed with practical tips, techniques,
techniques such as workflow modelling, use cases, and service “scripts,” checklists, and guidelines for the analyst. All
definition because it ensures a common understanding of the of the material is based on years of project experience;
things – the entities – that processes and applications deal abstract theory is avoided.
with. This workshop introduces entity-relationship modelling • The emphasis is on “business-friendly” techniques which
from a non-technical perspective, and explores contextual, support and encourage the full involvement of non-
conceptual, and detailed modelling techniques that maximize technical subject matter experts, which is essential for
user involvement. quality data models.
Essentials of Data Modeling • A structure for sorting terms and discovering entities
• What really is a data model? • Exercise – developing an initial conceptual data model
• Essential components – entities, relationships, and • Entities – what they are and are not
attributes • Guidelines for naming and defining entities
• The basics of diagramming – Entity-Relationnship Diagrams • Three questions to help you quickly develop clear, useful
(“ERDs”) entity definitions
• The narrative parts of a data model – definitions and • Five criteria that entities must satisfy, and four common
assertions errors in identifying entities
• Group exercise – getting started on a data model, then • Exercise – identifying flawed entities
refining it • Identifying relationships
• Common misconceptions about data models and data • Fundamental vs. irrelevant or transitive relationships
modeling • Good and bad relationship names
• The real purpose of a data model • Multiplicity or cardinality – 1:1, 1:M, and M:M relationships,
• Three types of data models – different levels of details for and useful facts about each
different purposes • Common errors and special cases – recursive, multiple, and
• Contextual, Conceptual, and Logical Data Models – purpose, supertype-subtype relationships
audience, definition, and examples • Attributes – guidelines and types
• How data models help in process impriovement, • Attributes in conceptual models vs. logical models
requirements definition, and reporting
• Forward- and reverse-engineering uses of data modeling Phase 2 – Develop the initial logical data model by
• Overview of a three-phase methodology for developing a adding rigor, structure, and detail
data model • What’’s involved in developing a logical model – shifting
• References – books and useful web sites the focus from entities to attributes
• Multi-valued, redundant, and constrained attributes, with
Phase 1 – Establish the initial conceptual data simple patterns for dealing with each
model • An understandable guide to normalization – first, second,
• Top down vs. bottom up approaches to beginning a data and third normal forms
model – when is each appropriate? • Higher order (fourth and fifth) and Boyce-Codd normal
• Advantages of a bottom-up approach forms
• A bottom-up approach focusing on collecting and analyzing • Guidelines for a smooth progression from conceptual to
terminology logical
• Exercise – developing the initial logical data model
• Four types of entities – kernel, characteristic, associative,
and reference
• Guidelines and patterns for dealing with each type of entity
• How to draw your E-R Diagram for maximum readability and
correctness
• Optional and mandatory relationships
• Considering time and history when looking at relationships
• Six questions to ask whenver a data range appears in a data
model
• Identifying and dealing with transitive relationships – clues
and proof
Course description
Phase 3 – Refine and extend the logical data model • Using event analysis to discover additional requirements
by discovering and meeting new requirements • Exercise – using event analysis and extending a data model
• Attribute granularity – definitions of non-atomic and • Presentation by teams of their solutions
semantically overloaded attributes • How data modeling relates to process modeling, use cases,
• Guidelines for making non-atomic attributes atomic and services
• The perils of semantic overload, and what to do about it • A layered framework for business analysts
• Dealing with derived attributes, and when to show them on • How other techniques (e.g., workflow modeling) support
the model data modeling
• A classword-based approach to attribute naming • A three-step procedure for meeting new requirements
• Typical attribute documentation • Advice on extending the model in an orderly fashion
• A common source of confusion and disagreement – primary • Exercise – meeting new requirements on the data model
keys • Recap – contextual, conceptual, and logical data models
• What primary keys are, what they’re really for, and three • Different skills and participants for conceptual vs. logical
essential criteria modeling
• Alternate and foreign keys • How the modeler/analysts’s role changes as a project
• Why meaningless primary keys are used, and guidelines for progresses
creating them • A little philosophy for effective data modeling
• Guidelines for reference data • The four Ds of data modeling – definition, dependency,
• Pulling it together – key techniques and guidelines covered detail, and demonstration
in the class so far • Wrap-up – the approach we followed throughout the class
ALEC SHARP
ALEC SHARP, a senior consultant with Clariteq Systems Consulting, has deep expertise in a rare combination of
fields – business analysis and requirements specification, data modelling, strategy development, facilitation,
and, of course, business process modelling, analysis, and design. His 30+ years of hands-on consulting
experience, practical approaches, and global reputation in model-driven methods have made him a sought-after
resource in locations as diverse as Ireland, Illinois, and India.
He is also a popular conference speaker on the Business Process Management, Business Analysis, and Data
Management circuits, mixing content and insight with irreverence and humor. Among his many “top-rated of the
conference” presentations are “The Lost Art of Conceptual Modelling,” “The Human Side of Data Modelling,”
“Getting Traction for ‘Process’ – What the Experts Forget,” “Mind the Gap! – Integrating Process, Data, and
Requirements Modelling,” and “Adventures in Reverse-Engineering – What You’ve Got and Why You Don’t Like It.”
At Enterprise Data World 2010, Alec was awarded DAMA’s 2010 Professional Achievement Award, a global award
given to one professional a year for contributions to the Data Management profession. At the Building Business
Capability 2012 and 2013 conferences, and several other recent events, Alec was the highest-rated speaker.
Alec literally wrote the book on business process modelling – he is the author of “Workflow Modelling: Tools
for Process Improvement and Application Development – second edition.” Popular with process improvement
professionals, business analysts, and consultants, it is consistently a top-selling title on business process
modelling, analysis, and design, and is widely used as an MBA textbook. The completely rewritten second
edition was published in 2009. His quarterly column “A Practitioner’s Perspective” appears at BPTrends.com.
Alec’s popular workshops on Working with Business Processes, Data Modelling (introductory and advanced,)
Requirements Modelling (with Use Cases and Business Services,) and Facilitation and Presentation Skills are
conducted at many of the world’s best-known organs. Conducted on five continents in the last year alone, his
classes are practical, energetic, and fun, consistently earning “excellent” ratings.
INFORMATION
In-House Training
Would you like to run this course in-company for a group of persons? We can provide a quote for running an in-house
course, if you offer the following details. Estimated number of delegates, location (town, country), number of days required
(if different from the public course) and the preferred date/period (month).