Please help, I am unsure if my model (image down below) is correct and has include everything state in the assignment below:

Homework Assignment 1

* Homework Assignment is to be completed individually. Make sure first that youve signed and submitted the AIS form assigned in Week 1.

All answers must be typed and draw by tool. No handwriting answers will be accepted

I. ER Modeling

Develop an ERD for the following scenario using UML notation. Make sure to represent multiplicity:

Scenario description:

A consulting company named Electronic Marketing Group (EMG) plans to create a database system, named EMGDB, to keep track of the information about its employees, clients, and projects.

Each employee has a Social Security Number, name, address, phone number, position, and salary. Each employee also has an account for the internal computer network (Intranet). For example, Jennifer Furmans account name is jfurman; Beth Kims account name is bkim.

EMG has a lot of clients from all over the country. Bellaware and Swan are two of the biggest clients. Each client has a name, address, phone number, contact person, and specialization (e.g., retailer, rental, telecommunication, etc.). EMG is also interested in the annual profit of each client.

EMG does projects for its clients. Each project is assigned a unique number and given a name. For example, a project for SWAN is assigned a project number P9820 and named SWAN web page design. Each project has a clearly defined schedule (consisting of a starting date and a due date), cost, and requirement. EMG tracks the current status of each project regularly. Each project has a manager and several workers, both of which should be EMG employees. For example, currently Jennifer is the manager of project P9820 and Beth is working with Jennifer on this project. Each project is associated with exactly one client. But any client may have many projects. For example, SWAN has had over ten projects with EMG.

TIPS:

• Entity: a singular noun with first letter capitalized, e.g., Employee, EmployeeAccount
• Attribute: a word in lower case (e.g., name, phoneNumber)
• Keys (e.g., PK) should be put in braces {}, not parentheses () or brackets [].
• Relationship: a verb or a short phrase with first letter capitalized (e.g., Manages, WorksFor); use a unique name for each relationship.
• Use horizontal or vertical lines for relationships.
• Multiplicity: x..y not x:y
• Attribute or entity? Consider whether multiple data entries are needed to record the information. Example: annual profit and project status.
• State all assumptions (always trying to model a finite set of information).

WorksOn> 1.1 Client Employee Project clientID {PK} projectNumber {FK} clientName project Number (PK} clientID {FK} projectName projectSchedule startDate clientAddress 1..1 employeeld (PK) projectNumber {FK} social SecurityNumber employeeAddress employee Street employeeCity employeePostcode employeeName client Street