The Furyx team follows a software development methodology that will ensure that delivery is both consistent and predictable. An incremental and iterative software development approach is used and the team works closely in conjunction with the User, which enables the User to always know exactly what the status of development is.
 
The Project Team follows an Object-Orientated software development approach.
 
The development methodology used is based on the Extreme Programming model using the Unified Modelling Language (UML). This is in our view the current leading methodology used worldwide for Object Oriented software development.

The advanced software architecture for all Furyx systems are designed to support our clients’ growth. This growth is dependent on a solid technical architecture foundation that implements the following goals:

• Robustness: The system must be flexible and resilient to both business and technology change.
• Manageability: Once deployed in the production environment the system must be easy to distribute and manage.
• Scalability: Continuous growth to meet user demand and business complexity must always be possible.
• Incremental Growth: The software architecture must support the ability to incrementally develop and deploy new business functionality and technology.
• Usability: The system as a whole must be well suited to the needs of its users. This includes not only end users, but also developers and systems management personnel.
• Reusability: The system must be constructed in such a way as to maximise reuse of components across business requirements.
• Integration: Co-existence with other systems is a key success factor. Furyx systems must integrate seamlessly with legacy systems, both at a data as well as a function level.
• Security: Protection of data and infrastructure from malicious attacks or theft.
• Maintainability: The software development methodology and tools must be reasonably mature, not overly complex and must emanate from the mainstream of technologies employed worldwide for similar software systems.
• Clear Responsibility: Software designs that clearly separate user interface related responsibilities from business logic and data responsibilities have been employed at a micro-level for many years now.