Automatically evaluating application architecture through architecture-as-code

1. A system, comprising:

one or more processors;

a system of record (SoR) in communication with the one or more processors;

a rules engine in communication with the SoR;

an output engine in communication with the rules engine;

memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to:

receive, at the rules engine, machine-readable code describing interactions among a plurality of applications in a software architecture;

evaluate, with the rules engine, compliance of the interactions among the plurality of applications according to the SoR;

identify, with the rules engine, and based on compliance evaluation, one or more dependencies among the plurality of applications;

generate, with the output engine, a system context diagram image comprising a graphical representation of the plurality of applications with associated interactions and dependencies; and

output, for display, the system context diagram image.

2. The system of claim 1 , wherein the machine-readable code describes dynamic software architecture interactions among the plurality of applications.

3. The system of claim 1 , wherein the machine-readable code is in a YAML format.

4. The system of claim 1 , wherein the rules engine utilizes authoritative data stored in the SoR to evaluate the compliance of the interactions among the plurality of applications against corporate standards or resiliency risks.

5. The system of claim 1 , wherein the instructions further cause the rules engine to evaluate and identify one or more critical dependencies among the plurality of applications.

6. The system of claim 5 , wherein the instructions further cause the output engine to generate unique graphical representations of the one or more critical dependencies.

7. The system of claim 5 , wherein the instructions further cause the rules engine to:

determine similarities among the critical dependencies;

pool similar critical dependencies; and

store the pooled similar critical dependencies in a repository.

8. The system of claim 5 , wherein the instructions are further configured to cause the rules engine to determine an overall risk score for the software architecture by computing a weighted average of each field of the machine-readable code associated with the one or more critical dependencies according to one or more of a dependency type and a dependency severity.

9. The system of claim 1 , wherein the output engine is configured to generate a graphical representation of network traffic associated with one or more of the plurality of applications.

10. The system of claim 1 , wherein the output engine is configured to generate a graphical representation of a resiliency risk for the software architecture.

11. The system of claim 1 , wherein the instructions are further configured to cause the one or more processors to:

output for display, a menu of one or more options for compliance remediation of the plurality of applications; and

remediate the machine-readable code automatically according to a selected option.

12. A method, comprising:

receiving, at a rules engine, machine-readable code describing interactions among a plurality of applications in a software architecture;

evaluating, with the rules engine in communication with a system of record (SoR), compliance of the interactions among the plurality of applications according to the SoR;

identifying, with the rules engine and based on the evaluating, one or more dependencies among the plurality of applications;

generating, with an output engine, a system context diagram image comprising a graphical representation of the plurality of applications with associated interactions and dependencies; and

outputting, for display, the system context diagram image.

13. The method of claim 12 , wherein the machine-readable code describes dynamic software architecture interactions among the plurality of applications.

14. The method of claim 12 , wherein the machine-readable code is in a YAML format.

15. The method of claim 12 , wherein the rules engine utilizes authoritative data stored in the SoR for evaluating the compliance of the interactions among the plurality of applications against one or more of corporate standards and resiliency risks.

16. The method of claim 12 , further comprising evaluating and identifying one or more critical dependencies among the plurality of applications.

17. The method of claim 16 , further comprising generating unique graphical representations of the one or more critical dependencies.

18. The method of claim 16 , further comprising:

determining similarities among the critical dependencies;

pooling similar critical dependencies; and

storing the pooled similar critical dependencies in a repository.

19. The method of claim 16 , further comprising determining an overall risk score for the software architecture by computing a weighted average of each field of the machine-readable code associated with the one or more critical dependencies according to one or more of a dependency type and a dependency severity.

20. A non-transitory computer-readable storage medium storing instructions that are configured to cause one or more processors to perform a method of:

receiving, at a rules engine, machine-readable code describing interactions among a plurality of applications in a software architecture;

evaluating, with the rules engine in communication with a system of record (SoR), compliance of the interactions among the plurality of applications according to the SoR;

identifying, with the rules engine and based on the evaluating, one or more dependencies among the plurality of applications;

generating, with an output engine, a system context diagram image comprising a graphical representation of the plurality of applications with associated interactions and dependencies; and

outputting, for display, the system context diagram image.