We've got to maintain a certain level of 'street-cred'.

Software Architecture vs. Building Architecture

Technology uses many terms, such as software architecture, that when understood give an individual power because they can speak the language. One of the ways to understand the technology is to compare it to something else.

Software architecture is similar in many respects to building architecture.

  1. Both need blueprints. In order to successfully build a building, there is a person who draws a blueprint. That blueprint includes all the details of the plan. As the blueprint is designed, the team is aware of the risks of building on that site and gives directions to mitigate the risk so the building is safe. When a building is built, it is built to stand and to last.

Similarly, software architecture uses a blueprint to define work assignments and which teams will complete that work. By using a blueprint, you have a design approach that will identify risks and mitigate them early in the design process. However, while a building is built to last, software is built with future changes in mind since technology is constantly changing.

  1. Both have a purpose. Building architecture is not done in a vacuum. The architecture of a building includes what the building will be used for, the security needed, and who will use the building. A building will not be built without knowing the users and reasons the users want a building.

Similarly, software architecture takes into account what the software will be used for, who will use the software, the needed security, and the anticipated changes in the world of technology. Software architecture will designed based on the user, the IT system available, and the goals of the individual or business.

Wondering how software architecture affects you? Just contact us and let's have that conversation.