ABC is a high$-$tech company where project teams and developers collaborate on projects. As a database $($DB$)$ designer of ABC, and you are asked to design a database with the following description:

$$ Each developer with developerName and developerID, is either a Full$-$time Developer or an Intern Developer. For a Full$-$time Developer, the DB should record

the SeniorityLevel. For an Intern Developer, the DB should record the End Date of

internship consisting of day, month, and year.

$$ The DB records all the IDCards with jobTitle, issuedDate and cardID. Each

developer has exactly one ID card, and each ID card belongs to a developer only.

$$ Project Teams with groupID and department information must serve for one or more projects with project name and projectID. A project must be served by a project

team. Note that a projectID can only be used to identify a project served by a project

team. That is$,$ for any two projects that belong to two different project teams, they

may have the same projectID.

$$ A project team must focus on at least one TechnicalArea with areaName and areaID

recorded. On the other hand, a TechnicalArea may not be focused by any project

teams.

$$ One or more Successor projects may be derived from one or more Predecessor

projects. Projects must be developed by developers with a report and must be led

by full time developers.

$[50\%]$ Task $1.$ Please draw an E$-$R diagram to capture all the requirements above.

$$ If there is any information about the data model that is not listed in the

specification, please make reasonable assumption$($s$)$ and write them down.

$$ Marks will be deducted if unnecessary components are added to the tables.

Please follow the problem specification when you name the components.

$$ For clarity, you are suggested to draw the E$-$R diagram with an editor. If you

choose to draw the E$-$R diagram by pen$/$pencil$,$ please make sure that the drawing

is clear, scan your work, and submit a PDF file.

$[50\%]$ Task $2.$ Please translate your E$-$R diagram into relational table schemas.

$$ For each relation, underline the primary key and specify all the foreign keys if

any.

$$ You only need to give the table schema in text form. You do not need to draw the

schema and do not need to provide the data type$/$SQL to create the tables.