A specific way of grouping packages in a model
at the same level of abstraction.
The organization of classifiers or packages at the same level of
abstraction. A layer represents a horizontal slice through an architecture,
whereas a partition represents a vertical slice. Contrast: partition.
A semantic connection among a tuple of objects. An instance of an
association. See: association.
An instance of an association end. See: association
An architectural view that
describes the main classes in the design of the system: major business-related
classes, and the classes that define key behavioral and structural mechanisms
(persistency, communications, fault-tolerance, user-interface). In the Unified
Process, the logical view is a view of the design
A core supporting workflow in the
software-engineering process, whose purpose is to plan and manage the
A specification of the conveyance of information
from one instance to another, with the expectation that activity will ensue. A
message may specify the raising of a signal or the call of an operation.
A class whose instances are classes. Metaclasses are typically used to
A model that defines the language for expressing a metamodel.
The relationship between a meta-metamodel and a metamodel is analogous to the
relationship between a metamodel and a model.
A model that defines the language for expressing a model.
A generic term for all metaentities in a
metamodeling language. For example, metatypes, metaclasses, metaattributes,
(1) A regular and systematic way of accomplishing something; the detailed,
logically ordered plans or procedures followed to accomplish a task or attain
a goal. (2) 1.1: The implementation of an operation, the algorithm or
procedure that effects the results of an operation.
The implementation of an operation. It specifies the algorithm or procedure
associated with an operation.
The point at which an iteration formally ends; corresponds to a release
A semantically closed abstraction of a system. In the Unified Process, a
complete description of a system from a particular perspective ('complete'
meaning you don't need any additional information to understand the system
from that perspective); a set of model elements. Two models cannot overlap.
A semantically closed abstraction of a subject system. See: system.
Usage note: In the context of the MOF specification, which describes a meta-metamodel,
for brevity the meta-metamodel is frequently referred to as simply the model.
A dimension of modeling that emphasizes particular
qualities of the metamodel.
For example, the structural model aspect emphasizes the structural qualities
of the metamodel.
The process of generating a repository
type from a published model. Includes the generation of interfaces and
implementations which allows repositories to be instantiated and populated
based on, and in compliance with, the model elaborated.
model element [MOF]
An element that is an abstraction drawn from the
system being modeled. Contrast: view
In the MOF specification model elements are considered to be metaobjects.
How concepts will be represented, restrictions on the modeling language that
the project team management has decided upon (i.e. dictums such as "Do
not use inheritance between subsystems."; "Do not use extend or
include associations in the Use Case Model."; "Do not use the friend
construct in C++."). Presented in the Software
Refers to something that occurs during a modeling
phase of the software development process. It includes analysis time and
design time. Usage note: When discussing object systems, it is often important
to distinguish between modeling-time and run-time concerns. See: analysis
Contrast: run time.
A software unit of storage and manipulation.
Modules include source code modules, binary code modules, and executable code
modules. See: component.
A semantic variation of generalization
in which an object may belong directly to more than one class. See: dynamic
A semantic variation of generalization
in which a type may have more than one supertype.
A specification of the range of allowable
cardinalities that a set may assume. Multiplicity specifications may be given
for roles within associations, parts within composites, repetitions, and other
purposes. Essentially a multiplicity is a (possibly infinite) subset of the
non-negative integers. Contrast: cardinality.
A model element with multiplicity
defined whose Multiplicity Type:: upper attribute is set to a number greater
than one. The term multi-valued does not pertain to the number of values held
by an attribute, parameter, etc. at any point in time. Contrast: single-valued.
An association among three or more classes. Each
instance of the association is an n-tuple of values from the respective
classes. Contrast: binary
A string used to identify a model element.
A part of the model in which the names may be defined and used. Within a
namespace, each name has a unique meaning. See: name.
A node is classifier that represents a run-time
computational resource, which generally has at least a memory and often
processing capability. Run-time objects and components may reside on nodes.
- n-ary association
An entity with a well-defined boundary and identity
that encapsulates state
State is represented by attributes
behavior is represented by operations,
and state machines.
An object is an instance of a class. See: class,
A diagram that encompasses objects
and their relationships at a point in time. An object diagram may be
considered a special case of a class diagram or a collaboration diagram. See: class
object flow state
in an activity
graph that represents the passing of
an object from the output of actions in one state to the input of actions in
A line in a sequence diagram that represents the existence of an object over
a period of time. See: sequence
An abstraction of a system's implementation.
A service that can be requested from an object to effect behavior. An
operation has a signature, which may restrict
the actual parameters that are possible.
operating system process
An unique address space and execution environment in which instances of
classes and subsystems reside and run. The execution environment may be
divided into one or more threads of control. See also process
An originator is anyone who submits a change
request (CR). The standard change request mechanism requires the
originator to provide information on the current problem, and a proposed
solution in accordance with the change request form.
Any artifact that is the result of a process step. See deliverable.