Prototype Before You Build

Prototyping is one of the most important activities of requirements analysis. Typically when people think

of requirements gathering, they think about writing a document. Although writing a formal document is

necessary, it is not sufficient to provide non-technical users a good understanding of the product that is

being built.

For most web applications, a simple prototype can be easily created using plain old HTML. This will

provide the customer with an understanding of the user interface of the application and the workflow of

the system. Misunderstandings can be quickly corrected thus putting the requirements on a firmer footing.

Prototypes are usually meant to be thrown away. This means that you don’t have to spend too much time

worrying about the source code of the prototype. The visuals and the workflow are what is important.

Getting a prototype up sooner saves time in the requirements analysis process and serves as a good

foundation for the rest of the project.

Visit IVESIA’S WEBSITE.Follow us at LINKEDINand TWITTER