Logical Design of the Budget System Crow's Foot

Logical design of the Budget System Crow's foot

Top-Down strategy is used for the schema design and it is primitively a decomposition of an entity type into several entity types. High level entity types are specified and then these entities are split into lower-level entity types and relationship with the help of Normalization rules. ER schema of the Budget system can be seen in. Cardinality and modality are indicated at both ends of the relationship line. Once

this has been done, the relationships are read as being 1 to 1 (1:1), 1 to many (1:M), or many to many (M:M). All these projects have their own budget in order to identify and group expenses. These expenses are also identified by cost centres with the coordination of the project management departments. Project managements departments are organised based on the type of projects we mentioned above. But the owner of these project budgets is not the cost center that has prepared it. Project budgets are owned by project management departments according to its group. 1 or more[b5] 1 and only 1 (exactly 1)[b6] zero or 1[b7] Cardinality and modality are indicated at both ends of the relationship line. Once

this has been done, the relationships are read as being 1 to 1 (1:1), 1 to many

(1:M), or many to many (M:M).

1:1 SEAT STUDENT fills [b8] 1:M COURSE INSTRUCTOR teaches [b9] M:M COURSE STUDENT takes [b10] 1:M SECTION PROFESSOR teaches [b11] Typically, ERDs are much more complex than this, involving quite a number of entities and relationships. If we join all of the above relationships together and add a few attributes, a small collection of data might be depicted in the following way using Crow's Foot Notation: teaches *section_number SECTION *professor_id professor_name professor_faculty PROFESSOR *course_name *course_number COURSE *student_id student_name student_address