In the internet industry, architecture diagrams are an important tool used to visually display the architecture of software, systems, applications, etc., and the relationships between their components. Common types of architecture diagrams include business architecture diagrams, application architecture diagrams, system architecture diagrams, technical architecture diagrams, deployment architecture diagrams, data architecture diagrams, product architecture diagrams, functional architecture diagrams, information architecture diagrams, etc.

Product architecture is the parent, and functional architecture diagrams and information architecture diagrams are the children.

Product structure diagram, the keyword is product, is the structured expression of the product;
Functional structure diagram, the keyword is function, is the structured expression of the function;
Information structure diagram, the keyword is information, is the structured expression of the information.

The main functional modules should not be too many to avoid confusion between primary and secondary, 5 to 9 is ideal, and the level is best controlled within 3 levels, further subdivision is not very meaningful.

Master Product Concept Design: During the drawing process, it can help product managers think and clearly understand the product's functional modules and their functional composition.

Organize Requirements: From a business perspective, gain an intuitive understanding of the entire product's functional structure in a bird's-eye view, avoiding the phenomenon of missing functional modules and functional points in the process of transforming business requirements into functional requirements.

Assist Development: Assisting development personnel in development.

Functional architecture is a collection of functions, making it easier for development or backend development to understand.
Information architecture diagrams are about functional interaction, making it easier for UI and frontend to understand.

1. Use function trees or layered block diagrams for clear expression;
2. Function naming should be consistent and concise, avoiding homonyms and multiple meanings;
3. Different module roles can be distinguished with colors (e.g., user side/backend);
4. Maintain 'appropriate abstraction', not delving into the implementation level.