Timescales - Days not months

With the spread of IT systems to all areas of business and the availability of the internet, business users have high expectations of available technology. Conventional development methodologies have failed to keep pace with these expectations.

As application complexity increases the following effects are frequently observed:

• the required team size increases.
• communication becomes an overhead; lack of efficient communication is a significant risk.
• communication bottlenecks can only be avoided through sound design and architecture. Team size increases to include design teams and architects.
• increased team size necessitates training in local/project standards. The creation and policing of standards often falls to the designers/architects - preventing them from doing 'real' work.
• management overhead increases, in order to manage people, risks, and communication.
• cost of the project/programme increases; thresholds are exceeded in terms of budget sign-off, and the required tendering processes. This adds further administrative overhead.

Consequently, development effort and overall cost increase exponentially against application complexity, as shown below.

In a conventional development environment, changes to requirements frequently spell disaster, as the rework that they entail can easily exceed available development resources.

Using kinodb, you can:

• Use smaller development teams
• Work far more closely with the system's users
• Identify required changes much earlier
• Accommodate changes without the need to recode logic, forms, reports

Users can start entering real data into your application as soon as there's a place to hold it: this means that users can be using the completed parts of a complex application as soon as they are developed, while additional data design and functionality are still being incorporated.

The development process becomes highly interactive to the point that you can even use kinodb in workshops and produce a working application as a direct output of a requirements gathering workshop.

Development time is more productive; users can review the completed parts of their application at any stage during its implementation.

IT departments can produce production-strength databases ready for enterprise-wide deployment in less time than is required for an initial demonstrable prototype using conventional methodologies.

Create simple applications in minutes, not weeks;
Complex applications in days, not months.

Also see