Study your flashcards anywhere!

Download the official Cram app for free >

  • Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key


Play button


Play button




Click to flip

40 Cards in this Set

  • Front
  • Back
A class that cannot be instantiated (no objects can be created), existing only to allow subclasses to inherit its attributes, methods and associations
Abstract Class
Behaviour that the system performs when an event occurs (similar to a use case).
Whole-part relationships between an object and its parts.
A class that represents a many-to-many relationship between two other classes
Association Class
A data entity that represents a many-to-many relationship between two other data entities
Associative Entity
One piece of specific information about a thing
Relationships between two different types of things, such as a customer and an order
Binary Relationships
The number of associations that occur among specific things, such as a customer places many orders and an employee works in one department
A type of classification to which all similar objects belong
Whole-part relationships in which the parts cannot be dissociated from the object
An attribute that contains a collection of related attributes.
Compound Attribute
A class that can be instantiated (objects can be created)
Concrete Class
The things the system needs to store information about in the traditional approach to information systems
Data Entities
Narrative memos, reports, or lists that describe some aspect of a system
Descriptive Model
An external agent or actor that receives data from the system.
A class diagram without methods, which is created as a requirements model
Domain Model
Covering or protecting each object so that it contains values for attributes and methods for operating on those attributes, making the object a self-contained (and protected) unit
An occurrence at a specific time and place that can be described and is worth remembering
A table that lists events in rows and key pieces of information about each event in columns
Event Table
An event that occurs outside the system, usually initiated by an external agent or actor
External Event
Hierarchies that structure or rank classes from the more general super-class to the more specialized sub-classes; sometimes called inheritance hierarchies.
Generalization/Specialization Hierarchies
Diagrams and schematic representations of some aspect of a system
Graphical Model
An attribute that uniquely identifies a thing
Identifier (key)
A concept that allows subclasses to share characteristics of their superclasses
A series of formulas that describe technical aspects of a system.
Mathematical Model
The behaviours of all objects of the class are capable of doing.
A synonym for cardinality (used with the object-oriented approach).
A relationship among n (any number of) different types of things
N-ary Relationship
The assumption that events should be included during analysis only if the system would be required to respond under perfect conditions.
Perfect Technology Assumption
A naturally occurring association among specific things, such as an order is placed by a customer and an employee works in a department
An output, produced by the system, that goes to a destination
An external agent or actor that supplies data to the system.
An event that occurs when something happens inside the system that triggers the need for processing
State Event
Checks or safety procedures put in place to protect the integrity of the system
System Controls
An event that occurs as a result of reaching a point in time.
Temporal Event
A relationship among three different types of things.
Ternary Relationship
A signal that tells the system that an event has occurred, either the arrival of data needing processing or a point in time
A relationship among two things of the same type, such as one person being married to another person
Unary (Recursive) Relationship
A series of actions that a system performs that result in a defined outcome (similar to an activity).
Use Case
Hierarchies that structure classes according to their associated components.
Whole-Part Hierarchies