EP1920357A1 - Migration et transformation de structures de donnees - Google Patents

Migration et transformation de structures de donnees

Info

Publication number
EP1920357A1
EP1920357A1 EP05784106A EP05784106A EP1920357A1 EP 1920357 A1 EP1920357 A1 EP 1920357A1 EP 05784106 A EP05784106 A EP 05784106A EP 05784106 A EP05784106 A EP 05784106A EP 1920357 A1 EP1920357 A1 EP 1920357A1
Authority
EP
European Patent Office
Prior art keywords
format
functional unit
data structure
filter
source
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP05784106A
Other languages
German (de)
English (en)
Inventor
Veit Florian Lier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LIER, VEIT FLORIAN
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Publication of EP1920357A1 publication Critical patent/EP1920357A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/84—Mapping; Conversion
    • G06F16/88—Mark-up to mark-up conversion

Definitions

  • the invention relates to a functional unit, a system, a description frame, a method for transforming a data structure, a computer program and a computer program product.
  • the functional unit according to the invention is suitable for the migration and transformation of data structures of at least one source system into data structures of at least one target system.
  • the functional unit is designed for coupling between at least one source system and at least one target system.
  • the at least one import filter is designed to transform a data structure present in a source-system-dependent format into an overall description format.
  • the at least one export filter is designed to transform the data structure present in the comprehensive description format into a target system-dependent format.
  • IT systems provide a way to store data in database systems.
  • the structure of these storage systems i. for example, the name of the tables as well as the names and specifications of these fields, such as type number, type date, etc., are commonly referred to as "data structure”.
  • data structure refers to the structure of a considered IT system, i. on the source or the target system, respectively their respective design. Accordingly, the term “data structure” encompasses not only a definition of used storage media but also a correspondingly used processing program logic as well as available input and display interfaces, a so-called user frontend and administrative design elements.
  • the core of the present invention is the migration and transformation of the design of IT systems, ie the design of the source system and the design of the target system, between different platforms and not just lent the migration of the data contained in the respective systems.
  • Data structure in the context of the present invention focuses on the structure of the design, which may also contain data in the true sense, but this need not.
  • the functional unit according to the invention can have an import filter for each source system and an export filter for each target system.
  • this is decomposed into structure elements.
  • These structural elements are checked and / or identified and then compared with structural elements stored in a configuration table. This is called “parsing" (English, for analyzing) the data structure.
  • a so-called DOM parser Document Object Model
  • New structure elements can be included in the configuration table.
  • the functional unit can expand continuously.
  • Structural elements which are classified as unidentifiable but are present in the data structure can be included in a protocol provided for such structural elements and, if necessary, analyzed and transformed by an administrator unit in an additional step.
  • a source-system-dependent or source-system-compliant structure element can be imported into a structure element of the overall description format via the import filter and then exported to a target system via the export filter. pending or target system compliant structural element are translated.
  • the comprehensive description format can also be referred to as an intersystem description format between two systems, that is, between the at least one source system and the at least one target system.
  • the comprehensive description format is to be understood as an auxiliary format, via which a transformation and migration between the source-system-dependent format and the target-system-dependent format is made possible.
  • the overall description format can therefore be regarded as a general or higher-level format under source-system-dependent and target-system-dependent formats.
  • the functional unit is in particular designed to perform at least one step of the inventive method presented below.
  • the present invention relates to a transformation system having the features of patent claim 8.
  • This transformation system is provided for the migration and transformation of data structures of at least one source system into data structures of at least one target system.
  • the transformation system has at least one source system, at least one destination system and a functional unit coupled between the at least one source system and the at least one destination system, wherein the functional unit has at least one import filter and at least one export filter.
  • the at least one import filter is designed to provide a source code that is provided by the source system.
  • the at least one export filter is designed to transform the data structure present in the overall description format into a target system-dependent format and to provide it to the target system.
  • the present invention also encompasses a description framework, a so-called framework, having the features of patent claim 9.
  • the inventive description frame is suitable for transforming and migrating a data structure of at least one source system into at least one destination system and is adapted to provide one provided by the at least one source system to represent in a source system dependent format present and transformed via at least one import filter data structure in a comprehensive description format, and to transform the data structure shown in the overall description format via at least one export filter in a target system dependent format.
  • the inventive method further provided for the migration and transformation of a data structure of at least one source system in at least one target system.
  • the data structure provided by the at least one source system and present in a source-system-dependent format is transformed via at least one import filter into a data structure which is present in an overall description format.
  • the data structure present in the overall description format is converted to at least one export filter in a format dependent on a target system present data structure transformed and provided to the at least one target system.
  • the at least one import filter and the at least one export filter are each derived from a source code by the processing frame according to the invention.
  • This source code can be generated from structural information stored in a configuration table or a configuration file.
  • the computer program with program code means according to the invention is suitable for carrying out all the steps of the method according to the invention when the computer program is executed on a computer or a corresponding arithmetic unit, in particular in the functional unit according to the invention.
  • the computer program product according to the invention with program code means which are stored on a computer-readable data carrier is designed to perform all steps of the method according to the invention when the computer program is carried out on a computer or a corresponding computing unit, in particular in the functional unit according to the invention.
  • the present invention provides a preferably software-based mutual migration solution and Transformation of data structures, such as various database systems or various computer applications on various development platforms ready.
  • the data structures are based, for example, on the XML format (Extensible Markup Language).
  • XML format Extensible Markup Language
  • a migration and transformation of database systems and computer applications across various development platforms based on XML is made possible by means of the present invention. Any other suitable format in addition to the XML format is also conceivable.
  • D 2 D-squared
  • D 2 objects The data structures presented in the general description format are referred to below as D 2 objects.
  • this data structure can be transformed again via at least one preferably dedicated export filter into a valid and compliant manufacturer-specific and system-dependent XML format for the at least one target system, so that the representation of the processing logic and the design elements are now available in a target-system-specific XML format.
  • All EDP systems can be supported, which allow a representation of their design in XML or XML dialects, such as Lotus Domino, MS Office 2003, .Net, etc., enable.
  • the description frame according to the invention referred to below as the D 2 framework, which is integrated in the functional unit, is based on a programming-language-independent and self-learning procedure for the interpretation and migration of data structures.
  • the data structures can be applications.
  • Translatable structure elements of the source-system-dependent data structure or corresponding design elements such as program code elements are identified as "positive” and do not present any problems in the context of a planned conversion.
  • non-translatable structure elements are identified as "negative” and into a for written such negative structural elements protocol provided.
  • This protocol can be edited by additional measures so that a suitable translation is provided for negatively identified structural elements and this translation is included in the configuration table for the future. If this protocol is evaluated with time and / or material costs, realistic estimates can be made for the planned changes via their aggregations.
  • the newly created data structure or application can be tested for functionality and evaluated. If no problems occurred during the migration, the source system-dependent data structure can be removed. If previously unknown code elements in the source system have been identified during the migration, these are logged in the protocol (D 2 - Log) of the functional unit. These unknown code elements or structural elements identified as "negative” can be revised and / or commented out in an evaluation of the protocol, so that a suitable translation can be assigned to these code elements or structural elements within the framework of the comprehensive description format. Now it is possible to extend the existing import and export filters and to achieve a more complete and therefore better result in another migration pass. In this way, complex migration projects can be processed in a modular and application-specific manner and automatically completed on a key date.
  • the corresponding inverse import filter is used to export the data structure. If, for example, an import filter is used for the transformation of a data structure from MS Word to D 2 , then the corresponding inverse import filter conversely serves as the export filter for the transformation from D 2 to MS Word. To do this, the import and export filters must be configured inversely to each other. Accordingly, in a preferred embodiment with an import filter and a corresponding export filter, a bidirectional transformation of a data structure which is present in a specific format dependent on a first system can be included in the general or general writing format and vice versa. This particular first system can be operated both as a source system by the import filter and as a target system by the corresponding export filter.
  • the transformation of the data structure takes place in two steps.
  • the data structure that exists in the source system-dependent format is transformed by the import filter by analysis, identification and assignment of structural elements in the overall description format.
  • This import filter can itself generate from the transferred data structure and the information that can be specified in a configuration system by processing, modifying and supplementing structural elements.
  • This import filter is thus a so-called self-learning code.
  • the information about the data structure present in the now comprehensive description format is temporarily stored in the overarching description frame of the functional unit.
  • a storage can in this case in a hierarchical class model or class System successes gen r wherein this class model is transferred to the base in the transformation or migration from the at least one source system reaped structural elements or a corresponding data structure.
  • the data structure present in the general description format can be transferred in a second step by analysis, identification and assignment of structural elements in any target system or platform for which the export filter is deposited.
  • the export filter identifies the structural elements stored in the description frame, for example litter or design elements or code blocks, and converts them into that target system-dependent format that can be interpreted by the target system. Unknown or non-existent structural elements within the target system are logged in this process for documentation purposes and carried along, these structural elements can be subsequently commented out and edited by an administrator unit and in particular translated manually.
  • computer systems can be transferred via an intermediate step of the comprehensive description frame with storage in the overall description format from a first platform or the source system to any other supported second platform or the target system.
  • the functional unit can be used, for example, to estimate the expected costs for an IT system conversion or to provide an overview of the code quality of the applications considered.
  • the functional unit according to the invention or the comprehensive description frame it is thus possible to analyze an IT infrastructure and to estimate how many percent of the data structures or applications associated with this IT infrastructure are simple, difficult or even impossible to migrate , If the results obtained from the protocol are brought into a so-called normal form, in which every unknown element is contained only once more, so that the results are clearly presented, a simple effort estimate can be derived about what a conversion to To devour resources and costs. If this estimation seems appropriate and acceptable to a user, the conversion of the original system, ie the source system, for example by replacing Word forms or Excel spreadsheets, can take place automatically via the comprehensive description frame or the functional unit.
  • a global filter or a transformation filter of the functional unit according to the invention which includes the import filter and the export filter, it is possible to develop a new platform or the target system in two steps.
  • an import filter can be created from the source system-dependent data structure or application in the overall description format.
  • a corresponding export filter for the target system-dependent data structure can be generated.
  • the processing frame from structural information which are stored in configuration tables for the respective data structures, each generates a source code from such source codes can then be derived the import and export filters. If both filters are present, this source system is integrated into the overall description frame and can be used at any time.
  • the functional unit according to the invention makes it possible to lift existing applications onto a new platform or to transform them into the target system, thereby providing a much simpler and faster conversion process.
  • the functional unit according to the invention can cover a much wider range of platforms or systems, ie source and target systems, since this is based on dynamic import filters and export filters.
  • the functional unit analyzes a recorded code and, if necessary, extends the stored configuration table.
  • This configuration table can be checked and modified by an administrator, so that the user can customize the functional unit to his needs, whereby this user decides which options are offered to him with the functional unit. Possibly occurring during the transformation or a translation of the code or a design errors are merely configuration problems and can be subsequently adapted without an update of the software support make the functional unit mandatory.
  • the user is thus able to analyze his existing infrastructure and deduce therefrom a cost estimate for the transformation and to focus on identifying obstacles.
  • the user is provided a wider range of functionality.
  • the functional unit according to the invention as well as the overarching description frame according to the invention as part of the functional unit offer the possibility of developing a global storage possibility of data structures which are present in any formats, in particular XML formats.
  • the hierarchical and possibly generalized class model may be provided in this case.
  • a number of translation filters necessary for the transformation can be considerably reduced with the functional unit or the comprehensive description frame. For example, assuming six different platforms or systems, a total of 30 transformation filters are needed for these six platforms, as each system translates into five other systems.
  • the functional unit according to the invention as a global container, which comprises the import and export filters and using the general description format, a number of the required transformation filters is reduced to two per system or platform used. Therefore, you only need one import filter and one export filter per system. Assuming a total of six platforms or systems, this functional unit has only 12 transformation filters. ter, ie six import filters and six export filters.
  • the functional unit is self-learning in that the functional unit includes new structural elements in a configuration table and independently extended programming interfaces (D 2 -API) and adapted to new conditions. Accordingly, the functional unit can automatically adapt the resulting changes to new versions of source or target data from corresponding source or target systems.
  • D 2 -API independently extended programming interfaces
  • the functional unit allows the data structure, ie a file or application, to be opened in a source-system-dependent format, for example in an XML format, and transfers the structural elements contained therein into a target system-dependent data structure and imports them automatically. Structural elements that can not be translated without error are marked accordingly and displayed in the log.
  • the user of the functional unit can derive from this protocol what and to what extent corrections have to be made before this part or application exactly meets the requirements that the original file or application had. All activities of the functional unit can be sorted, displayed and evaluated by application, user, date or type of individual steps performed in a report.
  • a user front-end or programming front-end that is used for interactive request, input, and display of data which can also be referred to as a user interface, is based on the specifications of a design study for Creation of an intuitive frontend and implements this technically possible.
  • the functional unit according to the invention is particularly suitable for users or companies that are considering an orientation in a field of computer-supported collaboration ("CSCW") or groupware.
  • CSCW computer-supported collaboration
  • a competitive situation prevailing in this market lends itself to the application of the functional unit and of the method.
  • the functional unit is suitable for companies that have a high need for support through largely automated IT tools.
  • the functional unit provides these companies with the opportunity to rethink their IT strategy against the backdrop of currently used systems, in this case source systems, and, if necessary, to improve them by converting or transforming them to more modern, more powerful systems, ie target systems.
  • the description frame according to the invention of the functional unit can be designed such that requirements of the standard "DIN EN ISO 9241 Part 10" can be taken into account in the area of a design of the user front-end and implemented as far as possible. Due to technical conditions, the following aspects can be emphasized:
  • the XML format can be used in an innovative manner with the functional unit.
  • XML was used as a data exchange format between IT systems, e.g. Web services thought.
  • the XML format can be used innovatively by using XML import and export options for replacing or setting up systems.
  • a migration is imminent, there are two options for the IT department or departments concerned: either a) a manual migration, which usually will be very time-consuming, or b) a tool-driven migration with subsequent manual check and correction. Since the aspect of quality assurance occurs in both cases, it can be neglected in a rating. If more than about 20 data structures are to be transformed as part of the IT changeover, it is advisable, from a mathematical point of view, to use the functional unit or the method according to the invention.
  • FIG. 1 shows a schematic representation of a preferred embodiment of a transformation system according to the invention.
  • FIG. 2 shows a schematic illustration of a preferred embodiment of a plane model of a functional unit according to the invention.
  • FIG. 3 shows a phase model for carrying out individual steps of a preferred embodiment of a method according to the invention.
  • Figure 4 shows a schematic representation of a preferred embodiment of a description frame according to the invention.
  • the transformation system 1 shown schematically in FIG. 1 in a preferred embodiment comprises a functional unit 3 which has at least one import filter 5, at least one export filter 7 and at least one programming interface 9 (API).
  • the functional unit 3 or the at least one export filter 7 and the at least one import filter 5 have access to various objects 11, such as tables required for transformation, in particular configuration tables or definition tables, as well as protocols.
  • a transformation and / or migration is intended with the functional unit 3 as well as with the executable by the functional unit 3 method feasible.
  • the data structure present in the source-system-dependent format 17 and provided by the source system 13 is transformed via the import filter 5 into a data structure present in an overall description format 18 and stored in the functional unit 3.
  • the data structure present in the overall descriptive format 18 is transformed via the export filter 7 into the data structure present in the target system-dependent format 19 and thus provided to the target system 15.
  • the functional unit 3 is therefore a platform and the method is a procedure for an automated transformation or migration of EDP systems via or between different platforms.
  • FIG. 2 shows a schematic representation of the procedure for an interpretation and migration of data structures or applications.
  • the basis of a description frame of the functional unit of FIG. 1 is the plane model illustrated in FIG. 2, which is designed to carry out the transformation 21 of data structures, and which has a computer application embedded in a display plane 23, a processing plane 25 with at least a global filter or a corresponding transformation filter, which has at least one import filter 24 and at least one export filter 26, and a data plane 27, which comprises the general description format 28.
  • the source system-dependent XML representation of the corresponding data structure or a source application from the source system is transferred to the overall description format 28 (D 2 format).
  • the data structure can be converted from the representation via the export filter 26 into a form for a the target system or a target platform can be transferred to an understandable target system-dependent XML representation.
  • the functional unit is adapted by constant updating to a high dynamics in the IT environment, thus new versions of a software or new design elements and thus also new XML structures can be transformed.
  • FIG. 3 shows a phase model corresponding to a process of transformation in a preferred embodiment of the method.
  • the method essentially comprises four phases or steps, namely an analysis 29, an extension 31 or an upgrade, a design 33 or a design and a transformation 35.
  • a provided source-system-dependent XML file is, for example, broken down into its structural elements or elements by means of a standard XML parser (DOM parser) in the phase of the analysis 29.
  • DOM parser a standard XML parser
  • Each identified feature or attribute, such as an XML node, and each XML attribute is compared against a configuration table.
  • the result of this check can have one of the following characteristics: a) The structure element is not yet included in the configuration table of the functional unit. b) The structural element is already included in the configuration table and in this neither as positive, ie known and translatable, nor negative, ie known and untranslatable, marked or identified.
  • the import filter logs that it is an undefined structure element, this structure element is included in a protocol provided for this purpose, so that it can be edited individually. If the structure element is contained in the configuration or definition table and marked as known and interpretable (case c), then this structure element is included in the description frame or a D 2 structure of the import filter. If the structure element has been identified as known but not translatable (case d), the import filter eliminates an associated node, in particular an XML node.
  • this point is taken up by the reference filter or a D 2 structure of the import filter.
  • Negative structural elements that are stored in the protocol provided for this purpose can be assigned an appropriate translation by an administrator.
  • the extension 31 is provided in the next phase. If the import filter encounters structures or structure elements that are not yet known to it, they are included in the configuration tables as described above. Based on the now changed configuration table, an object model of the description frame or the functional unit expands around the added structure elements and remembers these for the future. This automatically generates new object classes and integrates them into already integrated structure or code elements.
  • the source system-dependent data structure or a source file in the process step provided as draft 33 becomes a hierarchical class model based on the at least one transformation or migration Source system imported structural elements or Data structure transferred and a processing platform (D 2 platform) of the processing framework provided.
  • D 2 platform processing platform
  • the information contained in the overall description format or stored in a D 2 structure is validated against the export filter and logged as part of the transformation 35.
  • the export filter transfers the information stored in the overall description format or D 2 format into a data structure that conforms to the target system, in particular an XML file, on the basis of the new assignments and / or translation rules stored in the import and export filters.
  • An extension of the configuration table improves the import filter and export filter over time. If required, the import filter independently extends the general description format to dynamically adapt it to new situations. If new structural proposals are accepted by an administrator, they are permanently available for the future.
  • Figure 4 shows a schematic representation of the description frame 37 of the functional unit with a programming or user frontend 39, the import filter 41, the export filter 43, a class library 45, a base library 47 and a configuration table 49, the the arrows are displayed interacting by exchanging data, information and structural elements.
  • the processing framework 37 (D 2 framework) follows an object-oriented programming paradigm and uses the properties of inheritance in common programming languages through the use of classes.
  • the description frame 37 is - as far as an integration of code resources in the selected programming language is possible - language-independent.
  • DD_Base global objects can be defined and global functions can be made available. These are available in the system-dependent classes derived from the base class and use these for standard functions. From the structure information stored in the configuration table 49, the processing frame 37 automatically generates a source code for the manufacturer-specific and / or system-dependent data structure.
  • Import filter 41 and export filter 43 are then derived from this source code, which perform a corresponding transformation of data structures between different formats via the API interface stored in the class libraries 45.
  • these import filters 41 and export filters 43 Via the corresponding user front-end 39 in a selected platform, such as, for example, "Domino. Designer” in “Lotus Domino” or “Visual Studio” in “.Net Applications”, these import filters 41 and export filters 43 be addressed and adapted via the appropriately stored programming interface (API).
  • API appropriately stored programming interface
  • the base library 47 represents a base class on which all other classes build. It provides basic functions for interpreting XML files and transferring them to a class model.
  • the functional unit contains the cross-class objects required for further processing, such as a structure tree or basic XML node.
  • the XML elements identified in a base library 47 are - if not yet present - included in the configuration table 49, which serves to define the structure elements. Depending on the format, for example, "Lotus Domino", “MS Word”, etc., this creates a separate structure tree dynamically for each analyzed system or platform.
  • the functional unit and the programming interface (API) are dynamically generated from the information stored in the configuration table 49, by means of which the information stored in the D 2 structure can be displayed.
  • API programming interface
  • XML node XML node
  • class libraries 45 are generated in different programming languages and written as resources in a defined repository.
  • the import filters 41 and export filters 43 used in the method by the functional unit access and inherit the class libraries 45 from these properties and methods.
  • these functions are used to write the information from the XML file into the functional unit.
  • the information stored in the functional unit is passed to the corresponding class library 45 and rendered in a valid XML format.
  • Unknown or known, but not translatable structural elements and / or code elements are hereby recorded in protocols and thus commented out mitre. Such structural elements must and / or can be reworked manually in the target system if necessary. If there is a need to intervene in the transformation process via program code, which includes, for example, setting update information or creating technical documentation, this takes place in the selected language via the integrated programming interface (API).
  • API integrated programming interface

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'unité fonctionnelle (1) selon la présente invention de migration et de transformation de structures de données d'au moins un système source (13) en structures de données d'au moins un système cible (15) possède au moins un filtre d'importation (5) et au moins un filtre d'exportation (7). Le filtre d'importation (5) est conçu pour transformer une structure de données fournie par le système source (13) et existant dans un format (17) dépendant du système source en un format de description général (18) et le filtre d'exportation (7) est conçu pour transformer la structure de données existant dans le format de description général (18) dans un format (19) dépendant du système cible et pour fournir ladite structure au système cible (15).
EP05784106A 2005-08-30 2005-08-30 Migration et transformation de structures de donnees Withdrawn EP1920357A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2005/009340 WO2007025557A1 (fr) 2005-08-30 2005-08-30 Migration et transformation de structures de donnees

Publications (1)

Publication Number Publication Date
EP1920357A1 true EP1920357A1 (fr) 2008-05-14

Family

ID=35500821

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05784106A Withdrawn EP1920357A1 (fr) 2005-08-30 2005-08-30 Migration et transformation de structures de donnees

Country Status (4)

Country Link
US (1) US20090055421A1 (fr)
EP (1) EP1920357A1 (fr)
CN (1) CN101288072B (fr)
WO (1) WO2007025557A1 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7818665B1 (en) * 2006-06-22 2010-10-19 Advanced Micro Devices, Inc. Method and system for schema version transform verification
US8667382B2 (en) * 2006-06-28 2014-03-04 International Business Machines Corporation Configurable field definition document
CN101944128A (zh) * 2010-09-25 2011-01-12 中兴通讯股份有限公司 数据导出、导入的方法和装置
US20140122121A1 (en) 2012-10-31 2014-05-01 Oracle International Corporation Interoperable case series system
CN104035754A (zh) * 2013-03-05 2014-09-10 北大方正集团有限公司 一种基于xml的自定义代码生成方法及生成器
CN107578168B (zh) * 2017-09-05 2020-12-29 北京首钢冷轧薄板有限公司 一种用于缺陷库移植的方法、装置及电子设备
US11182174B2 (en) * 2019-02-10 2021-11-23 Hewlett Packard Enterprise Development Lp System configuration analysis for migration
CN115037610B (zh) * 2022-04-24 2023-09-22 浙江清捷智能科技有限公司 一种自动配置系统及自动配置方法

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5629846A (en) * 1994-09-28 1997-05-13 General Electric Company Method and system for document translation and extraction
US5708828A (en) * 1995-05-25 1998-01-13 Reliant Data Systems System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields
FR2742245B1 (fr) * 1995-12-08 1998-01-23 Transtar Procede de manipulation de modeles de donnees utilises en genie logiciel
US6032147A (en) * 1996-04-24 2000-02-29 Linguateq, Inc. Method and apparatus for rationalizing different data formats in a data management system
US6314429B1 (en) * 1997-10-08 2001-11-06 Mitel Corporation Bi-directional conversion library
US20020099735A1 (en) * 2001-01-19 2002-07-25 Schroeder Jonathan E. System and method for conducting electronic commerce
US6748402B1 (en) * 2001-04-02 2004-06-08 Bellsouth Intellectual Property Corporation System and method for converting and loading interactive pager address books
US7016963B1 (en) * 2001-06-29 2006-03-21 Glow Designs, Llc Content management and transformation system for digital content
US20030037031A1 (en) * 2001-08-16 2003-02-20 Birder Matthew D. Mechanism for automatically generating a transformation document
US7664795B2 (en) * 2003-09-26 2010-02-16 Microsoft Corporation Apparatus and method for database migration

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2007025557A1 *

Also Published As

Publication number Publication date
WO2007025557A1 (fr) 2007-03-08
CN101288072A (zh) 2008-10-15
US20090055421A1 (en) 2009-02-26
CN101288072B (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
DE10121790B4 (de) Softwarekonfigurationsverfahren zur Verwendung in einem Computersystem
DE69937332T2 (de) Verfahren und Gerät zur Software-Entwicklung
DE69819188T2 (de) Programmschnittstellenumsetzer für rechner mit mehreren umgebungen
DE60220662T2 (de) Methode und system zum ausgeben von xml daten basierend auf vorberechneten kontexten und einem dokument objekt modell
WO2007025557A1 (fr) Migration et transformation de structures de donnees
DE19705955A1 (de) Verfahren zum Generieren einer Implementierung eines Workflow-Prozessmodells in einer Objektumgebung
DE19960050A1 (de) Grafische Benutzerschnittstelle zur Entwicklung von Anwendungsbeispielen unter Verwendung einer Testobjektbibliothek
EP1176482A1 (fr) Méthode et logiciel pour la génération d'un système de régulation ou de commande
DE19712946A1 (de) Methode zum Generieren einer Implementierung wiederverwendbarer Teile von Containern eines Workflow-Prozessmodells
DE102005046996A1 (de) Anwendungs-generischer Sequenzdiagrammerzeuger, getrieben durch eine nicht-proprietäre Sprache
DE10308725A1 (de) System und Verfahren zum Verwalten und zum Austausch von Daten eines technischen Projektes, einer technischen Anlage sowie einzelner Anlagenkomponenten
WO2015185328A1 (fr) Procédé informatisé et successions de signaux pour un programme de réutilisation de configurations logicielles exécutables pour systèmes logiciels ainsi que système informatique et programme informatique avec code programme pour mettre en œuvre le procédé
DE102006039829A1 (de) Verfahren und Vorrichtung zur Anbringung von Anmerkungen oder Kommentaren an Bildern
EP2425331A1 (fr) Procédé de création d'un guide d'utilisation
DE69907714T2 (de) Komponentbasiertes quellcodegeneratorverfahren
DE102021116315A1 (de) Verfahren zum Zusammenführen von Architekturinformationen
DE102004009676A1 (de) Verfahren und Systeme zum Erzeugen von Unterstützungsdateien für Befehle
DE4417393A1 (de) Eine Methode zur Herstellung spezifischer Programm-Systeme und Sammlungen von Unterstützungsprogrammen (Tools) zur Erleichterung von Programmsystem-Herstellungsarbeiten
DE102016005519B4 (de) Verfahren zur Erstellung eines Metadaten-Datenmodells für eine BI-Infrastruktur
EP1202166B1 (fr) Système pour la verification de modèles de logiciels dans chaines d'outils pour developpement de logiciel
DE102015115797B4 (de) Verfahren zum Erzeugen von elektronischen Dokumenten
EP3441919A1 (fr) Procédé d'échange de données entre les outils d'ingénierie d'un système d'ingénierie ainsi que ??système d'ingénierie permettant la mise en uvre du procédé
DE69925108T2 (de) Ableitung einer objektklasse durch vererbung, instanzierung oder klonierung
EP2757466B1 (fr) Procédé implémenté par ordinateur destiné à générer du code de programme informatique
DE10233971A1 (de) Verfahren und Vorrichtung zur Erzeugung von Software

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080322

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20080606

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: LIER, VEIT FLORIAN

RIN1 Information on inventor provided before grant (corrected)

Inventor name: LIER, VEIT FLORIAN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20100611