Design and User Interface
After all requirements are collected a prototype is built. The prototype shows the main interface, flow of the application, and the functionality of the software being developed. Feedback is collected from client and integrated to the system documentation and prototype. Prototypes are important because the client not only read documents; client sees and feels how the final product is through the prototypes developed. Prototypes aren’t fully working modules but show the flow and the interaction between the user and the system.
Prototyping is suitable here for its different merits:
Prototyping insures that the final portal is really responding to client expectations and goals
Prototyping helps avoid waste of time many of which is associated with a product that does not respond to the user's need because the developers misinterpreted the functional requirements
Prototyping will provide an initial trimmed-down portal that can be very useful to launch initially and in a short period of time
Prototyping also sets better ground for the future expansion of the portal
If there is a need for more than one prototype will be presented until the client is satisfied with the end result.