I
Identify Business Processes
Within the RUP, Identify Business Processes is an activity within the Business Modeling discipline.
The purpose of this activity is to identify the business processes that the new system needs to execute.
identity
An object's identity is the property that uniquely identifies that object.
if expression
An if expression is an OCL expression that results in one of two alternative expressions depending on the evaluated value of a condition.
implement
The term implement is a stereotype attached to a component to signify that the component implements a classifier identified by a specification.
Implement a Class
Within the Unified Process, Implement a Class is an activity within the Implementation workflow.
There are four steps involved in this activity:
 |
Outlining the file that contains the source code for each design class |
|
Generating that source code |
|
Implementing the operations of each class, as methods |
|
Ensuring that the components provide the same interfaces as the design classes |
This activity involves ensuring that the requirements associated with each subsystem are implemented in the appropriate build by components and/or other subsystems. The term implementation refers to the definition of how something is constructed, such as how a method implements an operation, or computed.
implementation (description)
implementation (stereotype)
Within the RUP, the Implementation artifact set is the set of artifacts related to the deliverable system. The Implementation artifact set contains the following artifacts:
Implementation artifact set
|
build |
|
developer test |
|
implementation model |
|
integration build plan |
implementationClass
The term implementationClass is a stereotype attached to a class to signify that the class provides a static physical implementation of that class. This implementation includes attributes, associations with other classes, and methods.
An implementation class is usually associated with a static class within a programming language. Within the RUP, there are four purposes of the Implementation discipline:
Implementation discipline
Define the organization of the code in terms of implementation subsystems.
Implement classes and objects within components.
Perform unit testing of those components.
Integrate the components into an executable system.
The following activities comprise the Implementation discipline:
|
Implement Components |
|
Integrate Each Subsystem |
|
Integrate the System |
|
Plan the Integration |
|
Structure the Implementation Model |
implementation inheritance
The term implementation inheritance refers to the inheritance of the implementation of a given parent element's structure (attributes, operations, and associations) and code (methods).
The principle of substitutability applies to the inheriting element.
implementation model
Within the Unified Process, the term implementation model is a stereotype attached to a model to signify that the model contains a hierarchy of implementation subsystems.
The implementation model is meant to show how elements of the design model are implemented within the system, in terms of components. This model also describes how those components are organized and the dependencies among them.
Within the RUP, the following comprise the implementation model:
| implementation elements |
| implementation subsystems |
| testability elements |
| test stubs |
Within the RUP, the implementation model is part of the Implementation artifact set.
implementation requirements
Within the Unified Process, the term implementation requirements is a tag definition whose value contains text describing nonfunctional requirements, associated with either a design class or a use-case realization-design, that are identified and specified during the Design workflow but are better handled during the Implementation workflow.
implementation subsystem
Within the Unified Process, the term implementation subsystem is a stereotype attached to a subsystem to signify that the subsystem is used to organize components and interfaces within an implementation model.
An implementation subsystem can also contain other implementation subsystems.
implementation system
Within the Unified Process, the term implementation system is a stereotype that refers to the top-level package within the implementation model.
implementation view
The term implementation view refers to the set of components and files that together form a releasable system. This view focuses on configuration management.
The implementation view is captured primarily in component diagrams, and also in interaction diagrams, state machine diagrams, and activity diagrams.
The implementation view is a part of the static view. The implementation view is also one of the five interlocking views that comprise the architecture.
Implementation workflow
Within the Unified Process, the purpose of the Implementation workflow is to create an implementation model that describes the physical realization of the design model in terms of components.The following activities comprise the Implementation workflow:
|
Architectural Implementation |
|
Implement a Class |
| Implement a Subsystem |
| Integrate System |
|
Perform Unit Test |
Implement Components
Within the RUP, Implement Components is an activity within the Implementation discipline.
This activity involves implementing the classes and objects in the design model in the form of components.
Implement Test
Within the Unified Process, Implement Test is an activity within the Test workflow.This activity involves creating test components that automate test procedures by using a test automation tool, programming the components, or both.
implies
The term implies refers to an OCL operator that states that a given Boolean expression resolves to True if when the first Boolean is True, the second Boolean operand is also True. (If the first operand is False, the expression evaluates to True regardless of the value of the second operand.)
import
The term import is a stereotype attached to a dependency to signify that within the dependency, the names of one or more elements in the supplier package are added to the namespace of the client package.
There are two kinds of imports: element imports and package imports.
Improve Test Assets
Within the RUP, Improve Test Assets is an activity within the Test discipline.
This activity involves maintaining and improving the various test assets, including the test cases and test scripts.
in
The term in refers to an OCL construct that indicates the presence of a local variable that represents a value used more than once within a particular OCL expression.
inactive
The term inactive applies to a state that is not currently being held by a given object within a state machine.Inception phase
Within the Unified Process, the Inception phase is the phase of a development project in which the business case for the proposed system is developed and presented.The primary goal of this phase is to reach an initial agreement among the stakeholders as to what the new system will accomplish and how much time and money will be required to build it.
include
The term include refers to a directed relationship within which the supplier use case explicitly incorporates the behavior of the client use case at a location specified within the supplier.
One generally uses an include relationship to put behavior common to several use cases in its own use case.
includes
The term includes refers to an OCL operation that returns True if a specified object is an element of a given Collection.
includesAll
The term includesAll refers to an OCL operation that returns True if all of the elements within a specified Collection are elements of another given Collection.
including
The term including refers to an OCL operation that works on a Collection.
|
For a Bag, the operation adds a given element. |
|
For a Set, the operation adds a given element if that element is not already present. |
|
For a Sequence, the operation adds a given element at the end. |
incomplete
The term incomplete is a constraint attached to a generalization set to signify that not all children have been specified for those generalizations in the set and that more can be specified.increment
Within the Unified Process, an increment is a small and manageable part of the system being built, such as the delta between two successive builds.An increment is the result of an iteration. The term indexOf refers to an OCL operation that returns the position of a given element in a given OrderedSet or Sequence.
incremental process
An incremental process is a process that involves the continuous integration of a system's architecture to produce executable releases, with each new release containing incremental improvements on its predecessor.
indexOf
indirect instance
An indirect instance is an element that is an instance of a given element and also an instance of a child of that element.
An indirect substate is a substate that is contained by one state but referred to by one or more other states.
indirect substate
information flow
An information flow is a dependency within which one or more information items circulate from its sources to its targets.
information item
An information item is a classifier that represents some pieces of information that can be exchanged between objects.
inheritance
The term inheritance refers to a mechanism by which more specific elements incorporate structure and behavior defined by more general elements.
initialization
The term initialization refers to the act of setting the value of a newly created object, including the values of its attributes, its links, and its initial state.initial node
An initial node is a control node at which a control flow starts when an activity is invoked.
Initial Operational Capability
Within the Unified Process, the term Initial Operational Capability refers to the major milestone that concludes the Construction phase.
initial state
An initial state is a pseudostate that indicates the default starting place for a transition whose target is the boundary of a state,initial value
A initial value is an expression that specifies the value that a given attribute holds upon initialization.Within the OCL, an initial value is specified with the use of the word init.
An input pin is a pin that provides input values to an action. The term insertAt refers to an OCL operation that inserts a given element at a given position within a given OrderedSet or Sequence.
input pin
insertAt
instance
An instance is a named entity that has its own identity and value.
An instance represents a concrete manifestation of an abstraction.
Examples of instances within the UML include objects (instances of classes) and links (instances of associations).
instance scope
Instance scope, for an attribute or an association, is an indication that the values of that attribute, or the target values of that association, are instances.
An instance specification is a packageable element that describes an instance. The values connected with an instance specification are contained within slots. The description of an object is an example of an instance specification.
instance specification
An instance value is a value specification that specifies the value modeled by an instance specification.
instantiable
A generalizable element is instantiable if it can have instances.instantiate
The term instantiate refers to a stereotype attached to a dependency to signify that the dependency represents an instantiation.instantiation
The term instantiation refers to a dependency within which one or more operations belonging to the source class create instances of the target class.One models an instantiation using the instantiate stereotype.
integer
The term integer refers to a primitive type that represents integer values.
An integer constant expression is a numeric constant expression that refers to an integer.
Integrate Each Subsystem
Within the RUP, Integrate Each Subsystem is an activity within the Implementation discipline.
This activity involves integrating new and changed components into a new version of an implementation subsystem.
Integrate System
Within the Unified Process, Integrate System is an activity within the Implementation workflow.
This activity involves creating an integration build plan and then integrating each build so integration testing can be performed. Within the RUP, Integrate the System is an activity within the Implementation discipline. This activity involves adding new versions of
Integrate the System
integration build plan
Within the Unified Process, an integration build plan describes the sequence of builds required for a given iteration.
Within the RUP, integration build plans are part of the Implementation artifact set.
integration tester
Within the RUP, an integration tester is a person playing the role of performing integration tests.integrator
Within the RUP, an integrator is a person playing the role of planning the sequence of builds required in an iteration and integrating each build when its parts have been implemented. An interaction is a behavior that that focuses on the observable exchange of information, in the form of messages, between connectable elements. An interaction is comprised of one or more interaction fragments. Interactions are depicted on interaction diagrams.
intent
An intent is the set of behavioral features and structural features associated with a descriptor.
interaction
interaction constraint
An interaction constraint is a Boolean expression that guards an interaction operand within a combined fragment.
interaction diagram
An interaction diagram is a behavior diagram that shows aspects of an interaction.
The UML defines four kinds of interaction diagrams: 
| communication diagram |
| interaction overview diagram |
| sequence diagram |
| timing diagram |
An interaction fragment is a piece of an interaction.
There are six types of interaction fragments:
|
combined fragment |
|
continuation |
|
event occurrence |
|
execution occurrence |
|
interaction occurrence |
|
state invariant |
An interaction occurrence is an interaction fragment that represents the occurrence of a piece of a particular interaction with specific values replacing the value placeholders defined for the interaction. Interaction occurrences are generally used to factor out common behavior that exists within a number of interactions.
interaction occurrence
interaction operand
An interaction operand is an ordered set of interaction fragments, with optional interaction constraints serving as guards, that represents one operand of the expression given by an enclosing combined fragment.
The term interaction operator refers to an enumeration whose values represent the different kinds of operators that work on combined fragments. These values include the following:
|
alt (the combined fragment represents a choice of behaviors: at most one of the interaction operands will execute) |
|
assert (the combined fragment represents an assertion: The sequences of the operand of the assertion are the only valid continuations) |
|
break (the combined fragment represents a breaking scenario: the operand is performed instead of the remainder of the enclosing interaction fragment) |
|
consider (the combined fragment is designating which message types should be considered) |
|
critical (the combined fragment represents a critical region, which means that the traces of the region cannot be interleaved by other event occurrences on those lifelines included in the region) |
|
ignore (the combined fragment does not show at least one message type, which means that these message types can be considered insignificant and will be ignored if they appear in a corresponding behavior execution) |
|
loop (the combined fragment represents a loop: The loop operand will be repeated a number of times) |
|
neg (the combined fragment represents traces that are defined to be invalid) |
|
opt (the combined fragment represents a choice of behavior where either the sole operand happens or nothing happens) |
|
par (the combined fragment represents a parallel merge between the behaviors of the operands, which means that the event occurrences of the different operands can be interleaved in any way as long as the ordering imposed by each operand is preserved) |
|
seq (the combined fragment represents a "weak" sequencing between the behaviors of the operands, which means the following: [1] The ordering of event occurrences within each of the operands is maintained in the result; [2] Event occurrences on different lifelines from different operands may come in any order; and [3] Event occurrences on the same lifeline from different operands are ordered such that an event occurrence of the first operand comes before that of the second operand) |
|
strict (the combined fragment represents a strict sequencing between the behaviors of the operands) |
An interaction overview diagram is an interaction diagram that focuses on the overview of the flow of control.
This type of diagram resembles an activity diagram, in that interactions and/or interaction occurrences serve as the activity nodes. All other symbols that appear on sequence diagrams and activity diagrams can appear on interaction overview diagrams.
interaction view
The term interaction view refers to those aspects of a given model that involve exchanges of messages among objects to accomplish some purposes.The interaction view is captured in sequence diagrams and/or communication diagrams.
The interaction view is a part of the dynamic view. The term interface is a stereotype attached to a class to signify that the class is a named collection of externally visible operations provided by one or more classes, components, and/or subsystems. The UML defines two kinds of interfaces: provided interfaces and required interfaces.
interface
interface inheritance
The term interface inheritance refers to the inheritance of the interface of a given parent element, but not that element's implementation.
interface specifier
An interface specifier is a reference to an interface or a class that specifies the behavior required of a given class within a particular association.
internal transition
An internal transition is a transition that has an associated action but does not result in a change of state.
intersection
The term intersection refers to an OCL operation that combines two Sets, two Bags, or a Bag and a Set into a new Collection that contains the elements that appear in both Collections.
interruptible activity region
An interruptible activity region is an activity group that supports interrupts by terminating any tokens and behaviors connected with the activity nodes within the region.
interval
An interval is a value specification that defines the range between two other value specifications. This range takes the form lower..upper.
invariant
The term invariant refers to a stereotype attached to a constraint, which is in turn attached to an element, to signify a Boolean expression that must always hold true under the relevant circumstances.
An invocation action is an action that invokes behavior. There are four kinds of invocation actions:
invocation action
| broadcast signal action |
| call action |
| send object action |
| send signal action |
isEmpty
The term isEmpty refers to an OCL operation that returns True if a given Collection contains no elements.isOperationCall
The term isOperationCall refers to an OCL operation that returns True if the message wrapped in a given OclMessage instance corresponds with an operation.
isSent
The term isSent refers to an OCL operator that returns True if a given message has been sent to a given object.
isSignalCall
The term isSignalCall refers to an OCL operation that returns True if the message wrapped in a given OclMessage instance corresponds with a signal.
The term isUnique refers to an OCL operation that returns True if a specified OCL expression resolves to a different value for each element of a given Collection.
iterate
The term iterate refers to an OCL operation that evaluates a specified expression for each element within a given Collection.
The term iterate expression refers to an OCL expression that iterates over the elements of a Collection and results in some value.
iteration
Within the Unified Process, an iteration is a distinct set of activities, based on a plan and specified evaluation criteria, that together form a complete development cycle that results in a release of a partial or complete system.iteration expression
An iteration expression is an expression that yields a set of iteration cases, each of which specifies an execution of an action within its associated iteration.iteration plan
Within the Unified Process, an iteration plan is a fine-grained plan for one iteration within a project. This plan defines the tasks to be performed within the given iteration in terms of the key dates and the required resources.Within the RUP, the iteration plan is part of the Project Management artifact set.
iteration workflow
Within the Unified Process, an iteration workflow is a concrete instance of a workflow, from the perspective of what happens in a typical iteration.iterative process
An iterative process is a process that involves managing a stream of executable releases.
