Creating Functional Wireframes

Functional wireframes are an intrinsic part of any web development process. They illustrates how each page is structured as well as information about each  button, field, piece of content and functionality. It provides an overview of all of the different templates within a site inclusding their function and features.

Wireframe Content

Each wireframe contains the following information and a description:

  • Title: This is at the top of every wireframe. The wireframe title describes the purpose of the wireframe.
  • How to get here: this section describes how the user got to this content block
  • Concept/Purpose/Objective: this section describes what the objective or purpose is for this panel.
  • Content/Data: this section describes all the content on the panel including any buttons or icons.
  • Buttons/Links:
  • If: Then: This section describes a user behavior and the result of that behavior (e.g., what panel is rendered after the ‘If’ condition is met).
  • Navigation Links/Buttons: this section describes any navigation links on the page.
  • Error conditions: this section describes any errors that may result from a user behavior and what message wireframe they will receive.

More information on Functional Wireframes

The basics of web usability

In principle, the term usability as it relates to the creation of websites refers to how easy it is for users to learn and use a website to achieve the required outcomes and their level of satisfaction with the site processes. User-Centred-Design is a key methodology for creating sites based upon positive and intuitive user experiences. What Does Usability Measure

How does Usability work as a measure of a website’s success?

Usability is THE key measure of the quality of a user’s experience when using a web interface; whether that be a website, a web application or a mobile application/website. Usability, however is not one-dimensional, it combines many factors such as:

  • Ease of learning - how intuitively can a new visitor understand and use the interface to complete their required tasks?
  • Efficiency of use - once familiar with the interface, how quickly can the user accomplish what they require?
  • Memorability – how easy is it for a returning visitor to remember how to use the interface upon returning?
  • Frequency of errors and severity – how often do users make mistakes, how serious are they and how easy is it for users to recover from them?
  • Subjective satisfaction - how well does the user actually like using the site/application?