Describe modular design, and explain the two main prototyping methods.

What will be an ideal response?

In a modular design, you create individual components, called modules, which connect to a higher-level program or process. Each module represents a specific process, which can be represented in a graphical model, and documented in a process description. Modular design is especially important in designing large-scale systems because separate teams of analysts and programmers can work on different areas and then integrate the results.
Systems analysts generally use two prototyping methods, system prototyping and design prototyping.
System prototyping produces a full-featured, working model of the information system. A system prototype that meets all requirements is ready for implementation, as shown in Figure 8-21. Because the model is “on track” for implementation, it is especially important to obtain user feedback, and to be sure that the prototype meets all requirements of users and management.
Design prototyping is a method for verifying user requirements, after which the prototype is discarded and implementation continues. The approach is called design prototyping, or throwaway prototyping. In this case, the prototyping objectives are more limited, but no less important. The end product of design prototyping is a user-approved model that documents and benchmarks the features of the finished system. Design prototyping makes it possible to capture user input and approval while continuing to develop the system within the framework of the SDLC. Systems analysts typically use design prototyping as they construct outputs, inputs, and user interfaces.