1. Whether the code requires specification:
The code specification is yes, just like a USB excuse requires a standard specification, otherwise we how to use a USB stick on multiple computers. No rules inadequate surrounding area, code normalization for us to check, correction is also very helpful. And four of the arguments I think 3 is right, but I still want to choose 2, because the code is their own, there is a habit of their own way to write code is enough, others see your code needs to understand your specifications, read one can understand all, a person does not have to learn others, What a programmer needs more is a creativity, starting with the innovation of code specifications.
2. Code review:
Zhang Zekei's arithmetic code is relatively simple, and does not add what the topic requirements of the function, in the code specification, the program does not have any annotations and comments, resulting in other people can not understand, it takes more time to understand, the use of space is not very standard, in general, the code needs to have a standard of their own, To be able to make others understand or to be better at understanding the details of the program, to facilitate inspection and correction.
3.PSP records the time-consuming analysis of individual arithmetic projects:
Psp |
|
Time (h) |
|
Planning |
Plan |
3 |
|
Estimate |
Estimate how long the project will take |
3 |
|
Development |
Development |
5 |
|
Analysis |
Demand analysis |
1 |
|
Design Spec |
Creating a design Document |
0.4 |
|
Design Reveiew |
Design review (and colleague review design of the document) |
0.3 |
|
Coding Standard |
Code specification (to customize the appropriate specification for current development) |
0.3 |
|
Design |
Specific design |
0.5 |
|
Coding |
Specific code |
1 |
|
Code Review |
Code review |
1 |
|
Test |
Testing (self-test, code modification, commit modification) |
0.5 |
|
Reporting |
Report |
1 |
|
Test Report |
Test report |
0.3 |
|
Size Measurement |
Computational effort |
0.2 |
|
Postmortem & Process Improvement Plan |
Summarize afterwards and propose process improvement plan |
0.5 |
|
Job Three: Code specification