Experience in writing Architecture Design Documents

Experience in writing Architecture Design Documents

1. Architecture Design DocumentIntended audience:

Is a software engineer, platform product manager, not a customer of Party B; 2. Architecture Design DocumentPurpose and Significance: A. System Planning; B. It is conducive to the work of software engineers; C. It is convenient to allocate work and guide the work; 3. It is not about space, but about dry goods; 4.System Thinking, comprehensive thinking,Focus on planning, Focus on the design, consider the details, not limited to details, to solve the actual problem; such as software registration problems, involving user security, role, permission, password encryption, verification code issues. 5. the overall architecture of the platform should not copy the existing system, analyze the advantages and disadvantages of the existing system, develop strengths and circumvent weaknesses, avoid detours, And take shortcuts, focus on system scalability and scalability, and expand and develop in the next 3-5 years; 6. UML modeling tools can be used to further illustrate some technical issues. 7. focus on the depth of technology and the breadth of technology; 8. the document should be written as much as possible, so there should be no "we" colloquial words.

Experience in writing Architecture Design Documents