Software Development Process?

[tcj103]

I've recently stepped in as the software program manager, and was wondering what other teams do to develop software. Our current process is write code, load code, watch robot spin around, scratch head, re-write code, repeat.

I work on a military rotorcraft fly by wire flight control system, and have some background in software requirements management and design. We don't code, but are responsible for pseudo-code, system integration, and system testing. We are currently CMMI level 3, and trying to get to 5 this year. For those who don't know what I'm talking about, it's a system the government will soon require contractors to be certified to, and it shows that we document changes, measure our performance, etc.

I'm wondering what other teams do, ie does every change in code result in a new version number? Are old versions kept, no matter how small the change? Do teams perform specific tests once the robot is loaded with new software?

While this isn't the most exciting topic, I think it is important that the kids learn the importance of documentation, since it is part of what engineers do.

So what do other teams do for software development?

Ted