Abstract: A system utilizes an electrochemical reactor to convert salt into acid and base products. The salt is sourced from seawater, brine or another aqueous salt feedstock solution that typically also includes divalent ions. A small (slipstream) portion of the base product generated by the electrochemical reactor is fed back to a chemical precipitator where it is utilized to increase a pH level of the aqueous salt feedstock solution above a precipitation level of at least some the divalent ions, thereby causing precipitation of the divalent ions into insoluble solids. The insoluble solids are then filtered or otherwise separated/removed from the remaining supernatant solution (i.e., the aqueous salt/base solution formed by a mixture of the residual aqueous salt feedstock solution and base product). The supernatant solution is then supplied to the electrochemical reactor for conversion of its salt into additional acid and base product.

Abstract: The embodiments herein provide a system and method for bidirectional replication of scope changes for work items between applications are provided. The embodiments herein identify scope change for a given work item and transform the scope change of the work item from a source application to a target application. The embodiments herein further check if the work item in the target application is in an expected state and then move the work item from one scope to another in the target application. Moreover, if the target application fails to support the movement of the work item from one scope to another, then the embodiments herein deprecate the work item in an old scope of the target application and create a new work item in the target application with a new scope.

Abstract: A method and system of identifying risky impacted work items is provided. The method includes identifying work items impacted by a commit between a start tag and an end tag, and information associated with one or more delta lines associated with the impacted work files; computing delta lines for each of the identified work items impacted by the commit, for determining commits that have touched the delta lines and the commits impacted as a result of changes between the start tag and the end tag and fetching work items against which impacted commit was done and impacted work item wise delta lines details; computing delta code coverage information for the work items; determining a list of critical, blocker open issues against all impacted work items and scanning the delta code coverage information for identifying and filtering risky impacted work items based on predetermined criteria and based on the determined list.

Abstract: A processor implemented method for computing delta code coverage information for work items are provided. The method includes fetching details associated with one or more files touched between a start tag and an end tag from a source code management (SCM) tool; fetching one or more lines that are one of added, modified, or removed, for a given file, between the start tag and the end tag; fetching commit details; determining a map with work item id as key and a list of delta lines corresponding to the work item and computing, using a delta code coverage module, delta code coverage information corresponding to the fetched work items, by obtaining a list of delta lines for checking a number of delta lines covered as per the given coverage file for each work item id in the map.

Abstract: A system including an impact analysis engine (IAE) and a method for analyzing impact of changes to a software code are provided. The IAE iteratively processes and compares lines of the software code changed across different versions of the software code for deriving the impact of changes performed for a requested version. The IAE automatically identifies artifacts impacted by changes to each line of the software code across different versions by processing code change data. The code change data includes change data between start and end tags of the software code and commit actions previous to the start tag. The code change data includes unique identifiers of artifacts traced to the commit actions, which allow customized retrieval of artifact data including features, defects, and epics impacted by changes to each line of the software code. The IAE automatically identifies linked elements, for example, tests, traced to the identified artifacts.

Abstract: A system including an impact analysis engine (IAE) and a method for analyzing impact of changes to a software code are provided. The IAE iteratively processes and compares lines of the software code changed across different versions of the software code for deriving the impact of changes performed for a requested version. The IAE automatically identifies artifacts impacted by changes to each line of the software code across different versions by processing code change data. The code change data includes change data between start and end tags of the software code and commit actions previous to the start tag. The code change data includes unique identifiers of artifacts traced to the commit actions, which allow customized retrieval of artifact data including features, defects, and epics impacted by changes to each line of the software code. The IAE automatically identifies linked elements, for example, tests, traced to the identified artifacts.

Abstract: The embodiments herein provide a system and method for synchronization of data and recovery of failures during synchronization between two systems. The system for executing synchronization between the source and target systems comprises a connector framework, a process framework, a mapping manager, a recovery manager, a conflict manager and a failure manager. A method for bidirectional data synchronizing and integrating involves keeping information about integration user in integration database for each entity and update along with update time and audit id, only when the system does not keep information about the created and updated entity. A method of synchronizing only the entities qualifying a criterion, a method for failure recovery from a correct point during integration process, a method for handling recovery for changes coming from multiple end points and a method for recovery during server shutdown are also provided.

Abstract: The embodiments herein provide a system and method for synchronization of data and recovery of failures during synchronization between two systems. The system for executing synchronization between the source and target systems comprises a connector framework, a process framework, a mapping manager, a recovery manager, a conflict manager and a failure manager. A method for bidirectional data synchronizing and integrating involves keeping information about integration user in integration database for each entity and update along with update time and audit id, only when the system does not keep information about the created and updated entity. A method of synchronizing only the entities qualifying a criterion, a method for failure recovery from a correct point during integration process, a method for handling recovery for changes coming from multiple end points and a method for recovery during server shutdown are also provided.