Visual Paradigm which satisfies the following
business rules:
- Could You Please Construct A Logical Erd Using Visual Paradigm Which Satisfies The Following Business Rules Fill Each E 1 (102.16 KiB) Viewed 24 times
attributes:
- Could You Please Construct A Logical Erd Using Visual Paradigm Which Satisfies The Following Business Rules Fill Each E 2 (122.25 KiB) Viewed 24 times
conditions:
- Could You Please Construct A Logical Erd Using Visual Paradigm Which Satisfies The Following Business Rules Fill Each E 3 (51.88 KiB) Viewed 24 times
EACH ENTITY 1 ROAD CATEGORY LOCATION LOCATION ROAD PROJECT ROAD PROJECT CONTRACT ROLE EMPLOYEE May/Must (Participation) may be may may maybe must may be may may may be may be verb number (Cardinality) used by zero or many ROAD have zero or many ROAD have zero or many ROAD part of zero or many ROAD involve in one or many ROAD involved in zero or many PROJECT involve zero or many CONTRACT have zero or many EMPLOYEE (as managers) assigned to zero or many EMPLOYEE assigned zero or many ROLE ENTITY 2 (that start at the location) (that end at the location)
Roads: The details to be stored about roads are a unique road identifier (assigned by the ARC to uniquely distinguish one road from another), road name, description, and category. Each road is assigned a category, for example, main highway, secondary road, unsealed road etc. All roads must have a category - although not all categories may be used. The length in kilometres of the road must be stored. Some roads may be part of other roads. For example, "Main Highway 16" has a section called "Maytown Throughway", which is a five kilometre sub-section of the main highway. A road may be a sub-section of only one other road, although a specific road may have many sub-sections, each of which may also have sub-sections. Location: It is necessary to identify the location a road starts and the location at which that road ends. The information to be stored about a location is: location ID, name, latitude, longitude, and description. Projects: The ARC wishes to keep a record of all the projects carried out on the roads. A project has a project code, name and description, date started, and date completed. A record must be kept of all ARC staff assigned to each project, and the role undertaken by that staff member. Changes can happen to staff assigned to a project due to various unexpected reasons. Such changes must be recorded. The details about a staff member that must be stored are Employee ID, first name, last name, date first employed by ARC, date of birth, gender, postal address, contact phone number, and email address. A staff member may have many roles in a project over time. A role has a role name and a description. It is necessary to store the date that a role was assigned to a staff member, and when the assignment ended. A project must involve in at least one road and a road may have many projects carried out on it. Contracts: The ARC negotiates contracts with external construction contractors to carry out work on projects. A project may have several contracts over time. A contract has a contract number, name, description, estimated cost, actual cost, date started, and date ended. A contract has only one contractor company whose name, address, and preferred contact details are recorded. A contract may have, several contract managers (manager is a role) who are employees of ARC, over time, although there can only be one manager at any time. The ARC needs to store start and end dates that an appointed manager is responsible for a contract.
Construct logical ERD All entities are in third normal form (3NF) - [5 marks] All essential attributes identified for each entity - [5 marks] Cardinality and Participation for each relationship correctly identified and consistent with the model answers provided for the business rules - [5 marks] All primary and foreign keys are correctly identified and clearly indicated - [5 marks] Relationships are named using verb phrases in both directions, except where they are adjacent to bridging entities (used in resolving many-to-many relationships), in which case only the verb phrases related to the bounding entities need to be shown - [3 marks] ERD developed using Visual Paradigm (VP) - [4 marks] It is clear and readable - [3 marks]