In an article about the unreliability of embedded software, for some reason someone decided to add some comments about what they think you should do when improving software. http://www.baselinemag.com/article2/0,1540,1150971,00.asp however they claim they got it from ABN Amro Services Co.
Their points are:
What do people think about this advice?
The first two are established. A LittleDesignUpFront is always good, and bugs found early tend to be less bothersome. Xp advocates writing a test for any bug that is solved, probably not truly "all of them, individually", it's a matter of balance. Also, do it iteratively. Sounds good. . . but is this really "Improving Software"? This sounds rather testing specific. Improving could involve decoupling, formatting, removing redundancies, etc. . . It also sounds a lot like ContinuousTesting, and it could benefit from using TacticalTesting.
The first item should really be split into two items,