Modelling
Value:10%
Due Date:21-Dec-2018
Return Date:17-Jan-2019
Submission method options:Alternative submission method
Task
back to topOverview of business case:
Granite Sales Company keeps information on employees and the departments that they work in. For each department, the department name, internal mail box number, and office phone extension are kept. A department can have many assigned employees, and each employee is assigned to only one department. Employees can be salaried employees, hourly employees, or contract employees. All employees are assigned an employee number. This is kept along with the employee’s name and address. For hourly employees, hourly wage and target weekly work hours are stored (e.g. the company may target 40 hours/week for some, 32 hours/week for others, and 20 hours/week for others).
Some salaried employees are salespeople that can earn a commission in addition to their base salary. For all salaried employees, the yearly salary amount is recorded in the system. For salespeople, their commission percentage on sales and commission percentage on profit are stored in the system. For example, John is a salesperson with a base salary of $50,000 per year plus 2-percent commission on the sales price for all sales he makes plus another 5 percent of the profit on each of those sales. For contract employees, the beginning date and end dates of their contract are stored along with the billing rate for their hours.
Task 1: Write all possible business rules for the above case study. 3 Marks
Task 2: Create an ERD (using a specialization hierarchy if appropriate )that represents the entities, attributes, the relationships between entities, and the cardinality and optionality of each relationship that are described by this business rule. 7 Marks
NOTE
Use https://www.draw.io to create your ERD
Use Crows Foot notations
Include the PKs where appropriate
Any M:N relationship is to be resolved to a 1:M relationship
Manually drawing the ERD is NOT acceptable.
Rationale
back to topThis assessment task will assess the following learning outcome/s:
- be able to model complex business rules using Entity Relationship Diagrams (ERDs).
Marking criteria and standards
back to topThe marking criteria for this assignment is:
Criteria |
HD
|
DI
|
CR
|
PS
|
be able to model complex business rules using Entity Relationship Diagrams (ERDs).
|
Model identifies all PKs, attributes and relationships.
Model accurately represents all four business rules and includes all entities, PKs, attributes, relationships, associative entities (if applicable), cardinalities and optionalities. |
Model identifies PKs, attributes and relationships with minor omissions.
Model accurately represents the business rules and includes the identified entities, PKs, attributes, relationships, associative entities (if applicable), cardinalities and optionalities.
|
Model identifies key PKs, attributes and relationships.
Model represents key business rules and includes the related entities, PKs, attributes, relationships, associative entities (if applicable), cardinalities and optionalities.
|
Model represents key business rules and draws out the key relationships. It includes the related entities, PKs, attributes, relationships, cardinalities and optionalities with minor errors.
|
Presentation
back to topUse https://www.draw.io to create your ERD.
Requirements
back to topEither save your ERD diagram as a PDF or embed it in a Word document.
Don't use any other file formats
Don't submit your file in XML
Please include your student ID, name and subject code in the diagram