International Business Machines Corporation

Mila Keren

Anthony Hayden Lindsey

Gary Martin Johnston

Yael Shaham-Gafni

Zvi Yosef Yehudai

Lev Kozakov

Alan Hartman

Richard Kirchhofer

Laurent Balmelli

Yuval Ishai

Shiri Kremer-Davidson

Julia Rubin

Christopher Thomas Kello

Sai Zeng

Fausto Bernardini

Doron Cohen

Avraham Harpaz

Dafna Sheinwald

Dmitri Pikus

Ioana Boier-Martin

Tali Yatzkar-Haham

Jose Gomes

Man Mohan Singh

Shmuel Gal

Abraham Zehavi

José Gomes

Ofir Meir Brukner

Olga Golovenevsky

Mel Shalev

John M Marberg

Alan Hartmann

A method of telephone call management in process of service development that allows a user to model and create telephone call management schemes independent of telecommunications protocols and network layer details. The method of the invention operates by creating an abstract model of a telephone call life-cycle that is converted, using a set of communication threads, into executable code. Models in accordance with the method of the invention are constructed using an Integrated Development Environment (IDE) for creating and developing telecom services that embodies the Telecom Service Domain Specific Language (TS-DSL) which is implemented as a Unified Modeling Language (UML) extension for the telecom domain. By this method, individuals without specialized knowledge of telecom related software programming and protocols can successfully design and implement telecom services that manages calls. The ease of implementation of the method also reduces design time and, therefore, time to market of the finished product.

Protocol independent telephony call lifecycle management scheme

A method that includes: modeling a software system having pairs of coupled software components to yield a platform-independent model of pairs of respective platform-independent software component models associated with platform-specific software components; applying a materialization process to the platform-independent model to yield a platform-specific model by selecting respective concrete platform specific software components for the software component models; analyzing the platform-specific model to identify mismatched pairs of concrete platform-specific software components; re-modeling the platform-specific model such that each identified mismatched pair becomes coupled together via a configurable glue component model which comprises interface maps usable to eliminate the mismatch; configuring the glue component models by determining, in response to a feedback from a user, code snippets associated with any of the interface maps; and transforming the configured glue component model into a computer code in the platform-specific language by assembling all code snippets into a single piece of code.

Integrating software components in a software system using configurable glue component models

Described is a method and system of requirements management including the expression in a requirements management tool of a relationship selected from the group consisting of a satisfaction relationship, an alternative relationship, a conflict relationship, and a constant dependency relationship. Described is a requirements management method including a first automatic analyzing of a requirements set to find conflicts, having a conflict free requirements subset. and a second automatic analyzing of the requirements set to verify completeness.

Requirements management semantics modeling

A plurality of artifacts, in a plurality of repositories, are maintained under revision control. A plurality of artifact tuples, in another repository, are maintained under revision control. At least one first artifact tuple comprise first information providing access to at least one of the artifacts. At least one second artifact tuple comprises second information providing access to at least one other artifact tuple. Each of the artifact tuples are associated with at least one of a plurality of product development processes. An apparatus comprises a plurality of repositories, each maintaining under revision control a plurality of artifacts and another repository that maintains under revision control a plurality of artifact tuples. A workflow process is adapted to allow users to associate each of the artifact tuples with at least one of a plurality of product development processes.

Techniques supporting collaborative product development

A graphical user interface permits a user to graphically designate a range within data files as input to operations that manipulate the data and permits the user to graphically represent operations that thereafter can be selected for execution. In this way, a user can graphically designate a range of records within a data file on which a desired data manipulation operation will occur and can graphically represent the desired data manipulation operation with a single icon that can be selected for execution.

Object oriented data arranger graphical user interface

A method and system for displaying a resource schedule containing a plurality of objects in an N-level multiple hierarchy all of which objects are subject to a common dependency, comprising the steps of allocating different non-overlapping areas of a display device for each level of the resource schedules, and graphically displaying each level of the resource schedule in the respective area of the display device in synchronized relationship on a common axis representative of the common dependency. Editing tools are provided for allowing objects of the same level to be interchanged, objects of a given level i (where i<N) to be inserted into an object of a higher level (i&plus;1), and objects of a given level i (where i>1) to be disassembled into an object of a lower level (i&minus;1). The method and system are particularly suited for constructing and editing crew pairings for airlines and allow simple and efficient on-line, interactive manipulation of resources.

Method and system for displaying and editing a resource schedule

A technique, system, and computer program for presenting test coverage metrics in a visual programming environment. The information is presented in the same general visual manner in which a visual programmer creates a visual program. A number of alternative presentation styles are defined whereby the visual program is augmented to indicate test coverage status. For example, when displaying connections, one color may be used when displaying a connection to indicate that it has been covered, while a different color is used for connections that were not covered. Or, different line styles (such as solid versus dashed, or different degrees of line thickness) may be used to represent the same information. Alternatively, the test coverage status may be indicated by annotating the graphical representation of the visual program with text (such as &ldquo;covered&rdquo; or &ldquo;not covered&rdquo;).

Presentation of visual program test coverage information

A method, system, and computer program for presenting runtime performance data for analysis in a visual programming environment. The performance data is presented in substantially the same manner in which a visual programmer creates a visual program. A number of alternative presentation styles are defined whereby the visual program is augmented to indicate performance data. For example, when displaying connections, one color may be used when displaying a connection to indicate it has been executed a relatively high number of times, while a different color (or a different hue of the first color) is used for connections that were executed a relatively low number of times. Or, different line styles may be used (such as different degrees of line thickness, or solid lines compared to lines comprised of dashes of varying length) may be used to represent the same information. Alternatively, the performance data may be indicated by annotating the graphical representation of the visual program with text (indicating the number of times the connection was executed, for example). Total and local elapsed time will also be presented, using the same presentation techniques. Both the execution counts and the elapsed time may be indicated in actual numbers, or as a percentage of the corresponding totals.

Presentation of visual program performance data

A method, system, and computer program for providing test coverage metrics in a visual programming environment. A test coverage model for visual programming is defined, which accounts for the specialized nature of visual programming, and the metrics are based on this model. The metrics are expressed in terms of elements familiar to the visual programmer, as opposed to using source code metrics. In a preferred embodiment, these elements comprise events, actions, connections, and attributes. The code implementing a visual program is instrumented according to this model, and test coverage information is gathered as the instrumented program executes.

Technique for test coverage of visual programs

A method, system, and computer program for providing runtime performance analysis in a visual programming environment. A performance data collection technique for visual programming is defined, which accounts for the specialized nature of visual programming, and the analysis is based on this collected data. The performance data is expressed in terms of elements familiar to the visual programmer, as opposed to using a source code approach. In a preferred embodiment, these elements comprise events, actions, connections, and attributes. The code implementing a visual program is instrumented according to this performance data collection technique, and performance information is gathered as the instrumented program executes. Preferably, the information gathered comprises execution counts and elapsed time per element.

Visual program runtime performance analysis

A method is described for operating a data processing system having a plurality of processors to sort a set of data records each having an associated key for governing the sort process. The method comprises determining a range for the key values by sampling the key values. The range is divided into a plurality of quantiles, one for each processor, each quantile having a respective index. At each processor, a plurality of buckets are defined, each bucket corresponding to a respective one of a plurality M.sub.p of subintervals in the quantile, each subinterval having a respective index. The index of the quantile in which the key value lies and the index of the subinterval in which the key value lies are determined directly from the key values using fast operations. Each key is distributed to the processor corresponding to the quantile in which the key value lies. At each processor, the keys falling in the quantile corresponding to the processor are distributed into the buckets according to the indices of the subintervals in which the key values lie, the buckets being processed in sequence in order to sort the records and the keys in each bucket sorted if the bucket contains more than one key. Finally, the sorted keys from each processor are concatenated.

Data sorting

A graphical user interface (GUI) application program implemented in an object oriented programming language permits a user to instantiate new program objects by dragging an instantiation object from one GUI window to a new GUI window and dropping the instantiation object in the new window. When the instantiation object is dropped into the new window, an object specified by the new window type is automatically instantiated. If needed, the user is automatically prompted to provide parameters needed for the object instantiation according to the window in which the object is dropped.

Growing community of inventors

Nesher, Israel

Mila Keren