How We Do It  >  KnowledgeFrame Methodology  >   The Difference

The Difference

We created KnowledgeFrame because we saw a huge gap between what our clients needed, and what current design and development tools could deliver. We saw System Integrators re-inventing the wheel on each project, and too much dependence on hard to find (and expensive) IT expertise.

We designed KnowledgeFrame to complement the use of existing design and development tools. In particular we wanted to:

• support all aspects of the business requirements, not just the technical ones
• support the need for flexible and extensible solutions
• overcome proprietary dependencies
• dramatically reduce the level of effort required to achieve ambitious goals

KnowledgeFrame's architecture and methodology is designed to span the full business scope of a development project.

How does KnowledgeFrame differ from CASE and similar development tools?

• no code generation: generators produce complex code which is difficult to extend, while KnowledgeFrame uses inheritance to extend code;
• live rules: rules are instantiated at run time, allowing much more dynamic behaviours, enabling presentation, logic, and data separation;
• hides data, rule, and technology complexity;
• pre-built business and technical components;
• integrated deployment methodology;
• no vendor lock-in;
• capable of more advanced results, faster!

KnowledgeFrame is capable of more advanced results, faster!

Copyright © T4Bi. Email: contact@t4bi.com