Software Ag, Inc.

Thorsten Fiebig

Gary Woods

Daniel Adelhardt

Juliane Harbarth

Heiko Weber

Jürgen Harbarth

Kay Hans-Peter Winkler

Gunther Rademacher

Daniel Adelhart

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.

System and method for controlling the development of a software application

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.

Lifecycle management system with conditional approvals and corresponding method

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.

Method and system for propagating modification operations in service-oriented architecture

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:

Method and registry for enabling the enforcement of design-time policies during runtime in a service-oriented architecture

Executing a XML database query. The method may include compiling the XML database query to provide at least two alternative execution plans, wherein the at least two alternative execution plans provide the same response to the XML database query. The method may further include deciding during runtime, which of the at least two alternative execution plans is executed. The method may include executing the selected execution plan.

Method and database system for executing a XML database query

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.

Systems and/or methods for intelligently detecting API key domains

A method of pre-processing an XQuery on a XML data base and may comprise parsing the XQuery to obtain an abstract syntax tree and typing the abstract syntax tree to provide at least one pointer into a schema for XML documents of the XML data base. The typing step may involve the use of schema and accumulated instance data of the XML data base. Use of the accumulated instance data in addition to schema data allows for reduction of the set of pointers to a smaller set, which in turn reduces the number of documents to be examined when the query is executed.

Method and database system for pre-processing an XQuery

The invention concerns a method for generating at least one index () over XML documents () in an XML database (); the method comprising the steps of:

Method and system for generating indexes in an XML database management system

The present invention concerns an XML data base management system (XDBMS,) for an XML database () comprising XML documents (), each XML document () comprising one or more structural elements () and adhering to an XML schema (), wherein at least one of the structural elements () is protected against access of a user (), the XDBMS () comprising:

Growing community of inventors

Mannheim, Germany

Thorsten Fiebig