International Business Machines Corporation

Maneesh Mehra

Paul Komar

Geoffrey M Clemm

Bradley C Herrin

Dana Lea Price

Soobaek Jang

Kelly Abuelsaad

Rohit Dilip Kelapure

Renier Rodriguez Morales

Howard B Bernstein

Carol D Yutkowitz

Michael S Rieth

Presenting changes to versioned files. The method can include presenting a first view comprising a plurality of indicators, each of the indicators corresponding to a respective version of a file. A selection of a particular version of a file can be detected. A selection of another version of the file can be detected. In response to the selection of the other version of the file, the versions of the file can be compared to identify differences between the versions. Comparison information based on the differences can be generated. The comparison information can be filtered so that the comparison information fits within a second view having a desired size.

Displaying changes to versioned files

Parallel development of a software system having multiple streams is managed. A selected section from a first artifact in a first stream of the multiple streams is removed from a plurality of sections included within the first artifact. A second artifact is created and includes the selected section and does not include at least one other section of the plurality of sections. An annotation, as a computer data structure, is generated and the annotation specifies the first artifact, a range within the first artifact corresponding to the selected section, and the second artifact.

Parallel development of a software system

In general, embodiments of the present invention relate to conference management. Specifically, sequentially scheduled conferences (e.g., conference calls) are determined for a conference participant. The connection details (e.g., call-in details) for the second of the two conferences are retrieved. If the conference is not over when the second conference is scheduled to begin, a connection is initiated with the second conference using the connection details while maintaining a connection to the first conference.

Management of sequentially scheduled conferences

Arrangements described herein relate to adopting an existing automation script to a new framework. A first version of an automation script configured to execute in a first framework, and expected unit test results for the automation script, are received. A second version of the automation script is created from the first version of the automation script. The second version of the automation script is configured to execute in at least a second framework. The first version of the automation script is executed in the first framework to run a first version of a unit test and the second version of the automation script is executed in the second framework to run a second version of the unit test. Results generated by execution of the first and second versions of the automation script are analyzed to validate the second version of the automation script.

Adopting an existing automation script to a new framework

Software configuration management includes removing a selected section from a first artifact in a first stream. The first artifact includes a plurality of sections, and a second artifact in the first stream is created including the selected section. The second artifact does not include at least one other section of the plurality of sections. An annotation is generated using a processor that specifies the first artifact, a range within the first artifact corresponding to the selected section, and the second artifact into which the selected section is moved. The annotation is used to apply changes implemented in selected artifacts from one stream to another.

A code base, including a code base history, is searched for code term(s) and change(s) that have been made to the code term(s). The code base includes, but is not limited to, multiple: (i) instances of code; (ii) product releases; (iii) code components; and/or (iv) code drafting projects.

Analysis of source code changes

A method of task management for shared artifacts can include detecting a change tag associated with a software artifact and determining, via a processor, each software artifact that is dependent upon the software artifact. A task associated with each dependent software artifact can be generated. Each task can specify a need for a modification to the associated software artifact. A responsible party for each dependent software artifact can be determined. Each task can be automatically assigned to the responsible party for the software artifact associated with the task.

Task management for changes to shared artifacts

A method of software configuration management can include removing a selected section from a first artifact in a first stream, wherein the first artifact includes a plurality of sections, and creating a second artifact in the first stream including the selected section. The second artifact does not include at least one other section of the plurality of sections. An annotation can be generated using a processor that specifies the first artifact, a range within the first artifact corresponding to the selected section, and the second artifact into which the selected section is moved. The annotation can be used to apply changes implemented in selected artifacts from one stream to another.

Growing community of inventors

Westford, MA, United States of America

Maneesh Mehra