A system architecture is the conceptual model that defines the structure, behavior, and more views of a system
And this is example of a diagram of system architecture that was visualized to help understand
System architecture
An architecture diagram is a visual representation of all the elements
that make up part, or all, of a system.
It helps engineers, designers, stakeholders and anyone else involved
in the project, understand a system or app's layout
Like this image, architecture has many characteristics to use.
Now, we can know why we use system architecture
Why do we have to draw architecture diagram?
Is it totally OK to just understand the structure of the software system?
Are there any benefits to drawing architecture?
I wanted to know why we drew these diagrams
And here are some advantages to drawing software system diagrams
The structure of the architecture is well well known and developers can understand and modify the working of the software elements.
It is possible to understand and satisfy the requirements of customers through architecture.
It is rare that architectural handling handles both functional and quality requirements in the structure. Software System Architecture belongs to that kind.
Once a developer knows the architecture and its development fully, the organization's market position is improved, because who will say no to a supplier that understands customers very well
All the use cases are understood and solved in architecture by knowing the scenarios. This helps developers to boost their confidence and morale in and around them. Work satisfaction and thus, the revenue of the company is improved.
How to draw architecture?
I think there're some ways like this.
Gather the technology stacks needed to implement features
FrontEnd/BackEnd Frameworks
Database
Cloud services
Web sockets
etc..
Connecting according to the correlation of functions
ex: React should use a one-way arrow, because it carries information in one direction.
