System and method for providing access to data in a plurality of software development systems

• US 9,092,575 B2
• Filed: 08/25/2014
• Issued: 07/28/2015
• Est. Priority Date: 09/19/2013
• Status: Active Grant

• Current Assignee: FMR LLC
• Original Assignee: FMR LLC
• Inventors: Koenig, David Ira, Eldridge, Dean Edward, Moran, Sarah Ann, Rousseau, Susan Marie
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US14/468,048
• Publication Number:
  US 20150082281A1
• Time in Patent Office: 337 Days
• Field of Search: 717100-103, 717120-122, 717/108, 717114-117
• US Class Current: 1/1
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3668 Software testing software testing in telephone exchanges H04M3/242, testing of hardware G06F11/22

Abstract

Systems and method are provided for determining risk of product release failure in an environment where multiple independent releases come together into a shared environment. A risk factor for success or failure of a product release is based on release information input by a user and information input by other users regarding releases, the users typically on distinct development systems. The information from each distinct system is mapped (e.g., normalized and weighted) into a common schema. A risk index for the product release is determined. The risk index, risk factors, and/or associated information therewith, is presented to a user.

Claims

1. A computer-implemented method of determining risk of product release failure in an environment where multiple independent releases come together into a shared multi-product enterprise environment, the method comprising:

providing a plurality of application programming interfaces, at least two application programming interfaces are associated with at least two of a plurality of distinct development systems, respectively, and capable of retrieving data from and providing data to its respective development system of the two of the distinct plurality of development systems, the plurality of development systems each having a distinct data model and including project management systems, software development systems, quality control systems, change control systems, service management systems, asset management systems, configuration management systems, or any combination thereof;

receiving, via one application programming interface of the at least two application programming interfaces, a request for a determination of risk of product release failure within the shared multi-product enterprise environment, the request including a date and time for the product release;

receiving, via each application programming interface of the at least two application programming interfaces, a set of risk factors retrieved from each software development system of the two distinct plurality of software development systems that has a product release scheduled, each set of risk factors comprises one or more risk factors and a date for its respective product release;

normalizing, via a computing device, each distinct set of risk factors to a common set of risk factors, the common set of risk factors is based on a user defined domain mapping;

assigning, via the computing device, each item in each set of normalized risk factors a weight, the weight being based on the user defined domain mapping;

determining, a risk index for each of set of normalized risk factors, the risk index indicating the risk of product release failure within the shared multi-product enterprise environment based on each item in each set of normalized risk factors and each item'"'"'s assigned weight;

determining, via the computing device, a confidence factor for each risk factor in each set of collision risk factors; and

displaying, via the one application programming interface of the at least two application programming interfaces, the risk index for each set of normalized risk factors to the user.

2. The computerized-implemented method of claim 1 wherein each set of risk factors relates to a product change scheduled for its respective development system of the plurality of development systems.

3. The computerized-implemented method of claim 1 further comprising:

the confidence factor based on a type of operational tool the request was received from; and

displaying, via the computing device, the confidence factor to the user.

4. The computer-implemented method of claim 1 wherein the request further includes a request for determination of risk of collision for each change included in the product release.

5. The computer-implemented method of claim 1 wherein the risk factors include application criticality, database criticality, size of change, complexity of change, volatility of change, velocity of change, frequency of change, technology obsolescence, interdependency with other systems, interdependency with other databases, integration with other applications, common data elements, common infrastructure, stability history, market event, holidays, resource scarcity, or any combination thereof.

6. The computer-implemented method of claim 1 further comprising:

displaying, via the one application programming interface of the at least two application programming interfaces, an interactive display view of a calendar showing the risk index for each set of risk factors on the date of its respective product release.

7. The computer-implemented method of claim 6 wherein the interactive display view of the calendar further comprises a hourly view, a daily view, a weekly view, a monthly view or any combination thereof.

8. The computer-implemented method of claim 7 wherein in the hourly view, the daily view or the weekly view each risk factor name and value is displayed to the user.

9. The computer-implemented method of claim 1 further comprising:

displaying, via the one application programming interface of the at least two application programming interfaces, an interactive display view of assets that are in release conflict with other assets.

10. The computer-implemented method of claim 9 wherein assets comprise applications, databases, infrastructure components, or any combination thereof.

11. The computer-implemented method of claim 1 further comprising:

displaying, via the one application programming interface of the at least two application programming interfaces, an interactive display view that allows a user to choose a release window based on the risk index, availability, resources, or any combination thereof.

12. The computer-implemented method of claim 1 further comprising:

generating, by the computing device, an alert to inform managers of potential collisions and suggest changes, the alert comprising a phone call, an email message, a text message, or any combination thereof.