October 20, 2015

Technical Debt

PART 4 – What can companies do to address Technical Debt?

In this four part blog series, Neil Langmead (formerly of Emenda Software and now heading up Siemens' Clean Code Clinic) explains technical debt, its effects on a software project, and how organizations can begin to address it. In Part 3, Neil talked about how big a problem Technical Debt is in the software industry. Finally in Part 4, Neil discusses what companies can do to begin to address their Technical Debt issues.

Vector Software:
Okay, Neil. If I went home today or went to my office today and I started looking at my code and using the metrics you mentioned earlier and I found I had a problem what can I do to address these issues? What are some simple things or... Continue reading »

Posted by Niroshan Rajadurai in Embedded Testing, Technical Debt

October 13, 2015

How to Measure the Value of Testing

I was asked last week if the number of bugs found is the best measure of the value of testing.  Honestly, I had to think about this for a few minutes, and decided that the number of bugs found is actually a really poor way to measure the value of testing.   Consider low-level testing (unit and API testing).  When your developers write tests do you really want them to log formal bug reports for every error they find?  Of course not, this is a development activity, we should hope they are delivering a complete set of passing tests for each change they make and NO bugs.  How about for the functional testing done by the QA team on the integrated product, are you happier if they find 100 bugs with a new feature or 0?  Hmm, 100 means the feature was awful when it was sent to QA, but what... Continue reading »

Posted by John Paliotta in Software Quality

October 09, 2015

Interview on Technical Debt | Neil Langmead

PART 3 – How big a problem is Technical Debt?

In this four part blog series, Neil Langmead (formerly of Emenda Software and now heading up Siemens' Clean Code Clinic) explains technical debt, its effects on a software project, and how organizations can begin to address it. In Part 2, Neil discussed some examples of how companies can determine if they have Technical Debt. In Part 3, Neil talks about how pervasive Technical Debt is in the software industry.

Vector Software:
Neil, how big a problem is this? I mean, do you see many companies out there with Technical Debt?

Posted by Niroshan Rajadurai in Embedded Testing

October 02, 2015

Is Static Analysis Enough?

Software development is hard and building quality code bases is very costly. Every software development group in the world is searching for ways to improve productivity and quality, while reducing development time and cost. Two broad classes of tools that can greatly enhance software quality are: Static Analysis Tools and Automated Testing Tools.

Static Analysis Tools scan program source code to find potential bugs caused by syntax and semantic errors in the code base. Static tools are great at finding data access problems, such as buffer over-runs and pointer de-reference errors.

Automated Testing Tools, such as VectorCAST, formalize the expected behavior of entire applications, or... Continue reading »

Posted by John Paliotta in Software Quality

October 01, 2015

Technical Debt | Neil Langmead

PART 2 – How do you know if you have Technical Debt?

In this four part blog series, Neil Langmead (formerly of Emenda Software and now heading up Siemens' Clean Code Clinic) explains technical debt, its effects on a software project, and how organizations can begin to address it. In Part 1, Neil gave an overview of what technical debt is and how companies acquire it. In Part 2, Neil provides some examples of how companies can tell if they have Technical Debt.

Vector Software:
If I were a software developer and I'm working on a project, how would I know if I have technical debt?

Posted by Niroshan Rajadurai in Embedded Testing

September 25, 2015

Technical Debt | Neil Langmead

PART 1 – What is Technical Debt?

In this four-part blog series, Neil Langmead (formerly of Emenda Software and now heading up Siemens' Clean Code Clinic) explains technical debt, its effects on a software project, and how organizations can begin to address it. In Part 1, Neil gives a good overview of what technical debt is and how companies acquire it.

Vector Software:
We're here today with Neil Langmead. Today, Neil is going to talk to us about technical debt. So Neil, what is 'technical debt'?

Posted by Niroshan Rajadurai in Embedded Testing

Pages