Pace of change
Business applications all too frequently constrain the business rather than enabling it.
Analysts and developers are familar with the experience of gathering requirements and delivering functionality, only to discover that requirements gathered three months ago are no longer current. Conventional development tools don't cater for this pace of change as they require analysis and management of the many dependencies that exist in any complex system - the database structures, data validation, business rules, security model, reporting, external interfaces and so on.
After implementation, changing a system that is in use is difficult and risky, and therefore time-consuming and expensive. Making changes requires detailed knowledge of the same dependencies, and these will be hidden in reams of technical code, often created by developers no longer available to the maintenance project.
kinodb provides a simple solution to both of these problems: as the application's definition is recorded as a model, all dependencies can be investigated by the developer. The impact of any proposed change can therefore be determined swiftly and definitively. The development environment incrementally loads changes to the application definition as each is made, so a set of changes can be tested one by one and then fully, immediately on completion.
The incremental delivery of changes is robust and quick - kinodb includes sophisticated change management functionality that allows the managed propagation of sets of changes between environments. This means that changes can be delivered into a test environment whenever appropriate: it takes a couple of clicks to mark a set of changes as ready for distribution, and another couple to propagate them to a test or production environment. A full change history is maintained across development, test and production environments, so a developer can see when (for instance) a field was created, when its properties were changed and by whom.