International Business Machines Corporation

Joseph P Huchel

Jarir Kamel Chaar

Thomas A Jobson, Jr

Krishna Chaitanya Ratakonda

Daniel V Oppenheim

Yi-Min Chee

Fausto Bernardini

Raman Harishankar

Al A Hamid

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

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 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-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

A method, system, and computer-readable medium is presented for maintaining and supporting a semantic reconciliation of canonical data model exchange formats in support of software factory workflow management, state determination governing model transformations, and tool enabled processes across software development roles and methodologies used by a software factory.

Software factory semantic reconciliation of data models for work packets

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 aiding a user who is servicing a work packet request in a software factory. A full work packet-aware Integrated Development Environment (IDE) is created and sent to the user. This full work packet-aware IDE provides specifically tailored access to all hardware, software, licenses, normative guidance and other resources that are needed by the user to service the work packet request.

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.

Self-healing factory processes in a software factory

A method, system, and computer-readable medium that support an open marketplace for distributed service arbitrage with an integrated risk management is presented. Orders for work packets, which are processed within a software factory, are allowed to be bid upon only by software factories that have been previously ranked by a centralized marketplace portal, thus ensuring that only qualified software factories are allowed to service such orders.

Growing community of inventors

Morgan Hill, CA, United States of America

Joseph P Huchel