Glossary

In this glossary, only the terms that are specific to the RUP or that have a slightly different meaning in the RUP are defined. Terms in italics are defined elsewhere in the glossary.

Activity

A unit of work in the RUP that a role may be asked to perform. An activity may be decomposed in steps. Activities produce or modify artifacts .



Actor

Someone or something, outside the system (or business), that interacts with the system (or business).



Artifact

A piece of information that is produced, modified, or used by a process, defines an area of responsibility, and is subject to version control. An artifact can be a model, a model element, or a document.



Base
See [RUP Base]
Baseline

A reviewed and approved release of artifacts that constitutes an agreed-on basis for evolution or development and that can be changed only through a formal procedure, such as a change and configuration control procedure.



Build

An operational version of a system or part of a system that demonstrates a subset of the capabilities to be provided in the final product.



Builder
See [RUP Builder]
Component

A nontrivial, nearly independent, and replaceable part of a system that fulfills a clear function in the context of a well-defined architecture. A component conforms to and provides the physical realization of a set of interfaces.

See also [Process Component]


Construction

The third phase of the RUP development cycle, where most of the software is developed.



Cycle

A complete pass through all four phases of the RUP ( Inception, Elaboration, Construction, and Transition ), resulting in an external product release.



Deployment

A discipline in the RUP whose purpose is to ensure a successful transition of the developed system to its users.



Development Case

The actual process used by the performing organization. It is developed as a configuration, or customization, of the RUP product and is adapted to the project's needs.



Discipline

A logical grouping of role , activities , artifacts, and other process guidance in the description of a process.



Elaboration

The second phase of the RUP development cycle , where the product's vision , its requirements, and its architecture are fully defined.



Extended Help

A RUP feature allowing associated software development tools to provide a context to the RUP, which will make the RUP display appropriate topics based on the given context.



Inception

The first phase of the RUP development cycle , where the scope of the project and its motivations are defined.



Iteration

A distinct sequence of activities with a plan and evaluation criteria resulting in a release (internal or external).



Milestone

The point in time at which an iteration or a phase formally ends, corresponding to a release point.



Modeler
See [RUP Modeler]
MyRUP

The RUP browser allowing you to view the process, search, use the index, navigate graphically, and create your own personalized process views of your RUP Process Configuration .



Organizer
See [RUP Organizer]
Phase

The time between two major project milestones , during which a well-defined set of objectives is met, artifacts are completed, and decisions are made to move or not to move into the next phase.



Plug-In

A RUP Plug-In is a deployable unit for one or several RUP Process Components that can be readily "dropped" onto a RUP Base to extend it. A RUP Plug-In can be compiled into a physical file, allowing it to be moved around and added to a RUP Library with a compatible RUP Base .



Process Component

A RUP Process Component is a coherent , quasi-independent " chunk " or module of process knowledge that can be named, packaged, exchanged, and assembled with other process components.



Process Configuration

A RUP Process Configuration is a browsable set of RUP Process Components that constitutes a complete process ("complete" from the perspective of a particular use). It is a Web site that sits on the user 's machine or a server. RUP Process Configurations are compiled with RUP Builder .



Process View

A feature of MyRUP allowing you to customize what parts of the RUP Process Configuration you want to see in your MyRUP tree browser as well as external links. Process views can be role-based (for example, analyst, developer, tester) or personalized for the needs of a specific user.



Prototype

A release that is not necessarily subject to change management and configuration control. A prototype may be thrown away or may evolve into becoming the final system.



Rational Process Workbench ( RPW )

A process authoring toolkit. It is a combination of tools, processes, and other assets that allow a process engineer to develop RUP Plug-Ins . The RPW includes RUP Modeler , RUP Organizer , a RUP Library , and process guidance for process authoring.



Release

A subset of the end product that is the object of evaluation at a milestone . A release is a stable, executable version of the product, together with any artifacts necessary to use this release, such as release notes or installation instructions. A release can be internal or external. An internal release is used only by the development organization as part of a milestone , or for a demonstration to users or customers. An external release (or delivery) is delivered to end-users.



Risk

An ongoing or upcoming concern that has a significant probability of adversely affecting the success of major milestones .



Role

A definition of the behavior and responsibilities of an individual, or a set of individuals, working together as a team.



RPW
See [Rational Process Workbench]
RUP Base

A collection of RUP Process Components meant to be extended by applying plug-ins to generate RUP Process Configurations . It resides in a RUP Library .



RUP Builder

A tool within the RUP product used to create RUP Process Configurations out of a RUP Base and any number of RUP Plug-Ins .



RUP Exchange

A place on the Rational Developer Network where RUP Plug-Ins together with other process- related material are made available to the user community.



RUP Library

A collection of Process Components out of which a set of RUP Process Configurations may be compiled with RUP Builder . New process components can be added to a RUP Library through the means of RUP Plug-Ins .



RUP Modeler

A component of Rational Process Workbench . It allows a process engineer to visually model process elements such as activities , artifacts , roles , disciplines , and tool mentors and their relationships; assemble them into RUP Process Components ; and compile them into RUP Plug-Ins . RUP Modeler is an add-in to Rational XDE and works in conjunction with RUP Organizer .



RUP Organizer

A component of Rational Process Workbench . It allows you to associate content files with process elements such activities , artifacts , roles , disciplines , and tool mentors and to compile these RUP Process Components to create a RUP Plug-In with the new or modified files. The files can be examples, guidelines, or reusable assets. RUP Organizer also allows you to modify Extended Help .



Scenario

A described use-case instance or a subset of a use case.



Step

A subset of an activity. Not all steps needs to be performed each time an activity is invoked.



Tool Mentor

A description that provides practical guidance on how to perform specific process activities or steps using a specific software tool.



Transition

The fourth and last phase of the RUP development cycle , which results in a final product release .



Use Case

A sequence of actions a system performs that yields an observable result of value to a particular actor . A use-case class contains all main, alternate, and exception flows of events that are related to producing the "observable result of value."



Vision

The user's or customer's view of the product to be developed, specified summarily at the level of key stakeholders' needs and major features of the system.



Workflow

The sequence of activities performed in a business that produces a result of observable value to an individual actor of the business. Workflows in the software engineering process can be expressed in terms of sequences of activities .





The Rational Unified Process Made Easy(c) A Practitioner's Guide to Rational Unified Process
Programming Microsoft Visual C++
ISBN: N/A
EAN: 2147483647
Year: 2005
Pages: 173

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net