Opshub, Inc.

Other

Sandeep Jain

Prakash Chandra Tiwary

David Robert Knight

Aparna Garg

Hardik Shah

Anil Babubhai Savani

Gaurav Chavda

Dimple Jayendra Shah

Ramesh Venkataraman

Saachi Jain

Vibhuti Bhushan

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.

System and method for identifying risky impacted work items

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.

Method and system for providing delta code coverage information for work items

A processor-implemented method and a system for artifact order and rank synchronization is provided. The method includes determining, using a ranking module, if a rank of an artifact has changed across disparate tools in an organization eco-system of a source comprising an end system from where integration reads the data for synchronization, by determining if hierarchy processing is required or not. The method also includes updating, using a rank update module, the rank of the artifact in a target comprising an end system where integration writes data.

System and method for artifact order and rank synchronization

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.

System and method for bidirectional replication of scope changes for work items between applications

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.

Source traceability-based impact analysis

An application operating on a portable computing device that generates a suggested hypothesis of at least one of: a diagnosis, a treatment, and subsequent medical investigation. The application receives quantified subfactors, collectively defining factors, for each patient. Subfactors of the medical condition are related to the history, symptoms, signs, tests, and responses to the treatment. The application determines an odds ratio for each factor regarding each hypothesized medical condition as well as an associated prevalence. The application can also determine a respective sensitivity and specificity. Posterior probability distribution, such as using Bayesian statistics, can be applied using odds ratios, prevalence, sensitivity specificity, and the associated correlations to determine the suggested hypothesis of the diagnosis, treatment, and any next tests.

Medical patient synergistic treatment application

Communications software that minimizes recipient distractions from receiving messages receives, at an application running on a computing device of an application user referred to as a sender, input for a message to a recipient address. A notice of the message is received from the application to the recipient address at a distraction free messaging (DFM) server. The DFM server querying settings established by a recipient linked to the recipient address to determine a delivery time for the message. The DFM server conveys over a network the delivery time to the application running on the computing device of the sender. At the delivery time, the DFM server delivering the message to the recipient address enabling the recipient to view the message as a delivered message, wherein prior to the delivery time the recipient is permitted to preview the message via a distraction free message application operating in a pre-delivery mode.

Decreasing distractions caused by message overload

A system and method for analyzing risk factors to enhance the quality of program code have been disclosed. The risks are identified and evaluated, post which test cases are defined for each of the identified risk factors. Further, the defect density, code complexity and change rate corresponding to each of the test cases is determined. Risk profiles are created for each of the test cases. The risk profiles are categorized based on defect density, complexity of the code and change rate. The test cases are evaluated depending upon the risk posed by new scripts added to the program code. The scripts need to be executed for satisfying a necessary and sufficient condition are decided based on the correlation between program code files, activities on those files, defects corresponding to those files and test cases used to test those defects.

System and method for analyzing risks present in a software program code

A messaging server with a future message storage space for future messages, each being a sender created message not yet delivered to a recipient that has an associated sender specified message delivery time. Recipient specific delivery block details are specified for a set of delivery blocks for future messages. The future messages are received processed and stored. Until the respective sender specified message delivery time a respective one of the set of senders is able to retract and edit a corresponding one of the future messages. Future messages are delivered at the delivery time consistent with the delivery blocks. After delivery the sender is unable to retract and edit a corresponding delivered message. Future messages do not alert a recipient of arrival until the sender established delivery time, which minimizes cognitive distractions and provides the sender with notice for anticipating a time of response, without overly distracting the recipient.

Future messaging maximizing contextual relevancy and minimizing information overload based distractions

The various embodiments herein disclose a system and method for generating a delta code coverage information. The system for generating delta code coverage information comprises, a source control module configured for storing a plurality of software program code files to be processed and a plurality of code coverage data corresponding to the plurality of software program code files, a processor configured to generate a delta code coverage data for analysis for each of the plurality of software program code files on a line level or at a branch level by performing a time based delta code coverage process and a path based delta code coverage process.

Method and system for providing delta code coverage information

A medical protective gown comprising a gown body. A centrally located orifice passes through a central region of a front panel of the gown body. A tubular protective sleeve extends forward from the front panel of the gown body, the tubular protective sleeve being located circumscribing the centrally located orifice. A tubular protective sleeve distal end panel is located at a distal end of the tubular protective sleeve. The tubular sleeve is adapted to receive a stethoscope or any other desired medical instrument. A broadened interior pocket is assembled to an interior surface of the gown body to support an upper, broader portion of the stethoscope or other instrument. A flange can be included with the tubular protective sleeve and/or the broadened interior pocket to aid in attachment to the gown body. The tubular protective sleeve can include a sleeve contraction system to contract the protective sleeve.

Medical gown having an integral protective sleeve for medical equipment

The various embodiments herein provide a method and system for synchronization of links and attachments during synchronization between source and target devices. The system for executing synchronization between the source and target devices comprises a connector framework, a process framework, a mapping manager, a recovery manager, a conflict manager and a failure manager. The method comprises getting the 'as of state' of the attachment that is old and new attachment information list for the revisions, then the system having history for the attachment constructs 'as of state' and send as part of the event and system not having history for the attachment, stores attachment information in the history state table with the source update time information in poller as well as the time of adding attachment from the adapter.

System and method for synchronizing links and attachments between two computing devices

The embodiments herein provide a method and system for polling and processing data. The method comprises computing a maximum time from a source after a last update time, waiting for a preset time to ensure that all transactions with respect to a change in a data is completed, querying for a plurality of changes after an elapse of the preset waiting time since the last update time and up to the maximum time, generating a time window, collecting a list of changes occurred within the generated time window, sending the collected list of changes for processing; and updating the processed data at the destination. The time window comprises a time interval between the last update time and the maximum time.

Method and a system for polling and processing data

The various embodiments herein provide a system and method for identifying, analyzing and integrating the risks associated with a source code. The system comprises a code coverage module for collecting and transforming the code coverage information by a file name, a source code analyzer module for collecting and transforming source code violations information by the file name, a software configuration management module for collecting and transforming the source code commit information by the file name, a risk analyzer processing module for receiving and relating the collected code coverage information, source code violations information and source code commit information with each other by the file name and a report generation module for publishing the processed result of the collected code coverage information, source code violations information and source code commit information in a report. The report is reviewed for identifying, analyzing and integrating risks associated with source code.

System and method for identifying, analyzing and integrating risks associated with source code

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.

Growing community of inventors

Palo Alto, CA, United States of America

Sandeep Jain