No one has mentioned processon. Although it is a web application, its smoothness, beautiful pictures, and intelligent operation are far better than visio and ppt. Look at a few pictures drawn with it. knew.
About question 2: Architecture book
There are many kinds of architectures. I recommend books related to basic software pattern architecture: "Pattern-Oriented Software Architecture" (Volume 1 to Volume 4) from the shallower to the deeper.
The fundamental purpose of drawing software architecture diagram is to describe it from different angles, and it has little to do with the tools. I generally use the following tools in this way, for reference only:
1. xmind: Use mind maps to sort out requirements, or large functional blocks; PS: Mind maps are more flexible, and you can even change them while communicating with customers. 2. axure: Used to draw low-guaranteed prototypes of APP, in fact, PPT can also be used; 3. Use visual or EA's UML to draw software architecture:
Personally, I think that software architecture still needs to be practiced first. It is best to start a project from scratch, starting from setting up the framework, and then continue to refactor as the requirements change (you may have to refactor). At this time, read some books. They will teach you how to reconstruct from a theoretical perspective and some excellent practices, and then you can apply it to practice and repeat it. . . .
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
About question 1: Drawing software
No one has mentioned processon. Although it is a web application, its smoothness, beautiful pictures, and intelligent operation are far better than visio and ppt.
Look at a few pictures drawn with it. knew.
About question 2: Architecture book
There are many kinds of architectures. I recommend books related to basic software pattern architecture:
"Pattern-Oriented Software Architecture" (Volume 1 to Volume 4) from the shallower to the deeper.
xmind
"Must-Read Software Architecture for Programmers"
xmind、axure都可以，xmindThe style is more colorful, it depends on personal preference.I just use mindjet and flowchart software, haha, I am not an architect
The fundamental purpose of drawing software architecture diagram is to describe it from different angles, and it has little to do with the tools. I generally use the following tools in this way, for reference only:
1. xmind: Use mind maps to sort out requirements, or large functional blocks;
PS: Mind maps are more flexible, and you can even change them while communicating with customers.
2. axure: Used to draw low-guaranteed prototypes of APP, in fact, PPT can also be used;
3. Use visual or EA's UML to draw software architecture:
Personally, I think that software architecture still needs to be practiced first. It is best to start a project from scratch, starting from setting up the framework, and then continue to refactor as the requirements change (you may have to refactor). At this time, read some books. They will teach you how to reconstruct from a theoretical perspective and some excellent practices, and then you can apply it to practice and repeat it. . . .