Abstract: Certain example embodiments relate to techniques for controlling the development of a software application. The system includes an event channel for receiving at least one event that indicates an action performed by one of a plurality of existing development tools used in the development of the software application, a policy-based event engine for evaluating the at least one event and for initiating at least one action of one of the plurality of existing development tools in accordance with at least one policy, and a repository, for storing at least one artifact to define an architecture of the software application. The at least one artifact corresponds to a component of the software application and/or to a dependency between a first component and a second component of the software application.

Abstract: Certain example embodiments relate to techniques for controlling the development of a software application. The system includes an event channel for receiving at least one event that indicates an action performed by one of a plurality of existing development tools used in the development of the software application, a policy-based event engine for evaluating the at least one event and for initiating at least one action of one of the plurality of existing development tools in accordance with at least one policy, and a repository, for storing at least one artifact to define an architecture of the software application. The at least one artifact corresponds to a component of the software application and/or to a dependency between a first component and a second component of the software application.

Abstract: Certain example embodiments concern a lifecycle management system for at least one computing component. A lifecycle model, including lifecycle states assignable to the at least one computing component, is defined. The lifecycle states include a production state. The lifecycle management system ensures the at least one computing component can be productively used only if it is assigned the production state. A lifecycle transition request assigning a requested target lifecycle state of the lifecycle model to the at least one computing component is received. A conditional lifecycle state, different from the requested target lifecycle state, is assigned to the at least one computing component. At least one condition to be fulfilled for the at least one computing component to be assigned the requested target lifecycle state is assigned. The requested target lifecycle state is automatically assigned to the at least one computing component when the at least one condition is fulfilled.

Abstract: Certain example embodiments relate to techniques for propagating modification operations for Service-oriented Architecture (SOA) objects in a SOA. The SOA includes at least two SOA objects that are connected by at least one relationship that defines one SOA object as referencing SOA object and another SOA object as referenced SOA object. Steps of an appropriate may include: receiving a request for propagating a modification operation from the referencing SOA object to the referenced SOA object; evaluating at least one propagation rule to determine whether the requested modification can be performed on the referenced SOA object; and if it is determined that the requested modification cannot be performed in accordance with the at least one propagation rule, evaluating at least one approval rule to determine whether the requested modification can be performed on the referenced SOA object.

Abstract: Certain example embodiments concern a lifecycle management system for at least one computing component. A lifecycle model, including lifecycle states assignable to the at least one computing component, is defined. The lifecycle states include a production state. The lifecycle management system ensures the at least one computing component can be productively used only if it is assigned the production state. A lifecycle transition request assigning a requested target lifecycle state of the lifecycle model to the at least one computing component is received. A conditional lifecycle state, different from the requested target lifecycle state, is assigned to the at least one computing component. At least one condition to be fulfilled for the at least one computing component to be assigned the requested target lifecycle state is assigned. The requested target lifecycle state is automatically assigned to the at least one computing component when the at least one condition is fulfilled.

Abstract: Certain example embodiments described herein relate to an application programming interface (API) management system and/or method that automatically detects API domains, e.g., by analyzing consumer registration and runtime data, while also allowing API providers to provide approval for proposed detected domains and/or continued governance. The technology set forth herein not only provides an automatic detection mechanism, but also provides the capability of full management/control, while also allowing API producers to dynamically expand or otherwise modify their API domain offerings based on usage, etc. This dynamic process can be fully or partially automated and is efficient.

Abstract: Certain example embodiments relate to techniques for propagating modification operations for Service-oriented Architecture (SOA) objects in a SOA. The SOA includes at least two SOA objects that are connected by at least one relationship that defines one SOA object as referencing SOA object and another SOA object as referenced SOA object. Steps of an appropriate may include: receiving a request for propagating a modification operation from the referencing SOA object to the referenced SOA object; evaluating at least one propagation rule to determine whether the requested modification can be performed on the referenced SOA object; and if it is determined that the requested modification cannot be performed in accordance with the at least one propagation rule, evaluating at least one approval rule to determine whether the requested modification can be performed on the referenced SOA object.