FLiP Methodology Overview

The first phase of a project with FLiP involves identifying the personas and goals for the project. A Persona is a description of each of the application's typical users. We then identify each user’s goals. We use this information to help us to deliver the software needed to meet the goals of the end user.

The Wireframe is a quick way to model the proposed actions that will be performed by the web software. The result of this process is a clickable model of the application that doesn't look anything like the finished project, but gives the architect an idea of how the software will help each persona achieve their goals. It enables the customer to understand at a high level the functionality of the page/s without a confusing layer of graphics that divert attention from the functional aspects of the site. Using this method we are able to follow easily the flow of content being created and its usage.

Human Computer Interface Design? is the largest step in the FLiP cycle, generally taking the major part of the project's effort.

At this point, specialists in interface design create a set of pages that look exactly like the finished application, but with very limited functionality. The objective is to discover exactly what the client expects from the application, and how they want it to look. Once the prototype is finished, the Application Architecture is begun. At this stage we construct the application design and database schema, identifying the various page actions and organizing them into modules (known as fuses). Each behaviour is broken down into a set of components, and the architect writes Fusedocs documentation for each component to be produced.

At the FuseCoding stage the Fusedocs documentation is used to create the modules or [Fuse fuses] required. By using the Fusebox framework, the coder's work does not rely on the rest of the application. Each [Fuse fuse] can be coded and tested on its own, and will be plugged into the rest of the application later.

As each Fuse is coded, it is Unit Tested?. This ensures that the fuse produces the correct behaviour. It also allows the architect to employ any number of coders, none of whom need to know anything about the project as a whole in order to successfully contribute to it. Unit testing creates an elegant quality control system for the basic building blocks of the application, ensuring reliability of the entire project.

As the Fuse are completed, they are returned to the architect, who Integrates them into the final application. Daily builds are employed, gradually transforming the prototype into a working application.

Once complete, a User Acceptance Test? ensures that the application performs as required by the initial design. During the Deployment phase the software is installed and rolled out to the customer.