Modeling Tool in One of My System

Modeling Tool In one of my system projects, I used the Logical Data Model to build separate models for each logical entity of the project. With Logical Data Model, it allowed me to represent each area of the system with one model diagram. Thus, the entire project encyclopedia is composed of separate data models that can be assembled into one complete system.

Logical data modeling can meet the needs of every system development because it is a very efficient method of creating a project model especially if the system is a large system. This method minimizes confusion during the process of developing a system's model. This is because one only needs to focus on the main function of each entity, what the entity needs to do, use, and provide, to other entities of the system.

For instance, in a word processor application, we can have separate data model diagram for the Save, New Document, and Edit functions. Thus, if one is to work on the Save function, all he needs to think about is the logic behind saving a document, what the function needs to use, how to do the process of saving a document, and what the function needs to output that can later be used by other functions. Moreover, logical data modeling is effective, efficient, and user-friendly in terms of documentation.

Because each logical entity has a separate data model, information about an entity can be easily found should there be a need such as during system modifications. Also, logical data modeling can save time because each logical entity can be tested separately. However, although each logical area of a system has a separate data model, one drawback.