Accounting Information Systems, 3e - Chapter 3
Study online at https://quizlet.com/_dbz6gi
1. aggregation relationship A special-purpose UML no-
tation representing the re-
lationship between two
classes that are often con-
sidered together, such as
when a sports league is
made up of a collection of
teams.
2. association UML symbol that depicts
the relationship between
two classes; it is modeled
as a solid line that connects
two classes in a model.
3. attributes Data elements that de-
scribe instances in a class,
very much like fields in a
database table; character-
istics, properties, or ad-
jectives that describe each
class.
4. business rule Succinct statements of
constraints on business
processes; they provide the
logic that guides the be-
havior of the business in
specific situations.
5. cardinalities 'See multiplicities.' UML
symbols that describe the
, Accounting Information Systems, 3e - Chapter 3
Study online at https://quizlet.com/_dbz6gi
minimum and maximum
number of times an in-
stance of one class can
be associated with in-
stances of another class
for a specific association
between those two class-
es; they indicate whether
the two classes are part of
one-to-one, one-to-many,
or many-to-many relation-
ships.
6. class Any separately identifiable
collection of things (ob-
jects) about which the or-
ganization wants to col-
lect and store informa-
tion. Classes can repre-
sent organization resources
(e.g., trucks, machines,
buildings, cash, invest-
ments), persons (e.g., cus-
tomers, employees), events
(e.g., sales, purchases, cash
disbursements, cash re-
ceipts), and conceptual
structures (e.g., accounts,
product categories, bud-
gets). Classes are typically
implemented as tables in a
relational database, where
, Accounting Information Systems, 3e - Chapter 3
Study online at https://quizlet.com/_dbz6gi
individual instances of the
class are represented as
rows in the table.
7. class diagrams Structure models prepared
using UML notation.
8. composition relationship A special-purpose UML no-
tation representing the re-
lationship between two
classes that are often con-
sidered together, similar to
aggregation relationships,
except in composition rela-
tionships, one class cannot
exist without the other, such
as a book and the chapters
that compose the book.
9. constraints Optional or mandatory
guidance about how a
process should perform in
certain situations.
10. data models A graphic representation
of the conceptual contents
of databases; data mod-
els support communication
about database contents
between users and design-
ers of the database.
11. entities
Study online at https://quizlet.com/_dbz6gi
1. aggregation relationship A special-purpose UML no-
tation representing the re-
lationship between two
classes that are often con-
sidered together, such as
when a sports league is
made up of a collection of
teams.
2. association UML symbol that depicts
the relationship between
two classes; it is modeled
as a solid line that connects
two classes in a model.
3. attributes Data elements that de-
scribe instances in a class,
very much like fields in a
database table; character-
istics, properties, or ad-
jectives that describe each
class.
4. business rule Succinct statements of
constraints on business
processes; they provide the
logic that guides the be-
havior of the business in
specific situations.
5. cardinalities 'See multiplicities.' UML
symbols that describe the
, Accounting Information Systems, 3e - Chapter 3
Study online at https://quizlet.com/_dbz6gi
minimum and maximum
number of times an in-
stance of one class can
be associated with in-
stances of another class
for a specific association
between those two class-
es; they indicate whether
the two classes are part of
one-to-one, one-to-many,
or many-to-many relation-
ships.
6. class Any separately identifiable
collection of things (ob-
jects) about which the or-
ganization wants to col-
lect and store informa-
tion. Classes can repre-
sent organization resources
(e.g., trucks, machines,
buildings, cash, invest-
ments), persons (e.g., cus-
tomers, employees), events
(e.g., sales, purchases, cash
disbursements, cash re-
ceipts), and conceptual
structures (e.g., accounts,
product categories, bud-
gets). Classes are typically
implemented as tables in a
relational database, where
, Accounting Information Systems, 3e - Chapter 3
Study online at https://quizlet.com/_dbz6gi
individual instances of the
class are represented as
rows in the table.
7. class diagrams Structure models prepared
using UML notation.
8. composition relationship A special-purpose UML no-
tation representing the re-
lationship between two
classes that are often con-
sidered together, similar to
aggregation relationships,
except in composition rela-
tionships, one class cannot
exist without the other, such
as a book and the chapters
that compose the book.
9. constraints Optional or mandatory
guidance about how a
process should perform in
certain situations.
10. data models A graphic representation
of the conceptual contents
of databases; data mod-
els support communication
about database contents
between users and design-
ers of the database.
11. entities
