Design an ER diagram for the scenario below, showing all attributes, keys, cardinalities and participation constraints clearly. Note any unspecified requirements, and make appropriate assumptions to make the specification complete. Do not add any attributes of your own.
Upload your ER model below, please note:
Question:
A project is proposed to design a database to store details of laptops in a school. The shop has several laptops, where each laptop can be used by many users. Information to be stored about each laptop includes ID, users, type, and a list of software. Each chapter has exactly one main user and zero or more secondary users. A software has a unique name and validity. Each user has a name and a unique ID and it should be possible to search the database by users names, laptop IDs, and software keywords. Whenever any user uses a software on laptop, the date and time of usage should be recorded; this is used for reporting when a software was last used, as well as recording the number of times a software was used. Each user is identified by a unique ID, has a name and role (student, teacher, or administrator).
Already registered? Login
Not Account? Sign up
Enter your email address to reset your password
Back to Login? Click here