Detailed Classification of Architecture Diagrams
Process Type
Graphical expression
Mind Type
Structured expression
Note Type
Efficient expression
Treemap
Bracket Diagram
Default Mode
Supports real-time multi-user co-creation with shareable links for instant information transfer
Automatically generates graphics from text input and applies style enhancements
Prebuilt themes with full customization for personalized designs
Supports icons, images, labels, LaTeX formulas, code blocks, links, attachments and more
Export: PNG, VISIO, PDF, SVG | Import: VISIO, Mermaid
Real-time cloud storage, multi-device sync, version history, and secure data protection
A functional architecture diagram represents the required functions. It's like a car engine, showing which parts are needed, with each function being a part. Information architecture is a guide for assembling the parts, similar to an engine assembly manual.
The product structure diagram encompasses the product's functions and information, and can also indicate the logical transitions between functions. It can be simply expressed with a formula: product structure diagram = product functional structure diagram + product information architecture diagram.
The design principles for layering in a functional architecture diagram involve dividing system functions into multiple levels based on logical relationships, with each level representing a functional module. Typically, a three-level structure is used: the first level is the system-level functional domain, the second level is sub-modules, and the third level is specific functional items, which can be flexibly expanded based on business complexity.
The arrows in a functional architecture diagram indicate the direction of data flow or the dependency relationship between functions.
A functional architecture diagram should include the layered structure of the system, the functional description of each layer, and the direction of data flow.
The color scheme for a functional architecture diagram should be clear and concise, avoiding the use of too many colors.
They are commonly used in product planning, requirement analysis, module breakdown, function review, communication, and collaboration. They are key tools for product managers, business analysts, and development teams to communicate.
A functional architecture diagram shows the functional structure (what functions are there), while a flowchart shows the sequence of operations (how to use these functions to complete tasks).
It can be divided by business domain or system module, using partitioned management or layered structure (such as product end, operation end, backend end), supporting subsequent decomposition and evolution.
