Prototyping may seem to be an ideal way to overcome the shortcomings of "traditional" SDLC methods, but it may create its own serious problems. Briefly describe the possible problems

What will be an ideal response?

Unbalanced Architecture - Since the main thrust of prototyping is toward the user interface, developers tend to include more and more functionality in the outer layers of the information system, creating a distorted architecture.
The Illusion of Completeness - The real power of an application is "under the hood" (even if the application is a picture editor). For most users, however, the interface is what the application is all about. As a result, the clients might not understand why the developers insist that a lot more is to be done, especially if the prototype is of the throwaway variety.
Diminishing Changeability - Since prototyping can leave little trace of how the development evolved, modifying the application can resemble an archeological undertaking to piece together a lost civilization. If the Waterfall Model relies too much on documentation, prototyping can result in too little documentation or, more importantly, too little modeling.