In a company called BCCD engineers are charged of developing different types of applications.
Each engineer is identified by an Employee ID, First Name, Last Name, address, phone and E-mail (Please note that the company is only keeping data for one phone, and one e-mail – Thus, you do not have to worry about multivalued attribute).
Each application is identified by an application ID, Name and type.
Each engineer must work on one or many applications. Applications must be developed by one or more engineers. The company wants to keep track of the date each of the engineers started working on the assigned application.
Each engineer is allocated one personal computer. Each PC can only be used by one engineer. A couple of newly hired engineers have yet to get a PC.
A PC is identified by a Serial Number, Make, and Model.
After the above erd is created is created, make these additions to that same erd:
1- Some engineers were promoted to a supervisory position. Those promoted engineers supervise one or many other engineers. Each Subordinate engineer must be supervised by one and only one senior engineer.
2- The company contracted with a number of software learning institutions for their engineers to take professional development Courses. The company wants to record in the database the course that each of its engineers took, where (which institution) and when (Completion date). “Ternary relationship might be needed”
3- Each institution is identified by Inst_ID, Name, Location, Phone.
Each Course is identified by a Course_ID, Name, Type.
4- An institution must offer one or more courses. A course can be offered by more than one institution. An engineer must take one or more courses. A course might be taken by one or more engineers. (Some offered courses have 0 enrollment)
5- Add an entity detached from all the other entities. Call this entity: My Submission, the attributes for this entity are your own first Name, Last Name and School E-mail. Preferably set it at the top of the ERD.
