Automating service maturity analysis and estimation

Patent metadata

Field	Value
Publication number	US-11036474-B2
Application number	US-201816234435-A
Country	US
Kind code	B2
Filing date	Dec 27, 2018
Priority date	Dec 27, 2018
Publication date	Jun 15, 2021
Grant date	Jun 15, 2021

Abstract

Techniques for computer-implemented automation of analysis of service maturity and automation of estimation of service maturity for software applications and services are provided, identifying a service to determine the service maturity level compared to an identified task comprising optimal service maturity criteria. In response to identifying the service and task, determining that each criteria of the task is met by the service. Subsequently, updating a score for the overall task and the individual criteria based on the total service conformity to the criteria. The scores and differences can be displayed in an interface to indicate the maturity of the service.

First claim

What is claimed is:

1. A computer-implemented method comprising:
receiving, by a computing device, a first input identifying a computer program that is currently executing and is implemented as a microservice, the computer program comprising a set of service components;
receiving, by the computing device, a second input identifying a task comprising one or more checks, each check of the one or more checks comprising one or more criterion indicating a set of rules;
while the computer program continues executing, determining, by the computing device and for each check of the one or more checks, whether the set of service components conform to the set of rules indicated by the one or more criterion;
determining, by the computing device, a check score for each check, each check score indicating a level of conformity a respective service component of the set of service components has with the set of rules indicated by the one or more criterion;
determining, by the computing device, that at least one check score does not meet a threshold score value;
identifying, by the computing device, a service component of the set of service components corresponding to the at least one check score that does not meet the threshold score value;
in response to determining that the at least one check score does not meet the threshold score value and identifying the service component:
preventing, by the computing device, execution of the microservice;
restricting, by the computing device, a modification of the service component and the microservice;
receiving, by the computing device, a corrected service component;
replacing, by the computing device, the service component with the corrected service component;

determining, by the computing device, a task score of the task based, at least in part, an average of at least one updated check score of the corrected service component; and
causing display of, by the computing device:
an indicator specifying that the service component is replaced; and
a timer for each check, each timer indicating an amount of time that has passed since a respective check score was updated.

2. The method of claim 1 , further comprising:
receiving one or more weight scores, each weight score corresponding to a respective check of the one or more checks; and
updating the respective check score for each check, based on, at least in part, a corresponding weight score.

3. The method of claim 1 , further comprising:
determining a subset of checks of the one or more checks have a corresponding service component that is not part of the microservice; and
causing display of an indicator for each of the subset of checks.

4. The method of claim 1 , wherein at least one determination involves a check that is not part of the task.

5. The method of claim 1 , wherein determining, for each check, whether the respective service component satisfies the one or more criterion comprises determining whether the microservice has completed a security risk assessment survey.

6. The method of claim 1 , wherein determining, for each check, whether the respective service component satisfies the one or more criterion comprises determining whether the microservice is registered with a call schedule and, in response thereto, further determining whether all user accounts associated with the call schedule have created and stored contact data identifying one or more contact methods.

7. The method of claim 1 , wherein determining, for each check, whether the respective service component satisfies the one or more criterion comprises determining whether the microservice is executing a number of cross-environment programmatic calls that exceeds a stored maximum allowed number of cross-environment programmatic calls.

8. The method of claim 1 , wherein determining, for each check, whether the respective service component satisfies the one or more criterion comprises determining whether the microservice has defined a service level objective in a database and, in response thereto, determining whether one or more service level indicators of the microservice satisfy the service level objective.

9. The method of claim 1 , wherein determining, for each check, whether the respective service component satisfies the one or more criterion comprises determining whether the microservice is associated with one or more trouble tickets in a ticket tracking system.

10. One or more non-transient computer readable storage media comprising instructions which, when executed by a processor, cause the processor to:
receive a first input identifying a computer program that is currently executing and is implemented as a microservice, the computer program comprising a set of service components;
receive a second input identifying a task comprising one or more checks, each check of the one or more checks comprising one or more criterion indicating a set of rules;
while the computer program continues executing, determine, for each check of the one or more checks, whether the set of service components conform to the set of rules indicated by the one or more criterion;
determine a check score for each check, each check score indicating a level of conformity a respective service component of the set of service components has with the set of rules indicated by the one or more criterion;
determine that at least one check score does not meet a threshold score value;
identify a service component of the set of service components corresponding to the at least one check score that does not meet the threshold score value;
in response to determining that the at least one check score does not meet the threshold score value and identifying the service component:
prevent execution of the microservice;
restrict a modification of the service component and the microservice;
receive a corrected service component; and
replace the service component with the corrected service component;

determine a task score of the task based, at least in part, an average of at least one updated check score of the corrected service component; and
cause display of:
an indicator specifying that the service component is replaced; and
a timer for each check, each timer indicating an amount of time that has passed since a respective check score was updated.

11. The non-transient computer readable storage media of claim 10 , wherein the instructions further cause the processor to:
receive one or more weight scores, each weight score corresponding to a respective check of the one or more checks; and
update the respective check score for each check, based on, at least in part, a corresponding weight score.

12. The non-transient computer readable storage media of claim 10 , wherein the instructions further cause the processor to:
determine a subset of checks of the one or more checks have a corresponding service component that is not part of the microservice; and
cause display of an indicator for each of the subset of checks.

13. The non-transient computer readable storage media of claim 10 , wherein causing the processor to perform at least one determination involves a check that is not part of the task.

14. The non-transient computer readable storage media of claim 10 , wherein causing the processor to determine, for each check, whether the respective service component satisfies the one or more criterion comprises causing the processor to determine whether the microservice has completed a security risk assessment survey.

15. The non-transient computer readable storage media of claim 10 , wherein causing the processor to determine, for each check, whether the respective servic

Assignees

• Atlassian Pty Ltd
• Atlassian Inc

Inventors

• Caldwell Samuel
• HILL Patrick

Classifications

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• G06F11/3604 Primary

  Analysis of software for verifying properties of programs (testing of software G06F11/3668) · CPC title

• H04L63/1433

  Vulnerability analysis · CPC title

• G06F8/20 Primary

  Software design · CPC title