Abstract
AbstractThe 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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.