Architecture as a Solution Schema for a Class of Problems

The field of architecture has had some difficulty in defining precisely what architecture is, and how exactly it differs from design. There are widely accepted definitions, and other conceptions have been proposed, yet there is some sense that the full essence of what we intuitively grasp as architecture has not been explicated. We propose a simple framing, that architecture is a solution schema for a class of problems. We contend that taking an architectural approach to any problem involves abstracting the problem to selectively include not only the current instance, but future instances and variants into which this problem may morph over time. Formulation of this architectural problem through abstraction and a solution schema which asserts the capability to address selected stakeholder concerns differentiate architecture from point solution design. We show how this framing leads directly to the accepted definition that architecture consists of components, connectors and principles and guidelines governing system evolution. The discussion indicates why architecture necessarily involves holism and patterns, whereas design is more analytical.