Object-Oriented Analysis And Design (Exam 1)

Front 1

A class that can be used only as a superclass of some other class; no objects of this type of class may be created except as instances of a subclass.

Back 1

Abstract class

Front 2

The act of concentrating the essential or general qualities of similar things. Also, the resulting essential characteristics of a thing.

Back 2

Abstraction

Front 3

The property of an association representing a whole-part relationship and (usually) life-time containment.

Back 3

Aggregation

Front 4

A named characteristic or property of a class.

Back 4

Attribute

Front 5

A class that can have instances.

Back 5

Concrete class

Front 6

Defines the responsibilities and postconditions that apply to the use of an operation or method. Also used to refer to the set of all conditions related to an interface.

Back 6

Contract

Front 7

A dependency between elements, typically resulting form collaboration between the elements to provide a service.

Back 7

Coupling

Front 8

A formal boundary that defines a particular subject or area of interest.

Back 8

Domain

Front 9

A mechanism used to hide the data, internal structure, and implementation details of some element, such as an object or subsystem. All interaction with an object is through a public interface of operations.

Back 9

Encapsulation

Front 10

A set of collaborating abstract and concrete classes that may be used as a template to solve a related family of problems. It is usually extended via subclassing for application-specific behavior.

Back 10

Framework

Front 11

A feature of object-oriented programming languages by which classes may be specialized from more general superclasses. Attributes and method definitions from superclasses are automatically acquired by the subclass.

Back 11

Inheritance

Front 12

A set of public operations.

Back 12

Interface

Front 13

In the UML, an instance of a class that encapsulates state and behavior. More informally, an example of a thing.

Back 13

Object

Front 14

The investigation of a problem domain or system in terms of domain concepts, such as conceptual classes, associations, and state changes.

Back 14

Object-oriented analysis

Front 15

A named description of a problem, solution, when to apply the solution, and how to apply the solution in new contexts.

Back 15

Pattern

Front 16

The same operation implemented differently by two or more classes.

Back 16

Polymorphic operation

Front 17

The concept that two or more classes of objects can respond to the same message in different ways.

Back 17

Polymorphism

Front 18

A knowing or doing service or group of services provided by an element. It embodies one or more of the purposes or obligations of an element.

Back 18

Responsibility

Front 19

A named end of an association to indicate its purpose

Back 19

Role

Front 20

The condition of an object between events.

Back 20

State

Front 21

A change of state for an object; something that can be signaled by an event.

Back 21

State change

Front 22

First phase of UP

Back 22

Inception

Front 23

Second phase of UP

Back 23

Elaboration

Front 24

Third phase of UP

Back 24

Construction

Front 25

Fourth phase of UP

Back 25

Transition

Front 26

Artifacts started in Elaboration phase

Back 26

Domain model

Design model (class diagrams, object interaction diagrams, package diagrams)

Software architecture document

Data model

Use-case storyboards

UI prototypes