Abstract: Some embodiments provide a method for performing deep packet inspection (DPI) for an SD-WAN (software defined, wide area network) established for an entity by a plurality of edge nodes and a set of one or more cloud gateways. At a particular edge node, the method uses local and remote deep packet inspectors to perform DPI for a packet flow. Specifically, the method initially uses the local deep packet inspector to perform a first DPI operation on a set of packets of a first packet flow to generate a set of DPI parameters for the first packet flow. The method then forwards a copy of the set of packets to the remote deep packet inspector to perform a second DPI operation to generate a second set of DPI parameters. In some embodiments, the remote deep packet inspector is accessible by a controller cluster that configures the edge nodes and the gateways.

Abstract: A system for assessing a data model includes a data receiver, a model receiver, and a model assessment device. The data receiver receives training data, historical data, and production data. The model receiver receives the data model associated with the historical data and trained using the training data. The historical data includes a first outcome of the data model provided based on an input feature in the production data. The model assessment device identifies a key feature in the production data relative to the input feature based on a target category in the historical data and a statistical distribution of the input feature in the production data. The model assessment device determines a second outcome of the data model based on the key feature. In response to the second outcome being different from the first outcome, the model assessment device determines a veracity score for assessing the data model.

Abstract: Examples for enhancing veracity of data are described herein. Data from a repository may be received based on a data receiving rule. From the received data, a first dataset may be generated using statistical modeling. Also, a first data veracity score for the first dataset is generated which is indicative of a degree of usability of the dataset. Another aspect relates to identifying an anomaly in the first dataset, the corrector, for each anomaly, to identify a correction technique from amongst a plurality of correction techniques. Further, a second dataset is generated using the identified correction technique having second data veracity score higher than the first data veracity score.

Abstract: A system for assessing a data model includes a data receiver, a model receiver, and a model assessment device. The data receiver receives training data, historical data, and production data. The model receiver receives the data model associated with the historical data and trained using the training data. The historical data includes a first outcome of the data model provided based on an input feature in the production data. The model assessment device identifies a key feature in the production data relative to the input feature based on a target category in the historical data and a statistical distribution of the input feature in the production data. The model assessment device determines a second outcome of the data model based on the key feature. In response to the second outcome being different from the first outcome, the model assessment device determines a veracity score for assessing the data model.

Abstract: Examples for enhancing veracity of data are described herein. Data from a repository may be received based on a data receiving rule. From the received data, a first dataset may be generated using statistical modeling. Also, a first data veracity score for the first dataset is generated which is indicative of a degree of usability of the dataset. Another aspect relates to identifying an anomaly in the first dataset, the corrector, for each anomaly, to identify a correction technique from amongst a plurality of correction techniques. Further, a second dataset is generated using the identified correction technique having second data veracity score higher than the first data veracity score.

Abstract: Methods, systems, and devices for network integration are described. Some systems may implement an integration platform including a service composition layer (SCL), a network abstraction layer (NAL), and one or more application programming interfaces (APIs). The integration platform may support application and network flexibility, customization, and modular design based on the SCL and NAL. For example, the SCL may receive an execution request (e.g., an intent) corresponding to a service and may parse the execution request to determine a set of modular tasks. The SCL may send a modular task (e.g., via an API) to the NAL for processing. The NAL may determine a type of infrastructure architecture (e.g., including querying for network node connections, parameters, etc.) associated with the integration platform and may modify the modular task based on the information. The NAL may execute the modular task on one or more network devices to perform the service.

Abstract: Methods, systems, and devices for network integration are described. Some systems may implement an integration platform including a service composition layer (SCL), a network abstraction layer (NAL), and one or more application programming interfaces (APIs). The integration platform may support application and network flexibility, customization, and modular design based on the SCL and NAL. For example, the SCL may receive an execution request (e.g., an intent) corresponding to a service and may parse the execution request to determine a set of modular tasks. The SCL may send a modular task (e.g., via an API) to the NAL for processing. The NAL may determine a type of infrastructure architecture (e.g., including querying for network node connections, parameters, etc.) associated with the integration platform and may modify the modular task based on the information. The NAL may execute the modular task on one or more network devices to perform the service.

Abstract: A computer implemented model-driven method to generate platform specific code for a user interface is disclosed. In one embodiment, the method includes, capturing customer requirements of the software component in a schema, modeling business-software architecture of the software component in a first level of the schema, modeling technical architecture of the software system from the modeled business-software architecture in a second level of the schema, defining events in the schema that connect the first level and the second level of the schema, defining links in the schema that represent interactions between the user interfaces, defining integration services in the schema for each of the events, mapping each element in the first level to a corresponding one of the elements in the second level using the events, links, and integration services in the schema, loading the schema of the software component into a code generation repository.

Abstract: A method and system for providing relevant information to a mobile device. An entity structure is provided that includes entity records, each entity record corresponding to an entity that provides a service. Each entity record is associated with a proper subset of regions of a plurality of regions and is categorized into at least one category of a plurality of categories based on the service provided by the entity. A first region category index that is based on the entity structure is provided to a mobile device that is determined to be in a first region of the plurality of regions. The first region category index identifies only those categories in which at least one entity record associated with the first region has been categorized.

Abstract: Method and system for capturing device-independent user interface structure in a model based software system are disclosed. In one embodiment, at least one entry point is received from a user by a business system. Further, a user interface corresponding to the at least one entry point is provided. Furthermore, user interface meta-data associated with the user interface is captured. Also, at least one event associated with user interface elements is identified as a response to user actions based on the captured user interface meta-data. In addition, a pattern signature is identified in the model based software system for reuse in one or more model based software systems based on an expected behavior of the user interface when the identified at least one event occurs. Then, the identified at least one event is mapped to the identified pattern signature.

Abstract: User interfaces and software reuse in model based software systems is disclosed. In one embodiment, user interface data is captured from business documents. Further, user interface elements are mapped to the business documents. A data model is formed for the business documents. A set of business rules for each business component in the data model is provided. A sequence of business rules associated with each action in the data model is scanned. In addition, a first pattern signature associated with an action that uniquely identifies each of the sequence of business rules is formed. It is determined if the first pattern signature is present in other actions in the data model. If so, the first pattern signature is included in a set of pattern signatures of the data model, else step of determining for a second pattern signature that is a subset of the first pattern signature is repeated.

Abstract: A system and method for testing a software development activity of an enterprise application is disclosed. In one embodiment, the method includes obtaining a software structure specification for an enterprise application and automatically generating test plans using the software structure specification. The method also includes automatically determining at least one test path in each test plan using the software structure specification, and automatically deriving a plurality of test cases using each test path. Further, the method includes executing each of the plurality of test cases and recording test results.

Abstract: In a model based software system, a set of business rules is scanned, and patterns are identified. The patterns are then compared, and similarities identified which indicate that software can be reused in the system. In one embodiment, identifiers of the rules are scanned. In another embodiment, usage patterns are used for designing a middle layer and generating code. In another embodiment of the invention, a data model is generated by capturing data from a user interface for a business document.

Abstract: A system and method for model driven software is disclosed. In one embodiment, the method of handling changes to a software system in a business environment includes capturing customer requirements of the software system in a schema, modeling business-software architecture of the software system in a first level of the schema, modeling design architecture of the software system in a second level of the schema, defining events that connect the first level and second level of the schema, defining links that represent interactions between the user interfaces, defining integration services for each of the events, mapping each element in the first level to a corresponding one of elements in the second level using the events, links and integration services, creating a knowledge repository with a traversable user interface representing the mappings, identifying changes to the software system, and analyzing impact of the changes using the knowledge repository.

Abstract: Method and system for capturing device-independent user interface structure in a model based software system are disclosed. In one embodiment, at least one entry point is received from a user by a business system. Further, a user interface corresponding to the at least one entry point is provided. Furthermore, user interface meta-data associated with the user interface is captured. Also, at least one event associated with user interface elements is identified as a response to user actions based on the captured user-interface meta-data. In addition, a pattern signature is identified in the model based software system for reuse in one or more model based software systems based on an expected behavior of the user interface when the identified at least one event occurs. Then, the identified at least one event is mapped to the identified pattern signature.

Abstract: A computer implemented model-driven method to generate platform specific code for a user interface is disclosed. In one embodiment, the method includes, capturing customer requirements of the software component in a schema, modeling business-software architecture of the software component in a first level of the schema, modeling technical architecture of the software system from the modeled business-software architecture in a second level of the schema, defining events in the schema that connect the first level and the second level of the schema, defining links in the schema that represent interactions between the user interfaces, defining integration services in the schema for each of the events, mapping each element in the first level to a corresponding one of the elements in the second level using the events, links, and integration services in the schema, loading the schema of the software component into a code generation repository.

Abstract: A method and system of a software development using visual action elements is disclosed. In one embodiment, the method includes providing a user interface with action elements, and providing a mechanism for specification and review of the action elements using the user interface. For example, providing a user interface includes providing a prototype of the user interface in a web browser and providing a mechanism for specification and review includes providing a toolbar with functionality to record user comments regarding the action elements. The method may also include providing a user interface to document the user interface. The method may further include providing an animated view of stimulus response behavior of the action elements.

Abstract: A system and method for auditing enterprise data is disclosed. A non-intrusive enterprise application audit trail has the ability to configure and track only data that is selected, thereby conserving system resources. In one embodiment, a method includes providing one or more configuration facilities in an enterprise application, viewing configuration parameters, viewing modified enterprise data in the context of change management, and changing said configuration parameters so that data tracking in said enterprise application is performed only on select data. The method also includes invoking a database triggers facility to identify said select data to be tracked.

Abstract: An aspect of the present invention provides a method of handling a financial transaction in a transaction switch. The method includes receiving a primary transaction request from an initiator, identifying a host from a routing table for receiving the primary transaction request based on details provided in the primary transaction request, transmitting the primary transaction request to the identified host, receiving a response from the identified host, determining a need for transmitting the primary transaction request to another host and interpreting the response received and transmitting a final outcome back to the initiator.

Abstract: A system and method for model driven software is disclosed. In one embodiment, the method of handling changes to a software system in a business environment includes capturing customer requirements of the software system in a schema, modeling business-software architecture of the software system in a first level of the schema, modeling design architecture of the software system in a second level of the schema, defining events that connect the first level and second level of the schema, defining links that represent interactions between the user interfaces, defining integration services for each of the events, mapping each element in the first level to a corresponding one of elements in the second level using the events, links and integration services, creating a knowledge repository with a traversable user interface representing the mappings, identifying changes to the software system, and analyzing impact of the changes using the knowledge repository.