Information Technology Reference
In-Depth Information
Requirement
analysis V & V
Design V & V
Development
V & V
Prototype
design
Testing V & V
Quick
implementation
Deployment
V & V
Prototypes
Figure 7.6
Prototypes are important.
chalk-talk. It may also help them choose among alternate designs. A
possible side effect could be that if the prototype is seen as “too real,”
then one might walk away with the impression that most of the devel-
opment work is completed and a little more work on the prototype will
lead to delivery of the system. Building architects whose prototypes consist
of physical scaled models do not carry such impressions or raise such
expectations — the customer should not think that he can walk into the
building soon.
Throwaway or Reusable Prototypes
Care must be taken to define the scope and intent of the prototype. Some
prototypes may be created by simple configuration and customization
changes to the original OTS (off-the-shelf) product. These are helpful in
demonstrating the capability of the software in the context of the end
users, instead of showing the vanilla OTS product with a lot of “we can
build that for you” statements.
In your enthusiasm to cover all aspects of the final system, do not
land up building it in entirety. As previously discussed, prototypes might
be needed as a stage in the development life cycle of a new product,
idea, or concept.
