Skip to main content

Software Metrics Tools that are 'Pushed' by companies

In the last period of time I have been involved in different projects where quality is extremely important. Because of this we started to look around us and search for tools that can measure the quality of software (of the code itself) – software/code metrics.
This is why, this year I had some posts related to Sonar and different software metrics. Personally I looked on different tools that can measure this metrics and can share the content in a consistent and easy way. Until now, my search stopped over Sonar – that is a great tool, but can give you headaches when you need to configure it.
There are many companies that tracks the software metrics. This is a very good think. But in the same time I observed that this companies usually push only one tool that can be used to measure this metrics – THE TOOL. For them it is not important what kind of language you use for developing or if the given tool suites your needs. For them that tool is a standard and you need to obey.
Is this a good or bad thing?
From my opinion, the main scope of the company should be to ensure that for each project the metrics are measured and the team take them into consideration. The most important thing are the metrics them self, not the tool which is used to measure the metrics.
Why the tool is not important?
First of all different teams may feel conformable with different tools. The team should have the freedom to choose the tools that they like, as long as they respect the client or company standards. We are different and we have different preferences.
Also trying to push ‘the’ perfect tool for a job can create a lot of configuration and management problems. For example what happens if you have 20 teams that use a Sonar server and one of the team say that the update to the new version of Sonar or of a specific plugin cannot be made because there is an issues in the new version (of Sonar/plugin) that affect them? Another case can if you have 3 projects that are over 5M of lines of code.  In this cases you can have performance problems only one instance of the tool to measure and visualize the metrics.
If to push a tool as a standard, after a period of time you can realize that on the market the tool that you use is obsolete and there are new tools that make the job better. If you let each team to use any kind of tool, as long as the tools does what is required than you have better chance to use the best tools that are on the market all the time – natural selection. If one the market there is a tool that is perfect you can be sure that a large number of teams will use it.
The best scenario is to end up with 2 or more teams that wants to use the same tool and wants to share the same server. In this case it is clear that you will have the same tool for multiple teams. But this decision needs to come in a natural way from the team’s itself – not pushed by the management.

From the company perspective, it is important to create standards related to code quality and look at software metrics. This standards should require different metrics to be measured, but the tools that are used to make the measure should not be pushed. I’m not a fan to measure software metrics only to measure them. Because of this, the value of metrics has no value if no one interpret the results and take them into consideration.

Comments

  1. There is a reason some companies try to standardize on a set of tools (for metrics or something else) - learning curve, technical support and/or price.. The projects come and go, the team members come and go in projects that take many years, new projects appear where a few developers must become productive in a matter of days..

    Thats's why a big company usually have to standardize on a set of tools, but let a team choose another tool if they have a good reason for it and can afford the cost of learning it and training new members each time they join the project.

    ReplyDelete

Post a Comment

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.

Coding

Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms

Programming

Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming

Design

Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…