Page 187 -

154 part 2 • inforMation requireMents analysis

Figure 6.2
Analysts should modify their
original screen designs based on
user reactions to the prototype.

Modify your design
based on reactions
to your prototype.

WORKING IN MANAGEABLE MODULES. When prototyping some of the features of a system into
a workable model, it is imperative that an analyst work in manageable modules. One distinct
advantage of prototyping is that it is not necessary or desirable to build an entire working system
for prototype purposes.
A manageable module is one that allows users to interact with its key features but can be
built separately from other system modules. Module features that are deemed less important are
purposely left out of the initial prototype. As you will see later in this chapter, this is very similar
to the agile approach that emphasizes small releases.
BUILDING A PROTOTYPE RAPIDLY. Speed is essential to the successful prototyping of an information
system. Recall that one complaint voiced against following the traditional SDLC is that the
interval between requirements determination and delivery of a complete system is far too long to
address evolving user needs effectively.
Analysts can use prototyping to shorten this gap by using traditional information-gathering
techniques to pinpoint salient information requirements, and then quickly make decisions that
bring forth a working model. In effect the user sees and uses the system very early in the SDLC
instead of waiting for a finished system to gain hands-on experience.
Putting together an operational prototype both rapidly and early in the SDLC allows an ana-
lyst to gain valuable insight into how the remainder of the project should go. By showing users
very early in the process how parts of the system actually perform, rapid prototyping guards