International Business Machines Corporation

Jarir Kamel Chaar

Krishna Chaitanya Ratakonda

Thomas A Jobson, Jr

Joseph P Huchel

Daniel V Oppenheim

Yi-Min Chee

Naomi Meiko Mitsumori

Ronald D Finlayson

Dimitri Kanevsky

Francis Xavier Reddington

Saeed Reza Bagheri

Fausto Bernardini

Alexander Zlatsin

Clifford A Pickover

Nianjun Zhou

Bikram Sengupta

Shivali Agarwal

Ran D Zilca

Dinesh C Verma

Ramani Ranjan Routray

Robert G Farrell

Mahesh Viswanathan

David Frederick Bantz

Neal Martin Keller

Bernhard Julius Klingenberg

Robert Michael Rees

Sharon Mary Trewin

Rong Nickle Chang

Kiyoshi Maruyama

David Alson George

Roberto Sicconi

John C Hartley

Radha P Ratnaparkhi

Carmen P Allen

Edith H Stern

Charles Steven Lingafelt

Robert William Wisniewski

Juhnyoung Lee

Feng Liu

Christopher Ward

Raman Harishankar

Brent Tzion Hailpern

Melissa J Buco

Laura Zaihua Luan

Jean A Lorrain

Guerney Douglass Holloway Hunt

Santanu Paul

Ali ParandehGheibi

Vinay Kumar Reddy

Shun Shing Chan

Juan P Giraldo

Al A Hamid

Vincent J Cina, Jr

Rosemarie M Gratz

Thomas Jobson

William R Cope, Jr

Per J Kroll

Gaston Robert Williams

Steven R Lang

Hari Rajagopal

Terri A Vines

Mark Mei

Miram Zohar

Edwin S Park

A backup and archival policy method, system, and non-transitory computer readable medium, includes performing correlation analytics to determine identification of a backup policy aligned with a criticality of operational data and backup data including identifying low value backup data having a value less than a predetermined low value threshold, creating a one-time archival of the operational data and the backup data including the low value backup data, and removing the low value backup data from a future data protection policy.

System, method, and recording medium for alignment of backup and archival policy

A backup and archival policy method, system, and non-transitory computer readable medium, includes harnessing of metrics of data classification including both operational data and backup data from an end-to-end stack from a backup Information Lifecycle Governance (ILM) viewpoint.

A device receives a first input for authenticating a user and determines the first input fails to authenticate the user. One or more errors are identified in the input which match a tremor pattern for the user and the one or more errors are corrected to generate a corrected input. The user is authenticated using the corrected input.

Authentication of users with tremors

A method of managing instant messaging communication over a computer network is provided. One or more instant messaging session windows are organized in an instant messaging session manager. At least one distinguishing session characteristic is attributed to each of the one or more instant messaging session windows. The at least one distinguishing session characteristic is at least one of a sound clip associated with a user of the session, an instant messaging session window background associated with a user of the session, and a change in at least one of a color and an intensity of the instant messaging session window. The at least one distinguishing session characteristic increases a likelihood of identification of each of the one or more instant messaging session windows.

Methods and apparatus for managing and distinguishing instant messaging sessions and threads

An adaptive system enables providers to customize educational objects and support services to maximize user engagement. The system is a self-service system for education for providers that includes a learning environment with interfaces for stakeholders, metrics for measuring the level of user engagement, and a customizable service configured to maximize user engagement. The system may operate in many domains, such as higher education, retail, government, test preparation and certification services, negotiations, and others.

Self-service system for education

A method, system, and computer-readable medium for managing a work packet's life cycle, wherein the work packet is assembled in a software factory that creates custom software in a standardized manner, are presented. In one embodiment, the computer-implemented method comprises: defining a work packet to perform a sub-function of a custom software, wherein the work packet is a pre-stored, reusable, self-contained, discrete unit of software code; assembling the work packet; archiving the work packet in an asset repository; retrieving the work packet from the asset repository; and sending the work packet to an assembly line for consolidation with other work packets to create a custom software.

Life cycle of a work packet in a software factory

A computer-implemented method, system, and computer-readable medium for determining if a software factory is ready to take on a software project is presented. In a preferred embodiment, the computer-implemented method includes the steps of: determining if an infrastructure for a software factory has been procured; determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed; determining if a workflow event model for an assembly line in the software factory has been configured; determining if workload in the assembly line has been balanced; determining if communication channels between the software factory and a customer's computer system have been defined and cleared for data transmission; and in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory.

Software factory readiness review

A method, system, and computer-readable medium for maintaining a health of a software factory that creates custom software in a standardized manner is presented. In a preferred embodiment, the method includes the steps of: defining work packets to perform sub-functions of a custom software; tracking a transmission of the work packets to an assembly line in a software factory; monitoring any retrieval of software artifacts that are used to create the work packets; monitoring any on-going changes of work activities that are contained in the work packets; determining if execution of the work packets conforms to governance guidelines for the software factory; monitoring the software factory to ensure that the work packets comply with an architecture of the software factory; tracking quality metrics for an execution of the work packets in an assembly line in the software factory; and transmitting all tracked and monitored information to a dashboard.

Software factory health monitoring

A computer implemented method, system and/or computer program product schedules execution of work requests through work plan prioritization. One or more work packets are mapped to and assigned to each work request from a group of work requests. A complexity level is derived for and assigned to each work packet, and priority levels of various work requests are determined for each entity from a group of entities. A global priority for the group of work requests is then determined. The global priority and the complexity levels combine to create a priority function, which is used to schedule execution of the work requests.

Work plan prioritization for application development and maintenance using pooled resources in a factory

A computer-implemented method, system, and/or computer program product supports a user who is servicing a work packet request within a software factory. A tooling environment that is necessary to service a work packet request in a software factory is established. The software factory includes an assembly line that executes work packets to create the deliverable software, and a published set of services that describes what assembly services for assembling the work packets are offered by the assembly line. A full work packet-aware Integrated Development Environment (IDE) that is specific for a work packet identified by the work packet request is created. The full work packet-aware IDE and an associated Graphical User Interface (GUI) are transmitted to a user who has been assigned to service the work packet request, thus allowing resources depicted in the GUI to be interactively supplied to that user.

Supporting a work packet request with a specifically tailored IDE

Techniques are presented for managing execution of processes on a data processing system The data processing system comprises process instances that are each an execution of a corresponding process. Each process instance comprises activity instances. Business impacts are determined for the process instances, the activity instances, or both. Order of execution of the activity instances is managed by allocating resources to activity instances in order to achieve an objective defined in terms of the business impacts. In another embodiment, requests are received for the execution of the processes. For a given request, one or more of the operations of assigning, updating, aggregating, and weighting of first business impacts associated with the given request are performed to create second business impacts associated with the given request. Additionally, requests can be modified. Modification can include changing the process requested or process input as deemed appropriate, combining related requests into a single request, or both. Unmodified requests and any modified requests are managed.

Execution order management of multiple processes on a data processing system by assigning constrained resources to the processes based on resource requirements and business impacts

A computer implemented method, system and/or computer program product optimizes a service delivery system. A processor receives a first set of inputs that describes a current state of a service delivery system and a second set of inputs that describes a cost overhead for the service delivery system. The processor then optimizes the service delivery system in order to derive an optimized service delivery system.

Optimizing service delivery systems

A method, system, and/or computer-readable medium analyzes problems in a software factory. Factory metrics that describe resources and operations within the software factory are collected and analyzed to detect problems that might have occurred during an execution of a work packet within the software factory. If the detected problems exceed one or more threshold criteria, then a detailed analysis of the detected problems is performed by matching each detected problem to one or more specific root causes through an analysis of the factory process building blocks.

Analyzing factory processes in a software factory

A computer implemented method, system, and/or computer program product modifies a master template for an executable document. A version architecture comprises a master template for a master document, a new variation document that describes what changes are to be made to the master template for a specific context, and a resulting modified template based on the master template and rule-based instructions found in the new variation document. A processor defines an executable master document from the master template that, when executed, produces a final product. Specific rules set out conditions for modifying the master template for the specific context. These specific rules are used to define a new variation document, which is applied against the master template to generate a context-specific modified template. The context-specific modified template is then used to generate a context-specific executable document that, when executed, generates a final context-specific product.

Management of template versions

Growing community of inventors

Tarrytown, NY, United States of America

Jarir Kamel Chaar