The audit of an information system helps to reveal drawbacks of its architecture or implementation. At the same time it extends the system with a documantion that is naturally created during the audit. The point and the strength of an audit is in well-known but often disregarder fact - an independent observer with no personal feeling for the system can find weeknesses more efficiently. And what is our idea of the audit work-flow? It should evolve along the following sequence of steps
  1. Understanding the company culture - through discussions with the project leaders we will understand the metodologies, techniques, specialities and rules used locally to develop software. Without such a knowledge it is hardly possible to start the real solution.
  2. Study of the problem - in discussions with project leades or people resposible for the part of the system in question we get a notion of what the part of the system is used for and what its correct functions or problems are.
  3. Study of the code - we investigate the source codes in detail
  4. Demonstration of the results - we provide the partners with the documents created during the audit - documentation, unit tests, lists of errros and proposals for sorting out the errors, lists of suboptimal algorithms and their possible improvements, list of remarks for the architecture of the system.