Data Abstraction for Data Managers

The topic of abstraction and its uses and dangers in development, object-oriented programming, and data modelling is discussed by Howard. He shares his experience of learning about the hazards of abstraction from Steve Hoberman’s course and how it can create more responsibility for developers.

The concept of abstraction safety guide and its use in simplifying data models and presenting information to business users is explored. Partitioning and absorption are also discussed. The process of specifying, from business requirements to technical details, and the definitions of "specification" and "abstraction" are explained in detail.

The different levels of understanding for specifications, such as a detailed description of work or materials for a project, instructions on how to do or make something, and architect specifications for a new building, are described.

Creating a believable visual presentation to define high-level requirements and using a conceptual model to get precise definitions for eliciting requirements to create a business glossary and threading logic from top to bottom is explained.