Aspects of the subject disclosure may include, for example, receiving instructions to validate a configuration associated with an application under test, the instructions identifying the application under test that exists in a first particular software environment that is selected from among a plurality of software environments; receiving dependency data, the dependency data identifying a dependency application that exists in a second particular software environment that is selected from among the plurality of software environments; performing a first process to determine whether the application under test that exists in the first particular software environment can be instantiated as a first running application, the first process resulting in a first determination; responsive to the first determination being that the application under test that exists in the first particular software environment can be instantiated as the first running application, automatically performing with no user interaction a second process to determine whether the dependency application that exists in the second particular software environment can be instantiated as a second running application, the second process resulting in a second determination; and automatically outputting with no user interaction a report indicating the first determination and the second determination. Other embodiments are disclosed.

Aspects of the subject disclosure may include, for example, receiving instructions to validate a configuration associated with an application under test, the instructions identifying the application under test that exists in a first particular software environment that is selected from among a plurality of software environments; receiving dependency data, the dependency data identifying a dependency application that exists in a second particular software environment that is selected from among the plurality of software environments; performing a first process to determine whether the application under test that exists in the first particular software environment can be instantiated as a first running application, the first process resulting in a first determination; responsive to the first determination being that the application under test that exists in the first particular software environment can be instantiated as the first running application, automatically performing with no user interaction a second process to determine whether the dependency application that exists in the second particular software environment can be instantiated as a second running application, the second process resulting in a second determination; and automatically outputting with no user interaction a report indicating the first determination and the second determination. Other embodiments are disclosed.

A system, includes a memory and a processor, where the processor is in communication with the memory. The processor is configured to receive a request to generate source code associated with a unified model defined by a set of specifications. A first specification of the set of specifications is parsed into a first set of components and a second specification of the set of specifications is parsed into a second set of components. The first set of components and the second set of components are analyzed to determine a correlation set and groups within the first set of components and the second set of components. The first set of components and the second set of components, incorporating the correlation set and groups, are combined to generate the unified model. The source code associated with the unified model is generated.

A system, includes a memory and a processor, where the processor is in communication with the memory. The processor is configured to receive a request to generate source code associated with a unified model defined by a set of specifications. A first specification of the set of specifications is parsed into a first set of components and a second specification of the set of specifications is parsed into a second set of components. The first set of components and the second set of components are analyzed to determine a correlation set and groups within the first set of components and the second set of components. The first set of components and the second set of components, incorporating the correlation set and groups, are combined to generate the unified model. The source code associated with the unified model is generated.

A system and method for automatically routing datasets based on input and output requirements of information is disclosed. The example method includes obtaining a list of modules executing on one or more processing devices, each module to generate an output dataset of a respective output requirement based on an input dataset of a respective input requirement. The method also includes establishing connections between the modules based on the input requirements and output requirements, including a first connection between a first module and a third module and a second connection between a second module and the third module. The method also includes receiving a first output dataset from the first module and receiving a second output dataset from the second module and, responsive to determining that the first module reported an error, routing the second output dataset to the third module without routing the first output dataset to the third module.

A system and method for automatically routing datasets based on input and output requirements of information is disclosed. The example method includes obtaining a list of modules executing on one or more processing devices, each module to generate an output dataset of a respective output requirement based on an input dataset of a respective input requirement. The method also includes establishing connections between the modules based on the input requirements and output requirements, including a first connection between a first module and a third module and a second connection between a second module and the third module. The method also includes receiving a first output dataset from the first module and receiving a second output dataset from the second module and, responsive to determining that the first module reported an error, routing the second output dataset to the third module without routing the first output dataset to the third module.

An interrupt-driven system verification method based on interrupt sequence diagrams includes the steps of: establishing an interrupt-driven system model based on an interrupt sequence diagram, dividing interaction fragments in the obtained interrupt sequence diagram into basic interaction fragments and composite interaction fragments and sequentially converting the basic interaction fragments and the composite interaction fragments into the corresponding automaton models, combining the automaton models into one automaton model, adding the constraints in the interrupt sequence diagram to the converted automaton model, adding the verification attribute information as a constraint to the converted automaton model, describing an automaton as an input format acceptable to the automaton verification tool, and verifying the model with the automaton verification tool.

An interrupt-driven system verification method based on interrupt sequence diagrams includes the steps of: establishing an interrupt-driven system model based on an interrupt sequence diagram, dividing interaction fragments in the obtained interrupt sequence diagram into basic interaction fragments and composite interaction fragments and sequentially converting the basic interaction fragments and the composite interaction fragments into the corresponding automaton models, combining the automaton models into one automaton model, adding the constraints in the interrupt sequence diagram to the converted automaton model, adding the verification attribute information as a constraint to the converted automaton model, describing an automaton as an input format acceptable to the automaton verification tool, and verifying the model with the automaton verification tool.

Methods, computer readable media, and devices for rapid prototyping of both user experience and technical features in a combined approach. One method may include creating a set of known user experience (UX) components including a user interface element representing at least one of a data element and a data interaction, creating a UX screen including a set of UX elements within a UX prototyping tool, translating the UX screen into a set of standardized UX components, publishing the set of standardized UX components by mapping the set of standardized UX components to synthetic data, and validating a technical aspect of the published set of standardized UX components based on user interaction with the published set of standardized UX components.

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.