Training handouts-development specifications (01_02)

Previous Article Article Explained to the Team (for reference in this article)
The content of the ppt on the development specifications section during coding training,
Role of development specifications
1) Development specifications act on the internal development team to ensure that different developers are set in the work environment, Code Development specifications and daily development behaviors can meet common requirements.
2) Development specifications are used in various stages of development to ensure that all issues in development can be handled according to the development standards (such as code management, version conflicts, and code naming rules ).
3) The Development specification is used as the testing standard for the final development product code. Through the re-detection of the final product code, the code standardization and maintainability are ensured.
As a testing standard in development, development specifications constrain developers' development behaviors to improve development quality and reduce development costs within the team.

Requirements of development specifications
1) when developing and developing the content, the required content must have clear semantics to ensure that the content is not ambiguous.
2) For descriptive content in development, image descriptions are used to reduce text descriptions.
3) Avoid code naming and code logic layering after project development.
4) if the development specifications change, ensure that all the personnel in the project team develop according to the latest development standards.
5) version management is also required for development specifications.

Content of development specifications
As an ideal development specification, you must have the following development content:
1) Development Platform conventions
A) Development operating system environment and the most common user environment (including the servicepack version number)
B) development tool Version
C) The database type is already in version
D) network status
E) version control tools
F) development and use of hardware environment and composition
G) implementation of development specifications
2) Work Style conventions
A) actions before starting work (update code before starting work every day)
B) behavior after work (all code is required after the end of each day)
C) version control behavior (Requirements of code commit and solutions to conflicts)
D) file storage requirements (processing of new code files and backup files)
3) code writing conventions
A) code naming rules
B) code annotation requirements
C) Requirements for code modification
D) Requirements for saving code files (a class is saved in a medium file)
E) code appearance requirements (Code alignment and line feed requirements)
F) database code writing requirements
4)ProgramStructure conventions
A) General Code Processing Method
B) interface processing method
C) Requirements for the internal logic division of codes
D) program hierarchy requirements
E) program exception handling requirements
5) usage conventions of Auxiliary Tools
A) Use of version control tools
B) Use of the Code Generation Tool
C) Instructions for use of unit test tools
D) Use of the Bug Management Tool
6) Other conventions
A) unit test method Convention
B) version control conventions
C) Plan Management Convention
D) Test Data conventions

Implementation of development specifications
1) issue formulation
A) Encourage all project developers to participate in the formulation of specifications.
B) Developing standards requires consideration of code maintainability and convenience of actual development.
2) Execution Problems
A) Check the Code in accordance with the Development specifications and correct the existing problems.
B) implementing development standards through cross-checking of internal teams