4.6 Functionally Structured Design and Functional Flow Modeling

4.6.1 Software Design and Structured Charts – Limitations

Visualize a situation where you have been appointed software manager of the anti-skid braking system project. You have never worked on this project or even have any previous knowledge of the design. So, on day one, you set out to get an in-depth knowledge of the system and its software. Assume that the project documentation held by the software team consists of:

• A structure chart(s) as per Figure 4.41
• Source code modules for the application, at varying stages of completion:

Figure 4.70: CRC cards for the system of Figure 4.60

The question is, how helpful is this material, especially the structure chart? Well, it would certainly give you a very clear guide as to how the software should be structured. Moreover, it would allow you to do a code walk-through to check the compliance of the code (the implementation) with...