Academia.eduAcademia.edu

Figure 4 – uploaded by Andreas Hoffmann

See full PDFdownloadDownload figure
As depicted in Fig. 4, the FARCclientGUI is replaced by a test component. The test component is connected to the FARCmodel by means of the two _ interfaces FARCmodelView and FARCclientFeedback (c.f. Fig. 5).

Figure 4 As depicted in Fig. 4, the FARCclientGUI is replaced by a test component. The test component is connected to the FARCmodel by means of the two _ interfaces FARCmodelView and FARCclientFeedback (c.f. Fig. 5).

Related Figures (6)

Figure 1. Logical view of refactored FARC.
Figure 1. Logical view of refactored FARC.
Figure 2. RTE Space Methodology Overview. For test modeling the same abstraction in terms of platform-independent and platform-specific modeling can be applied as known from system modeling. In general, our approach uses both platform-independent and _platform- specific tests to validate the modernized system. The platform-independent model resulting from the code and model abstraction process is the starting point for the test development. It is used for the derivation of a platform- independent test model (PIT). proposes to base the modernization activities on the architectural models rather than code artifacts. Currently, the reverse engineering methods and tools (SOFTEAM Objecteering, IBM RSA/RSM, BORLAND Together) allow to obtain a UML model, which is usually referred to as Platform-Specific Model since it is very close to the code. In order obtain the PIM a specific PSM-to-PIM transformation method is required.
Figure 2. RTE Space Methodology Overview. For test modeling the same abstraction in terms of platform-independent and platform-specific modeling can be applied as known from system modeling. In general, our approach uses both platform-independent and _platform- specific tests to validate the modernized system. The platform-independent model resulting from the code and model abstraction process is the starting point for the test development. It is used for the derivation of a platform- independent test model (PIT). proposes to base the modernization activities on the architectural models rather than code artifacts. Currently, the reverse engineering methods and tools (SOFTEAM Objecteering, IBM RSA/RSM, BORLAND Together) allow to obtain a UML model, which is usually referred to as Platform-Specific Model since it is very close to the code. In order obtain the PIM a specific PSM-to-PIM transformation method is required.
ABLE I. CODE MIGRATION STATISTICS Tab. 1 presents the code migration statistics. The key result is that more than 70% of cases were rather simple to migrate with predefined rules. For these cases, we believe that the automatic translation from C++ to Java might be considered, while for the rest about 30% cases manual code re-writing was possible only.
ABLE I. CODE MIGRATION STATISTICS Tab. 1 presents the code migration statistics. The key result is that more than 70% of cases were rather simple to migrate with predefined rules. For these cases, we believe that the automatic translation from C++ to Java might be considered, while for the rest about 30% cases manual code re-writing was possible only.
Figure 3. General approach for testing campaign.
Figure 3. General approach for testing campaign.
The FARCmodel is considered to be the system under test (SUT). The communication between the components is based on XML encoding on top of CORBA communication and encoding. Even though the FARCserver is not directly connected to the test component, it is implicitly tested due to the hidden communication between the FARCmodel and the FARCserver when the FARCmodel is contacted by the test component.
The FARCmodel is considered to be the system under test (SUT). The communication between the components is based on XML encoding on top of CORBA communication and encoding. Even though the FARCserver is not directly connected to the test component, it is implicitly tested due to the hidden communication between the FARCmodel and the FARCserver when the FARCmodel is contacted by the test component.
Figure 6. Test specification “Add File Definition”.
Figure 6. Test specification “Add File Definition”.
Related topics:
Computer ScienceComputer ArchitectureObject Oriented ProgrammingSoftware MaintenanceConfiguration ManagementUnified Modeling Language
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved