Overview

Data modelling is critical to the design of quality databases, but is also essential to other requirements specification techniques such as workflow modelling, use cases, and service definition because it ensures a common understanding of the things – the entities – that processes and applications deal with.  This workshop introduces entity-relationship modelling from a non-technical perspective, and explores contextual, conceptual, and detailed modelling techniques that maximise user involvement.

Data modelling was originally developed as a tool for improving database design, but has become a fundamental requirements definition technique for all business analysts, whether they are primarily concerned with data structures, application logic, user interface behavior, or business processes.

A key driver is that applying data modelling early in requirements definition allows analysts and clients to develop a common understanding of the business entities (e.g., Customer, Order, Product, Part, etc.) that business processes and information systems deal with, their interrelationships, and the rules that govern them.  This eliminates the problems of inconsistent terminology and conflicting assumptions that otherwise plague application development, package selection and implementation, system integration, and process redesign projects.

This workshop introduces entity-relationship modelling from a non-technical perspective, thoroughly covering the basic components of a data model – entities, relationships, attributes, and identifiers.  In addition to showing how and when to use these components in developing a data model, it includes far more advice on the process of developing a data model than other courses, including specific methods for getting subject matter experts involved and maintaining their commitment. The content is presented within the context of a clearly-defined, three-phase data modelling methodology that supports progressive detail and precision.

  • This workshop is packed with practical tips, techniques, “scripts,” checklists, and guidelines for the analyst. All of the material is based on years of project experience; abstract theory is avoided.
  • The emphasis is on “business-friendly” techniques which support and encourage the full involvement of non-technical subject matter experts, which is essential for quality data models

All public courses are available as in-house training. Contact us for more information.

Learning Objectives

  • Apply a variety of techniques that support the active participation and engagement of business professionals and subject matter experts
  • Use entity-relationship modelling to depict facts and rules about business entities at different levels of detail, including conceptual (overview) and logical (detailed) models
  • Use top-down and bottom-up approaches to initiating development of a data model
  • Recognise the four basic patterns in data modelling, and when to use them
  • Effectively use definitions and assertions (“rules”) as part of data modelling
  • Use an intuitive approach to data normalisation within an entity-relationship model
  • Apply various techniques for discovering and meeting additional requirements
  • Read a data model, and communicate with specialists using the appropriate terminology

Course Outline

Essentials of Data Modelling
  • What really is a data model?
  • Essential components – entities, relationships, and attributes
  • Hands-on case study – how data modelling resolved business issues, and supported other business analysis techniques
  • The basics of diagramming – Entity-Relationship Diagrams (“ERDs”)
  • The narrative parts of a data model – definitions and assertions
  • Group exercise – getting started on a data model, then refining it
  • Common misconceptions about data models and data modelling
  • The real purpose of a data model
  • Three types of data models – different levels of details for different purposes
  • Contextual, Conceptual, and Logical Data Models – purpose, audience, definition, and examples
  • How data models help in process improvement, requirements definition, and reporting
  • Forward- and reverse-engineering uses of data modelling
  • Overview of a three-phase methodology for developing a data model
  • References – books and useful web sites

Establish the Initial Conceptual Data Model

  • Top down vs. bottom up approaches to beginning a data model – when is each appropriate?
  • Advantages of a bottom-up approach
  • A bottom-up approach focusing on collecting and analyzing terminology
  • A structure for sorting terms and discovering entities
  • Exercise – developing an initial conceptual data model
  • Entities – what they are and are not
  • Guidelines for naming and defining entities
  • Three questions to help you quickly develop clear, useful entity definitions
  • Five criteria that entities must satisfy, and four common errors in identifying entities
  • Exercise – identifying flawed entities
  • Identifying relationships
  • Fundamental vs. irrelevant or transitive relationships
  • Good and bad relationship names
  • Multiplicity or cardinality – 1:1, 1:M, and M:M relationships, and useful facts about each
  • Common errors and special cases – recursive, multiple, and supertype-subtype relationships
  • Attributes – guidelines and types
  • Attributes in conceptual models vs. logical models

Develop the Initial Logical Data Model By Adding Rigour, Structure and Detail

  • What’s involved in developing a logical model – shifting the focus from entities to attributes
  • Multi-valued, redundant, and constrained attributes, with simple patterns for dealing with each
  • An understandable guide to normalisation – first, second, and third normal forms
  • Higher order (fourth and fifth) and Boyce-Codd normal forms
  • Guidelines for a smooth progression from conceptual to 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 whenever a data range appears in a data model
  • Identifying and dealing with transitive relationships – clues and proof

Refine and extend the logical data model by discovering and meeting new requirements

  • Attribute granularity – definitions of non-atomic and semantically overloaded attributes
  • Guidelines for making non-atomic attributes atomic
  • The perils of semantic overload, and what to do about it
  • Dealing with derived attributes, and when to show them on the model
  • A classword-based approach to attribute naming
  • Typical attribute documentation
  • A common source of confusion and disagreement – primary keys
  • What primary keys are, what they’re really for, and three essential criteria
  • Alternate and foreign keys
  • Why meaningless primary keys are used, and guidelines for creating them
  • Guidelines for reference data
  • Pulling it together – key techniques and guidelines covered in the class so far
  • Using event analysis to discover additional requirements
  • Exercise – using event analysis and extending a data model
  • Presentation by teams of their solutions
  • How data modelling relates to process modelling, use cases, and services
  • A layered framework for business analysts
  • How other techniques (e.g., workflow modelling) support data modelling
  • A three-step procedure for meeting new requirements
  • Advice on extending the model in an orderly fashion
  • Exercise – meeting new requirements on the data model
  • Recap – contextual, conceptual, and logical data models
  • Different skills and participants for conceptual vs. logical modelling
  • How the modeler’s/analyst’s role changes as a project progresses
  • A little philosophy for effective data modelling
  • The four Ds of data modelling – definition, dependency, detail, and demonstration
  • Wrap-up – the approach we followed throughout the class

Who It's For

  • New or experienced Data Modellers, Data Analysts, and DBAs will benefit from the workshop’s practical methods and guidelines.
  • Business Analysts and Application Designers/Developers who need to understand data modelling and how it supports requirements definition or process analysis.
  • Business Professionals and Managers who need to understand how this technique can uncover and resolve inconsistency in business terminology, policy, and rules.

Speaker

Alec Sharp

Senior Consultant, Clariteq Systems Consulting

Alec Sharp, a senior consultant with Clariteq Systems Consulting, has deep expertise in a rare combination of fields – business process analysis and redesign, strategy development, application requirements specification, and data modelling. His 35 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, mixing content and insight with irreverence and humor. Among his many top-rated presentations are “The Lost Art of Conceptual Modeling,” “Modelling Failure,” “Getting Traction for ‘Process’ – What the Experts Forget,” and “Mind the Gap! – Integrating Process, Data, and Requirements Modeling.”

Alec wrote the book on business process modeling – he is the author of “Workflow Modeling: 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 modeling, and is widely used as an MBA textbook. The completely rewritten second edition was published in 2009, and has a “5 star” Amazon.com rating. Alec was also the sole recipient of DAMA’s 2010 Professional Achievement Award, a global award for contributions to the Data Management field.

Alec’s popular workshops on Working With Business Processes, Data Modeling (introductory and advanced,) Requirements Modeling (with Use Cases and Business Services,) and Essentials of Facilitation and are conducted at many of the world’s best-known organizations. His classes are practical, energetic, and fun, with a most common participant comment being “best course I’ve ever taken.”

Fees

  • 2 Days
  • £1245
  • £1,245 + VAT (£249) = £1,494
Group Booking Discounts
Delegates
2-3 10% discount
4-5 20% discount
6 + 25% discount

Cancellation Policy:
Cancellations must be received in writing at least two weeks before the commencement of the seminar and will be subject to a 10% administration fee. It is regretted that cancellations received within two weeks of the seminar date will be liable for the full seminar fee. Substitutions can be made at any time.

Cancellation Liability:
In the unlikely event of cancellation of the seminar for any reason, IRM UK’s liability is limited to the return of the registration fee only. IRM UK will not reimburse delegates for any travel or hotel cancellation fees or penalties. It may be necessary, for reasons beyond the control of IRM UK, to change the content, timings, speakers, date and venue of the seminar.

Venue

  • etc.venues Marble Arch
  • Garfield House
  • 86 Edgware Road
  • London W2 2EA

Accommodation

London Accommodation: IRM UK in association with JP Events Ltd has arranged special discounted rates at all venues and at other hotels nearby the venue. Please visit the JP Events website for further information.  Email: jane@jpetem.com Tel +44 (0)84 5680 1138 Fax +44 (0)84 5680 1139
This site uses cookies: Find out more.