The December 2022 issue of IEEE Spectrum is here!

Close bar

Texas Outsourcing Contract Performance Defended by IBM

IBM Wants Talks With State to Resolve Differences

1 min read
Texas Outsourcing Contract Performance Defended by IBM

Last Friday, IBM sent a letter to Texas Department of Information Resources (DIR) defending its performance on the $863 million, seven-year outsourcing contract that the state awarded to IBM in 2006, says a story in the Dallas Morning News.

As you may recall, in mid-July, the DIR sent a "Notice to Cure" letter to IBM stating that the company had 10 days to complete a plan that was acceptable to the DIR for curing the material breaches and correcting other deficiencies the DIR had identified, and that IBM must cure the contract breaches within 30 days. If IBM failed to do this, the DIR implied that it would seek to terminate the contract.

The Morning Star article states that IBM decided that it wouldn't be making a formal response to the DIR's cure notice, but would seek to meet with Texas state officials to try to work out a new plan of action.

In addition, the Morning Star quotes the IBM response to DIR as saying,

"As you know, we do not agree that IBM is responsible for the problems that you outline in that letter... (but that IBM recognizes DIR) is dissatisfied with the current state of the project."

That latter bit is somewhat of an understatement, I think.

Given the very public put downs by DIR of IBM and by IBM of DIR, I sure would like to be a fly on the wall of the next DIR-IBM meeting to see how they try to kiss and make up. To be sure, the meeting will be filled with lawyers from both sides subtly and politely blaming the other, but also trying to say let bygones be bygones.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}