P
package
A package is a named general-purpose mechanism for organizing model elements, including, for instance, classes, use cases, diagrams, and/or other packages, into groups.Each package within a model forms a namespace. Each package also defines the visibility for the elements it contains as a set.
A package diagram is a structure diagram that shows packages and, optionally, the relationships among them.
package diagram
packageable element
A packageable element is a named element that can be owned by a package.
package import
A package import is a directed relationship that involves a package adding the contents of another package to its namespace.
package merge
A package merge is a directed relationship that involves the merging of the contents of one package into another package. This is useful when elements of the same name are intended to represent the same basic concepts. The resulting merged package combines elements using generalization and redefinitions. There are two basic rules:
 | |
|
Package Product
Within the RUP, Package Product is an activity within the Deployment discipline.
This activity involves performing those tasks that need to occur for producing a "package software" product.
parameter (element)
A parameter is a specification of an argument used A parameter may have a default value (in the form of an expression). It may also have a direction (the possible values are contained in the parameter direction kind enumeration).
Every parameter is also associated with one classifier that specifies the type of the parameter.
The full form of a parameter is
[direction] name : type [= default-value]
parameterable element
A parameterable element is an element that can be exposed as a formal template parameter for a template or specified as an actual parameter in a binding of a template.
parameter direction kind
The term parameter direction kind refers to an enumeration that contains four values:
| so the caller doesn’t need to see it again) |
| returns it to the caller) |
| and may also change the value; the caller expects to see an inout parameter again) |
|
parameterized element
The term parameterized element is a synonym of template.
parameter list
A parameter list is an ordered list of parameter declarations.
parameter set
A parameter set is an element that provides alternative sets of inputs and outputs that a behavior may use.
parent
The term parent refers to the more general element within a given generalization.part
A part is an instance of a classifier that is contained within an instance of another classifier by composition.
part decomposition
A part decomposition is an interaction occurrence that describes the behavior of a part, which belongs to the internal structure of a connectable element, relative to a given interaction.
participates
A model element participates in a relationship.
passive class
A passive class is a class that does not represent an independent flow of control.
passive object
A passive object is an object that does not have its own thread of control.A path is a structural connection between two model elements on a communication diagram.
path
pathname
A pathname is a name that contains the name of the package(s) that contain(s) the named element.
pattern
A pattern is a parameterized collaboration that represents a common solution to a common problem in a given context.
The classifiers, relationships, and behavior associated with the collaboration can be applied via the binding of model elements to the roles of the given pattern.
performance tester
Within the RUP, a performance tester is a person who plays the role of conducting performance tests on the system.
Perform Architectural Synthesis
Within the RUP, Perform Architectural Synthesis is an activity within the Analysis and Design discipline.
This activity involves....
Perform Integration Test
Within the Unified Process, Perform Integration Test is an activity within the Test workflow.
This activity involves performing the tests which verify that the components interact properly with each other after they have been integrated into a build.
Perform System Test
Within the Unified Process, Perform System Test is an activity within the Test workflow.
This activity involves performing the tests which verify that the system functions properly as a whole.
Perform Unit Test
Within the Unified Process, Perform Unit Test is an activity within the Implementation workflow.
This activity involves performing specification, or "black-box," testing to verify each unit's observable behavior, and structure, or "white-box," testing to verify that unit's internal implementation.
permission
The term permission refers to a type of dependency that involves the granting of permission to the client to use some or all of the constituent elements of the supplier.
The term permit is a stereotype that indicates a permission dependency.
persistent object
A persistent object is an object that continues to exist after the process or thread that created it has ceased to exist.phase
Within the Unified Process, a phase is the period of time between two major milestones of a development process.The Unified Process defines four phases:
|
Inception phase |
|
Elaboration phase |
|
Construction phase |
|
Transition phase |
phase plan
Within the Unified Process, a phase plan is a coarse-grained plan for a project as a whole in terms of its phases.A phase plan has three elements:
|
Dates of the major milestones |
|
Staffing profile (which resources are required for which phases) |
|
Dates of the minor milestones |
A pin is an object node connected with an input to or output from an action.
There are two kinds of pins: input pins and output pins.
Plan Deployment
Within the RUP, Plan Deployment is an activity within the Deployment discipline.
This activity involves determining how and when the complete list of deliverables will be developed and ensuring that the end user has all of the necessary information to take delivery of the new software.
Within the RUP, Plan for Next Iteration is an activity within the Project Management discipline.
Plan Project Configuration and Change Control
Within the RUP, Plan Project Configuration and Change Control is an activity within the Configuration and Change Management discipline.
The purpose of this activity is to put together the configuration management plan, which describes the policies and procedures that will be applied to identify, safeguard, and report on all artifacts generated during the project lifecycle.
Within the RUP, Plan the Integration is an activity within the Implementation discipline.
Plan Test
Within the Unified Process, Plan Test is an activity within the Test workflow.
This activity involves describing a testing strategy, estimating the resources that will be required, and scheduling the testing effort.
polymorphic
An operation is polymorphic if its implementation may be supplied by a descendant class.
A port is a structural feature of a classifier that specifies a distinct interaction point between that classifier and its environment or between the classifier and its internal parts.
Ports group provided interfaces and/or required interfaces in that they serve as focal points through which requests can be made to invoke the behavioral features that the classifier makes available and also as gateways for calls that the class makes to external operations. Both parts and interfaces are connected to ports via connectors.
A behavior port is a special kind of port.
postcondition
The term postcondition refers to a stereotype attached to a constraint that specifies a condition that must hold true after a given operation completes its execution.powertype (classifier)
The term powertype refers to a classifier whose instances are also subclasses of another classifier.
powertype (stereotype)
The term powertype also refers to a stereotype attached to a dependency to signify that the target is a powertype of the source.@pre
The term @pre refers to an OCL construct that returns the value of an attribute or an association at the start of the execution of a given operation.One uses this term within a postcondition. Within the RUP, Prepare Environment for Iteration is an activity within the Environment discipline. This activity involves tasks such as completing the development case for the given iteration, preparing tools (and customizing them as necessary), and producing a set of project-specific templates. Within the RUP, Prepare Environment for Project is an activity within the Environment discipline. This activity involves tasks such as assessing the current development organization and tool support, developing a first draft of the development case, and producing a list of project-specific templates for key artifacts.
precondition
Prepare Environment for Iteration
Prepare Environment for Project
prepend
The term prepend refers to an OCL operation that adds a specified element to the beginning of a given Sequence.presentation element
A presentation element is a textual or graphical projection of one or more model elements.A primitive function is a predefined mathematical function, specified in a given external language, that depends only on input values (as opposed to values from memory or objects).
primitive type
A primitive type is a predefined basic datatype, such as Integer or String.Prioritize Use Cases
Within the Unified Process, Prioritize Use Cases is an activity within the Requirements workflow.This activity involves determining which use cases need to be developed in early iterations and which ones can be developed later in the project.
The results of this activity go into the architectural view of the use case model.
.
private
The term private refers to a visibility kind that indicates that a given element is not visible outside of its enclosing namespace, even to descendants.
private inheritance
The term private 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 does not apply to the inheriting element.
problem domain
Within the Unified Process, the term problem domain refers to a conceptual area within the domain model that involves the problem to be solved by the system being built.
A procedure is a set of actions that can be attached as a unit to parts of a model (for example, as the body of a method).
procedure expression
A procedure expression is an expression that resolves to the execution of a procedure that may affect the state of the running system.process
The term process refers to a stereotype attached to a component to signify that the component is transaction-based.Within the RUP, a process engineer is a person playing the role of configuring the process framework to form a process, before a project starts, and also continuously improving the process as the development effort proceeds. The term process view refers to the set of threads and processes that together form the concurrency and synchronization mechanisms of the given system. This view focuses on issues such as performance, scalability, and throughput.
process view
The process view is captured in class diagrams, object diagrams, interaction diagrams, state machine diagrams, and activity diagrams.
The difference between the process view and the design view, in terms of these diagrams, is that the process view focuses on active classes and active objects.
The process view is one of the five interlocking views that comprise the architecture. Within the RUP, Produce Deployment Unit is an activity within the Deployment discipline. This activity involves creating a deployment unit, which consists of the software and the accompanying artifacts required to install and use the product successfully.
product
The term product is a synonym of work product.
product release
Within the Unified Process, the term product release refers to the major milestone that concludes the Transition phase.
profile
A profile is a stereotype attached to a package to signify that the package contains model elements that have been customized for a particular domain or purpose via the use of stereotypes, constraints, and/or tag definitions. The primary purpose of a profile is to offer limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain. The UML defines a profile for software development processes that is primarily based on the Unified Process. Elements of this profile include stereotypes such as boundary class, design model, and test component, and tag definitions such as flow of events–analysis and special requirements.
A profile application is a package import that specifies that a given profile has been applied to a particular package.
projection
A projection is a mapping from a set of elements to a subset of itself.
Within the RUP, the Project Management artifact set is the set of artifacts related to the software business and to the management of a project. The Project Management artifact set contains the following artifacts:
Project Management artifact set
business case
deployment plan issues list
iteration assessment
iteration plans project measurements review record risk list
software development plan
status assessment
| work order |
Within the RUP, the Project Management discipline is a discipline whose purpose is to provide the following:
| |
| |
|
The following activities comprise the Project Management discipline:
| Close Out Phase |
| Close Out Project |
| Conceive New Project |
| Develop Software Development Plan |
| Evaluate Project Scope and Risk |
| Manage Iteration |
| Monitor and Control Project |
| Plan for Next Iteration |
project manager
Within the RUP, a project manager is a person playing the role of allocating resources, establishing priorities, coordinating interactions among the customers and the development team, and keeping the project team focused on the goals of the project.
Within the RUP, a project reviewer is a person playing the role of evaluating project planning and project assessment artifacts at major review points during the project. A property is a set of instances that are owned by a containing classifier instance.
property
protected
The term protected refers to a visibility kind value that indicates that a given model element is visible outside of its enclosing namespace only to descendants.Within the RUP, a protocol is a specification of a set of capsule ports.
protocol conformance
The term protocol conformance refers to a directed relationship within which a given protocol state machine specifies a protocol that conforms to a more general state machine protocol or that a specific behavioral state machine abides by the protocol of a more general protocol state machine. (Protocol conformance means that every rule and constraint specified for the general protocol state machine, including state invariants, preconditions, and postconditions for the operations it refers to, apply to the specific protocol or behavioral state machine.)
protocol state machine
A protocol state machine is a state machine that specifies which operations of a given classifier can be called when instances of that classifier are in particular states and under which condition(s), thus specifying the allowed call sequences on the classifier’s operations. A protocol state machine is indicated by the {protocol} keyword next to the name on a state machine diagram.
protocol transition A protocol transition is a transition that specifies that a given operation can be called for an instance of the given classifier in its initial state, under the initial condition specified as a precondition by a particular guard, and that at the end of the transition, the destination state will be reached under a specified postcondition, also specified as a guard. The notation for a protocol transition is the same as that for a regular transition, except that a protocol transition does not specify an action.
Prototype User Interface
Within the Unified Process, Prototype User Interface is an activity within the Requirements workflow.This activity involves building a logical user interface, and then a physical user interface prototype.
Provide Access to Download Site
Within the RUP, Provide Access to Download Site is an activity within the Deployment discipline.
This activity involves adding the product to the list of products offered through the Web and communicate that the product is available for purchase or delivery on demand.
provided interface One can think of a provided interface as specifying a "contract" for a class, component, or subsystem without specifying implementation. Note that a provided interface can be realized by more than one class or component.
A provided interface is an interface that a classifier provides to its clients.
pseudostate
A pseudostate is a vertex within a state machine that has the basic form of a state but does not behave like a full state.
The term pseudostate kind refers to an enumeration that contains 10 values:
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
public
The term public refers to a visibility kind value that indicates that a given element is visible outside of its enclosing namespace.
