International Business Machines Corporation

Paypal, Inc.

Brian C Schimpf

Yuhong Yin

Edith H Stern

Barry Edward Willner

Robert Cameron Weir

Shailaja Sthalekar Golikeri

Arthur Francis Crotty

Paul Komar

Vaughn Theodore Rokosz

Aaron Michael Cohen

Sreedhar Rella

Sally Ann Hehir

Lu Liang

Lee J Reamsnyder

Zhi Qiang Sun

Shaun Ruske

Bruce R Katz

Monica Luke

Kimberly A Frederick

Phyllis A Smith

Software lifecycle management includes, searching, using a processor, historical development data including prior development tasks for a software system. The searching is performed according to a current development task for the software system. A determination is made as to whether the current development task has an affinity with a selected prior development task implemented within the software system. A recommendation is provided for the current development task based upon the selected prior development task.

Affinity recommendation in software lifecycle management

Software development data indicative of a development activity is accessed. A component parameter of a component of a software development platform is set, in which the component parameter is based upon, at least in part, an anticipated component workload associated with the development actively. At least one system resource is allocated for the component of the software development platform based upon, at least in part, the component parameter.

Resource allocation for software development

A first signature log generated by a first processing system is received, the first signature log including a first listing of at least a recorded series of user inputs received by a computer program. The first listing of the recorded series of user inputs can be compared to at least one historical log indicating at least one historical path, each historical path including at least second listing of a series of historical user inputs that corresponds to a historical endpoint in the computer program. The at least one historical path to which the recorded series of user inputs at least partially corresponds and a deviation between the signature log and the historical log can be identified. Based on a predicted endpoint, a predicted path corresponding to the predicted endpoint can be selected, and the predicted path and the deviation between the signature log and the historical log can be output.

Mapping user actions to historical paths to determine a predicted endpoint

One or more RFID tags may be read. An electronic document associated with the RFID tag may be identified. One or more attributes associated with the electronic document can be identified. One or more workflows can be determined according to the attribute(s).

Rapid access to data oriented workflows

A user inspects at least one indicator of an event. The user enables a token corresponding to an account of an aggregating entity to be received by a transaction entity and identifies at least one type of event of interest to be reported by the transaction entity to the aggregating entity. The user obtains and inspects at least one indicator from the account of the aggregating entity, where each obtained indicator is adapted to be created by the aggregating entity based upon an event message received from the transaction entity. The event message comprises the token, which is adapted to be used by the aggregating entity to identify the account and the event message corresponds to an occurrence of an event of at least one type of event of interest to be reported by the transaction entity to the aggregating entity.

Inspecting event indicators

A first signature log generated by a first processing system is received. A first listing of the recorded series of user inputs included in the signature log is compared to at least one historical log indicating at least one historical path, each historical path including at least second listing of a series of historical user inputs that corresponds to a historical endpoint in the computer program. Responsive to comparing the first listing of the recorded series of user inputs to the at least one historical log, the historical path to which the recorded series of user inputs at least partially corresponds is identified and the at least one historical endpoint is identified as a predicted endpoint in the computer program. Based on the predicted endpoint, a predicted path corresponding to the predicted endpoint in the computer program is selected and output.

A system that generates display objects in a graphical user interface that enable the user of an application which accesses a data repository through result sets to dynamically construct a new query to show all database records having the same contents as a specified set of fields in a currently active database record. Display objects are further generated that enable the user to specify how the contents of the selected fields are to be matched (e.g. exact matching, inclusion, etc.) and/or logical relationships between specified field contents (e.g. Boolean operators such as AND, OR, NOT, etc.). In one embodiment, once a query is defined in this way, it is stored, for example in the user's profile, so that the user can access it across uses of the application.

Dynamically creating queries to find related records in a database

For each of a plurality of the work items, at least a first parameter to be associated with the work item can be received and associated with the work item. Each of the plurality of work items can be compiled in a work item list. In response to receiving a request to present the work item list to the user, the work item list can be filtered, via a processor, based on the first parameter and at least a second parameter associated with the user that corresponds to the first parameter. The filtered work item list can be presented to the user.

Presenting a filtered list of work items

A state transition model is dynamically generated for an active application. A graphical user interface is generated based upon, at least in part, the state transition model for the active application. The graphical user interface includes an indication of a current state of a record within the active application. The record is manipulated within the active application in response to an input received in association with the graphical user interface.

Growing community of inventors

Harvard, MA, United States of America

Brian C Schimpf