Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Submission Summary: 0 pending, 2 declined, 0 accepted (2 total, 0.00% accepted)

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Outsourcing Software Quality

Submitted by devonbowen
devonbowen (231626) writes "I'm doing the IT specifications for a project that's being outsourced. The goal is to completely rewrite some software that already exists in-house so that it follows some common standards (modern programming language, framework, browser support, etc). These things are pretty easy to define and it's also reasonably easy to test that the resulting product complies. But how can I specify software quality?

My concern is with maintainability. Is there anything we can write into the specs that will nudge them toward writing code that we'll consider readable and maintainable? Most "coding standards" documents tell you where to put curly braces but leave the bigger issues to be worked out within your corporate culture. And, of course, when outsourcing you are working across two different corporate cultures. One idea that has come up is to have code reviews early to help create some common understanding of code quality between us. Defining the frameworks and libraries should also help to some degree. But I was hoping for something more concrete.

Yes, I know that this problem could be avoided by simply not outsourcing the project. But that simply isn't an option here for political reasons. So given that it's necessary, how would you encourage quality in an outsourcing spec?"

"If truth is beauty, how come no one has their hair done in the library?" -- Lily Tomlin