Posts made in June, 2012

Check the quality of your software… ready, steady, go!

Posted by Guillermo Villarrubia on Jun 28, 2012 in Quality metrics, Software quality | 0 comments

The time to measure the quality of your software has arrived! Once you have decided to invest into quality and you have chosen the software characteristics it is time to get started. The first quality measure is like your first kiss: you will not forget it for the rest of your life. But do not worry about it! You are in time to do it better than your first kiss, but it will never be so magic!

Have you done a software ‘tasting’ lately?

Posted by Juan Pablo Tejela on Jun 25, 2012 in Quality model, Software quality | 0 comments

I don’t know about you, I love food and of course wine to go with it. In fact one of my latest weekend trips was to  one of the many wine regions in Spain, La Rioja. If you are a wine lover you have most probably heard of it and  even tasted one or more of its world re-known wines. Once there it is literally impossible not to visit a winery and engage in the most enjoyable art of wine tasting.

After a couple of glasses my mind started wandering… One thing is these casual tastings you do in weekend trip, and another thing is the professional tastings the wineries carry out to assure the quality of their products.

4 Steps to Improve Your Software Maintainability

Posted by Luis Rodríguez on Jun 21, 2012 in CTO Corner, Maintainability | 0 comments

As I said in my previous article, Software maintainability. The ‘Poor Cousin’ in the Technical Quality Family, code is usually not designed for change. Right.

Now, what can you do so your software maintainability is not the ‘poor cousin’ of technical quality anymore?

Software maintainability. The ‘Poor Cousin’ in the Technical Quality Family

Posted by Luis Rodríguez on Jun 21, 2012 in CTO Corner, Maintainability | 0 comments

Code is usually not designed for change. Thus, while code meets its operational specification, for maintenance purposes it is poorly designed and documented. Symptoms are well known: understanding code that needs to be changed is hard, testing is too difficult and takes excessive time and resources, too many regression defects after simple functional changes or refactoring (it is difficult to reliably implement changes). You suffer from this, wouldn’t you?

Ideas world vs. Real world. What can Plato teach us about usability?

Posted by David de Alba on Jun 18, 2012 in Usability | 0 comments

When Plato tried to teach his philosophy about ideas, could it be that he was thinking about how to design a web application? Maybe he wasn’t completely off topic…

According to his Allegory of the Cave, there were two worlds, the ideas world and the real world. In the ideas world we had the authentic representation of things. They were considered pure and immutable objects. However, in the real world things were shadows of those ideas perceived through our senses, therefore the image we get of ideas in the real world is highly influenced by the light deflected on them.