Hello, Folks. In this article, we’ll be talking about architecture and some specific terms, stakeholders, views, and viewpoints. This topic might be new to most of us, enjoy!

I think to understand what a software architect does, we must first understand what an architect does. An architect is a person who plans, designs, oversees the construction of buildings, and makes the image in their head the reality. Architects create the overall look of buildings and other structures, but the design of a building involves far more than its appearance. This work has special responsibilities, communicating with clients and business owners to understand the requirements, designing, engineering, and supervising.

The software architecture of a system is the set of structures needed to reason about the system, which comprises software elements, relations among them, and properties of both.

A software architect is a software development expert who makes high-level design choices and tries to enforce technical standards, including software coding standards, tools, and platforms.

I would say a software architect is a person who endeavors to solve a business or technical problem with the means of technology. Many people perform architectural activities, such as engineers when they are trying to come up with a solution for a specific issue. It maybe low-level architecture, but it’s still architecture. Engineers just mostly focus on how to implement the solution, yet architects focus on how to solve the problem.

Image for post
Image for post

Who are the stakeholders? A stakeholder is either an individual, group, or organization who is affected by the project. They can be within the team or outside the project i.e customers, clients, and users, or sponsoring the project.

Stakeholders are the people for whom we build the systems.

A key part of your role as an architect is knowing how to work with stakeholders in order to meet their requirements. I would say that this is a time-consuming process. There is often a misunderstanding of requirements, so architects meet with stakeholders not just once, but several times during requirement gathering and understand their wishes.

There are views and viewpoints, which are defined in slightly different ways in different places:

An architectural view — the representation of the architecture how he approaches the concerns held by stakeholder(s) from one or more appearances

A viewpoint — the collection of patterns and templates for building a view. Viewpoints consist of the proven architectural knowledge to guide the creation of architecture, described in a particular set of views (each view being the result of applying the guidance in a particular viewpoint).

Image for post
Image for post

Master of Computer Science and Data Analytics at ADA/GW Universities, Researcher, Psychology-lover, Meme-maker, Musician, Writer, AI & Sarcasms!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store