You are here: Home / Development Framework / Requirements and Design

Requirements and Design

The requirements and design phase includes steps of increasing detail that describe exactly what the app is to do and how it is to behave.

Requirements Documents

What must the app must accomplish to be successful? How will it accomplish them? This process should involve heavily the end user of the product! Eventually, through the exploration of these questions, a picture emerges of the technology that will satisfy the end user. Whenever feasible, a photo-realistic picture should be created to leave as little as possible to the imagination. 

Design Documents

Wireframes are simple sketches of an application to allow customers and developers a common understanding of the interaction between the application and user. Wireframes help identify logical and workflow issues, as well as assumptions made during the design.

Wireframes can be electronic or on paper- literally pencil sketches of application screens. They should be complete before coding begins, and should be updated when requirements change.

wireframe sample


Sitemaps make sense for some projects. Sitemaps prevent redundant content and allow for a hierarchical organization for content. 

sitemap sample

Final Design and Requirements Documents

Comp is short for 'Comprehensive Layout' - a complete picture of how the final product will look.

Exacting detail can be time consuming - comps are generally developed using Photoshop - so the amount of time allotted for this step must be balanced with the available resources.

comp sample

Test Plans

As part of the design phase, tests should be written with the customer so that there will be no question as to if the application meets the design.