The third pair programming operation
My blog address | link |
---|---|
Teammate blog address | link |
Fork github project address | link |
GitHub project address | link |
Address operational requirements | link |
Form a .PSP
PSP | Personal Software Process Stages | Estimated time consuming | The actual time-consuming |
---|---|---|---|
Planning | plan | 2Hour | 1.5Hour |
Estimate | Estimate how much time this task requires | 3Day | 3Day |
Development | Develop | 2Day | 1Day |
Analysis | Needs analysis (including learning new technologies) | 4Hour | 3Hour |
Design Spec | Generate design documents | 3Hour | 5Hour |
Design Review | Design review (and colleagues reviewed the design documents) | 5Hour | 1Hour |
Coding Standard | Code specifications (development of appropriate norms for the current development) | 3Hour | 4Hour |
Design | Specific design | 1Day | 1Day |
Coding | Specific coding | 1Day | 1Day |
Code Review | Code Review | 3Hour | 3Hour |
Test | Test (self-test, modify the code, submit modifications) | 3Hour | 2Hour |
Reporting | report | 4Hour | 4Hour |
Test Report | testing report | 2Hour | 2Hour |
Size Measurement | Computing workload | 1Hour | 1Hour |
Postmortem & Process Improvement Plan | Later summarized, and process improvement plan | 3Hour | 3Hour |
total | 76.5Hour |
II. Procedural requirements
The work is designed to achieve a WinForm randomly named program that can meet the basic needs of teachers named, required program can not run error, and have certain characteristics.
III. Formal operations
3.1 Specific division of labor
Student ID tail number 24234 Wu Hao Zheng (ie me) is responsible for window design, student information to improve the code, testing and evaluation.
Write student number 24214 tail number Xu Jiawen (my teammates) is responsible for program code development.
Despite this division, but we learn together faith, the principle of common progress, mutual cooperation, Qi force to complete the job.
3.2 answer ideas:
In fact, most begin to see the operational requirements of the time, me and my teammates believe the job for us, with some difficulty, and good teacher provides a clear answer thinking in the classroom, and to code written in terms of we offer a great help.
For this major program randomly named overall demand, we can be divided into four parts, a large task into several small operational tasks. This program has the following specific needs two things: 1 Load the list of students; 2 execution start and stop named named two commands to complete random roll call...
First, we believe that a good program window should have a more beautiful appearance, so it took some effort on the window designs. The final results are as follows:
We then give the teacher on the basis of the program has some optimization on the code to make the program more authenticity, but due to some students said privacy issues specially marked mosaic will learn number information. The following operating results for the program diagram:
3.3 Code Review
(1) review the code meaning: First, the problems found in the review of the code, the vast majority can be found independently by the developer. From this sense, the reviewer is in dry developers for developers should have to do. In addition, the code in question in the review and response to help team members understand each other, like martial arts person to watch each other as reviews. When the team has added a new member, code reviews can be very effective in helping new members understand the team's development strategy, programming style and workflow.
(2) Code review rule: Reference Professionals blog
(3) our code review stage: Since this is the work we accomplished together, while using two computers, you can always offer advice to each other, ready to see the progress of both sides when an error code is found or made a mistake because of personal reasons, then you can always point out, the review stage of our work will be relatively relaxed, not too many problems.
3.4 code analysis
3.4.1 Forms main code program (part) Theme:
3.4.2 progress bar codes theme
3.4.3 student data entry cap:
3.5 Unit Testing
Code Screenshot:
3.6 Additional Features
We try to add a search function in the original code, based on the system of higher utility named, but because of basic C # is not hard enough, eventually failed, in the future there is a chance, we'll ask the teacher, in order to improve our program.
3.7 Pair programming process and Photos
3.7.1 pair programming process: the whole process of pair programming, I and my teammates get along very harmonious, there are problems in time, not procrastination, there is more cooperation tacit understanding, rational division of labor, their duties, general the pair programming I was very pleased, and I learned from my teammates there also learned a lot of new things.
3.7.2 Pair job Photo:
IV. My thoughts and summary
This time the job is done based on the teacher to modify the program, through this work I realized that his own shortcomings, and for the future of the program and complement their own