|
|||||||||||||||||||
|
| |||||||||||||||||||
|
« Station Watching | Main | Nuclear Testing Goes Virtual »
TrackBack URL for this entry:
http://blogs.spectrum.ieee.org/cgi-bin/mt/mt-t.cgi/2266
This page contains a single entry from the blog posted on June 12, 2007 1:12 PM.
The previous post in this blog was Station Watching.
The next post in this blog is Nuclear Testing Goes Virtual.
Many more can be found on the main index page or by looking through the archives.
Comments (1)
Right. Software systems engineering is still a young art / skill, it doesn't yet have the same structure as for example hardware engineering. And, of course, because of that, it is much easier to sell "miracle" and "total" solutions than in many other fields. We have MIL.., etc standards for hardware - none for software as a system? Not that I'm fan of some, outdated, some non-working standards and the same model as used in HW doesn't fit too well to SW but there should be at least something?
This kind of blunders should not happen AND they only can happen when there is no strategy, planning, design, etc - only marketing, sales and profits. I'm sure most of the people in this project were very capable to build a working system - given a chance to do it. 30+ years in computers, fighting project after project for common sense and the usage of very skilled people, many times you just can't win, the (short term!!) profit is more important - often in both sides. Where was the project oversight from FBIs side? Why no external, maybe even paid(?), auditing throughout the project? And no excuses for vendor! You take a task, you do it!
And as in many this kinds of projects - given that amount of money, we are many who could do it, retire rich and happy, and they would have a well working, well documented and supported system. We just don't have the marketing / lobbying power some companies do. Sorry, involved to some, some successful, some not..
Posted by Tuomo Stauffer | July 3, 2008 12:42 AM
Posted on July 3, 2008 00:42