CISP Final
A relationship definition explains what action is being taken and possibly why it is important. It may be important to state who or what does the action, but it is not important to explain how the action is taken.
False
A state is a named property or characteristic of an entity that is of interest to the organization.
False
An aggregation is an association between the instances of one or more entity types that is of interest to the organization.
False
Operations can be classified into four type, depending on the kind of service requested by clients
False
Projects with purchased models take less time and cost more because the initial discovery steps are no longer necessary, leaving only iterative tailoring and refinement to the local situation.
False
The primary deliverable from the physical data modeling step within the analysis phase is an E-R diagram.
False
A primary key is an attribute that uniquely identifies each instance of an entity type.
True
A relationship definition explains what action is being taken and possibly why it is important. It may be important to state who or what does the action, but it is not important to explain how the action is taken.
True
A style-sheet based HTML is a Web design approach that separates content from the way in which it is formatted and preseted,, making ongoing maintenance easier and site-wide consistency much higher.
True
A supertype is a generic entity that has a relationship with one or more subtypes
True
A ternary relationship definition is a relationship between instances of two entity types and is the most common type of relationship encountered in data modeling
True
An entity has its own identity that distinguishes it from each other entity
True
An entity instance is a single occurrence of an entity type and is described just once in a data model, whereas many instances of that entity type may be represented by data stored in the database.
True
An entity type that associates the instances of only one type and contains attributes that are peculiar to the relationship between those entity instances.
True
An identifier is a candidate key that has been selected to be used as the unique characteristic for an entity type.
True
An object type is a collection of entities that share common properties or characteristics
True
Conceptual data modeling is not done in parallel with other requirements analysis and structuring steps during systems analysis
True
De-Normalization can increase the chance of errors and inconsistencies that normalization avoided.
True
Domain definitions typically specify some or all of the following characteristics of attributes: data type, length, format, range, allowable values, meaning, uniqueness, and null support.
True
One situation in which a relationship must be turned into an associative entity is when the associative entity has other relationships with entities besides the relationship that caused its creation.
True
The disjoint rule specifies that if an entity instance of the supertype is a member of one subtype, it can simultaneously be a member of any other subtype
True
The minimum cardinality of a relationship is the minimum number of instances of entity B that may be associated with each instance of entity A.
True
The other deliverable from conceptual data modeling is a full set of entries about data objects that will be stored in the project dictionary, repository, or data modeling software.
True
User-centered design refers to a design approach that involves an understanding of the target audience, their tasks and goals, information needs, experience levels, and so on.
True
