|
Term
|
Description
|
Pg |
|
Architecture
|
A systems concepts, structures, and interactions. Also, the description of a systems desired final architecture before construction.
|
6 |
|
Business Domain Model
|
An object-oriented model of the information and behavior of a business and its processes. Also, the computerized realization of the model.
|
28 |
|
Canvas
|
The description of how widgets are placed within an area (usually square) and other properties of that area (for example, background color and events monitored).
|
49 |
|
CanvasModel
|
A UI model that is designed to work with Canvases. Major responsibilities include instanciating and connecting WidgetModels to Widgets and connecting WidgetModel event notifications to application logic.
|
49 |
|
Container
|
An abstract object interface which provides query and manipulation behavior to a collection of objects.
|
32 |
|
Data Layer
|
The layer of an OOIS that is responsible for storing and retrieving object data with transactional consistency.
|
19 |
|
Database
|
A system that specializes on the transactional management of data.
|
|
|
Domain
|
Short term for the Business Domain Model.
|
|
|
Domain Layer
|
The layer of an OOIS that contains the business domain model and supporting frameworks.
|
19 |
|
DomainAdaptor
|
A UI model that is designed to present a domain object. It is structured to hold onto a single domain object and to use UI model adapters to present attributes of the domain object.
|
53 |
|
ExtentContainer
|
A Container which holds all the objects from the extent of a single domain type
|
33 |
|
Forwarder
|
A proxy which immediately forwards messages, possibly over process and machine boundaries, to the RealSubject.
|
37 |
|
Framework
|
A strong partition of generalized functionality common to many parts of an application. Also, more formally, a collection of interacting classes that describes most of the behavior a client requires and can be subclassed and parameterized to customize and complete the functionality.
|
9 |
|
Kernel
|
A system partition containing basic functionality needed for any type of application
|
18 |
|
Layer
|
A logical, horizontal division of a system that provides a particular system abstraction to the client above the layer.
|
9 |
|
Module
|
A base level subsystem: one which does not contain any other subsystems
|
|
|
Object-Oriented Information System
|
A transactional, multi-user system that saves and shares information structured using object-oriented techniques.
|
13 |
|
ObjectSpace
|
The object representing an instance of your business domain model and containing all the objects that determine the state of the business. An ObjectSpace can also support locating objects (by name or query) as a secondary domain object.
|
31 |
|
OOIS
|
Object-Oriented Information System
|
|
|
Optimistic Transaction
|
A transaction that is committed with the hope that the commit will succeed but without having received a guarantee from all the needed resources that it will.
|
40 |
|
Partition
|
A vertical division of a system into areas of related functionality.
|
8 |
|
Proxy
|
An object that stands in for another object (the RealObject) and manages the client interaction with the RealObject.
|
37 |
|
Replicate
|
A proxy which holds local state and performs local operations which are later propogated to the RealSubject
|
37 |
|
Secondary Domain Object
|
An object that should only have responsibility for domain model functionality that can not be appropriately allocated to standard domain objects.
|
31 |
|
Stub
|
A proxy which is simply a placeholder for the RealObject and must become another type of proxy (for example, forwarder or replicate) when interacted with by a client.
|
37 |
|
Subsystem
|
A division of a system into a cohesive unit of functionality (tightly related classes and internal subsystems) with a public interface and a private implementation.
|
8 |
|
Tier
|
A level on a hierarchy of processes over which a system is divided.
|
10 |
|
UI
|
User Interface
|
|
|
UI Layer
|
The layer of an OOIS that is focused on interacting with a user. This contains the UI frameworks, the non-graphical description of application functionality, and the GUI binding to that functionality.
|
18 |
|
UI model
|
Objects that provide the behavior for the user interface without having a graphical (i.e. on screen) representation
|
49 |
|
Uim
|
UI model
|
|
|
Widget
|
The graphical functionality that allows a user to view and control part of an application.
|
49 |
|
WidgetModel
|
A UI model that provides the widget level of application functionality: either holding onto values and objects (and notifying others when the held values change), or possibly much more functionality for complex widgets.
|
49 |
|
Window
|
A UI window and the outermost canvas for the area of the UI window.
|
49 |
|
WindowModel
|
A subtype of CanvasModel that also handles window responsibilities.
|
49 |