Watch the companion webinar at: http://embt.co/1v0tzNY Before joining Embarcadero’s Product Management team, Ron Huizenga worked as an independent consultant for 20 years. He used both ERwin and ER/Studio with a wide range of customers and concluded that ER/Studio had the right features and capabilities to address the complex enterprise data architecture needs of his clients. Based on his personal experience, he explains the top ten reasons why he made the switch to ER/Studio, and addresses topics including: + Clear views of both logical and physical models in the intuitive ER/Studio user interface + Flexible and user-friendly features including Macros, Naming Standards, and Compare and Merge operations + Capabilities such as Universal Mappings that ERwin doesn’t offer

1. EMBARCADERO TECHNOLOGIESEMBARCADERO TECHNOLOGIES
Top 10 Reasons Why I
Switched to ER/Studio
Ron Huizenga
Product Manager – ER/Studio
Ron.Huizenga@embarcadero.com

2. EMBARCADERO TECHNOLOGIES
Areas of Discussion
• Background
• Which major capabilities are most important?
• Which tool is better, and why?
• How long will it take me to be productive?
• Which tool has shown a pattern of innovation?
• Which is the best long term investment?
2

3. EMBARCADERO TECHNOLOGIES
My Background
• I have been in IT industry for > 30 years
• CIO (manufacturing organization)
• Consulting Firms
• Independent Consultant for 20 years
– Primary focus on data architecture, business modeling,
business transformation
• Many different industries
• Joined Embarcadero June 2014
3

4. EMBARCADERO TECHNOLOGIES
Modeling Tools
• Data Modeling tools including
– ADW, Engage, Silverrun, ERwin, ER/Studio +others
• CASE tools based on relational models
• Business / Process Modeling
• UML Tools
• Enterprise Architecture
• Designed and built reverse engineering tools
4

5. EMBARCADERO TECHNOLOGIES
The Top 10
1. Sub-models
2. Logical/Physical Separation
3. Reverse Engineering
4. Metadata extensions
5. Naming Standards
6. Compare and Merge
7. Macros
8. Universal mappings
9. Native support – Big Data
10. Repository, Publishing &
Collaboration
5

6. EMBARCADERO TECHNOLOGIES
1: Submodels
• What is a Submodel?
– A collection of model objects relevant to a specific topic or
audience
– Breakdown of business areas/subjects
– Business decomposition
– Ideally, should be business focused
6

7. EMBARCADERO TECHNOLOGIES
1: Business Decomposition (partial) Example
7
Supply Chain
Example
Corporate
Structure
Document
Management
Facilties and
Equipment
Equipment
Object
Facilities
Infrastructure
Maintenance
Planning
Operations
Inventory/Linefill
Sampling
Transit Metrics
Order Processing
Change Requests
Nominations and
Splits
Nominations -
Basic
Nominations -
Enhancements
Nominations -
Scenarios
Planning and
Scheduling
Capacity
Management
Scheduling
Rules Framework
Planning
Portal Framework
Portal
Permissions
Products Supply Contracts

8. EMBARCADERO TECHNOLOGIES
1: ER/Studio Submodels - collapsed
8

9. EMBARCADERO TECHNOLOGIES
1: ER/ Studio Submodels – expanded
9

10. EMBARCADERO TECHNOLOGIES
1: ERwin – Subject Areas
10
XXX Data Modeler – [Supply Chain Operations Sample.xxxxx ]
ViewEditFile Format Model Tools Services Window Help
Logical
Subject AreaModel

11. EMBARCADERO TECHNOLOGIES
1: Sub-Models - most capable
• ER/Studio
– Miles ahead in sub-model capability
– True business decomposition
– Enabled by the underlying design of ER/Studio
• Managing and addressing real world complexity
11

12. EMBARCADERO TECHNOLOGIES
2: Logical/Physical Model Separation
Data Management Body of Knowledge (DMBOK):
A data model is a representation of the data describing real-world
objects and the relationships between the objects, independent of
any associated process. Generally speaking, there are 3 levels of
data modeling that are utilized, in order of abstraction:
– Conceptual Models
– Logical Models
– Physical Models
12

13. EMBARCADERO TECHNOLOGIES
2: ERwin – Tightly Coupled Logical/Physical
• Design Layers
– Logical model file
– Physical model file
– Combined model file
(classic)
• 3 levels advocated
– Conceptual Logical model
– Generic physical model
– Database specific physical
model
13
XXX Data Modeler – [Supply Chain Operations Sample.xxxxx ]
ViewEditFile Format Model Tools Services Window Help
Logical
Subject AreaModel

14. EMBARCADERO TECHNOLOGIES
2: Conceptual Model - ER/Studio
• Abstract
• Business entities
• Business relationships
• Typically not fully attributed
• Typically not normalized
14

15. EMBARCADERO TECHNOLOGIES
2: ER/Studio – Logical/Physical Separation
15

16. EMBARCADERO TECHNOLOGIES
2: ER/Studio – Where Used
16

17. EMBARCADERO TECHNOLOGIES
2: Logical/Physical Separation - most capable
• ER/Studio
– True conceptual, logical, physical models
– Loose coupling for ultimate flexibility
– Where used for traceability
17

18. EMBARCADERO TECHNOLOGIES
3: Reverse Engineering
• The ability to create a data model by connecting to
an existing database
– Native connector
– ODBC
– Can also be SQL script rather than direct connection
• Vital to map & analyze complex data landscapes
18

19. EMBARCADERO TECHNOLOGIES
3: Reverse Engineering Wizard – ER/Studio
19

20. EMBARCADERO TECHNOLOGIES
3: Reverse Engineering – ER/Studio continued
20

21. EMBARCADERO TECHNOLOGIES
3: Reverse Engineering – Most capable
• Both tools are quite good
• ER/Studio has the edge
– Range of native platforms
– More intuitive
– Ease of use
21

22. EMBARCADERO TECHNOLOGIES
4: Metadata Extensions
• Definition and creation of additional metadata for
model objects
• Many uses
– Data governance
– Data quality
– Master data management
– Data retention policies
22

23. EMBARCADERO TECHNOLOGIES
4: ERwin – User Defined Properties
23

24. EMBARCADERO TECHNOLOGIES
4: ER/Studio – Attachment Setup
24

25. EMBARCADERO TECHNOLOGIES
4: Attachments on Diagrams
25

26. EMBARCADERO TECHNOLOGIES
4: ER/Studio – Attachments, Data Dictionary
26

27. EMBARCADERO TECHNOLOGIES
4: Metadata Extensions – Most Capable
• ER/Studio
– More flexible, centralized definition
– Ease of use
– Ability to attach actual documents
– Traceable bindings
– Expanded even further in Team Server Core
• Including business glossaries & term
27

28. EMBARCADERO TECHNOLOGIES
5: Naming Standards
• Extremely important
– Define
– Apply
– Enforce
• Represent real world
business objects
• Typically comprised of
– Business terms
– Abbreviation for each
– Template (specify order)
– Case
– Prefixes, Suffixes
28

29. EMBARCADERO TECHNOLOGIES
5: Naming Standards Setup/Usage
• Typical use case (both tools)
– Logical -> physical
• Entity name -> table name
• Attribute name -> column name
• Landscape Mapping (ER/Studio)
– Physical -> logical
– Table name -> entity name
– Column Name -> attribute name
29

30. EMBARCADERO TECHNOLOGIES
5: ERwin – Apply Naming Standards
30
• Macro formulas
– Defaults provided
– Model naming options editor
• Tight coupling of logical -> physical models
• Also utility to find/display nonstandard names
• Names can be locked down (name hardening)

31. EMBARCADERO TECHNOLOGIES
5: ER/Studio – Apply naming Standards
• Can invoke with other wizards
– General Physical Model
– Compare & Merge
– XML Schema Generation
– Model Validation
• Can apply to model or sub-model at any
time
• Either Direction
• Selective review/apply
• Enabled by loose model coupling
• Name lockdown (freeze names)
31

32. EMBARCADERO TECHNOLOGIES
5: Naming Standards – Most Capable
• ER/Studio
– Flexible
– Intuitive
– More powerful
– Bidirectional
– Invoke in combination with other wizards
32

33. EMBARCADERO TECHNOLOGIES
6: Compare and Merge
• Compare Model (or sub-model) to
– Another model (sub-model)
– Database
• Where there are differences
– Characteristics to merge from source -> target specified
• Reports can be Generated
33

34. EMBARCADERO TECHNOLOGIES
6: ERwin – Complete Compare
34

35. EMBARCADERO TECHNOLOGIES
6: ER/Studio Compare & Merge Scope
• Compare logical model to
– A physical model in the same .dm1 file.
– A logical model of another ER/Studio Data Architect data model.
– A physical model of another ER/Studio Data Architect data model.
• Compare physical model to
– The logical model of the same data model.
– Another physical model of the same data model that shares the same DBMS
platform (and version).
– A logical model of another ER/Studio Data Architect data model.
– A physical model of another ER/Studio Data Architect data model sharing the same
DBMS platform (and version).
– A live database.
– An SQL file.
35

36. EMBARCADERO TECHNOLOGIES
6: ER/Studio – Compare and Merge A
36

37. EMBARCADERO TECHNOLOGIES
6: ER/Studio – Compare and Merge B
37

38. EMBARCADERO TECHNOLOGIES
38
6: ER/Studio – Compare and Merge C

39. EMBARCADERO TECHNOLOGIES
39
6: ER/Studio – Compare and Merge D

40. EMBARCADERO TECHNOLOGIES
40
6: ER/Studio – Compare and Merge E

41. EMBARCADERO TECHNOLOGIES
41
6: ER/Studio – Compare and Merge F

42. EMBARCADERO TECHNOLOGIES
42
6: ER/Studio – Compare and Merge Script

43. EMBARCADERO TECHNOLOGIES
6: Compare & Merge – Most Capable
• ER/Studio (miles ahead)
– Very intuitive
– Much easier to use
– Less error prone
– Flexible sources/targets
– Bidirectional capability
43

44. EMBARCADERO TECHNOLOGIES
7: Macros
• Scripting language to
– Apply automation within the tool
– Apply changes to model objects
44

45. EMBARCADERO TECHNOLOGIES
7: ERwin Macros
• Typically used for
– Name physical objects (application of naming standards)
– Pre & post scripts
• Table level
• Model level
– Stored procedure templates
– Trigger templates
• ERwin Macro Scripting
– Toolbox (not intuitive at all)
– Cumbersome syntax using special characters (formulas)
– Difficult to grasp, especially for new users
45

46. EMBARCADERO TECHNOLOGIES
7: ER/Studio - Macros
• True language (SAX basic)
• Fully functional editor
• Automation interface
– Scriptable controls
– Automate repetitive tasks
– Event Handlers
• Some use cases
– Update objects
– Import/export metadata
– Change display properties
– Model layout
– Generation of physical DB metadata
• Extensive macro set shipped with product
– Can be copied, modified
– New can be built from scratch if desired
46

47. EMBARCADERO TECHNOLOGIES
7: Macros – Most Capable
• ER/Studio (no contest)
– Much more capable
– True programming language
– Much easier to use
– Many included as part of the product
47

48. EMBARCADERO TECHNOLOGIES
8: Universal Mappings
• Ability to link “like” or related objects
– Within same model file
– Across separate model files
• Entity/Table level
• Attribute/Column level
48

49. EMBARCADERO TECHNOLOGIES
8: ER/Studio – Universal Mappings
49

50. EMBARCADERO TECHNOLOGIES
8: Universal Mappings – Most Capable
• ER/Studio
– Feature is exclusive to ER/Studio
50

51. EMBARCADERO TECHNOLOGIES
9: Native Support for Big Data
• Ability to model big data constructs
– Nested objects
– Nested object arrays
• Natively reverse engineer big data platforms
– Internal to tool as opposed to MetaWizard
• Forward engineering
51

52. EMBARCADERO TECHNOLOGIES
9: ER/Studio – Native Big Data Support
• MongoDB
– Versions 2.4 and 2.6
• Hadoop Hive
– Versions 0.12 and 0.13
• Capabilities
– Diagramming
– Reverse Engineering (JSON, BSON)
– DDL supported for Hive
52

53. EMBARCADERO TECHNOLOGIES
9: ER/Studio – Big Data Notation Enhancement
• Physical Model
– Objects instead of Tables
• Nested Objects
– “Is Contained In”
relationship type
53

54. EMBARCADERO TECHNOLOGIES
9: Native Support for Big Data – Most Capable
• ER/Studio
– Extended notation
– Native drivers for reverse/forward engineering
– True native support not offered in ERwin
54

55. EMBARCADERO TECHNOLOGIES
10: Repository, Publishing, Collaboration
• Support of large, collaborative teams
– Data architects, modelers
– Business analysts
– Business stakeholders
• Repository-based Checkout, checkin
– Full sub-models
– Individual objects
• Publish & collaborate
– Web portal
– Native reports
• Business stakeholder active participation in creation of metadata
• Notifications
55

56. EMBARCADERO TECHNOLOGIES
10: Repository
ERwin
• Model Manager Mart
• Model/subject area
checkout
• Mart is approx. 25 tables
– Name/value pair storage
ER/Studio
• ER/Studio Repository
• Model/submodel or individual
object checkout
• Repository is relational
database with many tables
• Named versions
• Branch & merge
• Business architect workspace
checkin & checkout
56

57. EMBARCADERO TECHNOLOGIES
10: Publishing
ERwin
• Portal Publishing
• Native Reports
– Html, pdf
– Static images in html
ER/Studio
• Portal Publishing (Team Server)
• Native Reports
– Html, rtf
– Clickable drill down to metadata
in html
– Rtf can be augmented in a tool
like word, then published (rtf, pdf
etc)
57

58. EMBARCADERO TECHNOLOGIES
• Powerful enterprise glossary, model & metadata collaboration
• Integrate key business terms and definitions with business systems
• View, store, and manage a single source of business definitions
• Attach business policies to daily workflows with contextual alerts and tips
10: Collaboration
58

59. EMBARCADERO TECHNOLOGIES
10: ER/Studio Team Server – Model Explorer
59

60. EMBARCADERO TECHNOLOGIES
10: ER/Studio Team Server Core – Glossary/Terms
60

61. EMBARCADERO TECHNOLOGIES
10: Repository, Publishing, Collaboration – Most Capable
• ER/Studio
– More advanced in repository & publishing
– Collaboration functionality is way ahead
61

62. EMBARCADERO TECHNOLOGIES
Comparative Review
1. Sub-models
2. Logical/Physical Separation
3. Reverse Engineering
4. Metadata extensions
5. Naming Standards
6. Compare and Merge
7. Macros
8. Universal mappings
9. Native support – Big Data
10. Repository, Publishing &
Collaboration
62

63. EMBARCADERO TECHNOLOGIES
Concluding Remarks
63

64. EMBARCADERO TECHNOLOGIES
Thank you!
• Learn more about the ER/Studio product family:
http://www.embarcadero.com/data-modeling
• Trial Downloads:
http://www.embarcadero.com/downloads
• To arrange a demo, please contact Embarcadero
Sales: sales@embarcadero.com, (888) 233-2224
64