Personal third job - Pair Programming
First, the twinning partner
| Github repository address | https://github.com/S21loganmc/PairProgramming |
|---|---|
| Address operational requirements | https://www.cnblogs.com/cherish599/p/11577268.html |
| Twinning partners | Li Nan |
| student ID | 201731024101 |
Second, the twinning process and the PSP form
When teachers post assignments, we completed the team for the first time, and many discussions with our topics and code design. We chose a design class roll call system. At first we thought not very clear and precise, but the teacher in the classroom to explain several times, we have to seriously study record.
The picture shows a form teacher for operation and demonstration programs
after school, we chose to be discussed in the tea shop, and complete the steps.The picture shows the group Pair job site
after the discussion, we have the overall framework of the overall work process and complete the corresponding form design PSP.PSP table
| PSP | Personal Software Process Stages | Estimated time consuming (min) | The actual consuming (min) |
|---|---|---|---|
| Planning | plan | 20 | 20 |
| Estimate | Time estimates | 600 | 720 |
| Development | Develop | 500 | 630 |
| Analysis | demand analysis | 30 | 60 |
| Design Spec | Generate design documents | 35 | 60 |
| Design Review | Design review (and colleagues reviewed the design) | 15 | 20 |
| Coding Standard | Code specifications (development of appropriate norms for the current development) | 30 | 60 |
| Design | Specific design | 30 | 30 |
| Coding | Specific coding | 240 | 280 |
| Code Review | Code Review | 60 | 60 |
| Test | Test (self-test, modify the code, submit modifications) | 60 | 60 |
| Reporting | report | 60 | 90 |
| Test Report | testing report | 20 | 30 |
| Size Measurement | Computing workload | 20 | 30 |
| Postmortern&Process Improvement Plan | Hindsight, and propose improvement plan | 20 | 30 |
| total | 600 | 720 |
Third, the job description
1. achieve the basic functions (data loading progress bar and track)
2. Interface package
3. Test Unit
4.Github warehouse upload
Fourth, feelings and experiences
Overall, this pair programming is not only further strengthen the capacity of individuals, to better cultivate cooperative learning ability. The pair programming more successful, and my teammates have benefited. Here not only learned how to write code to carry out, as well as the class of thinking is reflected in the algorithm. I have to say the reference code readability is very high, it is difficult not to use the function. Notes appropriate levels of detail, no description of the place, through group discussions, can be read. The function of each function of the clear, clear call relations, facilitate the expansion and modification subsequent write new features.
But have to say, No gold no one is perfect, there is still a lack of us to each other, for some statements to use, there are still a smattering of feeling, but also the follow-up to practice more. Identify gaps, improve, down to earth, will eventually progress. Come on!