The Fusebox Lifecycle Process (FLiP) is a process for developing web-based applications. The primary concern with FLiP is to create the system that the customer is expecting. 

To this end, FLiP is made up of a series of steps that represent a movement towards the finished result. FLiP allows changes to be made when they are still quick and inexpensive to make, understanding to be amplified and for misunderstandings to be eliminated. FLiP also allows business processes and rules to be described in English without the distraction of web page designs so that all aspects of the business process are captured and recorded.  FLiP creates an environment where the page designers, business owners and developers are forced to formalize their approach to development and clarity is a requirement and not a wish 

The FLiP Process 

WireFrame.  The FLiP process starts with a WireFrame, which is a model of your application from a business process perspective.  The WireFrame will incorporate all the business rules and process flow of the application. 

Prototype / Front end.  This is where you build the front end and invite comment from the Designers, Usability and Conformity specialist, Trainers and User Manual Authors, and the Business users. 

Architecture.  This is where the architect/lead developer plans the overall structure of the application and divides the development into suitable packages of work.  The packages of work involved will be sufficiently detailed to enable the developer to write the code and test all the input and output data that the finished module will process.

Coding and Testing. This is the really worrying part from the business point of view and is when traditionally the lights seem to go out on your visibility of progress. With FLiP and Fusebox, this is not the case. The developers will at this point be working on each block of code logged as a development task.  They will be testing that the code responds as expected to the business rules defined in the Wireframe and architecture phases of the process. 

Integration Testing.  At this point the modules from the developers are brought together by the architect and put through the various pre-defined use cases identified during the WireFrame stage.  These are sets of activities that users will expect to do with the system based on the users' roles. 

Deployment.  This is the final stage of the FLiP process.  All the planning and care in the previous stages of the FLiP process means that the system will function just as expected.