Software quality is a term most companies fear. The principle is simple, put out a product that is stable and free of defects. However, in practice this is an extremely daunting task. The factors that contribute to the difficulty are primarily in the product development cycle and not in the coding.
Most products are carefully plotted out in a project plan with tight timelines. The plan describes things like systems analysis, design, coding, and testing. Each of these items can be expanded into numerous sub items, but the essentials are basically the same. Generally, the majority of the time is spent redesigning and coding. If the upfront analysis and design had been properly completed, this would not occur. The end results are buggy code and greatly reduced testing time. This is a perfect environment to foster a software product that maintains the industry standard of abysmally low quality.
Why is ObjectFusion software different?
There are a few key factors that give us a significant advantage in the quality arena. First, we do the upfront design work. This sounds simple, but it is frequently overlooked. It the designed is static and the code will be written with this in mind. All of the modules will be crafted with one common objective. This alone, can make an enormous difference in software stability.
Coding standards can also make a marked improvement in quality. This is nothing new; most companies have coding standards, but it still doesn't solve the problem. Coding standards are usually obtained from the latest programming text. I have seen standards enforced that came from different languages. One company that I'm familiar with uses Java standards for their C++ development. An interesting approach but misguided at best. Our standards didn't come from a single best seller or from another language; they come from experience. We have built our guidelines from numerous years of software development and several good texts. They always help to produce readable and reliable code.
The final difference relates the project timeline. Our development staff has exclusive control of release dates. This insures that a product isn't released before it is finished. Unfortunately, this method is not widely used in the industry. Software is frequently released with many known bugs still in the code. The usual course of action is to follow the release with patches and service pack to correct the initial deficiencies. That means that the consumer has to work around the bugs until they are patched. We prefer to imply extend the release date and avoid all of this floundering.
You, the customer, benefit from our methods. The end result of our efforts is solid software that enables you to accomplish your task quickly and easily.