Fichas
Bus 342 Chapter 5 Key Terms
Fichas del conjunto (24)
- 1Aggregation RelationshipUML notation representing the relationship between two classes that are often considered together. ex. sports league and teams
- 2AssociationUML symbol that depicts the relationship between two classes. Solid line between classes in model
- 3AttributesData elements that describe instances in a class. Like fields in a database table
- 4Business ruleSuccinct statement of constraints on a business process. Provides logic that guides behavior of the business in situations.
- 5CardinalitiesHow many instances of one entity that can be related to another
- 6Data ModelsGraphic representation of the conceptual contents of databases.
- 7EntitiesPeople, things, and events in the domain of interest. UML notation they are modeled as classes
- 8Foreign KeyAttribute that allows database tables to be linked together. Are primary keys of other tables placed in the current table to support the link.
- 9Generalization relationshipUML symbol that supports grouping of things that share common characteristics. Reduces redundancy because the shared characteristics need only be modeled once.
- 10MultiplicitiesUML symbols that describe the minimum and maximum number of times an instance of one class can be associated with instances of another class for a specific association between those two classes
- 11Primary KeyAttribute or combination of attributes that uniquely identifies an instance of a class in a data model or a specific row in a table.
- 12RelationshipBusiness purpose for the association between two classes or two database tables.
- 13Structure ModelConceptual depiction of a database, such as a UML model or an entity-relationship model.
- 14ClassesSeparately identifiable collection of things which the organization wants to collect and store as information.
- 15Composition RelationshipUML notation representing the relationship between two classes that are often considered together, except that one class cannot exist without the other. ex. chapters in a book.
- 16Obligatory RuleWhat should occur
- 17Prohibited RuleWhat should not occur
- 18Post override EnforcementViolation is authorized after the violation already occurred.
- 19Pre override EnforcementViolation is authorized in advance
- 20Strict EnforcementViolations are never authorized
- 21Preventative ControlDeter problems before they arise
- 22Detective ControlFinds the problems
- 23Corrective ControlLooks to fix the problems
- 24EntitySeparately and uniquely identifiable things of interest in a system
Información
- Descripción
- Key terms from Acconting Information Systems 4th Edition Chapter 5
- Creado por
- Richard Kramer
- Visitas
- 52
- Etiquetas
- Valoración