Source code design, implementation, source code control

After completing the software requirements analysis before the beginning of software design, I think the use of flexible form of mind map can help us to do graphical modeling, using the divergence of our thinking can take into account all aspects of software design. After the completion of the graphical modeling of the code to be written, this phase of the workload is often required to cooperate with the two people in the source code is often a lot of problems, such as the two people's writing style is very different and so on, but the code style has some big principle is: concise, easy to read, no ambiguity.

In writing code, there is an important part of the note, that a software is generally not written by a person to complete, so you want to work well with the need to do a good job of comments to let the peer quickly and accurately understand your code, I think that in our past study did not develop a good habit of writing comments, so when working together, you will encounter a lot of problems leading to slower coding progress.

In the process of writing code, we all make big and small mistakes, and at this point we are going to do the right error handling, including parameter handling and assertions.

The code review is done after the entire code is written, and the significance of the code review is to see if the code solves the problem correctly within the framework of the Code specification. The most basic method of review in software engineering is peer review. Pairing can be programmed after the code review is complete.

After the end of the software design, we will try to design the software and then collect the user's experience and views, after this phase is to test the software and then promote the use, follow-up software maintenance to ensure the quality of the software. So we've made a piece of software.

Source code design, implementation, source code control