Question

Software architecture is often compared to the architecture of buildings as a conceptual analogy. What are the strong points of that analogy? What is the correspondence in buildings to software architecture structures and views? To patterns? What are the weaknesses of the analogy? When does it break down?

Answer 1

Software architecture is the designing and implementation of high-level structure of software. While other forms of software design are largely about algorithm and data structures, software architecture is mainly about elements, forms, and rationale of the design at a larger scale (Clements et al. 66). Software architecture comes about through assembly of architectural elements in well-chosen forms to satisfy the functionality and performance needs of system. It also satisfies other non-functional system requirement including scalability, portability, reliability, and availability of software.!

Answer 2

Following is the answer to this question:

Explanation:

• Software architecture comes about as the assembly of architectural components in well-chosen manners to suit the performance and functionality needs of the system.

• The strength of the analogy among software architecture and building architecture depends on the fact that both of them require the larger picture of the design.

• Software architecture regulates how system components are recognized and allotted and how they work together to form the entire system.

• This is more or less like building architecture which decides how different aspects and components of a structure or set of structures cooperate to form a specific building.

• Exactly like in building architecture where diverse structures must be organized in a particular way to fit the desired application and pattern, system architecture guarantees that system components interact in a preferred manner to be functional and to fit user needs and wants.

• Both software and building architects must examine the reliability of the structures they build and confirm that their structures obey the drafted outline offered to the client.

• The weaknesses of this analogy are that while building architecture generates final designs that can’t be altered, software architecture must be adaptable to constant modifications and changes.