System design and project management considerations

System design and project management considerations:
1. In the database design, you must reserve a certain number of extended fields for business data, such as 10, to meet the needs of adding business object attributes.
2. When writing a stored procedure script, be sure to pay attention to its versatility. The functions are similar or similar and should be shared as much as possible.
Increasing the number of stored procedures will make subsequent changes or maintenance more and more difficult!
3. Minimize the Coupling Degree (associativity) between system modules. In this way, the mutual influence is minimized, changes and maintenance are easier, and module reuse is more convenient.
4. For public objects, such as function modules, projects, user controls, classes, pages, JS script files, CSS style sheet files, code blocks, script blocks,
Functions should be taken out independently to ensure universality. For Common Object Attributes, tables should be created independently to ensure their independence. If these attributes are changed, you only need to change one. Avoid copying large amounts of code in the system.
5. For system configuration or maintenance functions, try to combine the functions to avoid repeated configuration. For example, the connection string should be guaranteed.
A system only needs to configure one character string in one location for the connection to the same database. A configuration file cannot have multiple identical connection configuration points,
You cannot place the same connection configuration point in multiple different configuration files, nOr Write the connection configuration to the Code (this is
Common disadvantages of cainiao-level figures ).
6. The Code submitted for testing should be in a standardized format and uniform style (Follow naming rules and do not name the code without any meaning, such as ABC or XYZ. Try not to name the code in pinyin,
Do not use personal names, birthdays, or other variables as default values. Scripts are fixed on the page, and the positions of referenced script files and style sheet files are fixed,
Class attributes, fields, global variables, constructor, and initial functions are fixed). Annotations are detailed, clear, and neat. do not include comments.
7. The testing time must be calculated for the preparation of the development plan, including unit testing and integration testing. Even for a small number of functions, a certain amount of adjustment buffer time must be reserved.
8. strict requirements on project members, including work methods, work attitude, and attendance.
9. The control of the project progress should be done by urging the project members to increase resource investment and adjust the plan. Of course, the former is preferred.
10. Potential risks encountered during project implementation should be discovered and evaluated as soon as possible. risks that are difficult to avoid should be reported to the upper layer as soon as possible.