Info

this case, it is probably easier to take the time to write correct code than to try and correct bad code through testing!

Adopting a structured approach involves approaching the solution in two parallel and related tracks. On the one hand, you flesh out the code in a top-down fashion. This is done in such a fashion that at any step, the code at that point can be used for prototyping purposes. Concurrent to this top-down development, add key components that act as "bridges" between application-specific and Excel-specific components and terminology. As you complete these components, they become support functions that mesh perfectly with the overall code being developed top-down.

With each "pass" through the code, flesh out the code some more, until you get to a fully functional system.

0 0

Post a comment