Новости и пресс-релизы СМ-Консалт

Архив "Новости и пресс-релизы СМ-Консалт"

Каталог наших проектов. Текущие проекты. Прошлые проекты. Отзывы о нас.

Портфолио→Каталог наших проектов. Текущие проекты. Прошлые проекты. Отзывы о нас.

• Детальная информация о проектах (3)

Software Configuration Management Strategies and IBM Rational ClearCase (eng)

activity

1. A unit of work an individual might be asked to perform. Activities can be of different types. For example, a defect, enhancement request, and issue are all activities. This unit of work ties directly into the change-request management system and processes. An activity can also be a child of another activity that appears in the project-management system.

2. A ClearCase UCM object that tracks the work required to complete a development task. An activity includes a text headline, which describes the task, and a change set, which identifies all versions that you create or modify while working on the activity. When you work on a version, you must associate that version with an activity. If your project is configured to use the UCM-ClearQuest integration, a corresponding Clear Quest record stores additional activity information, such as the state and owner of the activity [ClearCase, 1999].

activity-based configuration management

The management of change to a software system based on higher-level activities (such as task, defect, enhancement) rather than individual file versions. This requires an SCM tool to track which file versions go to implementing a specific activity and then to present activities as key objects. The idea is to simplify complexity and ensure that when the system says a defect is included in a specific build, it has, in fact, been included.

administration VOB

A VOB containing global type objects that are copied to client VOBs on an as-needed basis when users want to create instances of the type objects in the client VOBs. Administration VOBs are not a special type of VOB, but are defined as relationships that a VOB can have with other VOBs.

ALBD server

Atria Location Broker Daemon. This ClearCase master server runs on each Clear Case host. It starts up and dispatches messages to the various ClearCase server programs as necessary.

architecture

1. The set of significant decisions about the organization of a software system: the selection of the structural elements and their interfaces by which the system is composed, together with their behavior, as specified in the collaboration among those elements, the composition of the structural and behavioral elements into progressively larger sub systems, and the architectural style that guides this organization, these elements, their interfaces, their collaborations, and their composition. Software architecture is concerned not only with structure and behavior, but also with usage, functionality, performance, resilience, reuse, comprehensibility, economic and technology constraints and trade-offs, and aesthetic issues [Booch, 1999] [Kruchten, 2000].

2. The organizational structure of a system or component [IEEE Glossary, 1990].

3. The architecture of a software system (at a given point in time) is its organization or structure of significant components interacting through interfaces; those components are composed of successively smaller components and interfaces [RUP 5.5, 1999].

assembly integration

The software-development activity in which separate software component baselines are combined into an executable whole.

See also [integration]

attribute

A metadata annotation attached to an object, in the form of a name/value pair. Names of attributes are specified by user-defined attribute types; users can set values of these attributes. For example, a project administrator might create an attribute type whose name is QAed. A user then could attach the attribute QAed with the value of yes to versions of several file elements.

attribute types

An object that defines an attribute name for use within a VOB. It constrains the attribute values that can be paired with the attribute name (for example, an integer in the range 1 to10).

backward delta

A delta storage approach that stores the latest version of the file in its entirety and stores only the delta of the previous versions.

baseline

A ClearCase UCM object that typically represents a stable configuration for one or more components. A baseline identifies activities and one version of every element visible in one or more components. You can create a development stream or rebase an existing development stream from a baseline.

branch

An object that specifies a linear sequence of element versions.

branch/LATEST development

A branching strategy in which team members work in isolated views but check out and check in on the same branch. Changes become visible to other team members at check-in time rather than file save time. Branch/LATEST development minimizes isolation and maximizes integration.

branching strategy

A strategy for isolation and integration of changes on a software project through the use of branches. A branching strategy defines the types of branches you use, how these branches relate to one another, and how you move changes between branches.

build

The process during which a build program (such as clearmake) produces one or more derived objects. This can involve actual translation of source files and construction of binary files by compilers, linkers, text formatters, and so on.

build audit

The process of recording which files and directories (and which versions of them) are read or written by the operating system during a build.

build avoidance

The capability of a ClearCase build program called clearmake to fulfill a build request using an existing derived object, instead of creating a new derived object by executing a build step.

change request

A general term for any request from a stakeholder to change an artifact or process. Documented in the change request is information on the origin and impact of the current problem, the proposed solution, and its cost.

See also [enhancement request]

See also [defect]

change request management

The recording, tracking, and reporting of requests from any stakeholder to change a software system. Change request management includes the decision-making processes an organization uses to decide what changes to make and the resolution processes used to make them.

change set

A list of related versions associated with a UCM activity. ClearCase records the versions that you create while you work on an activity. An activity uses a change set to record the versions of files that are delivered, integrated, and released together.

Some in the SCM industry distinguish between two terms: change package and change set. The difference is subtle and has to do with the implementation. A change set is defined as the actual delta that composes the change even if it spans files. A change package involves grouping together a set of file versions. ClearCase uses the term change set to denote a change package.

check-out/check-in

The two-part process that extends a branch of an element's version tree with a new version. The first part of the process, check-out, expresses your intent to create a new version at the current end of a particular branch. The second part, check-in, completes the process by creating the new version.

Performing a check-out of a branch does not necessarily guarantee you the right to perform a subsequent check-in. Many users can check out the same branch, as long as they are working in different views. At most, one of these can be a reserved check-out, which guarantees the user's right to check in a new version. An unreserved check-out affords no such guarantee. If server users have unreserved check-outs on the same branch in different views, the first user to perform a check-in wins. Other users must perform a merge if they want to save their checked-out versions.

checkpointing

The ability of developers to check in an intermediate version of a file that they have been working on without this change being made visible to other team members. The ability of developers to checkpoint their work depends on what branching strategy an organization uses. For example, a branch/LATEST strategy does not allow checkpointing.

clearmake

A make-compatible build tool that is part of the ClearCase product and that provides build audit and build avoidance features.

component

1. A physical object in the CM system containing files and directories that implement one or more logical packages. A ClearCase component is a set of files and directories contained under a common root directory. ClearCase components are versioned, shared (reused), and released as a single unit. A large system typically consists of many components. A small system might be contained in only one component.

2. A ClearCase object that groups a set of related directory and file elements within a UCM project. Typically, you develop, integrate, and release the elements that make up a component together. A project contains at least one component, and it can contain multiple components. Projects can share components [ClearCase, 1999].

3. 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. A physical, replaceable part of a system that packages implementation and conforms to and provides the realization of a set of interfaces. A component represents a physical piece of implementation of a system, including software code (source, binary, or executable) or equivalents such as scripts or command files [RUP 5.5, 1999].

component-based development

The creation and deployment of software-intensive systems assembled from components, as well as the development and harvesting of such components.

component subsystem

A stereotyped subsystem representing the logical abstraction in design of a component. It realizes one or more interfaces and can be dependent on one or more interfaces. It can enclose zero or more classes, packages, or other component subsystems, none of which is visible externally (only interfaces are visible). It can also enclose zero or more diagrams that illustrate internal behavior (such as state, sequence, or collaboration diagrams) [RUP 5.5, 1999].

composite baseline

A UCM structure that logically associates baselines together. A composite baseline can itself be a member of another composite baseline.

concurrent changes

Changes made by two or more developers to the same files at the same time. The SCM tool must also support the merging or integration of the changes, thus recombining the work that was done in parallel. Concurrent change on a large scale made by two or more teams is referred to as parallel development.

configuration

1. A labeled or baselined set of versions that form a consistent set.

2. The set of versions selected by a view.

configuration and change control

An element of configuration management that consists of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items [IEEE Glossary, 1990].

configuration control

An element of configuration management that consists of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification [IEEE Glossary, 1990].

configuration identification

An element of configuration management that consists of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation [IEEE Glossary, 1990].

configuration management

A more general definition than software configuration management, applying to both hardware and software configuration management.

See also [software configuration management]

configuration record

A bill of materials for a derived object, indicating exactly which file system objects (and which specific versions of those objects) were used by the rebuild as input data or as executable programs and which files were created as output.

configuration specification

A set of configuration rules specifying which versions of VOB elements a view selects. The config spec for a snapshot view also specifies which elements to load into the view.

configuration status accounting

An element of configuration management that consists of the recording and reporting of information needed to manage a configuration effectively [IEEE Glossary, 1990].

defect

An anomaly, or flaw, in a delivered work product. Examples include such things as omissions and imperfections found during early life cycle phases and symptoms of faults contained in software that is sufficiently mature for test or operation. A defect can be any kind of issue you want tracked and resolved.

See also [change request]

deliver

A ClearCase operation that enables developers to share their work with the rest of the project team by merging work from their own development streams to the project's integration stream. If required, the deliver operation invokes the Merge Manager to merge versions.

See also [interproject deliver]

delta

The physical change made between one version of a file and the next.

deployment

The act of moving the staged artifacts to other systems for further testing. In some cases, deployment can be the act that moves the software from the staging area to the production server to be used by the end user.

derived object

A ClearCase-specific name for the output files produced during a software build using clearmake.

development stream

A ClearCase UCM object that determines which versions of elements appear in your development view and maintains a list of your activities. The purpose of the development stream is to let you work on a set of activities and corresponding versions in isolation from the rest of the project team. The development stream configures your development view to select the versions associated with the foundation baselines, plus any activities and versions that you create after joining the project or rebasing your development stream.

development view

A view associated with a UCM development stream. A development view is used to work on a set of activities and corresponding versions isolated from the rest of the project team. You then can share changes made in a development view with the rest of the project team by delivering activities to the project's integration stream. A development view can be either a dynamic view or a snapshot view.

dynamic view

A type of view that is always current with the VOB. Dynamic views use the MVFS to create and maintain a directory tree that contains versions of VOB elements. Dynamic views are not supported on all ClearCase platforms.

element

An object that encompasses a set of versions, organized into a version tree. Elements can be either files or directories.

enhancement request

A type of stakeholder request that specifies a new feature or functionality of the system. Enhancement requests specify a new feature of the system or a change to the "as designed" behavior of a system.

See also [change request]

entity

A record in a ClearQuest user database. Every entity is based on a specific entity type. Entities based on UCM-enabled entity types can be automatically associated with activities.

entity type

A metadata object that appears in a ClearQuest schema that describes the structure of a type of record, including its fields, states, actions, and forms.

follow-on project

A project that starts from an existing ongoing project. A follow-on project inherits the ongoing project's component baselines as its starting configuration.

forward delta

A delta storage approach that stores the first version of a file in its entirety and the other versions as deltas.

foundation baseline

A property of a stream. Foundation baselines specify the versions and activities that appear in your view. As part of a rebase operation, foundation baselines of the target stream are replaced with the set of recommended baselines from the source stream.

full baseline

A baseline created by recording all versions below a component's root directory. Generally, full baselines take longer to create than incremental baselines; however, ClearCase can look up the contents of a full baseline faster than it can look up the contents of an incremental baseline.

hyperlinks

A logical pointer between two objects. For example, a predefined hyperlink type of Merge defines merge relationships between versions on different branches. A hyperlink can have a from string as well as a to string, which are implemented as string-valued attributes on the hyperlink object.

A bidirectional hyperlink connects two objects in the same VOB or in different VOBs and can be navigated in either direction: from-object to to-object, or to-object to from-object. A unidirectional hyperlink connects two objects in different VOBs and can be navigated only in the direction of from-object to to-object.

implementation view

An architectural view that describes the organization of the static software elements (code, data, and other accompanying artifacts) of the development environment in terms of packaging, layering, and configuration management (ownership, release strategy, and so on).

incremental baseline

A baseline created by recording the last full baseline and versions of elements that have changed since the last full baseline was created. Generally, incremental baselines are faster to create than full baselines; however, ClearCase can look up the contents of a full baseline faster than it can look up the contents of an incremental baseline.

in-line delta

An approach to delta storage in which no copy of the file is stored in its entirety; only deltas are stored.

integration

1. The process of bringing together independently developed changes to form a testable piece of a software system. Integration can occur at many levels, eventually culminating in a complete software system.

2. The software-development activity in which separate software components are combined into an executable whole [RUP 5.5, 1999].

integration stream

A ClearCase UCM object that enables access to versions of the project's shared elements. A project contains only one integration stream. The integration stream maintains the project's baselines and configures integration views to select the versions associated with the foundation baselines, plus any activities and versions that have been delivered to the integration stream.

integration view

A view associated with a UCM project's integration stream. An integration view is used to build and test the latest versions of a project's shared elements. It can be either a dynamic view or a snapshot view.

interproject deliver

A deliver operation that enables developers to share their work with another project team by merging work from their own development streams to another project's integration stream (or development stream). If required, the deliver operation invokes the Merge Manager to merge versions.

See also [deliver]

iteration

A distinct set of activities with a baselined plan and valuation criteria, resulting in a release (internal or external).

label

An instance of a label type object that supplies a user-defined name for a version. A label is attached to a version of an element.

label type

A named tag that can be used to identify a consistent set of element versions. For example, you could create a label type called RELEASE1 and attach instances of the label type to all the versions of the elements that make up the first release of a software system.

license server

A host whose albd_server process controls access to the licenses defined in its license database file.

main branch

The starting branch of an element's version tree. The default name for this branch is main.

mainline project

A UCM project that serves as an integration and release point for multiple subprojects. It also serves as the starting point for follow-on projects.

mastership

The capability to modify an object or to create instances of a type object.

merge

The act of combining the contents of two or more files or directories into a single new file or directory. Typically, when merging files, all the files involved are versions of a single file element. When merging directories, all contributors to the merge must be versions of the same directory element.

merge integration

The resolution of parallel changes made by different team members to common files, directories, or components. In some cases, this can be automated. In others, manual decisions must be made (such as when conflicting changes have been made to the same files).

metadata

Data associated with an object, supplementing the object's file system data.

multiversion file system (MVFS)

A directory tree that, when activated (mounted as a file system of type MVFS), implements a ClearCase VOB. To standard operating system commands, a VOB appears to contain a directory hierarchy; ClearCase commands can also access the VOB's metadata. MVFS also refers to a file system extension to the operating system, which provides access to VOB data. The MVFS is not supported on all ClearCase platforms.

package

A collection of metadata (fields, actions, forms, and so on) that can be added to a schema. In the UCM model, adding the UCM package to a schema allows entities based on that schema to be automatically associated with activities and collect change sets.

parallel development

1. Concurrent changes made to individuals files or an entire software system by two or more individuals or teams. Parallel development also includes the capability to merge the changes that have been made in parallel.

2. The concurrent creation of versions on two or more branches of an element [ClearCase, 1999].

posted delivery

See [pull delivery]

project

1. A ClearCase UCM object that contains the configuration information needed to manage a significant development effort, such as a product release. The project is used to set policies that govern how developers access and update the set of files and directories used in the development effort. A project includes one integration stream, which configures views that select the latest versions of the project's shared elements, and typically multiple development streams, which configure views that allow developers to work in isolation from the rest of the project team. A project can be ClearQuest-enabled so that its activities will be associated with UCM-enabled ClearQuest entities [ClearCase, 1999].

2. An endeavor performed by people, constrained by limited resources, and planned, executed, and controlled. A project is a temporary endeavor undertaken to create a unique product or service. Temporary means that every project has a definite beginning and a definite end. Unique means that the product or service is different in some distinguishing way from all similar products and services. Projects are undertaken at all levels of the organization. They might involve a single person or many thousands. They might require fewer than 100 hours to complete or more than 10,000,000. Projects might involve a single unit of one organization or might cross organizational boundaries, as in joint ventures and partnering. Projects are often critical components of the performing organization's business strategy [PMI, 1996].

project VOB (PVOB)

A VOB that stores UCM objects, such as projects, streams, activities, and change sets. Every UCM project must have a PVOB. Multiple projects can share the same PVOB.

See also [versioned object base (VOB)]

promotion level

A property of a UCM baseline that can be used to indicate the quality or degree of completeness of the activities and versions represented by that baseline. You can use promotion levels to define policy for a UCM project. UCM provides an ordered set of default promotion levels and also supports user-defined promotion levels. The action of changing the promotion level of a baseline is called promoting or demoting the baseline.

pull delivery

With pull delivery, developers indicate that their changes are ready for integration, but the integrator is responsible for integrating the developer's changes into the project's integration stream.

See also [deliver]

push delivery

With push delivery, a developer is responsible for integrating his or her changes into the project's integration stream, where the integrator can create baselines and perform project builds.

See also [deliver]

PVOB

See [project VOB (PVOB)]

rebase

A ClearCase UCM operation that makes your development work area current with the set of versions represented by a more recent baseline in the integration stream.

recommended baseline

The set of baselines that the project team should use to rebase its development streams. In addition, when developers join a project, their development work areas are initialized with the recommended baselines. The recommended baselines represent a system configuration, or set of components, that has achieved a specified promotion level. A baseline becomes part of the set of recommended baselines when the project manager promotes it to a certain promotion level, such as TESTED.

registry server

The host on which all ClearCase data storage areas (all VOBs and views) in a local area network are centrally registered.

release

The process of putting the runtime software into its final form and making it available to its intended users.

replica

An instance of a VOB, located at a particular site. A replica consists of the VOB's database, along with all the VOB's data containers.

reserved check-out

See [check-out/check-in]

schema

Defines the metadata for entities and other information in a ClearQuest user database.

single-stream project

A project whose UCM attributes specify that all development will occur on the integration stream for the project. No development streams or other child streams can be created in this type of UCM project.

snapshot view

A view that contains copies of ClearCase elements and other file system objects in a directory tree. You use an update tool or rebase operation to keep the view current with the VOB (as specified by the configuration specification).

software configuration management (SCM)

A software-engineering discipline that comprises the tools and techniques (processes or methodology) a company uses to manage change to its software assets.

staging

The process of putting the derived object files (executables, libraries, data files, generated header files, and so on) under version control.

stream

A ClearCase UCM object that determines which versions of elements appear in any view configured by that stream. Streams maintain a list of baselines and activities. A project contains one integration stream and typically multiple development streams.

subsystem

1. A generic name used to refer to a ClearCase component.

2. A model element that has the semantics of a package, so that it can contain other model elements, and a class, so that it has behavior. (The behavior of the subsystem is provided by classes or other subsystems it contains.) A subsystem realizes one or more interfaces, which define the behavior it can perform. A subsystem is a grouping of model elements, of which some constitute a specification of the behavior offered by the other contained model elements [RUP 5.5, 1999].

trigger

A monitor that specifies one or more standard programs or built-in actions to be executed automatically whenever a certain ClearCase operation is performed.

trivial merge

A merge between two branches in which it is possible to automatically copy the contents of one file version on one branch to another using information contained in the version tree.

un-check-out

The act of canceling a check-out operation.

Unified Change Management (UCM)

1. Rational Software's approach to managing change in software system development, from requirements to release. UCM spans the development life cycle, defining how to manage change to requirements, design models, documentation, components, test assets, and source code.

One of the key aspects of the UCM model is that it ties together or unifies the activities used to plan and track project progress and the artifacts being changed. The UCM model is realized by both process and tools. The Rational products ClearCase and ClearQuest are the foundation technologies for UCM. ClearCase manages all the artifacts produced by a software project, including both system artifacts and project-management artifacts. ClearQuest manages the project's tasks, defects, and requests for enhancements (referred to generically as activities), and provides the charting and reporting tools necessary to track project progress.

2. An out-of-the-box process, layered on base ClearCase and ClearQuest functionality, for organizing-software development teams and their work products. Members of a project team use activities and components to organize their work [ClearCase, 1999].

unreserved check-out

See [check-out/check-in]

version

An object that implements a particular revision of an element. The versions of an element are organized into a version tree structure. Checked-out version can also refer to the view-private file that corresponds to the object created in a VOB database by the check-out command.

version control

A subset of software configuration management that deals with tracking version evolution of a file or directory.

version tree

The hierarchical structure in which all versions of an element are (logically) organized. When displaying a version tree, ClearCase also shows merge operations (indicated by arrows).

versioned object base (VOB)

A repository that stores versions of file elements, directory elements, derived objects, and metadata associated with these objects. With ClearCase MultiSite, a VOB can have multiple replicas at different sites.

view

A ClearCase object that provides a work area for one or more users to edit source versions, compile them into object modules, format them into documents, and so on. Users in different views can work on the same files without interfering with each other. For each element in a VOB, a view's configuration specification selects one version from the element's version tree. Each view can also store view-private files that do not appear in other views. There are two kinds of views: snapshot and dynamic.

view server

The daemon process that interprets a view's configuration specification, mapping element names into versions, and that performs workspace management for the view.

VOB

See [versioned object base (VOB)]

VOB server

The process that provides access to the data containers that store versions' file system data.

workspace

1. A private area where developers can implement and test code in accordance with the project's adopted standards, in relative isolation from other developers [RUP 5.5, 1999].

2. A generic SCM term for a ClearCase view. Sometimes used to refer to the combination of a view and a stream in a UCM context.

workspace management

The process of creating and maintaining a workspace.

30.11.2008

Решения и программные модули для IBM Rational и Microsoft

Наши решения и услуги→Решения и программные модули для IBM Rational и Microsoft

09.10.2009 03:45:30
'GanttChart for ClearQuest' Модуль отображения иерархии и планирования задач ClearQuest в виде диаграммы Ганта
Планирование и отображение иерархии задач в виде диаграммы Ганта. Представляет собой Plug-in для IBM Rational ClearQuest версий 7.0, 7.1 и выше. Модуль представляет собой практический интерес для всех, кто использует IBM Rational ClearQuest и кому не хватает возможностей по проектному управлению. Модуль не подменяет существующие продукты для управления проектами, а лишь добавляет оперативные срезы в IBM Rational ClearQuest. Для большинства пользователей функций, предоставляемых модулем достаточно для полноценного планирования и оперативного управления проектами.
Модуль не имеет аналогов!
Тип решения: Модуль - Plug-ins для IBM Rational ClearQuest Eclipse.
Ограничения: Требует предустановленного IBM Rational ClearQuest.
Поставка: Мультиплатформенный пакет.
Совместимость: Совместим с ClearQuest старше 7.0.
Поддержка кириллицы: Да (мультиязычный интерфейс)
Схема лицензирования: безлимитная лицензия на организацию
GanttChart for ClearQuest размещен в Глобальном каталоге IBM  (Российский вариант, Мировой вариант) Ему присвоен идентификатор 41151 в каталоге IBM Global Solutions Directory
Текущая версия 1.2

10.11.2008 00:25:00
Модуль расширенной интеграции ClearQuest с MS Project (ProjectTracker)

Позволяет интегрировать ClearQuest и MS Project. Модуль позволяет осуществлять более глубокую интеграцию, чем стандартный модуль Rational. 
Тип решения: Внешнее приложение, устанавливаемое на каждое клиентское место.
Ограничения: Требует предустановленного ClearQuest.
Поставка: Дистрибутив для Windows.
Совместимость: Совместим с ClearQuest любой версии.
Поддержка кириллицы: Да
Схема лицензирования: безлимитная лицензия на организацию
ProjectTracker версии 2.5.1. размещен в Глобальном каталоге IBM (Российский вариант, Мировой вариант) Ему присвоен идентификатор 38662 в каталоге IBM Global Solutions Directory

 

22.03.2008 03:19:49
Модуль UML2ClearQuest. Преобразование UML диаграмм в набор состояний ClearQuest Designer
Модуль предназначен для облегчения процесса преобразования логических диаграмм UML, описывающих  жизненный цикл запросов на изменения  в их физическую реализацию в виде схемы ClearQuest Designer. Экспорт производится из IBM Rational Software Architect, MS Visio и StarUML. Решение UML2ClearQuest обеспечивает возможность создания и модификации жизненного цикла для типов записей IBM Rational ClearQuest на основе UML-диаграмм версий 2.1 и ниже.Программа предназначена в основном для менеджеров системы IBM Rational ClearQuest, которые занимаются проектированием и разработкой схем для этой системы как для своей, так и для сторонних организаций.
Тип решения: Внешнее приложение RSA, Visio, StarUML.
Ограничения: Не требует дополнительной настройки.
Поставка: Дистрибутив для Windows.
Совместимость: Совместим с любой версией ClearQuest, RSA, Visio, StarUML. Поддерживает любую схему ClearQuest.
Поддержка кириллицы: Да

Архив "Наши решения и услуги"