Bücher von Steve Hoberman

The Align > Refine > Design series covers conceptual, logical, and physical data modeling (schema design and patterns) for leading technologies, combining proven data modeling practices with database-specific features to produce better applications. Read Cassandra Data Modeling and Schema Design if you are a data professional who needs to expand your modeling skills to include Cassandra or a technologist who knows Cassandra but needs to grow your schema design skills.The book's introduction and three chapters cover the Align, Refine, and Design approach. We include what the level does in the name by rebranding Conceptual, Logical, and Physical into Align, Refine, and Design. The introduction covers the three modeling characteristics of precise, minimal, and visual; the three model components of entities, relationships, and attributes (including keys); the three model levels of conceptual (align), logical (refine), and physical (design); and the three modeling perspectives of relational, dimensional, and query. Chapter 1, Align, is about agreeing on the common business vocabulary so everyone is aligned on terminology and general initiative scope. Chapter 2, Refine, is about capturing the business requirements. That is, refining our knowledge of the initiative to focus on what is essential. Chapter 3, Design, is about the technical requirements. That is, designing to accommodate our model's unique software and hardware needs.Align, Refine, and Design-that's the approach followed in this book and reinforced through an animal shelter case study. If you are interested in learning how to build multiple database solutions, read all the books in the Align > Refine > Design series. Since each book uses the same template, you can quickly skill up on additional database technologies.

The Align > Refine > Design series covers conceptual, logical, and physical data modeling (schema design and patterns) for leading technologies, combining proven data modeling practices with database-specific features to produce better applications. Read TerminusDB Data Modeling and Schema Design if you are a data professional who needs to expand your modeling skills to include TerminusDB or a technologist who knows TerminusDB but needs to grow your schema design skills.The book's introduction and three chapters cover the Align, Refine, and Design approach. We include what the level does in the name by rebranding Conceptual, Logical, and Physical into Align, Refine, and Design. The introduction covers the three modeling characteristics of precise, minimal, and visual; the three model components of entities, relationships, and attributes (including keys); the three model levels of conceptual (align), logical (refine), and physical (design); and the three modeling perspectives of relational, dimensional, and query. Chapter 1, Align, is about agreeing on the common business vocabulary so everyone is aligned on terminology and general initiative scope. Chapter 2, Refine, is about capturing the business requirements. That is, refining our knowledge of the initiative to focus on what is essential. Chapter 3, Design, is about the technical requirements. That is, designing to accommodate our model's unique software and hardware needs.Align, Refine, and Design-that's the approach followed in this book and reinforced through an animal shelter case study. If you are interested in learning how to build multiple database solutions, read all the books in the Align > Refine > Design series. Since each book uses the same template, you can quickly skill up on additional database technologies.

The Align > Refine > Design series covers conceptual, logical, and physical data modeling (schema design and patterns) for leading technologies, combining proven data modeling practices with database-specific features to produce better applications. Read Elasticsearch Data Modeling and Schema Design if you are a data professional who needs to expand your modeling skills to include Elasticsearch or a technologist who knows Elasticsearch but needs to grow your schema design skills.The book's introduction and three chapters cover the Align, Refine, and Design approach. We include what the level does in the name by rebranding Conceptual, Logical, and Physical into Align, Refine, and Design. The introduction covers the three modeling characteristics of precise, minimal, and visual; the three model components of entities, relationships, and attributes (including keys); the three model levels of conceptual (align), logical (refine), and physical (design); and the three modeling perspectives of relational, dimensional, and query. Chapter 1, Align, is about agreeing on the common business vocabulary so everyone is aligned on terminology and general initiative scope. Chapter 2, Refine, is about capturing the business requirements. That is, refining our knowledge of the initiative to focus on what is essential. Chapter 3, Design, is about the technical requirements. That is, designing to accommodate our model's unique software and hardware needs.Align, Refine, and Design-that's the approach followed in this book and reinforced through an animal shelter case study. If you are interested in learning how to build multiple database solutions, read all the books in the Align > Refine > Design series. Since each book uses the same template, you can quickly skill up on additional database technologies.

The Align > Refine > Design series covers conceptual, logical, and physical data modeling (schema design and patterns) for leading technologies, combining proven data modeling practices with database-specific features to produce better applications. Read Neo4j Data Modeling if you are a data professional who needs to expand your modeling skills to include Neo4j or a technologist who knows Neo4j but needs to grow your schema design skills.The book's introduction and three chapters cover the Align, Refine, and Design approach. We include what the level does in the name by rebranding Conceptual, Logical, and Physical into Align, Refine, and Design. The introduction covers the three modeling characteristics of precise, minimal, and visual; the three model components of entities, relationships, and attributes (including keys); the three model levels of conceptual (align), logical (refine), and physical (design); and the three modeling perspectives of relational, dimensional, and query. Chapter 1, Align, is about agreeing on the common business vocabulary so everyone is aligned on terminology and general initiative scope. Chapter 2, Refine, is about capturing the business requirements. That is, refining our knowledge of the initiative to focus on what is essential. Chapter 3, Design, is about the technical requirements. That is, designing to accommodate our model's unique software and hardware needs.Align, Refine, and Design-that's the approach followed in this book and reinforced through an animal shelter case study. If you are interested in learning how to build multiple database solutions, read all the books in the Align > Refine > Design series. Since each book uses the same template, you can quickly skill up on additional database technologies.

<strong>Creating a precise diagram of business terms within your projects is a simple yet powerful communication tool for project managers, data governance professionals, and business analysts.</strong><br><br><br>With more and more data being created and used, combined with intense competition, strict regulations, and rapid-spread social media, the financial, liability, and credibility stakes have never been higher and therefore the need for a Common Business Language has never been greater. Appreciate the power of the BTM and apply the steps to build a BTM over the book's five chapters:<ol><li>Challenges. Explore how a Common Business Language is more important than ever with technologies like the Cloud and NoSQL, and Regulations such as the GDPR.</li><li>Needs. Identify scope and plan precise, minimal visuals that will capture the Common Business Language. </li><li>Solution. Meet the BTM and its components, along with the variations of relational and dimensional BTMs. Experience how several data modeling tools display the BTM, including CaseTalk, ER/Studio, erwin DM, and Hackolade.</li><li>Construction. Build operational (relational) and analytics (dimensional) BTMs for a bakery chain.</li><li>Practice. Reinforce BTM concepts and build BTMs for two of your own initiatives alongside a real example. </li></ol>

Learn how blockchain works, where to use it within your organization, and how it will impact data management.This book contains three parts: Explanation. Part I will explain will explain the concepts underlying blockchain. A precise and concise definition is provided, distinguishing blockchain from blockchain architecture. Variations of blockchain are explored based upon the concepts of purpose and scope. Usage. Now that you understand blockchain, where do you use it? The reason for building a blockchain application must include at least one of these five drivers: transparency, streamlining, privacy, permanence, or distribution. Usages based upon these five drivers are shown for finance, insurance, government, manufacturing and retail, utilities, healthcare, nonprofit, and media. Process diagrams will illustrate each usage through inputs, guides, enablers, and outputs. Also examined are the risks of applying these usages, such as cooperation, incentives, and change. Impact. Now that you know where to use blockchain, how will it impact our existing IT (Information Technology) environment? Part III explores how blockchain will impact data management. The Data Management Body of Knowledge 2nd Edition (DAMA-DMBOK2) is an amazing book that defines the data management field along with the often complex relationships that exist between the various data management disciplines. Learn how blockchain will impact each of these 11 disciplines: Data Governance, Data Architecture, Data Modeling and Design, Data Storage and Operations, Data Security, Data Integration and Interoperability, Document and Content Management, Reference and Master Data, Data Warehousing and Business Intelligence, Metadata Management, and Data Quality Management.Once you understand blockchain concepts and principles, you can position yourself, department, and organization to leverage distributed ledger technology.

Data models are the main medium used to communicate data requirements from business to IT, and within IT from analysts, modelers, and architects, to database designers and developers. Therefore it's essential to get the data model right. But how do you determine right? That's where the Data Model Scorecard® comes in.The Data Model Scorecard is a data model quality scoring tool containing ten categories aimed at improving the quality of your organization's data models. Many of my consulting assignments are dedicated to applying the Data Model Scorecard to my client's data models - I will show you how to apply the Scorecard in this book.This book, written for people who build, use, or review data models, contains the Data Model Scorecard template and an explanation along with many examples of each of the ten Scorecard categories. There are three sections:In Section I, Data Modeling and the Need for Validation, receive a short data modeling primer in Chapter 1, understand why it is important to get the data model right in Chapter 2, and learn about the Data Model Scorecard in Chapter 3.In Section II, Data Model Scorecard Categories, we will explain each of the ten categories of the Data Model Scorecard. There are ten chapters in this section, each chapter dedicated to a specific Scorecard category: Chapter 4: Correctness Chapter 5: Completeness Chapter 6: Scheme Chapter 7: Structure Chapter 8: Abstraction Chapter 9: Standards Chapter 10: Readability Chapter 11: Definitions Chapter 12: Consistency Chapter 13: DataIn Section III, Validating Data Models, we will prepare for the model review (Chapter 14), cover tips to help during the model review (Chapter 15), and then review a data model based upon an actual project (Chapter 16).

Master how to data model MongoDB applications.Congratulations! You completed the MongoDB application within the given tight timeframe and there is a party to celebrate your application's release into production. Although people are congratulating you at the celebration, you are feeling some uneasiness inside. To complete the project on time required making a lot of assumptions about the data, such as what terms meant and how calculations are derived. In addition, the poor documentation about the application will be of limited use to the support team, and not investigating all of the inherent rules in the data may eventually lead to poorly-performing structures in the not-so-distant future.Now, what if you had a time machine and could go back and read this book. You would learn that even NoSQL databases like MongoDB require some level of data modeling. Data modeling is the process of learning about the data, and regardless of technology, this process must be performed for a successful application. You would learn the value of conceptual, logical, and physical data modeling and how each stage increases our knowledge of the data and reduces assumptions and poor design decisions.Read this book to learn how to do data modeling for MongoDB applications, and accomplish these five objectives: Understand how data modeling contributes to the process of learning about the data, and is, therefore, a required technique, even when the resulting database is not relational. That is, NoSQL does not mean NoDataModeling! Know how NoSQL databases differ from traditional relational databases, and where MongoDB fits. Explore each MongoDB object and comprehend how each compares to their data modeling and traditional relational database counterparts, and learn the basics of adding, querying, updating, and deleting data in MongoDB. Practice a streamlined, template-driven approach to performing conceptual, logical, and physical data modeling. Recognize that data modeling does not always have to lead to traditional data models! Distinguish top-down from bottom-up development approaches and complete a top-down case study which ties all of the modeling techniques together.