Posts Tagged "Robert Martin"
Agile development and software quality, or software quality and agile development. What comes first?
I’ve always said that before starting a new development project, if you want to measure and control the quality of the final product, you have to sit back, relax and come up with solid quality model to fit your needs. No matter what development methodology you are going to use.Read More
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?Read More
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?Read More
Let’s keep on talking about software metrics by introducing a new bunch of software metrics: the ones defined by “Uncle Bob” Martin back in the mid-nineties.
Why should I care another set of nasty metrics?
Slow down cowboy! You should only consider have a look to these metrics if you want to design a successful object-oriented system… so I guess you will keep on reading this post.
Robert Martin stated a ‘desirable pattern’ that must fulfill any software. The pattern requires a set of metrics that measure the interdependence between the subsystems that are part of the system in various ways. Let’s find out what he was talking about.