Q. The schema which specifies that all the database users requirements have been met is called

View solution

Q. For a relationship type, the participation constraints and cardinality ratio are considered together to make

View solution

Q. The parent entity type or identifying entity type are considered as other names of

View solution

Q. The relationship type with two degrees is classified as

View solution

Q. The constraint which specifies the minimum number of relationship instances is classified as

View solution

Q. In the commercial database management system, the relational database model is also known as

View solution

Q. In constructing ER diagrams, the double ovals are used to denote

View solution

Q. The total participation constraint is also known as

View solution

Q. The weak entities are represented in UML diagrams by using aggregations called

View solution

Q. The attributes which have only more than one value for a specific entity are classified as

View solution

Q. The derived attributes in entity relationship diagrams are denoted by

View solution

Q. In designing of software, the functional requirements are specified with the help of

View solution

Q. In the database, the set of all entities related to a particular entity type is classified as

View solution

Q. In entity-relationship, the entity type which has existence dependency constraint is classified as

View solution

Q. The set of key attributes that identify weak entities related to some owner entity is classified as

View solution

Q. In DBMS, the set of associations can be defined among different entities from different entity types as

View solution

Q. The two main types of constraints of entity relationships are

View solution

Q. In ER diagrams, the partial participation is shown by

View solution

Q. The partial key is differentiated by other keys in database by underlining the key with

View solution

Q. In entity-relationship diagram, the key attributes are represented by

View solution