After determining the highest value use cases of a system, these use cases are incrementally designed and developed. The goal with this iterative approach is to have a system with as much value as possible as soon as possible. Rather than large blocks of functionality delivered at once, critical subsystems can progress through refinement after refinement as later developed subsystems are just being analyzed.

This organic process of "feature spiking" enables us to deliver a functional product at nearly any interim point of the full development process with some fraction of the full end functionality in complete working order. Additional "bells and whistles" and less strategic functionality are added over time.

You can be confident that the system, as delivered, accurately reflects your organization's current business processes. Should business rules change, and they almost always do, our object-oriented methodology allows for painless modification of any subsystem seldom affecting the whole, reducing maintenance costs considerably. If a budget gets trimmed before the complete "perfect picture" has been painted, you can rest assured that your organization can benefit from the effort expended to that point.

The final product of this stage, along with accepted prototypes, is a matured feature point analysis count.