View source for 20240045756. Structured Software Delivery And Operation Automation simplified abstract (Dynatrace LLC)

=Structured Software Delivery And Operation Automation=


==Organization Name==

[[:Category:Dynatrace LLC|Dynatrace LLC]]


[[Category:Dynatrace LLC]]

==Inventor(s)==

[[:Category:Alois Reitbauer of Linz (AT)|Alois Reitbauer of Linz (AT)]][[Category:Alois Reitbauer of Linz (AT)]]

[[:Category:Dirk Wallerstorfer of Linz (AT)|Dirk Wallerstorfer of Linz (AT)]][[Category:Dirk Wallerstorfer of Linz (AT)]]

[[:Category:Andreas Grabner of Linz (AT)|Andreas Grabner of Linz (AT)]][[Category:Andreas Grabner of Linz (AT)]]

==Structured Software Delivery And Operation Automation - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240045756 titled 'Structured Software Delivery And Operation Automation

==Simplified Explanation==

The abstract describes a system and method for automating the delivery and operation of software functionality. It proposes using a declarative notation approach to describe automation sequences independently from specific automation tools and services. An automation service abstraction layer is introduced to hide the characteristics of concrete automation services from the automation definition layer. This allows for transparent changes or updates to automation services without affecting the automation sequences that use them. For operation automation, the system can be combined with monitoring systems that identify critical changes in operating conditions and their root causes. Upon notification of a critical change, the system can automatically apply remediation actions to counteract the identified root cause changes.

* The system proposes a declarative notation approach for describing automation sequences independently from specific automation tools and services.
* An automation service abstraction layer is introduced to hide the characteristics of concrete automation services from the automation definition layer.
* The system allows for transparent changes or updates to automation services without affecting the automation sequences that use them.
* For operation automation, the system can be combined with monitoring systems to identify critical changes in operating conditions and their root causes.
* The system can automatically apply remediation actions upon notification of a critical change to counteract the identified root cause changes.

== Potential Applications ==
* Automation of software delivery and operation processes
* Streamlining and standardizing automation sequences across different automation tools and services
* Efficient and transparent updates or changes to automation services without disrupting existing automation sequences
* Automated remediation of critical changes in operating conditions

== Problems Solved ==
* Incompatibility and dependency issues between automation sequences and specific automation tools or services
* Difficulty in updating or changing automation services without affecting existing automation sequences
* Manual identification and remediation of critical changes in operating conditions

== Benefits ==
* Simplified and standardized automation processes
* Flexibility to change or update automation services without disrupting existing automation sequences
* Efficient identification and remediation of critical changes in operating conditions
* Improved reliability and stability of software functionality delivery and operation


==Original Abstract Submitted==

a system and method for the structured automation of the delivery and operation of software functionality is proposed. a declarative notation approach is used to describe automation sequences independently from concrete automation tools and services that may be used to execute the automation sequences. an automation service abstraction layer is introduced that hides concrete automation service characteristics from the declarative automation definition layer. the service abstraction layer enables a transparent change or update of concrete automation service without affecting automation sequences that use the corresponding service abstractions. for operation automation, the automation execution may be combined with causation-capable monitoring systems that both identifies critical changes of operating conditions for which automated remediation is indicated and corresponding root cause changes for those critical changes. the remediation automation may, on notification of such a critical change, identify and apply remediation actions that counteract the identified root cause changes.



[[Category:G06F11/07]]
[[Category:G06F11/34]]
[[Category:G06F11/30]]
[[Category:G06F8/35]]