Friday, February 08, 2008

software skeleton when doing development

Lately I've been spending more time reviewing software development basics than studying graphics. I've heard of building a software "skeleton" and then adding meat to it but am looking for a definition of the concept in specific software development terms. The integration chapter of Code Complete has some information about it. He organizes it under the topic of incremental integration and describes the skeleton as a small, functional system. It is the smallest functional, difficult, critical, or some combination of those qualities that will run. After thoroughly debugging and testing it, new classes may be added a little at a time after they have been tested on their own. This helps make debugging the entire system easier.

The way classes are added is described in the later part of the chapter. For example, there are bottom up, top down, T-shaped methods.

No comments: