When developing a database design, there are many elements that are confusing and difficult to decipher. That is where an entity-relationship diagram (ERD) comes in. ERD’s are used to describe the data requirements in a database system. They are used to describe the relationships between the entities (Entity Relationship, paragraph 1). Entities are anything which an organization needs to store data. A diagram is put into a picture for of the database design. Understanding a database is easier by looking at a diagram. This tool serves as a communication source between designers and users (Data Model, paragraph 2).
The Journal Entry Adjustment is the relationship of the entity. A database has more tables, which represent entities. Links among database tables represent the relationship with other tables. In this database, the relationship of a journal entry adjustment is with the entity “accounts to be adjusted.”
The entity of this database is “accounts to be adjusted.” Because; the entity is the characteristic of the database, a description of the entity. The accounts which need to be adjusted are the main source of a database table. The accounts needed to be adjusted will be related in other database tables. For example, to build a report of adjustments made for a period that could be found in different reports. Payroll and open accounts payable are examples of accounts that might need to be adjusted.
“Cardinalities are a notation showing the nature of a relationship among entities” (Moscove, Simkin, and Bagranoff, 2003, p.201). The relationship among accounts being adjusted is, one-to-many. Normally, the accounts being adjusted are the same ones for the end of an accounting period; one account, many times adjusted (1,N).
The amount adjusted and date of adju ...