Systems and methods for generating SLO specifications using annotations are generally described. In various examples, first source code associated with a first computer-implemented service is received. In various cases, a first annotation in the first source code may be received. The first annotation may include first metadata defining a name of an SLO specification. A second annotation in the first source code may be received. The second annotation may include second metadata defining a service-level objective (SLO) of a first aspect of the first computer-implemented service. In some cases, the first computer-implemented service may be executed using the first source code. In various examples, the SLO specification may be generated based on the first annotation and the second annotation.

Techniques for automated system requirements analysis are disclosed. A system requirements analysis (SRA) service generates a system model that includes system requirements, at least by performing natural-language processing on a natural-language representation of the system requirements. Based at least on the system model, the SRA service performs an analysis of the system requirements against codified system requirements rules. The SRA service determines, based at least on the analysis of the system requirements against the codified system requirements rules, that the system requirements include a violation of a system requirements rule. The SRA service generates a report that identifies at least (a) the violation of the system requirements rule and (b) a suggested action to remediate the violation of the system requirements rule.

Techniques for automated system requirements analysis are disclosed. A system requirements analysis (SRA) service generates a system model that includes system requirements, at least by performing natural-language processing on a natural-language representation of the system requirements. Based at least on the system model, the SRA service performs an analysis of the system requirements against codified system requirements rules. The SRA service determines, based at least on the analysis of the system requirements against the codified system requirements rules, that the system requirements include a violation of a system requirements rule. The SRA service generates a report that identifies at least (a) the violation of the system requirements rule and (b) a suggested action to remediate the violation of the system requirements rule.

Systems and methods may be provided for generating and modifying dynamic user experience (UX) applications that may be agile, personalized, quickly delivered, and capable of being seamlessly integrated across an organization. The behavior and functionality of the applications (e.g., user interfaces therein) may be tailored specifically to individual users in response to learned user preferences or tendencies, for example. Consequently, these dynamic UX applications may be rapidly deployed and capable of providing a satisfactory yet pliable user experience across applications.

In example embodiments, techniques are provided for decoupling user access to infrastructure models from proprietary software that maintains and updates the infrastructure models. A backend application may include an infrastructure modeling backend module that, among other functions, handles communication with an infrastructure modeling frontend module of a frontend application that provides user access to the infrastructure model, infrastructure modeling hub services that maintain repositories for the infrastructure model, and an infrastructure modeling native module that creates, performs operations upon, and updates local instances of a database that stores the infrastructure model. While the infrastructure modeling backend module may pass information obtained from the infrastructure modeling frontend module and infrastructure modeling hub services to the infrastructure modeling native module, it may be functionally separated from the software of the infrastructure modeling native module that understands how to maintain and update infrastructure models, including interacting with local instances of the database.

A focused specification for an interactive graphical design is generated by receiving a first user input from a user, the first user input identifying a first design element of the interactive graphical design. A set of selectable data elements associated with the first design element is identified and a specification template that includes the set of selectable data elements is generated. A second user input is received from the user, the second user input identifying a set of selected data elements using the generated specification template. The set of selected data elements includes one or more of the selectable data elements. The focused specification is generated using the set of selected data elements, the focused specification including the set of selected data elements and excluding selectable data elements that were not selected.

A focused specification for an interactive graphical design is generated by receiving a first user input from a user, the first user input identifying a first design element of the interactive graphical design. A set of selectable data elements associated with the first design element is identified and a specification template that includes the set of selectable data elements is generated. A second user input is received from the user, the second user input identifying a set of selected data elements using the generated specification template. The set of selected data elements includes one or more of the selectable data elements. The focused specification is generated using the set of selected data elements, the focused specification including the set of selected data elements and excluding selectable data elements that were not selected.

In some examples, software CoBot engineering, execution, and monitoring may include extracting a CoBot requirement from a requirement specification for a CoBot that is to be implemented. Based on application of a CoBot description language to the CoBot requirement, a CoBot workflow that specifies a plurality of tasks to be performed by the CoBot may be generated. A determination may be made as to whether a task is to be performed by a bot or by a human. A team that includes a plurality of bots and at least one human may be generated to execute the CoBot workflow. The bots of the team may be prioritized to identify a bot that is a best match to the CoBot requirement. The CoBot that includes configured bots may be deployed in an operational environment to perform the CoBot workflow.

In some examples, software CoBot engineering, execution, and monitoring may include extracting a CoBot requirement from a requirement specification for a CoBot that is to be implemented. Based on application of a CoBot description language to the CoBot requirement, a CoBot workflow that specifies a plurality of tasks to be performed by the CoBot may be generated. A determination may be made as to whether a task is to be performed by a bot or by a human. A team that includes a plurality of bots and at least one human may be generated to execute the CoBot workflow. The bots of the team may be prioritized to identify a bot that is a best match to the CoBot requirement. The CoBot that includes configured bots may be deployed in an operational environment to perform the CoBot workflow.

Provided is a process including: writing classes using object-oriented modelling of modeling topics; scanning the classes to determine class definition information; receiving from a subscribing modeling object a request for a subscription to a given modeling topic in a given modeling topic class, the subscription request including a modeling topic filter to select the given modeling topic from a plurality of modeling topics described by the given modeling topic class; registering a modeling topic accessor associated with the subscribing modeling object and a modeling topic mutator associated with the subscribing modeling object; processing, through the modeling topic filter a modeling topic that is accessed through an accessor and is described by the modeling topic class, the modeling topic being received from a modeling publisher object; notifying the subscribing object of the received modeling topic through a registered modeling topic listener; and mutating the received modeling topic.