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...


Question:<br>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<br>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.<br>Whenever any user uses a software on laptop, the date and time of usage should be recorded; this is used<br>name and role (student, teacher, or administrator).<br>r 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<br>

Extracted text: 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 name and role (student, teacher, or administrator). r 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
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<br>your own.<br>

Extracted text: 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.

Jun 06, 2022
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here