At the heart of every Flexeye OI system is a ‘goal directed design’. All decisions made in the design process are based upon a formal definition of the user’s operational goals.

This design methodology is based on Alan Cooper’s (creator of Visual Basic) and Larry Keeley’s idea that software products must balance business viability and engineering capability with the desires of the user.

The results of the client brief are set out by Flexeye in a ‘Blueprint’, a ‘live’ document that can adapt and evolve so the balance of viability, capability and desirability is maintained through the creative process. The Blueprint captures the key design elements of the system under development including user goal definitions, metadata models of relationships between objects, and key User Interface designs.

The Blueprint gives Flexeye’s System and Data Analysts the guidance necessary to configure a system prototype on the Flexeye OI Engine. Configuration is undertaken according to a development process called Dynamic System Development Methodology (DSDM).

The prototype is trialed by users throughout the configuration process and feedback used to improve the design. Flexeye adheres to best practice PRINCE2 standards in project management, ensuring communications between our design team and the client are transparent and clear.

This focused, balanced approach to system design ensures that Flexeye OI systems achieve the operational goals of the users.