Abstract: Techniques for configuring a software system include generating a hierarchy of entities representing usage of the software system by a set of users, wherein the hierarchy includes a first set of nodes representing a set of tasks, a second set of nodes representing a set of components that implement the tasks, and a set of edges between the first set of nodes and the second set of nodes. The techniques also include updating the hierarchy based on a first set of configurations for the tasks, wherein the updated hierarchy indicates one or more tasks that have been enabled for the users. The techniques further include determining, based on the updated hierarchy, one or more components that implement the task(s). Finally, the techniques include generating, based on the hierarchy, one or more runbooks that execute the task(s) using the component(s).

Abstract: Techniques for managing anomalies in a software system include monitoring the software system for anomalies via a plurality of signals and determining that signal results associated with the signals indicate a presence of an anomaly in the software system. The techniques also include identifying a hierarchy of sensors associated with the anomaly, where the hierarchy includes a parent sensor and a set of child sensors that are direct or indirect descendants of the parent sensor. The techniques additionally include executing the parent and child sensors to analyze the software system for one or more causes of the anomaly, and determining the cause(s) of the anomaly based on sensor results generated by the parent and child sensors. Finally, the techniques include causing remediation of the cause(s) of the anomaly based on one or more child sensors associated with the cause(s) and one or more resolutions mapped to the child sensor(s).

Abstract: Techniques for configuring a software system include generating a hierarchy of entities representing usage of the software system by a set of users, wherein the hierarchy includes a first set of nodes representing a set of tasks, a second set of nodes representing a set of components that implement the tasks, and a set of edges between the first set of nodes and the second set of nodes. The techniques also include updating the hierarchy based on a first set of configurations for the tasks, wherein the updated hierarchy indicates one or more tasks that have been enabled for the users. The techniques further include determining, based on the updated hierarchy, one or more components that implement the task(s). Finally, the techniques include generating, based on the hierarchy, one or more runbooks that execute the task(s) using the component(s).

Abstract: Techniques for configuring a software system include generating a hierarchy of entities representing usage of the software system by a set of users, wherein the hierarchy includes a first set of nodes representing a set of tasks, a second set of nodes representing a set of components that implement the tasks, and a set of edges between the first set of nodes and the second set of nodes. The techniques also include updating the hierarchy based on a first set of configurations for the tasks, wherein the updated hierarchy indicates one or more tasks that have been enabled for the users. The techniques further include determining, based on the updated hierarchy, one or more components that implement the task(s). Finally, the techniques include generating, based on the hierarchy, one or more runbooks that execute the task(s) using the component(s).

Abstract: Techniques for managing anomalies in a software system include monitoring the software system for anomalies via a plurality of signals and determining that signal results associated with the signals indicate a presence of an anomaly in the software system. The techniques also include identifying a hierarchy of sensors associated with the anomaly, where the hierarchy includes a parent sensor and a set of child sensors that are direct or indirect descendants of the parent sensor. The techniques additionally include executing the parent and child sensors to analyze the software system for one or more causes of the anomaly, and determining the cause(s) of the anomaly based on sensor results generated by the parent and child sensors. Finally, the techniques include causing remediation of the cause(s) of the anomaly based on one or more child sensors associated with the cause(s) and one or more resolutions mapped to the child sensor(s).

Abstract: A software development tool for developing software that implements a customer's business processes. The software development tool determines a plurality of models to define the software to be developed, wherein at least one model of the plurality of models is a business model that comprises at least one business process, and the at least one business process is a set of interrelated business process paths that accomplish a business goal. The software development tool defines at least one business process path, wherein the at least one business process path is a route through the at least one business process taken during a single execution of the at least one business process, and the at least one business process path comprises at least one step.

Abstract: A software development tool for developing software that implements a customer's business processes. The software development tool determines a plurality of models to define the software to be developed, wherein at least one model of the plurality of models is a business model that comprises at least one business process, and the at least one business process is a set of interrelated business process paths that accomplish a business goal. The software development tool defines at least one business process path, wherein the at least one business process path is a route through the at least one business process taken during a single execution of the at least one business process, and the at least one business process path comprises at least one step.

Abstract: A method for the definition of data categories is described. The method uses logic templates and may be used in database processing. One embodiment of the method comprises: selecting a plurality of attributes from a group of attributes, each attribute describing a possible data item in a set of data; selecting a logic template from a group of logic templates, each logic template comprising a predetermined logic expression containing one or more variables; and assigning one or more selected attributes to each variable within the selected the logic template to produce a logic expression defining the data category. A computer program product and a user interface for achieving this method are also described.

Abstract: A method for the definition of data categories is described. The method uses logic templates and may be used in database processing. One embodiment of the method comprises: selecting a plurality of attributes from a group of attributes, each attribute describing a possible data item in a set of data; selecting a logic template from a group of logic templates, each logic template comprising a predetermined logic expression containing one or more variables; and assigning one or more selected attributes to each variable within the selected the logic template to produce a logic expression defining the data category. A computer program product and a user interface for achieving this method are also described.