Abstract: Certain example embodiments tie the business process governance and Service Oriented Architecture (SOA) governance processes together through the use of Business Process Model and Notation (BPMN) and Event Driven Architecture (EDA) based messaging. That is, in certain example embodiments, a BPMN agent integrated into a SOA registry and publish/subscribe agents deployed to the SOA registry and a business process engine are used to bring the business and SOA governances together through an EDA that helps generate relevant messages from a BPMN model representing the various governance mechanisms. Advantageously, a Complex Event Processing (CEP) engine and business analytics modules may provide monitoring and feedback to both parts of the overall architecture.

Abstract: Compressive imaging apparatus employing multiple modulators in various optical schemes to generate the modulation patterns before the signal is recorded at a detector. The compressive imaging apparatus is equally valid when applying compressive imaging to structured light embodiments where the placement is shifted from the acquisition path between the subject and the detector into the illumination path between the source and the subject to be imaged.

Abstract: Certain example embodiments relate to application intelligence gathering systems and/or methods, e.g., in connection with Event Driven Applications and/or the like. More particularly, certain example embodiments relate to the effective recording of application evolution and usage information for usage learning and/or event auditing purposes. With respect to usage learning, certain example embodiments may help to capture data on the usage patterns and/or apply learning algorithms that work on the captured data to provide required intelligence to the application. With respect to event auditing, certain example embodiments may help to identify the “who”, “what”, “when”, “where”, “how”, and/or “why” of particular operations. Application intelligence optionally may be used in determining application “hotspots” or commonly used features that could help in areas such as application maintenance, performance tuning, and/or the like.

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: Compressive imaging apparatus employing multiple modulators in various optical schemes to generate the modulation patterns before the signal is recorded at a detector. The compressive imaging apparatus is equally valid when applying compressive imaging to structured light embodiments where the placement is shifted from the acquisition path between the subject and the detector into the illumination path between the source and the subject to be imaged.

Abstract: Certain exemplary embodiments relate to a method for integrating at least one Open Services Gateway initiative (OSGi) environment into a Service-oriented Architecture (SOA). The OSGi environment includes at least one OSGi object, and the SOA includes a SOA registry. The method includes publishing the at least one OSGi object to the SOA registry. The publishing includes creating an SOA object in the SOA registry corresponding to the at least one OSGi object. The SOA object includes information reflecting at least one relationship of the at least one OSGi object to at least one further OSGi object within the OSGi environment.

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 relate to computer-implemented methods enabling the enforcement of design-time policies during runtime in a service-oriented architecture (SOA). The SOA includes SOA assets (e.g., web services), and at least one runtime container configured to enforce runtime policies on SOA assets executed therein. Example methods may include: obtaining at least one design-time policy from a SOA registry, the at least one design-time policy applying to SOA assets grouped into a design-time domain; automatically deriving at least one runtime policy from the at least one design-time policy and at least one runtime domain from the design-time domain, the runtime domain indicating at least one runtime container; performing a compatibility check to determine whether the at least one runtime policy is enforceable by the at least one runtime container; and depending on the compatibility check, automatically deploying the at least one runtime policy to the runtime container.

Abstract: A golf club may include a control unit that detects a swing of the golf club and generates a signal based on at least one goal swing parameter during the swing of the golf club. The golf club may include a stimulation generation module, configured to generate a stimulation in response to the signal.

Abstract: Compressive imaging apparatus employing multiple modulators in various optical schemes to generate the modulation patterns before the signal is recorded at a detector. The compressive imaging apparatus is equally valid when applying compressive imaging to structured light embodiments where the placement is shifted from the acquisition path between the subject and the detector into the illumination path between the source and the subject to be imaged.

Abstract: Certain example embodiments relate to systems and/or methods for determining and/or executing an appropriate subset of tests in response to a code change. In certain example embodiments, hash digests or other unique values for code structures (such as, for example, classes, methods, and/or other structural elements) may be created. Tests associated those associated code structures may be identified. New hash digests or other unique values may be generated for the code structures after the source code has been modified. In response to a mismatch as between the existing and new hash digests or other unique values, a list of associated tests for possible subsequent execution may be retrieved. Certain example embodiments additionally or alternatively provide an incremental but consistent way of analyzing performance issues, e.g., in connection with a profiler.

Abstract: Certain example embodiments relate to application intelligence gathering systems and/or methods, e.g., in connection with Event Driven Applications and/or the like. More particularly, certain example embodiments relate to the effective recording of application evolution and usage information for usage learning and/or event auditing purposes. With respect to usage learning, certain example embodiments may help to capture data on the usage patterns and/or apply learning algorithms that work on the captured data to provide required intelligence to the application. With respect to event auditing, certain example embodiments may help to identify the “who”, “what”, “when”, “where”, “how”, and/or “why” of particular operations. Application intelligence optionally may be used in determining application “hotspots” or commonly used features that could help in areas such as application maintenance, performance tuning, and/or the like.

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 tie the business process governance and Service Oriented Architecture (SOA) governance processes together through the use of Business Process Model and Notation (BPMN) and Event Driven Architecture (EDA) based messaging. That is, in certain example embodiments, a BPMN agent integrated into a SOA registry and publish/subscribe agents deployed to the SOA registry and a business process engine are used to bring the business and SOA governances together through an EDA that helps generate relevant messages from a BPMN model representing the various governance mechanisms. Advantageously, a Complex Event Processing (CEP) engine and business analytics modules may provide monitoring and feedback to both parts of the overall architecture.

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.

Abstract: Certain example embodiments relate to computer-implemented methods enabling the enforcement of design-time policies during runtime in a service-oriented architecture (SOA). The SOA includes SOA assets (e.g., web services), and at least one runtime container configured to enforce runtime policies on SOA assets executed therein. Example methods may include: obtaining at least one design-time policy from a SOA registry, the at least one design-time policy applying to SOA assets grouped into a design-time domain; automatically deriving at least one runtime policy from the at least one design-time policy and at least one runtime domain from the design-time domain, the runtime domain indicating at least one runtime container; performing a compatibility check to determine whether the at least one runtime policy is enforceable by the at least one runtime container; and depending on the compatibility check, automatically deploying the at least one runtime policy to the runtime container.

Abstract: Certain example embodiments relate to systems and/or methods for determining and/or executing an appropriate subset of tests in response to a code change. In certain example embodiments, hash digests or other unique values for code structures (such as, for example, classes, methods, and/or other structural elements) may be created. Tests associated those associated code structures may be identified. New hash digests or other unique values may be generated for the code structures after the source code has been modified. In response to a mismatch as between the existing and new hash digests or other unique values, a list of associated tests for possible subsequent execution may be retrieved. Certain example embodiments additionally or alternatively provide an incremental but consistent way of analyzing performance issues, e.g., in connection with a profiler.