We want to write characterization tests on our Legacy C application, with the goal of transferring the knowledge to another team, or during an outsourcing.

What should be the scope of this ‘characterization’? When can we consider that our test coverage is sufficient? Is it possible to quantify the effort it represents?

• En français : Application Legacy – Refactoring ou reengineering? (VI)
• In English: Legacy application – Refactoring or reengineering? (VI)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (VI)

Following of our previous post about characterization tests, for our Legacy C application.

• En français : Application Legacy – Refactoring ou reengineering? (V)
• In English: Legacy application – Refactoring or reengineering? (V)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (V)

Back from summer vacations and back on this series about Legacy code. In this post, we will talk about the importance of unit testing in order to understand and a Legacy application, before to start any change.

• En français : Application Legacy – Refactoring ou reengineering? (IV)
• In English: Legacy application – Refactoring or reengineering? (IV)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (IV)

Enjoy!

We continue our series about estimating the costs of refactoring or reengineering a legacy C application. Would you say that the most complex programs and functions also have the highest number of violations to the best practices about readibility and undestandability ?

• En français : Application Legacy en C – Refactoring ou réingénierie ? (III)
• In English: Legacy C application – Refactoring or reengineering? (III)
• En Castellano: Aplicación Legacy C – ¿Refactorización o reingeniería? (III)

Enjoy!

We continue our series about Legacy C applications and how to proceed when deciding about refactoring or reengineering. In this post, complexity and size of functions an programs.

• En français : Application Legacy en C – Refactoring ou réingénierie ? (II)
• In English: Legacy C application – Refactoring or reengineering? (II)
• En Castellano: Aplicación Legacy C – ¿Refactorización o reingeniería? (II)

Enjoy!

An interview of Manuel Recena Soto and Antonio Manuel Muñiz de ClinkerHQ afteir their presentation about ‘Continuous Integration’ to the Madrid DevOps Meetup Group.

• En français : Madrid DevOps – Intégration Continue
• In English: Madrid DevOps – Continuous Integration
• En Castellano: Madrid DevOps – Integración Continua

Enjoy!

We continue our series about Legacy C applications, with the example of the first release of Word (1.1a). Imagine that you have to recommend a strategy for such an application. How would you proceed?

• En français : Application Legacy en C – Refactoring ou réingénierie ? (I)
• In English: Legacy C application – Refactoring or reengineering? (I)
• En Castellano: Aplicación Legacy C – ¿Refactorización o reingeniería? (I)

Enjoy!

Second post of our series about analyzing the source code of Word 1.1a. In this one, I will have a look to the compliance to best practices and the kind of violations that can be found.

• En français : Audit d’une application Legacy en C – Microsoft Word 1.1a (II)
• In English: Audit of a Legacy C application – Microsoft Word 1.1a (II)
• En Castellano: Auditoría de una aplicación Legacy en C – Microsoft Word 1.1a (II)

Enjoy!

Microsoft has released this week the source code of Word 1.1a (1990) and I did analyze it. I was curious to see what would be the results, both in terms of quantitative metrics (size, complexity, documentation, duplications, etc.) and qualitative numbers (violations of best programming practices). Also, what would be the technical debt on this software.

Note that I am not looking to debug this Word release so I don’t need the best precision in my analysis. I just want to get an overall view of its quality and think to what can we learn from all of this.

There will be serveral posts. Here is the first one:

• En français : Audit d’une application Legacy en C – Microsoft Word 1.1a (I)
• In English: Audit of a Legacy C application – Microsoft Word 1.1a (I)
• En Castellano: Auditoría de una aplicación Legacy en C – Microsoft Word 1.1a (I)

Enjoy!

Some statistical calculations about Qualilogy’s visitors in 2013.

Guess who is leading? Does the sun arise on the west or on the east? Are the old ladies still attractive? Is swiss chocolate better than italian gorgonzola or belgium fries?

• En français : Résultats Qualilogy 2013
• In English: Qualilogy – Results 2013
• En Castellano: Resultados Qualilogy 2013

Enjoy!