International Business Machines Corporation

Julia Rubin

Mila Keren

Tali Yatzkar-Haham

Sai Zeng

Alan Hartman

Ioana Boier-Martin

Laurent Balmelli

Man Mohan Singh

Dolev Dotan

Shiri Kremer-Davidson

José Gomes

Tal Haham

Ofir Meir Brukner

Methods and systems are provided for adding variability support for a modeling language. Developers may utilize the added support to transform a model written in a preexisting domain-specific modeling language for product line development in which there is structural and configurational diversity. A variability layer is incorporated into the model, which permits product developers to better use the language to model product line variants.

Variability layer for domain-specific modeling languages

A system that includes: a configuration management system configured to receive resource updates submitted by developers of a product line; an update monitor configured, in manual monitoring, to mark each submitted resource update with respective variability data specified as relevant to the update submission, by the developer; and a tracer configured, in automatic monitoring, to trace portions of the updated resource into respective features or products of the product line, to determine variability data relevant to the update submission, wherein when an update request is initiated by the developer, the configuration management system is configured to associate the submitted resource updates with the update request based on common variability data, to provide resource updates on demand, based on variability data, wherein in automatic update, the configuration management system is configured to notify developers on resource updates, based on variability data common to the updated resource and the notified developers.

Configuration management system for software product line development environment

A method that includes: modeling a software system having pairs of coupled software components to yield a platform-independent model of pairs of respective platform-independent software component models associated with platform-specific software components; applying a materialization process to the platform-independent model to yield a platform-specific model by selecting respective concrete platform specific software components for the software component models; analyzing the platform-specific model to identify mismatched pairs of concrete platform-specific software components; re-modeling the platform-specific model such that each identified mismatched pair becomes coupled together via a configurable glue component model which comprises interface maps usable to eliminate the mismatch; configuring the glue component models by determining, in response to a feedback from a user, code snippets associated with any of the interface maps; and transforming the configured glue component model into a computer code in the platform-specific language by assembling all code snippets into a single piece of code.

Integrating software components in a software system using configurable glue component models

A plurality of artifacts, in a plurality of repositories, are maintained under revision control. A plurality of artifact tuples, in another repository, are maintained under revision control. At least one first artifact tuple comprise first information providing access to at least one of the artifacts. At least one second artifact tuple comprises second information providing access to at least one other artifact tuple. Each of the artifact tuples are associated with at least one of a plurality of product development processes. An apparatus comprises a plurality of repositories, each maintaining under revision control a plurality of artifacts and another repository that maintains under revision control a plurality of artifact tuples. A workflow process is adapted to allow users to associate each of the artifact tuples with at least one of a plurality of product development processes.

Techniques supporting collaborative product development

Growing community of inventors

Haifa, Israel

Julia Rubin