International Business Machines Corporation

Daniel V Oppenheim

Krishna Chaitanya Ratakonda

Jarir Kamel Chaar

Thomas A Jobson, Jr

Joseph P Huchel

Yi-Min Chee

Fausto Bernardini

Steven R Abrams

Donald Philip Pazel

James L Wright

Feng Liu

Qian Ma

Saeed Reza Bagheri

Biplav Srivastava

Nianjun Zhou

Raman Harishankar

Ru Fang

Zhi Le Zou

Ramana V Polavarapu

Al A Hamid

Matthew J Callery

Robert D Dill

Lauretta Jones

Rohit M Lotikar

A metadata management system and method enables complex query searches by users, e.g., different users having different query needs, using the same infrastructure. For querying metadata, the metadata management system provides functionality for aggregating all the concepts (metadata items) and relationships of the metadata across one or more users in a common format; extracting concepts and storing them in a metadata store (e.g., a relational database); extracting relationships and modeling them in a standard semantic representation. The system and method further records users' different needs on relationships into user-specific configuration files. The system is configured for retrieving, in response to a user query, relevant data items by using the meta-data selectively. In one embodiment, a selection of meta-data used in the retrieving is determined according to captured context information.

System and method to customize metadata for different users running on the same infrastructure

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

A method for managing projects in a software factory is presented. A project management tool includes an end-to-end project plan for a project to create a software product by using a software factory in a global delivery network. A status block is appended to a work packet that is utilized when executing the project. After initiating the project, an alert is automatically triggered whenever the execution status of the work packet changes. The alert is transmitted to the project management tool to update a project schedule for the project, such that a completion status of the end-to-end project plan reflects a status of a project schedule for the project described by the end-to-end project plan.

Work packet enabled active project management schedule

A method, system, and computer-readable medium for staged validation of work packets within a software factory are presented. In one embodiment, the method includes creating a preliminary work packet. A validation constraint is appended to the preliminary work packet to create a constrained work packet. The constrained work packet is submitted to the software factory, within which the validation constraint is validated at different stages to confirm that the validation constraint is proper for the constrained work packet. If a validation result fails to meet all requirements of the validation constraint at each stage, the validation constraint is resolved, and the constrained work packet is re-submitted at that stage.

Staged automated validation of work packets inputs and deliverables in a software factory

A method, system and computer program product is disclosed for supporting role-based access control in a collaborative environment, wherein pluralities of users work together in a collaborative process using a software system. The method comprises componentizing the software system into a multitude of software components, and limiting access to specific software components to certain users based on roles assigned to the users as defined by a run-time state of the collaborative process. The set of components that a user can access is dynamic, that set can change based on the 'context' or the step where the user is in a collaborative workflow/process. Thus, in comparison with traditional access control mechanisms, an embodiment of the invention combines three different elements: a) the set of components that comprise the application is partitioned in such a way as to make componentized role-based access control feasible, b) a method for specifying inter-component dependencies to enable role-based groups, and c) enabling the modification of the access privileges based on contextual information from a collaborative process.

Supporting role-based access control in component-based software systems

A method, system, and computer-readable medium for determining competence levels of factory teams are presented. In a preferred embodiment, the method includes the steps of: creating a template for an initial work packet, wherein the initial work packet is a self-contained work unit that is assembled within the software factory; creating a partially instantiated work packet by populating the template with details that describe pre-conditions and post-conditions necessary to execute the work packet; provisionally selecting a human team to complete coding of the partially instantiated work packet to create a final work packet; determining whether the human team is competent to create the final work packet; and in response to determining that the human team is competent to create the final work packet, ordering the human team to create the final work packet within the software factory.

Determining competence levels of teams working within a software

A method, system and computer-readable medium for utilizing the design centers, assembly line and job shops of a global delivery network across multiple software factories are presented. Pre-qualified factory organizational units in a software factory are identified. Identified qualified factory organizational units, including design centers, assembly lines and job shops, are matched to customer requirements. If the identified qualified factory organizational units are available, then they are load balanced and deployed to create software deliverables to the customer.

Configuring design centers, assembly lines and job shops of a global delivery network into 'on demand' factories

A method, system, and computer-readable medium for maintaining a project schedule of projects being executed within a software factory are presented. A project management tool receives alerts from the software factory as completion statuses, of software packets being used within the software factory, change. These alerts enable a consolidated and coordinated updating of the project schedule.

Work packet enabled active project schedule maintenance

A method, system, and computer-readable medium for utilizing the design centers, assembly line and job shops of a global delivery network across multiple software factories are presented. A work packet is examined to determine if it is authorized to be sub-contracted out to a different design center, assembly line or job shop than the design center/assembly line/job shop that have primary responsibility for the work packet. If the work packet is authorized to be sub-contracted out, then the work packet is reassigned to a different pre-qualified design center/assembly line/job shop.

Work packet delegation in a software factory

Each work item from a group of work items is categorized as either complex or intense, and a unique work requirement statement is derived for each work item based on whether it is complex or intense. A unique resource value statement is assigned to different human resources. Past performances of the human resources are analyzed against completed work items in order to adjust the unique resource value statement, thus creating updated human resource value statements. An optimized work requirement statement is created by recalculating the unique work requirement statement for each work item based on the updated human resource value statements. A schedule for automated allocation of human resources to functional areas of an enterprise activity environment and scheduling of work items to the functional areas is formulated based on the optimized requirement statement for each work item in the group of work items.

Scheduling resources from a multi-skill multi-level human resource pool

A method and system for analyzing capabilities of an entity includes inputting data regarding an entity's capabilities, and using a capability model to detect a capability pattern among the capabilities and generate an action plan based on the capability pattern.

Method and system for analyzing capabilities of an entity

A method, system, and computer-readable medium for identifying root causes of problems in a software factory. Each work packet being executed within the software factory is assigned meta-data, which describes a relationship between that work packet and other work packets, as well as a relationship between that work packet and resources within the software factory. These metrics provides means for identifying any problems within the software factory.

Application/service event root cause traceability causal and impact analyzer

Work packets are assembled, within a software factory, into a customized deliverable unit of software by software factory components that have been rated as being the most suitable according to requirements set by the customer. The work packets comprise exit criteria for returning the work packets and the customized deliverable unit from an assembly line to a software factory operations unit in the software factory.

Management of work packets in a software factory

A method, system, and computer-readable medium for self-healing a software factory are presented. Factory metrics that describe resources and operations within the software factory are collected and analyzed. If the analysis reveals a significant problem within the software factory, then corrective measures are taken and stored, thus enabling the software factory to evolve and improve over time.

Growing community of inventors

Croton on Hudson, NY, United States of America

Daniel V Oppenheim