DE10314832B3 - Computer software modification method with initial conversion of selected software components at modification points and delivery in mixed form for final conversion of software components on user side - Google Patents

Abstract

The method has selected components of the software (SW) expressed in source text (SC1,SC2,..SC) converted into a first XML code (CodeML) at each modification point, with delivery of the software (SW*) in mixed form and conversion of the XML code on the user side into a second XML code (CodeML*) via one or more transformations (T) for direct or indirect provision of modified software at the modification points which varies from the original software in its program sequence or program content. Also included are Independent claims for the following (a) a source code modification method; (b) a software modification arrangement; (c) a source code modification arrangement.

Description

The The invention relates to a method and an arrangement for transformation of software in which a software, in a representation in converted to a meta markup language, e.g. XML, there, transformed with XSLT, for example, and then in the meta markup language formulated transformed representation in a modified software, for example the same source language, is converted back.

Out the Internet at http://beautyj.berlios.de/ is a Java Source Code Transformation Too1 BeautyJ known to have a Java source code is converted into an XML representation using the Sourclet API, for example by inserting of spaces or changed Comments in certain places, "embellished" and then the modified source code back in Java source code can be converted. A transformation using XSLT is here For this Purpose, only suggested, but not implemented.

The The object underlying the invention is now a method and to provide an arrangement for modifying source code at a further, more flexible and efficient modification the source code is reached.

This Task is with regard to the process by the features of Claim 1 and with regard to the arrangement by the features of claim 6 according to the invention. The further claims relate to preferred embodiments of the invention.

The Invention essentially consists of selected components software, classes and / or individual fragments, as points of variation VP can serve by formulating it in a meta markup language first code (CodeML) are converted, the software is now in mixed form, i.e. compiled code and CodeML, is deployed, and the first Code CodeML provided by the customer through one or more transformations T, e.g. XSLT, only depending of transformation rules TR, the modification rules for the variation points VP included, in a second formulated in the meta markup language Code CodeML * can be converted and this second code in turn the processing sequence, either as a variation point or in a compiled form and / or the behavior of the software changes, from which it follows that distinguish the first and second software at the variation points.

The The invention is illustrated below with reference to that in drawing 1 For example closer explained. there shows

drawing 1 is an overall block diagram for explaining the invention.

In Drawing 1 is an overall block diagram to illustrate the invention, at first a software SW consisting of source text SC1, SC2 and SC into one extraditable Software SW * is converted, with some parts of the software like e.g. SC1 now as binary code / byte Code B1 available stand, and other parts such as SC2 by a CONV converter in a first formulated in a meta markup language Code CodeML are converted so that they are in the executable software SW * now form variation points VP, e.g. VP1. This software SW * can be modified before / or at runtime in a way that the code VP shown in the meta markup language, for example VP2, with a transformation T and transformation rules TR into a second in the meta markup language formulated code CodeML * is converted, which is now either as changed Variation point e.g. VP2 * is present in SW * or by a RCONV converter after the transformation T into a source code SC * and then converted into a byte code / binary code VP2B * using COMP. Differentiate in both cases SW and SW * at the points of variation and can on in this way to specific requirements (e.g. Tookit exchange, Updates, etc.).

The Codes CodeML and CodeML * or VP and VP * are for example in formulated the meta markup language XML, whereby "XML" for Extended Markup Language is there.

It is particularly advantageous that this does not have to be done by the program developer, but can be done by the suitably equipped and informed customer himself. For this an operator or administrator on the customer side only needs to apply a corresponding transformation T with the required replacement, modification and removal rules TR in order to adapt the software to his special needs or to carry out an update or patching. Up to now, problems due to inconsistencies have frequently arisen when updating or patching customer-specific ones, which can be avoided right from the start by this invention and the possibility of pipeline application or ordered sequential execution.

The Program listings in the Appendix Listing 1 to Listing 5 show this with a concrete example: Typically, one Software delivery to two different customers different Use toolkits that differ in terms of performance, price, etc. differ.

So here is a code of the original a registry class import electric.registry.Registry from one Glue Toolkit used two new "registration classes" import org.apache.axis.client.Call for the second customer and import org.apache.axis.client.Service from an Axis-Tookit use.

geschehen. Schablonen bzw. Templates werden in XSL auf das in match definierte Muster angewendet, das import-Template im Listing-Beispiel also auf alle ursprünglichen import-Anweisungen. Im konkreten Beispiel ignoriert es einfach alle ursprünglichen GlUE-Registry-Imports, und fügt stattdessen die zwei Axis-spezifischen imports ein.In XSL this can be done using, for example

happen. Stencils or templates are applied in XSL to the pattern defined in match, the import template in the listing example thus to all original import statements. In the specific example, it simply ignores all of the original GlUE registry imports and instead inserts the two Axis-specific imports.

• 1. Es ist nur ein System für Problemstellungen wie Patching, Customizing, Updating, etc. erforderlich und nicht eine Reihe verschiedener teilweise proprietärer Werkzeuge.
• 2. Das Verfahren basiert auf Standards wie XML und XSLT und ist hinsichtlich der Konvertierbarkeit in andere Programmiersprachen geringeren Beschränkungen unterworfen als andere Verfahren zur Modifikation von Quellcode.
• 3. Selbst für spezielle und komplizierte Quellcode-Modifikationen sind keine proprietären Speziallösungen erforderlich, sondern es können hierfür existierende Standards wie XSLT, XPath und XQuery genutzt werden.
• 4. Diese Art der Modifikation erlaubt die Erstellung von Hierarchien u.a. durch die Möglichkeit zur geordneten, automatisierten Hintereinanderausführung (Pipelines) mehrerer Transformationen, bspw. von Patches.
• 5. Die Transformationen können für eine allgemeine Wiederverwendung in XSLT-Dateien gespeichert werden, so daß Bibliotheken z.B. für bestimmte Abläufe entstehen können.
• 6. Es kann eine XML-Repräsentation des Quellcodes in einer XML-Datenbasis gespeichert und bei Bedarf mit Hilfe einer XSLT in einfacher Weise an die jeweiligen Kundenbedürfnisse angepasst werden (Customization).
• 7. Durch die Verwendung der Standards XMLSchema oder DTD oder entsprechende XSLTs kann der Code vorab (ohne Kompilierung), auf bestimmte Korrektheitsaspekte hin, überprüft (validiert) werden.
• 8. Übliche XML-Tools können zur einfachen Bearbeitung bzw. Visualisierung und Bestimmung von Beziehungen im Code verwendet werden.
• 9. Dauerhafte XML-basierte Programmbibliotheken, die XPath-Anfragen unterstützen, können die Wiederverwendung von Code durch besseres Auffinden eines Codes bzw. von Code-Fragmenten oder Templates verbessert werden.

The method according to the invention results in a number of additional advantages, such as:

• 1. Only one system for problems such as patching, customizing, updating, etc. is required and not a number of different, partly proprietary tools.
• 2. The method is based on standards such as XML and XSLT and is subject to fewer restrictions with regard to convertibility into other programming languages than other methods for modifying source code.
• 3. Even for special and complicated source code modifications, no proprietary special solutions are required, but existing standards such as XSLT, XPath and XQuery can be used for this.
• 4. This type of modification allows hierarchies to be created, inter alia, by the possibility of orderly, automated execution (pipelines) of several transformations, for example patches.
• 5. The transformations can be saved for general reuse in XSLT files, so that libraries can be created for certain processes, for example.
• 6. An XML representation of the source code can be stored in an XML database and, if necessary, can be easily adapted to the respective customer needs using an XSLT (customization).
• 7. By using the XMLSchema or DTD standards or corresponding XSLTs, the code can be checked (validated) in advance (without compilation) for certain correctness aspects.
• 8. Common XML tools can be used for simple editing or visualization and determination of relationships in the code.
• 9. Permanent XML-based program libraries that support XPath requests can be re-created use of code can be improved by better finding a code or code fragments or templates.

Attachment:

Listing 1: TestRegistry.java

Listing 2: TestRegistry.xjava

Listing 3: VariationPointT1.xsl

Listing 4: TestRegistry.xjava (*)

Listing 5: TestRegistry.java (*)

Claims (6)

Procedures for customizing software, - in which in advance from the manufacturer from a source code only (SC1, SC2, SC) existing original Software is a hybrid of the original software is that at least a part (SC1) of the source code in a byte or binary code (B1, .., B) compiles and at least one other part (SC2) of the source text in one in a meta markup language formulated code (CodeML) for at least one variation point (VP2, .. VP) is converted, - in which then only at least one variation point as required by the customer (VP2) the mixed form (SW) of the original software by a Transformation (T) depending of transformation rules (TR) in at least one in the meta markup language formulated other code (CodeML *) is converted and - in which the other code (CodeML *) directly a changed variation point (VP2 *) an adapted software (SW *) or from the other code (CodeML *) by a converter (RCONV) a source code (SC *) and then by means of a compiler (COMP) a binary or byte code (B *) of the changed one Variations point (VPB2) of an adapted software (SW *) formed will, being the original (SW) and the adapted software (SW *) in their program flow or Differentiate program content. The method of claim 1, wherein the transformation rules (TR) have at least one modification rule for a variation point. The method of claim 1 or 2, wherein the modification rule triggers an update to a newer software version or patching. The method of claim 1 or 2, wherein the modification at least one point of variation (VP) through the transformation done at runtime. Method according to one of the preceding claims, the programming language of the Java source code and the meta markup language the variation points is XML and the transformation and the rules are described using XSLT and XSL. Arrangement for customization of software, according to the method of claim 1 - in which a mixed form of original software is available such that at least a part (SC1) of a source text compiles into a byte or binary code (B1, .., B) and at least one further part (SC2) of the source text has been converted into a code (CodeML) formulated in a meta markup language for at least one variation point (VP2, .. VP), - In which a device for transformation (T) is provided such that only at least one point of variation (VP2) of the mixed farm (SW) of the original software is transformed into at least one in the transformation (T) depending on transformation rules (TR) Meta markup language formulated other code (CodeML *) is convertible, whereby the other code (CodeML *) directly forms a modified variation point (VP2 *) of an adapted software (SW *) or from the other code (CodeML *) by a converter ( RCONV) a source code (SC *) and then by means of a compiler (COMP) a binary or byte code (B *) of the changed variation point (VPB2) of an adapted software (SW *) can be formed and the original (SW) and the Distinguish adapted software (SW *) in their program flow or program content.