click below
click below
Normal Size Small Size show me how
CCS0021 S1
| Question | Answer |
|---|---|
| organized collection of logically related data | database |
| Different system/programs have separate copies of the same data in database approach (T/F) | false |
| people who use the applications and the database | end users |
| inconsistencies are always found in a database approach (T/F) | false |
| a _____ approach to the database has a REPEATED implementation and maintenance of activities with a new PROTOTYPE version | prototyping |
| element of a database approach that is a NOUN FORM describing a person, place, object, event, or concept | entity |
| non-standard file format exists in program data dependency (T/F) | true |
| is limited data sharing with no centralized control of data a disadvantage of file processing? | yes |
| component of a database environment that is the STOREHOUSE of the data | database |
| maintenance in database approach causes more maintenance headaches (T/F) | false |
| SDLC is a long-development cycle (T/F) | true |
| operational programs, documentation and training materials are the deliverables of the implementation step in SDLC | false (actually true, pero false sa formative) |
| database technology that has started in the 1960s and has became a legacy system in the mid 1980s | flat files |
| E-R models are found in the _____ schema of the database | conceptual |
| projects are initiated and PLANNED during the _____ stage of SDLC | planning |
| the purpose of _____ in SDLC is the preliminary understanding of what the system is (T/F) | planning |
| expand the acronym RAD | rapid application development |
| new requirements is always applied to the revised and enhanced prototype in RAD (T/F) | true |
| type of attribute whose values can be calculated FROM RELATED attribute value | derived |
| in this diagram, what is the cardinality of the relationship between entities? | one to one |
| relationship _____ specify how many of each entity type is allowed | cardinalities |
| relationship _____ specify number of entity types involved | degrees |
| this cardinality of relationship shows entities on both sides of the relationship can have many related entities on the other side | many to many |
| required attribute must have a value for every entity (T/F) | true |
| an optional attribute means that the value can be left blank (T/F) | true |
| all relationships for the associative entity should be many (T/F) | true |
| a _____ entity has its OWN identifier, and exists independently of other types of entities | strong |
| a _____ entity is dependent on a strong entity, and cannot exist on its own; does not have a unique identifier (only partial) | weak |
| attributes that contain data that will change overtime is the best attribute for an identifier (T/F) | false |
| there may be a value for every entity in an optional attribute (T/F) | true? |
| disadvantage of file processing wherein programmers must design their OWN formats | lengthy development times |
| The biggest problems of file processing are inconsistencies and compromised data integrity. (T/F) | true? |
| the CENTRALIZED storehouse of metadata | repository |
| data types, field sizes, allowable values, and data context are included in _____ | metadata |
| personnel that is responsible for DESIGNING databases and software | system developer |
| data that describes the PROPERTIES and CONTEXT of user data | metadata |
| In program data dependency, there is coordination and central control of data (T/F) | false |
| a good business rule is declarative, precise, atomic, consistent, expressible, distinct, and business-oriented (T/F) | true |
| a disadvantage of file processing wherein different systems/ programs have SEPARATE COPIES of the same data | duplication of data |
| the purpose of the _____ step in SDLC is develop technology and organizational specifications | physical design |
| the database administrator determines the schema for each different users (T/F) | true? |
| the step in SDLC that its purpose is a thorough requirements analysis and structuring the system | analysis |
| SDLC is a detailed, well-planned development process (T/F) | true |
| The _____ schema of the database involves the logical and physical structures of the database | internal |
| Which among the following became a legacy system during the 1990s? | network, hierarchical |
| The _____ schema shows that different people have different views of the database | external |
| type of attribute that may take on MORE THAN ONE value for a given entity instance | multivalued |
| _____ of a relationship is the number of entity types that participate in it | degree |
| the properties or CHARACTERISTICS of an ENTITY or relationship type | attribute |
| ternary relationships should be converted to associative entities (T/F) | true |
| In the attributes of the entity PatientHistory, Diagnosis is a simple attribute (T/F) | true |
| an attribute that has meaningful component parts (attributes) (e.g. address, birthday, date) | composite attribute |
| stored representations of meaningful objects and events | data |
| data PROCESSED to increase knowledge in the person using the data | information |
| all programs maintain metadata for each file they use | program-data dependence |
| no centralized control of data | limited data sharing |
| a software system that is used to create, maintain, and provide controlled access to user databases; a software for managing the database | database management system |
| Cursory attempt at conceptual data modeling | prototyping |
| Improved data sharing and improved data consistency is found in a database approach (T/F) | true |
| numbers, text, dates | structured data |
| images, video, documents | unstructured data |
| analyzing database to ensure it meets application needs and fixing the errors of the database is in what process of RAD | database maintenance |
| Database activity in the _____ step of SDLC involves database maintenance, performance analysis, and tuning and error tuning | maintenance |
| Implementation and maintenance activities are done repetitively with new prototype versions (T/F) | true |
| The _____ schema is the underlying design and implementation of the database | internal |
| During the ___ stage of SDLC, the database activity here is a thorough and integrated conceptual data modeling | analysis |
| Enterprise modeling and early conceptual data modeling are the database activity during the _____ stage of SDLC | planning |
| Which schema in the database consists of the user views | external schema |
| Perfect identifiers are the attributes that contain locations (T/F) | false |
| combination of relationship and entity | associative entity |
| The associative entity could have meaning independent of the other entities (T/F) | true |
| attribute or combination of attributes that UNIQUELY IDENTIFIES individual instances of an entity type | identifier (key) |
| A _____ degree of the relationship is an entity related to another of the SAME entity type | unary |
| In choosing an identifier for an entity, choose an entity that will not change in value and will not be null (T/F) | true |
| an attribute that could be a key...satisfies the requirements for being an identifier | candidate identifier |
| extends original ER model with new modeling constructs | enhanced ER model |
| subgrouping of the entities in an entity type that has attributes distinct from those in other subgroupings | subtype |
| generic entity type that has a relationship with one or more subtypes | supertype |
| The instances of a subtype may participate in a relationship unique to that subtype (T/F) | true |
| Total Specialization Rule | yes (double line) |
| Partial Specialization Rule | no (single line) |
| process of defining a more GENERAL entity type from a set of more SPECIALIZED entity types. | generalization; bottom-up |
| process of defining one or more subtypes of the supertype and forming supertype/subtype relationships. | specialization; top-down |
| An instance of a subtype is also an instance of the supertype (T/F) | true |
| In diagram 4, the attributes of the Buildings entity are inherited by the Apartment, House and Commercial_building entities. | true |
| In diagram 4, the attribute of Title of the House entity can be inherited by the Buildings entity. | true |
| Relationships at the supertype level indicate that all subtypes will participate in the relationship | true |
| set of one or more entity types and associated relationships grouped into a single abstract entity type | entity cluster |
| An instance of the supertype could be MORE THAN one of the subtypes | overlap rule |
| An instance of the supertype can be only ONE of the subtypes | disjoint rule |
| These are keys that are unique identifiers of the relation | primary keys |
| A primary key of a table guarantees that all columns are unique (T/F) | true |
| a named, two-dimensional table of data | relation |
| _____ corresponds to an attribute of an entity type | columns |
| _____ correspond with entity instances and with many-to- many relationship instance | rows |
| _____ correspond with entity types and with many-to-many relationship types | relations |
| The word relation (in relational database) is NOT the same as the word relationship (in E-R model) (T/F) | true |
| Allowable values for an attribute | domain constraints |
| Keys in a relation have two purposes, which are the primary key and foreign key (T/F) | true? |
| If you have an entity that Student, that has the following attributes: {IdNumber, Name, Address, Birthday}, which among the attributes should be a primary key? | IdNumber |
| What is another name for tables in database? | relation |
| What is wrong with the relation below if the primary key is EmpId | The relation is composed of employees with different projects assigned to them, therefore multiple values that are the same in the primary key is allowed ? |
| A candidate key is not allowed to be a primary key (T/F) | false |
| A ___ has no partial dependencies. | 1NF |
| changing data in a row forces changes to other rows because of duplication | modification anomaly |
| adding new rows forces user to create duplicate data | insertion anomaly |
| deleting rows may cause a loss of data that would be needed for other future rows | deletion anomaly |
| When there is an existing multivalued attribute in a 1NF table, it means its relation (T/F) | true? |
| In functional dependencies, each key field is functionally dependent on every candidate key (T/F) | true? |
| A table with no multivalued attributes is considered to be in what form? | 1NF |
| A well-structured relation contains no redundancy and allows users to insert, delete, and update rows without cause data inconsistencies (T/F) | false; minimal |
| whether an instance of a supertype may SIMULTANEOUSLY be a member of two or more subtypes | disjointness constraint |
| Whether an instance of a supertype must also be a member of at least one subtype | completeness constraint |
| A rule that specifies that each entity instance of a supertype must be a member of some subtype in the relationship | total specialization rule |
| A rule that specifies that an entity instance of a supertype is allowed not to belong to any subtype | partial specialization rule |
| it is a subtype entity that inherits values of all attributes of the supertype | attribute inheritance |
| Mapping unary relationships into relations with a one-to-many relationship has a recursive foreign key in the same relation. (T/F) | true |
| Rows correspond with entity instances and with many-to- many relationship instances (T/F) | true |
| The order of the rows and columns in the database table must be irrelevant. (T/F) | true |
| Key fields can only be simple keys or one single field. (T/F) | true? |
| A relation’s attributes (columns) in tables must have unique names. (T/F) | true |
| What happens when a relation has a null value for the primary key? | The null value is not allowed by the database because of Entity Integrity |
| What is wrong with the relation below if the primary key is EmpId | The primary key should be unique, therefore there is something wrong with the values of the primary key. |
| A 2NF is a 1NF plus no transitive dependencies. (T/F) | true |
| A 1NF table is a table with composite attributes and every attribute is atomic. | true |
| A 2NF is a 1NF plus every non-key attribute is fully functionally dependent on the entire primary key. | true |
| Which among the following is not true about table anomalies? | modification is same as deletion |
| In diagram 4, the attributes of the entity Buildings are inherited by all its subtypes. | true? |
| In diagram 4 ,the attribute Location of the Buildings entity will be inherited only by the Commercial_Building entity. | false? |
| An attribute of the supertype whose values determine the target subtype(s) | subtype discriminator |
| In diagram 4, the attributes of the Buildings entity are inherited by the Apartment, House and Commercial_building entities | true |
| A subtype can have a relationship with other subtypes (T/F) | true |
| what does EERD stand for? | enhanced entity-relation diagram |
| Key fields can either be simple or composite keys (T/F) | true |
| the rule states that any foreign key value (on the relation of the many side) MUST match a primary key value in the relation of the one side? | referential integrity |
| Primary key on the one side becomes a foreign key on the many side | one-to-many |
| Create a new relation with the primary keys of the two entities as its primary key | many-to-many |
| Primary key on mandatory side becomes a foreign key on optional side | one-to-one |
| Regular entities that are mapped into relations with simple attributes should use only their simple, component attributes. | false |
| E-R attributes map directly onto the relation | simple attributes |
| Use only their simple, component attributes | composite attributes |
| becomes a separate relation with a foreign key taken from the superior entity | multivalued attributes |
| When mapping a supertype/subtype relationships into relations, supertype attributes go into supertype relation, including its identifier and subtype discirminator. (T/F) | true |
| A 1NF has no partial dependencies. (T/F) | true |