IS320_Week 2 Assignment_IngramJ

docx

School

Grantham University *

*We aren’t endorsed by this school

Course

320

Subject

Computer Science

Date

Jan 9, 2024

Type

docx

Pages

6

Uploaded by Ingram254

Report
Running head: [SHORTENED TITLE UP TO 50 CHARACTERS] 1 Week 2 Assignment Jason Ingram Grantham University
[SHORTENED TITLE UP TO 50 CHARACTERS] 2 3.1: Discuss the role of a high-level data model in the database design process. High-level data models provide concepts such as entity types, relationships, and constraints in detailed descriptions for the conceptual design. While also providing detailed descriptions, high-level data models are also used as a reference point to make sure all data requirements are being met with no conflict. This allows for easier designs without the pressure of thinking about storage and implementation details. 3.2: List the various cases where use of a NULL value would be appropriate. In order to set a NULL value the value would have to be unknown or nonmeaningful. 3.3: Define the following terms: Entity: An entity is a basic concept for an ER model, it is considered to be a thing or an object for the real world with an independent existence. Attribute value: This describes the entity, such as employee’s name, age, address, salary, and job title. Relationship instance: This refers to the specific occurrences of relationships between entities in a database. Composite attribute: Are more basic attributes with independent meaning that can be broken up into smaller subparts. Multivalued attribute: This is an attribute that can have more than one value associated with the key to the entity. An example would be a person having more than one college degree. Derived attribute: This is a form of an attribute or property in a table that has been calculated or derived using other attributes in the database. Complex attribute: This would be when there are two or more composite or multi-value attributes for a person or thing. Such as having more than one address and phone numbers.
[SHORTENED TITLE UP TO 50 CHARACTERS] 3 Key attribute: This is when there is an entity type that has multiple attributes that are unique to an individual. Value set: This specifies a set value that may be assigned to that attribute for the individual entity. 3.4: What is an entity type? What is an entity set? Explain the differences among the entity, an entity type, and an entity set. An entity type is a collection of entities that have the same attributes. While an entity set is a collection of all the entities of a particular entity type. 3.5: Explain the difference between an attribute and a value set. The difference between attribute and value set is that attribute is the characteristic of the entity, such as name, age, job, etc. Value set is specific to the values that are assigned to each attribute for individual entities. 3.6: What is the relationship type? Explain the difference between relationship instance, a relationship type, and a relationship set. The difference between these three relationships is that a relationship type is what entities and their participants in the relationship, relationship set is a set of relationships of a specific type, and finally relationship instance is a relationship between two entity instances. 3.15: Discuss the naming conventions used for the ER schema diagram. When it comes to the naming for the ER schema diagram; the names are uppercase, the attributes will be initials and capitalized, and the roles will be lowercase.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
[SHORTENED TITLE UP TO 50 CHARACTERS] 4 5.1:Define the following terms as they apply to the relational model of data: Domain: Is a set of atomic values. Attribute: Is the name of a role played by some domain. n-tuple: An ordered list of set n values. Relation schema: Is made up of a relation name R and a list of attributes. Relation state: is a set of n-tuples. Degree of a relation: Is the number of entity types that participate in a relationship. Relational database schema: Is a set of relation schemas and a set of integrity constraints. Relational database set: Is a collection of information that organizes data points with defined relationships of easy access. 5.2: Why are the tuples in a relation not ordered? Tuples are not in order because a relation attempts to represent facts at a logical or abstract level. 5.3: Why are duplicate tuples not allowed in a relation? Duplicate relations are not allowed in relation because they create redundancy of data inside a database. This would slow down the data processing like querying, inserting, deleting, and updating of the database. 5.4: What is the difference between a key and a super key? A super key specifies a uniqueness constraint that no two distinct tuples in any state can be of the same value meaning it can be redundant, while a key has no redundancy. A super key can be a key, but a key can not be a super key.
[SHORTENED TITLE UP TO 50 CHARACTERS] 5 5.5: Why do we designate one of the candidate keys of a relation to be the primary key? The primary key is designated by the database to uniquely identify tuple in a table. Only one key can be designated to retrieve tuples from the table. 5.6: Discuss the characteristics of relations that make them different from ordinary tables and files. A relation looks like a table, but it has some added limits to it to use the link between two tables in a well-organized way. A file is an assembly of records, or a table kept on a physical device. 5.9: Define foreign key. What is the concept used for? A foreign key is a column in relational database table the provides a link between data in two tables. 5.10: What is a transaction? How does it differ from an update operation? A transaction is logical unit of processing in a DBMS which entails one or more database access operation. Update operations refers to updating an existing element from the array at a given index.
[SHORTENED TITLE UP TO 50 CHARACTERS] 6 References U Certify. (ND). Based on: Fundamentals of Database Systems. ISBN:978-1-61691-149-2. Data Modeling Using the Entity-Relationship ER Model. U Certify. (ND). Based on: Fundamentals of Database Systems. ISBN:978-1-61691-149-2. The Relational Data Model and Relational Database Constraints.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help