|
| |
[I J]
- IEEE
The Institute of Electrical and Electronics Engineers, Inc.
ISO
The International Organization for Standardization.
implementation
A core process workflow in the
software-engineering process, whose purpose is to implement and unit test the
classes.
A definition of how something is constructed or computed. For example, a
class is an implementation of a type, a method is an implementation of an
operation.
implementation inheritance
The inheritance of the implementation of a more specific element. Includes
inheritance of the interface. Contrast: interface
inheritance.
implementation mechanism
An architectural mechanism
used during the implementation process. They are refinements of design
mechanisms, and specify the exact implementation of the mechanism. For
example, one particular implementation of the inter-process communication
analysis mechanism is a shared memory design mechanism utilizing a particular
operating system’s shared memory function calls. Concurrency conflicts
(inappropriate simultaneous access to shared memory) may be prevented using
semaphores, or using a latching mechanism, which in turn rest upon other
implementation mechanisms.
implementation model
The implementation model is a collection of components,
and the implementation subsystems
that contain them.
implementation subsystem
A collection of components and other
implementation subsystems, and is used to structure the implementation
model by dividing it into smaller parts.
implementation view
An architectural view that
describes the organization of the static software elements (code, data, and
other accompanying artifacts) on the development environment, in terms of both
packaging, layering,
and configuration management
(ownership, release strategy, and so on). In the Unified Process it is a view
on the implementation model.
import
In the context of packages, a dependency that
shows the packages whose classes may be
referenced within a given package (including packages recursively embedded
within it). Contrast: export.
import-dependency
A stereotyped dependency in the design
whose source is a design package, and
whose target is a different design package. The import dependency causes the
public contents of the target package to be referenceable in the source
package.
inception
The first phase of the Unified Process, in
which the seed idea, request for proposal, for the previous generation is
brought to the point of being (at least internally) funded to enter the elaboration
phase.
include
A relationship from a base use case to an inclusion use case, specifying how
the behavior defined for the inclusion use case can be inserted into the
behavior defined for the base use case.
include-relationship
An include-relationship is a relationship from a base use case to an
inclusion use case, specifying how the behavior defined for the inclusion use
case is explicitly inserted into the behavior defined for the base use case.
increment
The difference (delta) between two releases at the end of subsequent iterations.
incremental
Qualifies an iterative development strategy in which the system is built by
adding more and more functionality at each iteration.
inheritance
The mechanism that makes generalization possible; a mechanism for creating
full class descriptions out of individual class segments.
The mechanism by which more specific elements incorporate structure and
behavior of more general elements related by behavior. See generalization.
input
An artifact used by a process. See static
artifact.
inspection
A formal evaluation technique in which some artifact
(model, document, software) is examined by a person or group other than the
originator, to detect faults, violations of development standards, and other
problems.
instance
An individual entity satisfying the description of a class
or type.
An entity to which a set of operations can be applied and which has a state
that stores the effects of the operations. See: object.
integration
The software development activity in which separate software components are
combined into an executable whole.
integration build plan
Defines the order in which components are to be implemented and integrated
in a specific iteration. Enclosed in the Iteration
Plan.
interaction
A specification of how stimuli are sent between instances
to perform a specific task. The interaction is defined in the context of a
collaboration. See collaboration.
interaction diagram
A generic term that applies to several types of diagrams that emphasize
object interactions. These include: collaboration
diagrams, sequence diagrams,
and activity diagrams.
interface
A collection of operations that are used to
specify a service of a class or a component.
A named set of operations that characterize the behavior of an element.
interface inheritance
The inheritance of the interface of a more specific element. Does not
include inheritance of the implementation. Contrast: implementation
inheritance.
internal transition
A transition signifying a response to an
event without changing the state of an object.
iteration
A distinct sequence of activities with a base-lined plan and valuation
criteria resulting in a release (internal or
external).
[K]
- key mechanism
A description of how an architectural
patterns is realized in terms of patterns of interaction between
elements in the system. Presented in the Software
Architecture Document
|
