What do you think?
Rate this book
Data Modeling Made Simple: With Er/Studio Data Architect
Data Modeling Made Simple with ER/Studio Data Architect (DA) will provide the business or IT professional with a practical working knowledge of data modeling concepts and best practices, along with how to apply these principles with ER/Studio DA. You'll build many ER/Studio DA data models along the way, applying best practices to master these ten This book contains four
Section I introduces data modeling and the ER/Studio DA landscape. Learn why data modeling is so critical to software development and even more importantly, why data modeling is so critical to understanding the business. You will also learn about the ER/Studio DA environment. By the end of this section, you will have created and saved your first data model in ER/Studio DA and be ready to start modeling in Section II!
Section II explains all of the symbols and text on a data model, including entities, attributes, relationships, domains, and keys. By the time you finish this section, you will be able to 'read' a data model of any size or complexity, and create a complete data model in ER/Studio DA.
Section III explores the three different levels of conceptual, logical, and physical. A conceptual data model (CDM) represents a business need within a defined scope. The logical data model (LDM) represents a detailed business solution, capturing the business requirements without complicating the model with implementation concerns such as software and hardware. The physical data model (PDM) represents a detailed technical solution. The PDM is the logical data model compromised often to improve performance or usability. The PDM makes up for deficiencies in our technology. By the end of this section you will be able to create conceptual, logical, and physical data models in ER/Studio DA.
Section IV discusses additional features of ER/Studio DA. These features include data dictionary, data lineage, automating tasks, repository and portal, exporting and reporting, naming standards, and compare and merge functionality.
Section I introduces data modeling and the ER/Studio DA landscape. Learn why data modeling is so critical to software development and even more importantly, why data modeling is so critical to understanding the business. You will also learn about the ER/Studio DA environment. By the end of this section, you will have created and saved your first data model in ER/Studio DA and be ready to start modeling in Section II!
Section II explains all of the symbols and text on a data model, including entities, attributes, relationships, domains, and keys. By the time you finish this section, you will be able to 'read' a data model of any size or complexity, and create a complete data model in ER/Studio DA.
Section III explores the three different levels of conceptual, logical, and physical. A conceptual data model (CDM) represents a business need within a defined scope. The logical data model (LDM) represents a detailed business solution, capturing the business requirements without complicating the model with implementation concerns such as software and hardware. The physical data model (PDM) represents a detailed technical solution. The PDM is the logical data model compromised often to improve performance or usability. The PDM makes up for deficiencies in our technology. By the end of this section you will be able to create conceptual, logical, and physical data models in ER/Studio DA.
Section IV discusses additional features of ER/Studio DA. These features include data dictionary, data lineage, automating tasks, repository and portal, exporting and reporting, naming standards, and compare and merge functionality.
268 pages, Paperback
First published April 15, 2013
2 people are currently reading
4 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
May 27, 2018
This is not a book on data modeling. It is just a user manual for the ER studio. I have a license and am learning it, but I guess this book is not where you should start.
Displaying 1 of 1 review