Abstract: Provided are systems and methods for visualizing spatio-temporal data of a user location. In one example, the method may include receiving spatio-temporal movement information of a first user device associated with a first user, and receiving spatio-temporal movement information of a second user device associated with a second user, identifying a point in time when the first user and the second user could have met based on the received spatio-temporal movement information of the first and second user devices, outputting, via a user interface, a first timeline indicating movement of the first user device over time and a second timeline indicating movement of the second user device over time, and displaying a visual indicator with respect to the first and second timelines indicating the identified point in time when the first and second users could have met.

Abstract: Provided are systems and methods for visualizing spatio-temporal data of a user location. In one example, the method may include receiving spatio-temporal movement information of a first user device associated with a first user, and receiving spatio-temporal movement information of a second user device associated with a second user, identifying a point in time when the first user and the second user could have met based on the received spatio-temporal movement information of the first and second user devices, outputting, via a user interface, a first timeline indicating movement of the first user device over time and a second timeline indicating movement of the second user device over time, and displaying a visual indicator with respect to the first and second timelines indicating the identified point in time when the first and second users could have met.

Abstract: Provided are systems and methods for visualizing spatio-temporal data of a user location. In one example, the method may include receiving spatio-temporal movement information of a first user device associated with a first user, and receiving spatio-temporal movement information of a second user device associated with a second user, identifying a point in time when the first user and the second user could have met based on the received spatio-temporal movement information of the first and second user devices, outputting, via a user interface, a first timeline indicating movement of the first user device over time and a second timeline indicating movement of the second user device over time, and displaying a visual indicator with respect to the first and second timelines indicating the identified point in time when the first and second users could have met.

Abstract: Location information for a plurality of target subjects can be depicted as a plurality of routes with indications of respective contemporaneous locations of the target subjects at a point in time. A graphical slider can be used to update the visualization to depict contemporaneous locations of the target subjects at a different point in time. A point on one of the routes can be activated to update the visualization to depict contemporaneous locations of the target subjects at a different point in time. Metrics for characteristics of the location data can be displayed proximate the slider. Other features provide a user interface that allows for a rich set of visualization functionality.

Abstract: A system, a method, and a computer program product for automatic detection of semantics are disclosed. A user interface containing a first element and a second element in a plurality of elements is generated. At least one semantic relationship is defined between the first element and the second element. An action on the first element is performed based on an action performed on the second element using the semantic relationship.

Abstract: A current use context can be extracted based on concrete data related to a currently displayed user interface feature in a business software architecture user interface environment. Relevant related business objects and transactional data for concrete instances of a process or scenario relevant to the current use context can be identified and a specific business object instance can be determined from a plurality of business object instances related to a specific current instance of the process or scenario relevant to the current use context. At least one target user interface feature associated with the process or scenario can be pre-populated with at least one parameter specific to a current data entry state of the specific current instance of the process or scenario and displayed via a user interface.

Abstract: A business scenario landscape map can show a scenario-centric view of a business scenario landscape that includes business scenarios accessible to members of an organization and supported by a business software architecture. In the scenario-centric view, first user interface elements can be arranged to show a linear representation of business process features of a selected business scenario and a visual depiction of relationships between the selected business scenario and other business scenarios.

Abstract: A definition of a new user interface feature of a business software architecture supporting a business configuration used by an organization can be received and a rule in a scenario model of a business scenario can be accordingly modified to associate the new user interface feature with business process feature(s) of the business scenario. A selection of a business process feature received as a user interaction with first user interface elements arranged in a linear order in a navigation pane of a user interface to represent at least some of the plurality of business process features of the business process can result in the concurrent display via the user interface of a work frame comprising the new user interface feature.

Abstract: A single meta-model can include metadata defining a business scenario landscape that includes business scenarios accessible to members of an organization that are supported by a business software architecture. The metadata can include business process definitions and relationships between business processes. A user interface can present first, second, and/or third visualization layers based on the metadata. The first visualization layer can include first user interface elements forming a business scenario landscape map showing business scenarios and at least one relationship between the business scenarios. The second visualization layer can include second user interface elements displayed in a navigation pane concurrently with a work pane.

Abstract: Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature.

Abstract: DSEI (dynamic service extension infrastructure) enables registration of an extension application as a service, storage of application files and development resources, runtime access to runtime artifacts, generic data persistency, Web enablement of application maintenance and persistence access, and so on. An integrated development environment that supports file access may be used for the creation of application service. DSEI provides a WebDAV folder for each extension application, so that the user may work on the application files and resources. Application services may be built with standard Web technologies. It is possible without knowing the technical infrastructure of a cloud application in the cloud platform, to extend the cloud application by creating application services or to enhance existing application services.

Abstract: A business scenario landscape map can show a scenario-centric view of a business scenario landscape that includes business scenarios accessible to members of an organization and supported by a business software architecture. In the scenario-centric view, first user interface elements can be arranged to show a linear representation of business process features of a selected business scenario and a visual depiction of relationships between the selected business scenario and other business scenarios.

Abstract: External transactional data relating to a completion status of an external business process feature of a specific business scenario instance supported by a business software architecture can be received and persisted at a repository. The business scenario can include business process features that include the external business process feature, which can be unsupported by a core software platform of the architecture. Navigation and work panes can be concurrently displayed to include first user interface elements arranged in a linear progression to represent the business process features in the linear sequence and second user interface elements corresponding to functionality related to a currently selected one of the plurality of business process features, respectively.

Abstract: A single meta-model can include metadata defining a business scenario landscape that includes business scenarios accessible to members of an organization that are supported by a business software architecture. The metadata can include business process definitions and relationships between business processes. A user interface can present first, second, and/or third visualization layers based on the metadata. The first visualization layer can include first user interface elements forming a business scenario landscape map showing business scenarios and at least one relationship between the business scenarios. The second visualization layer can include second user interface elements displayed in a navigation pane concurrently with a work pane.

Abstract: A selection by a user of a first business process feature defining a starting point and a second business process feature defining an end point of a requested key performance indicator calculation can be received and a set of business objects related to a plurality of business process features that impact calculation of the requested key performance indicator can be determined based on the start point and the end point and on a meta-model of each of the related business process features. An algorithm for making the requested key performance indicator calculation can be generated based on metadata from retrieved from the meta-models, and transaction data can be retrieved from instances of business objects matching limiting criteria. A value for the requested key performance indicator calculation can be calculated based on the algorithm and the retrieved transaction data.

Abstract: A current use context can be extracted based on concrete data related to a currently displayed user interface feature in a business software architecture user interface environment. Relevant related business objects and transactional data for concrete instances of a process or scenario relevant to the current use context can be identified and a specific business object instance can be determined from a plurality of business object instances related to a specific current instance of the process or scenario relevant to the current use context. At least one target user interface feature associated with the process or scenario can be pre-populated with at least one parameter specific to a current data entry state of the specific current instance of the process or scenario and displayed via a user interface.

Abstract: A single meta-model can include metadata defining a business scenario landscape that includes business scenarios accessible to members of an organization that are supported by a business software architecture. The metadata can include business process definitions and relationships between business processes. A user interface can present first, second, and/or third visualization layers based on the metadata. The first visualization layer can include first user interface elements forming a business scenario landscape map showing business scenarios and at least one relationship between the business scenarios. The second visualization layer can include second user interface elements displayed in a navigation pane concurrently with a work pane.

Abstract: A user interface can concurrently display a work frame including business configuration user interface elements relating to a selected business process feature of a business scenario and a navigation frame including first user interface elements arranged within the navigation frame to represent at least some of a plurality of business process features of the business scenario. The business scenario can be part of a business configuration of a business software architecture used by an organization. A user input relating to a change to the business configuration can be received via the business configuration user interface elements, and a business configuration model storing the business configuration can be updated to reflect the received change.

Abstract: Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature.

Abstract: A definition of a new user interface feature of a business software architecture supporting a business configuration used by an organization can be received and a rule in a scenario model of a business scenario can be accordingly modified to associate the new user interface feature with business process feature(s) of the business scenario. A selection of a business process feature received as a user interaction with first user interface elements arranged in a linear order in a navigation pane of a user interface to represent at least some of the plurality of business process features of the business process can result in the concurrent display via the user interface of a work frame comprising the new user interface feature.