When applied to IS, it refers to the fundamental structures of the system and the construction of these structures. There are several definitions which describe the architecture of an IS. According to Shaw and Garlan (1996), the architecture of an information system defines that system in terms of components and interactions among those components, from the viewpoint of specific aspects of that system, and based on specific structuring principles. In their book, Software Architecture in Practice, Bass, Clements, and Kazman (2003) define the software architecture of a program or computing system as the structure of the system which comprise the software elements, the externally visible properties of those elements, and the relationships among them. The Open Group Architecture Forum (TOGAF) has two definitions for architecture; a formal description of a system, or a detailed plan of the system at component level to guide its implementation; the structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time. Martin Fowler’s (2002) views on architecture do not conform with the above-mentioned definitions. Instead, he feels that the term ‘architecture’ is an overloaded word. In his book on Patterns of Enterprise Application Architecture, he identifies two important elements to define architecture - one is the highest-level breakdown of a system into its parts and the second; the decisions that are hard to change. He further states that a system has multiple architectures and what may seem architecturally significant, may change over a system’s
When applied to IS, it refers to the fundamental structures of the system and the construction of these structures. There are several definitions which describe the architecture of an IS. According to Shaw and Garlan (1996), the architecture of an information system defines that system in terms of components and interactions among those components, from the viewpoint of specific aspects of that system, and based on specific structuring principles. In their book, Software Architecture in Practice, Bass, Clements, and Kazman (2003) define the software architecture of a program or computing system as the structure of the system which comprise the software elements, the externally visible properties of those elements, and the relationships among them. The Open Group Architecture Forum (TOGAF) has two definitions for architecture; a formal description of a system, or a detailed plan of the system at component level to guide its implementation; the structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time. Martin Fowler’s (2002) views on architecture do not conform with the above-mentioned definitions. Instead, he feels that the term ‘architecture’ is an overloaded word. In his book on Patterns of Enterprise Application Architecture, he identifies two important elements to define architecture - one is the highest-level breakdown of a system into its parts and the second; the decisions that are hard to change. He further states that a system has multiple architectures and what may seem architecturally significant, may change over a system’s