The main reverse engineering task for this collaborative demonstration is to propose a new architecture for the SORTIE system that facilitates expected future development. In proposing the new architecture, participants will need to perform a number of sub-tasks, such as recovering the existing architecture.

Reengineering of the SORTIE system is expected (but not required) to follow the tasks outlined in Figure 1. Source code from the legacy system will be parsed to extract key information. This information will then be analysed to produce documentation and/or diagrams.

These two steps will be iterative. The reverse engineering phase will mostly involve rearchitecting the system and may be followed by a reengineering phase with some implementation to apply the changes to the source code. Teams will be expected to use the results from tools in adjacent or complementary phases.

Figure 1: Expected Reverse Engineering Process

Since we are also interested in comparing peer technologies, the actual process may be similar to that shown in Figure 2.

Figure 2:Collaboration Between Phases

The collaborative demonstration will be a longitudinal tool evaluation
involving both peer and complementary technologies. Comparisons can be made between tools in the same phase (peer technologies) and between tools in different phases (complementary
technologies). Teams will be expected to share data and information with each other (ideally using GXL, the emerging standard exchange format).

See the case study description for a description of the user requirements for this project.