Database Design- Dependency Diagram - Essay Example

s Dependency diagram and its use A dependency diagram is a graphical representation of a dependency chart graphs. These diagrams are vital in software pack development by outlining the complexity and the interrelationships of various functional elements (Bagui and Earp 739). However, in the dependency diagrams arrows point from the modules they are dependent to other modules they depend upon. These dependency diagrams are used to assist in the normalization of data in a given database. They are used to show the high level of dependence between modules in a database structure.

It might not be necessary to show all the data dependencies among the various modules because some module might be unconnected in a sequence or time and hence these are not illustrated on a dependency diagram. For example, a module might give data that cannot be used by another module until time lasts. In this scenario, the existing dependency among these modules will be left off in the dependency diagram.The dependency diagrams are also vital and useful when there exits’ complex dependency of module in a database system.

Otherwise, the effort which is required to complete the dependency diagram is not warranted in complex dependencies. In this case the recommendation is the decomposition of the diagram to a less complex one such as an action diagram or a structural chart which is outlined to form a suitable dependency diagram. Action diagrams might not be used to illustrate further elaborate details such as in the shared accesses to the main storage, which is not illustrated in a dependency diagram. A CRUD diagram might also be used to illustrate dependency among some of the processes that are not shown in the dependency diagram such as the year –end time dependency among processes. Fig 1.1 dependency diagram Work citedBagui, Sikha, and Richard Earp.

Database design using entity-relationship diagrams. 2nd ed. Boca Raton, FL: CRC Press, 2012. Print.