Blog Timeline Full Width

  • Can a developer read an entity/relationship diagram?

    During a recent data modeling training class, someone asked based on my experience, can developers read entity/relationship diagrams? This question was not a jab to developers. (There were quite a few developers in the room!) This question was asked because in this organization, data modelers build data models...

    Read more
    0
    Steve Hoberman
  • From VSAM to MongoDB

    An organization facing big data pressures is migrating from VSAM to MongoDB. Although VSAM is 1970s technology, it stores data hierarchically which is very similar in structure to NoSQL document-based databases such as MongoDB. Therefore the data migration from VSAM to MongoDB could be straightforward. However,...

    Read more
    0
    Steve Hoberman
  • Unstructured data classwords

    Each attribute on our data model ends in a classword. For example, “Number” is the classword in Account Number, “Name” is the classword in Customer Last Name and “Date” is the classword in Order Entry Date. As we start modeling more and more unstructured data, we...

    Read more
    0
    Steve Hoberman
  • Evolutionary or revolutionary approach to modeling NoSQL?

      The symbols we use on our data models were created with relational databases in mind. Luckily, conceptual and logical data models are independent of technology so we can still use our symbols for modeling non-relational (NoSQL) databases. When we reach the physical level however, things...

    Read more
    0
    Steve Hoberman
  • Reverse Engineering a MongoDB Document

    You are the data modeler responsible for building a logical data model of an existing NoSQL MongoDB database. Your plan is to reverse engineer the existing database into a physical data model using your data modeling tool, and then translate this physical data model into a logical...

    Read more
    1
    Steve Hoberman