Understanding the scope and nature of a set of changes and the cascading impact of the changes on a system is difficult because most systems have a network of tightly-coupled internal subsystems. A change or set of changes made to one or more of the subsystems usually involves changing other related subsystems. Furthermore, changes are often in a format that is convenient for machines to process but that is not easily understandable by humans.
One or more sets of system changes can be parsed, analyzed and transformed from a machine friendly form into a natural language presentation such as a report or display that can be understood by a human. The report or display can be persisted. It can be customized for a particular environment, user interface culture or user profile (e.g., database administrator, developer, executive, etc.). It can be custom formatted. It can calculate performance indicators for the system. The report or display can provide information concerning the nature and scope of the changes. It can provide a targeted impact analysis of application of the changes on a system. It can identify domain-specific performance indicators. A domain can be a database domain, a virtual runtime environment domain, a native runtime environment domain, a program development domain or any other application or business area.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In the drawings:
a illustrates an example of a system 100 that provides human-consumable information associated with the impact of application of one or more sets of changes on a system in accordance with aspects of the subject matter disclosed herein;
b illustrates an example of a system 112 that converts a set of changes comprising imperative commands into declarative definitions in accordance with aspects of the subject matter disclosed herein;
c illustrates a more detailed example of the system of
d illustrates an example of a usage pattern in accordance with aspects of the subject matter disclosed herein;
e illustrates an example of a report or display in accordance with aspects of the subject matter disclosed herein;
One or more sets of changes to a system of interconnected subsystems can be parsed, analyzed and transformed from a machine-consumable form into a human-consumable presentation such as a natural language report or display. The changes can be in any form including but not limited to declarative definitions and imperative commands.
A declarative change defines the change itself, that is, the declarative change defines the desired state. For example, in a database domain, a declarative change can be “Create a table, Table 1, having Columns A and B”. The present or current state of the system does not need to be known. In a declarative environment, the imperative commands that have to be applied to the system to reach the state specified by the declarative change can be programmatically computed.
In contrast, an imperative change in the database domain can be “Alter Table 1, Add Column C”. The state of the system has to be known so that the commands needed to get the system to a desired state can be correctly developed. For example, attempting to add a Column C to a table that already has a Column C will likely result in an error. Hence, typically imperative changes are specific to a particular target environment whereas declarative changes are not. In a declarative environment, the system can compare the declarative definitions of the source state (e.g., state A) and the target state (e.g., state B) to determine an imperative plan to move the system from state A to state B.
The report or display can be customized to include domain-specific performance indicators. The report or display can be customized for any user interface environment. The report or display can be customized for any user profile. Statements in the report or display can be related back to one or more changes in the set or sets of changes. Repercussions or results of any particular change on one or more subsystems within the system can be provided in absolute terms. Repercussions or results of any particular change on one or more subsystems within the system can be provided relative to a particular target system, subsystem or environment. The usage pattern (a repeatable set of acts) of running change sets in imperative commands over a clone of a target system can be provided. The resulting state of the cloned system can be compared to the original system. Reverse engineering can be used to determine the declarative equivalent of a set of changes. The changes themselves and the effect of the changes can be described in a natural language report or display. This paradigm can be used to generalize changes meant for one target environment to other target environments.
A snapshot of a running system can be taken before applying the one or more sets of changes. The changes can take the form of imperative commands to the system. After the changes are applied to the system, the state of the system can be compared to the snapshot. Reverse engineering can be used to determine the declarative equivalent of the changes. The changes can be described in a report or display. This paradigm can be used to furnish a post mortem report. The change reports can be logged along with corresponding change sets in source control and version tracking systems. Two versions of the target system (the proxy before update and the proxy after update) can be used to determine the delta by reverse engineering. An analysis report or display can be provided. This paradigm can be used to create email notification systems per change set or for a specified period of time.
System 100 may include one or more computers or computing devices such as a computer 102 comprising: one or more processors such as processor 141, etc., a memory such as memory 143, and a telemetry system such as telemetry system 104. The telemetry system may receive one or more sets of changes such as set of changes 106, etc. and a target system such as target system 108 and generate a display or report such as display/report 110. Set of changes 106 can be a source model. (For example, for a source model of a database that includes two tables, the set of changes can be the definitions of the two tables, e.g., Table 1 having Columns A, B and C and Table 2 having Column D.) When a change set comprises declarative definitions, the state of the target system 108 does not need to be known. The set of imperative commands needed to place the target system into the desired state (the state in which two tables exist, Table 1 having Columns A, B and C and Table 2 having Column D) can be computed. The system can be a running system or a representation of a system such as but not limited to a snapshot or a source code project, scripts, output artifact, diagram or any description of intent.
Imperative commands can be converted to declarative definitions as illustrated in FIG. lb. System 112 can comprise a portion of system 100. System 112 can include an update engine 120 that receives one or more imperative commands as a change set 114 comprising imperative commands and can apply the one or more imperative commands to a target environment runtime proxy such as proxy system 116 to generate an updated system 118. System 112 can include a reverse engineering program module or component such as reverse engineering module 122. Change set 114 is specific for a particular target. That is, the state of the target system has to be known in order to generate a correct set of imperative commands. For example, consider an imperative command, “Add Column C to Table 1”. To successfully add Column C to Table 1, the system has to know that Column C does not already exist in Table 1.
The imperative commands of the imperative change set can be converted to declarative definitions by applying the following usage pattern. A reverse engineering snapshot of the running system can be taken. The snapshot can be used as the source model (e.g., proxy system 116). The imperative changes (e.g., imperative set of changes 114) can be applied to the proxy system to create the mutated target model, updated system 118. The reverse engineering module 122 can compare the source model and the target model to compute a set of declarative definitions. That is, the reverse engineering module 122 can receive the source model (e.g., proxy system 116) and the updated system 118 and reverse engineer the state of the updated system 118 to produce the set of changes in the form of declarative definitions such as declarative definitions 123.
Referring now to
The source model 132 and the target model 134 can be compared by a model comparer 136. The model comparer 136 can create a delta model such as delta model 138. Delta model 138 can represent the differences between source model 132 and target model 134. To continue with the example used herein, the delta model in the example provided would contain a definition for Table 1, Column C. The delta model 138 can be used to comprehend the changes intended to be made from source change set to target environment. Pre-written domain specific introspective rules can be run on the delta model and target model by the impact analyzer to prepare the change and impact analysis. That is, the impact analyzer such as impact analyzer 140 can access the source model (e.g., source model 132), the target model (e.g., target model 134) and the delta model (e.g., delta model 138). The impact analyzer 140 can comprise domain-specific code that determines the impact of the changes represented in the delta model. Now suppose, for example, the original system has Table 1 with Columns A, B and C. Suppose the change represented in the change set removes Column C from Table 1. The impact analyzer can compare the target model that has Column C with the delta model that does not have Column C and can determine that the data in Column C will be lost.
An update planner such as update planner 142 can access the source model 132, the target model 134 and the delta model 138 to generate an update plan such as update plan 144. The update plan can add additional changes to other subsystems affected by the original set of changes. For example, an update plan for adding Column C to Table 1 can be the imperative commands Alter Table 1, Add Column C to Table 1. Because the update plan is domain specific, the update plan can also include dropping the index and rebuilding it. The impact analyzer and the update planner can be separate or can be combined into a single program module or component. A report generator such as report generator 146 can receive the update plan 144, source model 132 and target model 134. The report generator can serialize the update plan and can convert the format of the update plan to a form that is able to be readily understood by humans. The language in which can the report is provided can be in a language localized for the user (e.g., in German for a German user, etc.)
The report generator 146 can include one or more program modules or components comprising a report analyzer. The report analyzer can be used to categorize the operation of domain-specific interests. Common interests include but are not limited to: potential long running operations, potential data loss operations, operations that touch sensitive objects and/or any other domain specific rules or patterns. The report generator can include one or more program modules or components comprising a custom formatter that can format the report for human consumption.
d illustrates an example illustrating change over time in accordance with aspects of the subject matter disclosed herein. FIG. ld system 160 illustrates a source code project 162 and a target system 164 that are potential inputs to the telemetry system 104. Source code project 162 can be deployed at time 0 (t0) to a target system 162. At this point the source code project 160 and the target system 162 represent the same system. For example, the source code project 162 and the target system 164 both define Table 1 having Columns A and B. Now suppose that changes are made to the source code project, but the changes have not been deployed to target system 164, represented in
e illustrates an example of a report that can be generated by the report generator 146. A report such as report 150 can include a Highlights section such as Highlights section 152, a Warnings section such as Warnings section 154, a User actions section such as User actions section 156 and a Supporting actions sections such as Supporting actions section 158. Suppose the report 150 describes a set of changes that change the datatype of a Column, Column C in a database table, Table 1. The User actions section of the report can provide information associated with the set of changes that describes the user actions taken that change a system from a first state to a second state. For example, User actions section 156 of report 150 indicates that the Customers Table of Database X has been altered. The Highlights section of the report can provide information associated with the effects of the user-initiated changes. For example, Highlights section 152 can indicate the implications of the user action. Highlight section 152 indicates that the alteration made to the Customers Table changes the datatype for the Customer Name Column from 40 characters to 15 characters and that data loss could occur. (Customer names that are longer than 15 characters will be truncated to 15 characters.) The Warnings section of the report can provide information associated with the set of changes that describes potential undesirable effects of the changes. For example, Warnings section 154 warns that the alteration made to Customers Table changes the datatype for the Customer Name Column from 40 characters to 15 characters and that data loss could occur. The Supporting actions section identifies dependencies and additional changes that have to be made (e.g., to subsystems) as a consequence of making the user-initiated changes. For example, Supporting actions section 158 indicates that because the length of Customer Name has changed, the existing index that includes or points to Customer Name will have to be rebuilt. The existing Index will be discarded or dropped and a new Index will be created (the Index will be rebuilt) to reflect the 15 character Customer Names. The multi-staged solution described herein can increase the granularity of information that can be collected for analysis and reporting. Because discrete acts work on distinct input and output, a pluggable and extensible architecture is possible. Additional acts can be added. Existing actions can be improved without affecting other parts of the telemetry system.
At 202 a target system or a reference to a target system is received by a telemetry system. The telemetry system can also receive one or more sets of changes that can be applied to the target system. The one or more change sets can be a set of declarative definitions. The one or more sets of changes can be in the form of imperative commands. If one or more of the changes are imperative commands, the imperative commands can be converted to declarative definitions as described above with respect to
In order to provide context for various aspects of the subject matter disclosed herein,
With reference to
Computer 512 typically includes a variety of computer readable media such as volatile and nonvolatile media, removable and non-removable media. Computer storage media may be implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CDROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other transitory or non-transitory medium which can be used to store the desired information and which can be accessed by computer 512.
It will be appreciated that
A user can enter commands or information into the computer 512 through an input device(s) 536. Input devices 536 include but are not limited to a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, and the like. These and other input devices connect to the processing unit 514 through the system bus 518 via interface port(s) 538. An interface port(s) 538 may represent a serial port, parallel port, universal serial bus (USB) and the like. Output devices(s) 540 may use the same type of ports as do the input devices. Output adapter 542 is provided to illustrate that there are some output devices 540 like monitors, speakers and printers that require particular adapters. Output adapters 542 include but are not limited to video and sound cards that provide a connection between the output device 540 and the system bus 518. Other devices and/or systems or devices such as remote computer(s) 544 may provide both input and output capabilities.
Computer 512 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computer(s) 544. The remote computer 544 can be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 512, although only a memory storage device 546 has been illustrated in
It will be appreciated that the network connections shown are examples only and other means of establishing a communications link between the computers may be used. One of ordinary skill in the art can appreciate that a computer 512 or other client device can be deployed as part of a computer network. In this regard, the subject matter disclosed herein may pertain to any computer system having any number of memory or storage units, and any number of applications and processes occurring across any number of storage units or volumes. Aspects of the subject matter disclosed herein may apply to an environment with server computers and client computers deployed in a network environment, having remote or local storage. Aspects of the subject matter disclosed herein may also apply to a standalone computing device, having programming language functionality, interpretation and execution capabilities.
A user can create and/or edit the source code component according to known software programming techniques and the specific logical and syntactical rules associated with a particular source language via a user interface 640 and a source code editor 651 in the IDE 600. Thereafter, the source code component 610 can be compiled via a source compiler 620, whereby an intermediate language representation of the program may be created, such as assembly 630. The assembly 630 may comprise the intermediate language component 650 and metadata 642. Application designs may be able to be validated before deployment.
The various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus described herein, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing aspects of the subject matter disclosed herein. As used herein, the term “machine-readable medium” shall be taken to exclude any mechanism that provides (i.e., stores and/or transmits) any form of propagated signals. In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. One or more programs that may utilize the creation and/or implementation of domain-specific programming models aspects, e.g., through the use of a data processing API or the like, may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.