First, identify needs and define the framework
Before coming to a project, prototypes and products listed requirements, will communicate the project is not yet before the actual project, you need to try the various aspects of the project are taken into account, confirm that demand is a very important process that needs to products with good identification of needs, whether these discussions do. In the course of discussion on the need to confirm what kind of framework fit.
We have a current project is to interact with the device, the customer requires a connection to the server APP is a long connection, since denied the request http way, then you can not use the web components, but the use of netty framework for development.
Second, the testing framework
If familiar with a framework, such as a familiar SpringBoot + mybatis this frame, and used in multiple projects, then it may not be required to test this framework. But if the introduction of a not particularly familiar with the framework, such as rocketmq messaging middleware, you need to test this framework, there is a sample, there is a test case, and whether the middleware to meet their own needs.
Enough to make their own tests to understand the component meets their needs before they can be introduced into the original framework without error.
But under normal circumstances, such a test little or nothing, is pure Into a function of the component only.
This step also includes also a core point of a project, such as the project is a highly concurrent, then the frame whether support high concurrency, you need to take this test, and confirm that the feature point is feasible, if not feasible to quickly get a new program .
At this stage we need to do two things, the introduction of the framework is to test the performance, whether the test frame supporting the project core function point.
Third, write interface documentation
Write interface documentation, that the functional requirements set out point. For example, a project function point:
The above is probably a function of the project, these are only approximate function points, then you can just add, this project will have a general understanding. Once we have that understanding, you can assign tasks, plan time to complete, and the last time to arrange delivery according to the function point.
Fourth, write code
Write code to implement the project, this should be the last second step, the last step is to test, we will give testers do. Coded in accordance with specifications required to do, what standard, a specification that is the first company specifications, then Ali Java development specifications manual content. The third is the overall coding style.
为什么需要注意代码规范，这个是让其他人方便阅读代码，不能随心所欲，不能由着自己的性子来。
编码是一个严谨的过程，需要逻辑清晰，代码优美，这个过程是需要不断积累的，积累到能够将代码编写的艺术起来。