Let's step back to the year 1978. Sony introduces hip portable music with the Walkman, Illinois Bell Company releases the first mobile phone, Space Invaders kicks off the video game craze, and William Kent writes Data and Reality. We have made amazing progress in the last four decades in terms of portable music, mobile communication, and entertainment, making devices such as the original Sony Walkman and suitcase-sized mobile phones museum pieces today. Yet remarkably, the book Data and Reality is just as relevant to the field of data management today as it was in 1978.
Data and Reality gracefully weaves the disciplines of psychology and philosophy with data management to create timeless takeaways on how we perceive and manage information. Although databases and related technology have come a long way since 1978, the process of eliciting business requirements and how we think about information remains constant. This book will provide valuable insights whether you are a 1970s data-processing expert or a modern-day business analyst, data modeler, database administrator, or data architect.
This third edition of Data and Reality differs substantially from the first and second editions. Data modeling thought leader Steve Hoberman has updated many of the original examples and references and added his commentary throughout the book, including key points at the end of each chapter.
The important takeaways in this book are rich with insight yet presented in a conversational writing style. Here are just a few of the issues this book tackles:
Has "business intelligence" replaced "artificial intelligence"?
Why is a map's geographic landscape analogous to a data model's information landscape?
Where do forward and reverse engineering fit in our thought process?
Why are we all becoming "data archeologists"?
What causes the communication chasm between the business professional and the information technology professional, and how can the logical data model bridge this gap?
Why do we invest in hardware and software to solve business problems before determining what the business problems are in the first place?
What is the difference between oneness, sameness, and categories?
Why does context play a role in every design decision?
Why do the more important attributes become entities or relationships?
Why do symbols speak louder than words?
What's the difference between a data modeler, a philosopher, and an artist?
Why is the 1975 dream of mapping all attributes still a dream today?
What influence does language have on our perception of reality?
Can we distinguish between naming and describing?