Comparison of interfaces between software components

• US 8,707,255 B2
• Filed: 03/23/2006
• Issued: 04/22/2014
• Est. Priority Date: 03/24/2005
• Status: Expired due to Fees

• Current Assignee: Dspace Digital Signal Processing And Control Engineering Gmbh
• Original Assignee: Dspace Digital Signal Processing And Control Engineering Gmbh
• Inventors: Niggemann, Oliver, Stroop, Joachim, Otterbach, Rainer, Hanselmann, Herbert
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): NGUYEN, DUY KHUONG THANH
• Application Number:
  US11/909,594
• Publication Number:
  US 20090144704A1
• Time in Patent Office: 2,952 Days
• Field of Search: 717/107, 717/120
• US Class Current: 717/107
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

The invention relates to a method for testing the compatibility between two software components of a control device network, a technical interface description being assigned to each software component, this interface description having a specified description standard, and each description standard having a hierarchical position in an hereditary hierarchy of all possible description standards. The common description standard, which is nearest in the hereditary hierarchy, of the software components to be compared is determined based on the hereditary hierarchy, and the common portion of the respective interface descriptions is determined based on the common description standard of the common portion of the respective interface descriptions and compared with one another.

Claims

1. A method to test compatibility between two software components of a network of control devices, with each software component having at least one corresponding technical interface description that comprises at least one value describing at least one feature of the software component, said technical interface description conforming to a certain description standard, said description standard specifying the at least one feature described in the least one corresponding technical interface description, comprising:

providing each description standard with a hierarchic position in a hereditary hierarchy of description standards, wherein the hereditary hierarchy is formed such that each description standard specifies every feature specified by its hierarchic next higher description standard, and further specifies at least an additional feature;

determining, based on the hereditary hierarchy, the closest common description standard in the hereditary hierarchy in reference to the software components to be compared;

based on the closest common description standard, determining and comparing the values, in the respective technical interface descriptions, that describe the common features of the corresponding software components to each other; and

reporting to the user when the value of a feature reveals an incompatibility between the software components to be compared, wherein software components of the control device network are composed via a particular graphic network design tool, where an interface manager necessary for a comparison is determined and executed depending on the hereditary hierarchy during the operation of the network design tool.

2. The method according to claim 1, wherein the interface descriptions or the software components of the network of control devices to be compared are compared based on determinations in the closest common description standard.

3. The method according to claim 1 wherein an interface description of a software component of the network of control devices describes the technical features offered by the software component and/or the technical features requested.

4. The method according to claim 3, further comprising:

comparing whether the requested abilities of an interface are fulfilled by the offered abilities of another interface.

5. The method according to claim 1 wherein description standards of interface description previously not allocated in the hereditary hierarchy are changed for an allocation and expansion of the hereditary hierarchy such that they have a portion in common with the existing hereditary hierarchy.

6. The method according to claim 1,

wherein each description standard of the hereditary hierarchy is allocated to the interface manager used for comparing two interface descriptions, the interface manager being selected from the closest common description standard of two interface descriptions.

7. The method according to claim 1 wherein a description standard of an interface description not having any portion equivalent to a description standard of the hereditary hierarchy is transformed via a transformer into a description standard, having a portion equivalent to a description standard of the hereditary hierarchy.

8. The method according to claim 1 wherein an interface description with a first description standard not having any portion equivalent to the description standard of the hereditary hierarchy is compared via a special interface manager to another interface description, with the interface manager temporarily transforming the first description standard such that both description standards have, at least during the comparison, a common closest description standard to the interface description to be compared to.

9. A method for testing the compatibility of a first software component with a second software component, each software component having at least one corresponding technical interface description that comprises one or more values describing one ore more features of the software component, each technical interface description having a corresponding description standard that specifies at least one feature described in the corresponding technical interface description, the method comprising:

forming a hereditary hierarchy of description standards such that each description standard specifies all of the features specified by its hierarchic next higher description standard and further specifies at least one additional feature;

determining the position to the hereditary hierarchy of a first description standard that corresponds with a first technical interface description of the first software component;

determining the position in the hereditary of a second description standard that correspond with a second technical interface description of the second software component;

traversing up the hereditary hierarchy of description standards to determine a third description standard that is the closest common description standard in the hierarchy connected to both the first description standard and the second description standard;

identifying the features of the third description standard as features that are common to the first and second technical interface descriptions;

for each feature specified in the third description standard, comparing the corresponding values of the first and second software components technical interface descriptions of that feature to determine compatibility of the first and second software components with regard to that feature; and

based on that comparison, reporting to the user when the value of a feature reveals an incompatibility between the first and second software components,

wherein software components of the control device network are composed via a particular graphic network design tool, where an interface manager necessary for a comparison is determined and executed depending on the hereditary hierarchy during the operation of the network design tool.