In the internet industry, architecture diagrams are an important tool used to visually display the architecture of software, systems, applications, 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.

Business Capability: What the enterprise 'can do'--high-level abstract functions, such as 'Customer Management', 'Order Processing'

Business Process: Describes how business activities 'are done'--such as 'Order Placement Process', 'Customer Service Process'

Business Role: Roles with specific responsibilities within the organization, such as 'Customer Service Staff', 'Sales Representative'

Organizational Structure: Departments, branches, etc., within the enterprise's organizational structure

Information Object: Data used and generated in business, such as 'Order', 'Customer Profile'

Service: Callable business functions, such as 'Invoicing Service', 'Account Inquiry'

Strategic Goals: Clarify the company's long-term vision and short-term goals.

Value Stream: Identify and optimize business processes to ensure maximum value.

Business Capability: Determine the organization's core competencies and service capabilities.

Top-Middle-Bottom Structure: Resource Layer—Data Layer—Platform Layer—Business Layer—User Layer.

Left-Middle-Right Structure: Upstream Industry—Business Model—Downstream Industry.

Horizontal: Parallel structure, left and right should be at the same level

Vertical: Should be layered, upper layers depend on lower layers, the bottom layer is more important.

Symmetry: Emphasizes symmetry and balanced distribution of functional structures.

Dashed Box: Multiple modules that can logically be grouped together can use a dashed box.

Color: Color matching should have distinctions; each major business function should be differentiated by color, but the overall style should be consistent.

Size Format: Size should be consistent, with a unified format.

Module Grading: Modules at the same level should be of the same grade, and granularity should also be unified.

Vocabulary Description: Vocabulary should be accurate, allowing developers or users to understand.

Module Granularity: Details should be abstracted into modules, granularity should be appropriate, neither too specific nor too broad.

Product Reporting: In product planning and reporting meetings, business architecture diagrams can be used to present the overall state of the business.

Technical Reporting: When reporting, it's not enough to talk only about technology; business development should also be discussed. Business architecture diagrams can easily present the overall business situation.

Employee Training: When training new employees on business, providing them with a business architecture diagram can give them a comprehensive understanding and awareness of the overall business.