Browse Prior Art Database

Native User Multi-System Call

IP.com Disclosure Number: IPCOM000016166D
Original Publication Date: 2002-Jul-12
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 191K

Publishing Venue

IBM

Abstract

In today's world of cross site/ cross project product deliveries, the sharing of data (source code, binaries, project management data) has become increasing difficult. Even when two instances of the same development/project management tool are used, critical data cannot readily be shared. As software development tool sets evolve, sharing of cross site/cross project data will become increasingly more common. Until software development tool sets embrace the concept, a means for sharing data is necessary. The Cross Development Environment (CDE) solves this problem. CDE is a bridge between multiple library control systems, problem tracking systems, and user builds. The Native User Multi-System Call is one piece of the CDE bridge, which allows users to continue using their existing software development tool sets. Projects can now share cross site data without introducing new tools and disrupting the user's environments.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 2

Native User Multi-System Call

   In today's world of cross site/ cross project product deliveries, the sharing of data (source code, binaries, project management data) has become increasing difficult. Even when two instances of the same development/project management tool are used, critical data cannot readily be shared. As software development tool sets evolve, sharing of cross site/cross project data will become increasingly more common. Until software development tool sets embrace the concept, a means for sharing data is necessary. The Cross Development Environment (CDE) solves this problem. CDE is a bridge between multiple library control systems, problem tracking systems, and user builds. The Native User Multi-System Call is one piece of the CDE bridge, which allows users to continue using their existing software development tool sets. Projects can now share cross site data without introducing new tools and disrupting the user's environments.

The cross site/cross project issue has been around for a long time. Generally, the problem is solved either by manual intervention or introducing new interfaces or tool sets. Through the use of exit support in native software development tools, the Native User Multi-System Call within the CDE can be used to determine on which system and action should be invoked as shown in Figure 1.

N a tiv e U s e r M u lti-S y s te m C a ll

D ev e lo p m e n t In te rfa ce

Eclipse

Project M anagem ent W eb C lient

W eb C lient

Client APIs

Common interface for:

Prob lem Tracking

Feature T ra ckin g

V ersion C o ntrol

C ro ss D e v e lo p m e n t Environm ent Bridge

R ep o sito ry A P Is

Native User M u lti-S y s te m C a ll

Native User M u lt i-S y s t e m C a ll Native User

M u lt i-S y s t e m C a ll

Native User M u lt i-S y s t e m C a ll

Native User M u lt i-S y s t e m C a ll

D efects

Features

V C

CPTRs

Project M gt

V C

Problem

W B S

V C

Problem

V C

ClearQ uest

ClearCase

CM VC

CM V C (Roch)

CRS

CV S

*Rational

Figure 1.

1

[This page contains 1 picture or other non-text object]

Page 2 of 2

The main advantage of the Native User Multi-System Call is the elimination of new tools for the end user every time a new project or partner to a project is introduced. The following example shows the use of the Native User Multi-System Call for two problem tracking systems - CPTR and CMVC Defects. The...