Our approach

How datb's development technology delivers benefits

kinodb system characteristics

kinodb delivers systems that:

  • are delivered earlier

  • meet requirements better

  • outlast the technologies that first delivered them

  • save their owners multiples of their entire lifetime cost.​

framework overview page card 2

What's the problem?

Development traditionally involves developers translating business requirements into technical code.  Developers specialise in the implementation of specific technologies and, as these technologies change, developed systems need to be updated to avoid a slide into obsolescence.

Conventional systems development results in the business functions of a system and its technical implementation becoming inextricably intertwined, so changing one requires changes to the other.  This means that system owners and maintainers face a choice between the expense and risk of successive changes to a system, or simply allowing a system to turn into a legacy problem over a few years.

And as business requirements change, developers face the same problem.  Systems fall out of sync with users' needs, and again there's the need to successively make changes, leading to the gradual attrition that results from continual modification.  Again, it's the intermingling of business requirements with their technical implementation that creates this conflict.

How have we solved this?

We have changed the way that business applications are developed, deployed and maintained.

In the same way that CAD applications revolutionised engineering design and manufacturing processes, we have separated the business and technical aspects of systems development.

Our technology allows developers to build a model of the application instead of building the technical components themselves.
 

wireframe model       rendered model       printed model

framework overview card 3

The metadata model

At the core of our technology lies a metadata model of the application - all of it, from physical data structures to the security model, processing rules, reporting and interfaces.

This model contains no technology, so in the same way that a 3D CAD model can be used by a variety of rendering, visualisation and manufacturing technologies, the application model exists independently of its technical implementation.

This fundamentally changes the development process in the following ways:

Speed

Removing the need to hand-craft technical code means that implementation takes a small percentage of the time normally required - for a typical project, use of kinodb generally reduces development time by around 85%.  This speed means that development can be truly agile, with users involved in iteratively refining complex functionality to ensure that the delivered system exactly meets their needs.

Technology independence

As new database versions and platforms appear, existing applications are made compatible with them, not by changes to the applications themselves, but by updates to the deployment framework.  This also means that an existing application deployed to a workgroup of 20 users using a free-to-use database such as MariaDB or MySQL can be migrated - literally at the click of a mouse - to an Oracle Enterprise implementation supporting thousands of concurrent users.

Just keeping up with new browser versions causes major headaches to application developers and maintainers.  Again, by separating the technical implementation from the application definition, kinodb applications can support the full range of corporate and end-user browsers.  A consequence of this is that applications developed over a decade ago can now be used on smartphones and tablets - devices that did not even exist when the applications were developed - and this has again been achieved without requiring changes to the applications themselves.

And as new functionality is added to the framework - powerful end-user reporting capabilities, XML interfacing, graphing support, single sign-on and so on - these become available for use within existing systems.

Flexibility

As the whole of the application is defined within the model, it's easy to assess the scope and impact of any proposed change.  Large-scale systems that are unmanageable when implemented using conventional tools suddenly become simple to maintain, as the technical aspects of making a change within a system of any scale (for instance checking hundreds or thousands of SQL statements after a change to data structures) are handled by the model.

     

    Key Benefits

    Developers don't have to write technical code, reducing development time by as much as 85% and greatly reducing the risk of technical errors in implementation

    As the impact of any change can be investigated before it is made, applications can be maintained and enhanced with far lower risk, providing an unparalleled ability to keep pace with changing business requirements

    kinodb handles the technical implementation of the application model, safeguarding applications against technical obsolescence

    The productivity of the development environment enables truly 'Agile' development, with users able to see the results of changes faster than ever before 

    The speed of iteration means that opportunities for improvement can be exploited and blind alleys avoided as a normal part of the development process.

    Cost of Ownership

    Greatly enhanced speed of development leads to lower resource cost and lifetime cost of additional work

    Building systems incrementally, with users able to review key components as they are produced, removes much of the time, cost and uncertainty associated with traditional 'waterfall' developments

    The ability to support short iterations removes the risk of surprises on delivery and ensures that user requirements are met first time

    Developers can report on the design of the application within the model, so systems don't become unmanagable as they grow

    The deployment framework is updated to cover new versions of components such as database platforms and browsers, removing the need for periodic re-engineering of complete systems.

    Put us to the test