Background for the header
To the home page of the University of Antwerp



Project 2009: make Tyrant multilingual


Tyrant is a game of heroic adventure, where you pit your wits and cunning against a fearsome array of monsters and ̃endish puzzle in your attempt to gain fame and fortune.

Tyrant is a graphical Roguelike fantasy adventure game in the tradition of many other great games such as the original Rogue, Nethack, Angband and ADOM. It features intricate randomly generated landscapes, towns and dungeons. These games emphasize addictive gameplay and randomly generated universes to create an immersive and imaginative game that looks deceptively simple yet contains a great deal of detail and strategic depth.

It is written in Java with a highly extensible game engine.


As a reengineering team, you are asked to restructure the architecture and implementation of Tyrant such that Tyrant can easily be released as a multilingual game.

Thus, the choice of the natural language for the GUI and the messages to the user of a certain Tyrant-release, should become an implementation detail.

More specifically, we ask you to perform the following activities, and report about these in your project report:

[Design recovery]

  1. Describe the current design of the implementation of Tyrant. Clearly indicate how this design is located in the architecture of the project.


  1. Compose a generic design that describes how the userinterface functionality can be extracted from the current design, and that gives insight in how the design handles the interaction with the user. This interface should clarify that the choice for a specific language to communicate with the user is merely an implementation detail. It will be necessary to redesign the test suite in such a way that it can cope with a multilingual game.

  2. [Management]

    1. Estimate the effort required for (i) refactoring towards the new userinterface; and (ii) changing/extending the tests.


    1. Refactor the current implementation of Tyrant such that it can handle multilinguality.

    2. Adjust/extend the tests of the project to preserve their effectiveness and coverage during and after refactoring.

You will be required to perform a number of techniques presented during the lab sessions. These are:

  • Analyse:
    • Duplicated Code Analysis
    • Mining Software Repositories
    • Metrics and visualization
  • Restructuring:
    • Testing
    • Refactoring

This project emphasizes the sound, systematic analysis of the presented problem, the associated solution space and the chosen solution(s). The software reengineering sessions are composed in such a way as to prepare you for such a project. We stimulate you to assess the benefits and drawbacks of the techniques presented in the lab sessions, and ask you to exploit the analysis techniques wisely. You are free to use alternative analysis techniques.

What concerns the refactoring-part, we emphasize the use of tests. Our minimum requirements are:

  • Determine the extent to which the current tests provide feedback on your future refactoring-steps. Quantify this.
  • Compose an argument discussing why the tests are (in)adequate for your chosen refactoring scenario, and adjust the tests in case this is required. Be efficient with regard to the time invested in testing.


To show that you have passed the assignment, you will have to demonstrate the following:

  • You have made a selection of analysis techniques (e.g., duplicated code analysis, mining software repositories, metric and visualization as seen in the lab sessions, but others are allowed as well), and have applied these techniques in a sound, systematic manner. You have indicated clearly (using screenshots, results of the interpretation of the output of the techniques) how you have used the results of these analysis techniques.

  • You have performed the above 5 activities (decomposed into (i) Design Recovery; (ii) Design; (iii) Management; and (iv) Refactoring) and discussed them in your project report.

  • The restructurings you have applied are behavior preserving.

    • You can demonstrate the mapping between each of the classes from the original structure with the new structure.
    • The compilation process succeeds flawlessly.
    • The tests run without flaws, and demonstrate clearly that the new userinterface is implemented correctly.

  • The introduction of the new design clearly indicates the project is ready to be released in a language of choice. You are not supposed to carry out the refactoring process completely. Select and execute a set of refactorings that sufficently illustrate your proposed solution.


Aspects that we typically like to see addressed in the report are:

  • Context: Briefly discuss the context in which you are running your project.
  • Problem at hand: Clarify the problem at the base of the project, and indicate its intrinsic difficulties.
  • Project management: Demonstrate how you have organized the work, and how you are controlling it (instead of the work controlling you!)
    • Scope: What are the boundaries of your project? What is not included in the project?
    • Risks: Which risks were envisioned, and which have been mitigated? What is the priority of the risks that still need to be migitated? E.g., which external dependencies might have an affect on your outcome? Which alternatives have you prepared in case this risk instantiates?
  • Software reengineering:
    • Tests: How can you verify that you satisfy the requirements? Which testing strategy have you selected, and what are the arguments for this selection? How confident are you that your solution satisfies the requirements?
    • Quality assurance: What are the non-functional requirements? E.g., how do you differentiate between a good and a bad solution?


Two UA-students started in 2005 with refactoring Tyrant in order to seperate the engine from the GUI. They documented their findings and committed an (incomplete?) version of their report to a branch in the CVS repository. You can consider their work as available documentation. But as good software reengineers you should validate their findings before using them in your own reengineering process.

Note: similar to previous years, it is once again possible to submit your own project proposals. These proposals will be approved in case they provide a well-structured exercise on the reengineering techniques presented in the lab sessions. E.g., you can always propose to reengineer another software system, for instance the software system used in your thesis, or written for another case.


Valid HTML 4.01! Valid CSS!

 Lab On REengineering - Antwerpen, last modified 15:56:17 05 June 2009