Abstract: A method includes receiving, from a first remote device, an initial first plurality of status metrics corresponding to a first domain, each of the initial plurality of status metrics indicating whether a corresponding parameter of the first domain requires remediation. The method includes comparing the initial plurality of status metrics to a reference database, the reference database listing previously encountered problems with known remediation solutions. The method includes receiving from the first remote device, an updated plurality of status metrics corresponding the first domain, each of the updated plurality of status metrics indicating whether a corresponding parameter of the first domain requires remediation. The method includes applying an algorithm to the updated plurality of status metrics to generate a maturity score of the first domain. The method includes combining the maturity score of the first domain and a maturity score of a second domain to generate a maturity report.

Abstract: A method of performing root cause analysis of communication system testing results and submitting communication system defect tickets along with associated previously resolved communication system defect tickets that provide insights for repairing the communication system defects. The method comprises categorizing by a categorization engine error messages in logs received from applications undergoing test, remediating the test data errors and rerunning a test case by a test data error handling script, for each error message categorized as a valid error, searching a data store by a valid error handling script to identify previously resolved defect tickets that match the valid error, and, for each error message categorized as a valid error, generating a defect ticket by the valid error handling script that describes the error message categorized as a valid error and identifies at least some of the previously resolved defect tickets that match the valid error.

Abstract: Methods and systems are disclosed for merchant system identity validation. One method comprises generating, by an access management system, a primary key associated with an integrator system and transmitting the primary key to the integrator system. The access management system may also generate a hash value associated with a merchant system, and may transmit the hash value to the merchant system. When a payment transaction is initiated at the merchant system, the access management system may receive an authorization request comprising a key-hash pair. The key-hash pair may be validated against a validation database. Upon successful validation, the access management system may transmit the authorization request to an acquirer processor.

Abstract: A fault model representation of a computer network is generated, wherein the computer network includes a set of connected computer network elements that was at least in part configured based on a specified declarative intent in forming the computer network. A symptom representation for the computer network is determined based on telemetry data of one or more elements of the set of connected computer network elements and a behavior specification repository identifying symptoms and their associated root causes. The fault model representation and the symptom representation are provided to a root cause analysis to determine one or more root causes of one or more detected symptoms of the computer network.

Abstract: In an example, suspect scores for impacting elements that can cause an error state of a first element are computed. The computation is performed based on states of each element for which the impacting element can cause the error state.

Abstract: Aspects include methods, systems, and computer programs to identify changes in a plurality of resources in a collaborative effort system, comprising receiving, by the collaborative effort system, an input of a suspect resource, generating, by a processor, a list of identified resources based on the suspect resource, generating a list of changes of the identified resources, and displaying, by a user interface of the collaborative effort system, the list of the changes of the identified resources.

Abstract: Supplemental functionalities may be provided to an executable program via the ontology, for example, without having to modify the application code of the executable program or without having to recompile the executable program. In some embodiments, objects may be extracted from a collection of documents. The objects may be converted to one or more data sets having a pre-defined format. One or more relationships between the data sets may be defined. An ontology may be generated based on the data sets and the relationships. Supplemental information may be generated for an executable program based on the ontology. The supplemental information may be related to one or more functionalities of an application. The supplemental information may be provided as input to the executable program, where the supplemental information causes the functionalities of the application be made available via the executable program.

Abstract: A system for determining a root cause of a performance issue of a software application executing in a distributed computer system. The system includes constructing a hierarchical graph of metrics of a component of the distributed computer system based on search traces of the metrics of different users. A parent-child edge between a first metric and a second metric in the hierarchical graph is constructed when there is a sequential association between the search traces. A sibling edge between the first metric and the second metric in the hierarchical graph is constructed when there is no sequential association between the search traces. A metric investigation recommendation is provided to address the performance issue based on traversal of the hierarchical graph of the metrics.

Abstract: After power activation, a transferer 14 detects a bootstrap program 111 having a first error check code 114 assigned thereto and being stored in a first storage device 11, subjects the bootstrap program 111 to an error detection/correction process, and transfers the bootstrap program 111 to the second storage device 12. If the transfer is properly completed, by executing the bootstrap program 111 on the second storage device 12, the CPU 10 performs an error detection/correction process for a main program 112 having a second error check code 115 assigned thereto, and transfers the main program 112 to a third storage device 13, after which the CPU's control branches out to the main program 112 on the third storage device 13. As a result, system boot can be performed without employing a NOR type flash memory.