Abstract: Techniques are provided for versioning and refactoring of mashups. During the design phase of a mashup that is operable to access multiple external services, design information that defines or modifies a plurality of design elements included in the mashup is received from a user. Without receiving from the user any input that causes the plurality of design elements to be versioned, current versions of the plurality of design elements are automatically stored in a repository when the plurality of design elements are saved during development of the mashup. The mashup is deployed to one or more servers. Without receiving any input from the user that causes the mashup to be versioned, deploying the mashup comprises automatically storing in the repository a current version of the mashup and versioning information that associates the current version of the mashup with the current versions of the plurality of design elements.

Abstract: Techniques are provided for designing a mashup. In an example embodiment, a user input is detected. The user input relates a first GUI object, which represents a first widget, to a second GUI object that represents a second widget. The first widget conforms to a first widget specification and the second widget conforms to a second widget specification that is different than the first widget specification. In response to the user input, a variable is defined, where, at run-time, a value of an output parameter of the first widget is assigned to the variable and the variable is used as an input parameter of the second widget. An event definition that defines an event is generated based on the user input, where the event, when detected at run-time, causes contents of at least one of the first widget and the second widget to be refreshed.

Abstract: Techniques are provided for baselining across multiple domains. Relationship information that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A particular requirement object from the collection of requirement objects is determined. Based on the relationship information, one or more configuration management objects that are associated with the particular requirement object are determined. A baseline that includes copies of the one or more configuration management objects is created and stored, where the copies include specific versions of the one or more configuration objects.

Abstract: Techniques are provided for identifying suspect links between objects from multiple domains. A plurality of links that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A determination is made that a particular requirement object was changed. In response to determining that the particular requirement object was changed, one or more links of the plurality of links are automatically determined. The one or more links respectively associate one or more configuration management objects, of the set of configuration management objects, with the particular requirement object. The one or more links are then identified as suspect.

Abstract: Techniques are provided for versioning and refactoring of mashups. During the design phase of a mashup that is operable to access multiple external services, design information that defines or modifies a plurality of design elements included in the mashup is received from a user. Without receiving from the user any input that causes the plurality of design elements to be versioned, current versions of the plurality of design elements are automatically stored in a repository when the plurality of design elements are saved during development of the mashup. The mashup is deployed to one or more servers. Without receiving any input from the user that causes the mashup to be versioned, deploying the mashup comprises automatically storing in the repository a current version of the mashup and versioning information that associates the current version of the mashup with the current versions of the plurality of design elements.

Abstract: Techniques are provided for designing, deploying, and executing mashups that integrate human workflows with automated processes. In an example embodiment, a system for executing mashups comprises a human interaction module, an event manager module, and a process orchestration module. The human interaction module is configured to receive user input while a human workflow included in a mashup is being executed, and to raise an event in response to the user input. The event manager module is configured to: receive the event from the human interaction module; based on the event, identify a particular automated process from one or more automated processes that are included in the mashup; and invoke the process orchestration module to execute the particular automated process based on the event. The process orchestration module is configured to execute the particular automated process in response to being invoked by the event manager module.

Abstract: Techniques are provided for designing a mashup. In an example embodiment, a user input is detected. The user input relates a first GUI object, which represents a first widget, to a second GUI object that represents a second widget. The first widget conforms to a first widget specification and the second widget conforms to a second widget specification that is different than the first widget specification. In response to the user input, a variable is defined, where, at run-time, a value of an output parameter of the first widget is assigned to the variable and the variable is used as an input parameter of the second widget. An event definition that defines an event is generated based on the user input, where the event, when detected at run-time, causes contents of at least one of the first widget and the second widget to be refreshed.

Abstract: Techniques are provided for identifying suspect links between objects from multiple domains. A plurality of links that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A determination is made that a particular requirement object was changed. In response to determining that the particular requirement object was changed, one or more links of the plurality of links are automatically determined. The one or more links respectively associate one or more configuration management objects, of the set of configuration management objects, with the particular requirement object. The one or more links are then identified as suspect.

Abstract: Techniques are provided for baselining across multiple domains. Relationship information that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A particular requirement object from the collection of requirement objects is determined. Based on the relationship information, one or more configuration management objects that are associated with the particular requirement object are determined. A baseline that includes copies of the one or more configuration management objects is created and stored, where the copies include specific versions of the one or more configuration objects.