Methods and systems consistent with the present invention provide a data processing system having a business object model reflecting the data used during a business transaction. Consistent interfaces are generated from the business object model. These interfaces are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.

Consistent set of interfaces derived from a business object model

Computer-implemented systems and methods are disclosed for providing a tagging interface for tagging external content In accordance with some embodiments, a method is provided for tagging content external to a database system The method comprises accessing the external content via a web browser of an electronic device The method also comprises enhancing the web browser by providing a tagging interface for tagging at least a portion of the external content The method further comprises receiving created tag associated with a tagged portion of the external document content, and exporting the external content and the received tag to the database system The tagging interface can also provide an option to export the created tag to an internal database system

Systems and methods for providing a tagging interface for external content

Managing consistent interfaces for business objects across heterogeneous systems

Methods and apparatus, including computer program products, to realize a software model are described. Process components are defined that characterize software implementing respective and distinct business processes and additionally define at least one process agent that enables communications between a business object associated with the corresponding process component and a business object associated with any other process component. Business Process Variant Types are also defined that associate one or more of the process agents for the corresponding process component so that selection of a process variant type causes the associated one or more process agents to be activated.

Software model business process variant types

Techniques for visual data import into an object model are described. A graphical user interface concurrently displays a first icon that represents a first object type and a second icon that represents a second object type. Input defining object-to-data mappings between properties of the object types and structured data of one or more data sources is received. Further input defining a relationship type for relationships between the first object type and the second object type is also received. In response to the second input, a graphical representation of the relationship type is displayed, visually linking the first icon to the second icon. Based at least on the object-to-data mappings, the definition of the relationship type, and the structured data, an object model is created, comprising first objects of the first object type, second objects of the second object type, and relationships between the first objects and the second objects.

Visual data importer

Methods and apparatus, including computer program products, to realize a business scenario are described. A plurality of process components and context independent interactions among the process components are defined. Each of the process components characterizes software implementing a respective and distinct process. In addition, each of the process components defines at least one respective service interface for interacting with business objects associated with other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components.

Software model integration scenarios

Methods and apparatus, including computer program products, for forming deployment units. Groups of process components, each group characterizing software that is independently operable, are identified. Thereafter, a plurality of deployment units, each deployment unit associated with at least one identified group of process components are formed. Each process component is entirely included in exactly one deployment unit. In addition, each of the process components characterizes software implementing a respective and distinct business process, and each of the process components defines at least one respective service interface for interacting with other process components, wherein all communication and interaction between process components takes place through the respective interfaces of the process components.

Software model deployment units

Methods and apparatus, including computer program products, for defining one of a plurality of process components. At least one inbound operation initiated by an external process component to read or modify data encapsulated in a business object solely associated with the process component is defined. Additionally at least one outbound operation to read or modify data encapsulated in a business object solely associated with an external process component is defined. Each of the process components characterizes software implementing a respective and distinct process, and each of the process components defines a respective at least one service interface for communicating and interacting with other process components. In addition, all communication and interaction between process components takes place through the respective interfaces of the process components.

Software model process component

Methods and apparatus, including computer program products, to realize a software model are described. A user-centric modeling component is defined, the user-centric modeling component modeling an interactive software system and including a plurality of process steps, the plurality of process steps defining a business scenario. For each process step in the plurality of process steps one or more service requirements are identified, where a service requirement represents functionality necessary to accomplish a step. For each service requirement a process component capable of providing the service requirement is identified, the process component modeling software implementing a business process and defining a service operation for providing the service requirement and for interacting with other process components.

Jens Freund

Papers

Software model business process variant types

Software model integration scenarios

Software model deployment units

Software model process component

Composite application modeling