We believe that a separation of technical infrastructure and business-specific code leads to improved software quality, developer productivity and code consistency while at the same time lowering risk. We also believe in agile project practices.
To illustrate what we mean by "technical infrastructure", let us examine a scenario relating to business applications.
The majority of business applications that we work on vary wildly in functionality but share much in the way of data processing themes. Regardless of business function, these applications receive data via a keyboard or an external system, then validate, process and transform that data before finally storing it in a database or mainframe system. Later, the data is retrieved for display or transmission to other systems. These applications also share quality of service requirements in the areas of security, performance, instrumentation, operator consoles, root-cause error reporting and a continuously-integrating build system.
These common data processing stages and quality-of-service areas should be supported by proven technical infrastructure in the form of techniques, frameworks and code-generational approaches that are independent of the nature of the business.
The key to the Paradigm Logic approach is that we have numerous pieces of proven technical infrastructure on hand to bring to a project. This enables us to also release early and often. We are committed to continuing to evolve these infrastructures in accordance with, and in excess of, industry best-practices.