Project Address: https://github.com/lzzz7/PairProgramming.git
twinning partners work address: https://www.cnblogs.com/wangxu3/p/11615736.html
job link: https://www.cnblogs.com /cherish599/p/11577268.html
Part1, PSP form
| PSP2.1 | Personal Software Process Stages | Estimated time consuming (minutes) | The actual time-consuming (minutes) |
|---|---|---|---|
| Planning | plan | 20 | 20 |
| Estimate | • Estimate how much time this task requires | 20 | 20 |
| Development | Develop | 600 | 710 |
| · Analysis | · Needs analysis (including learning new technologies) | 120 | 150 |
| · Design Spec | Generate design documents | 60 | 60 |
| · Design Review | · Design Review (and his colleagues reviewed the design documents) | 30 | 30 |
| · Coding Standard | · Code specifications (development of appropriate norms for the current development) | 30 | 20 |
| · Design | · Specific design | 60 | 60 |
| · Coding | · Specific coding | 150 | 230 |
| · Code Review | · Code Review | 60 | 60 |
| · Test | · Test (self-test, modify the code, submit modifications) | 90 | 100 |
| Reporting | report | 105 | 125 |
| · Test Report | · testing report | 50 | 60 |
| · Size Measurement | · Computing workload | 25 | 30 |
| · · Postmortem & Process Improvement Plan | · Hindsight, and propose process improvement plan | 30 | 35 |
| . | total | 725 | 855 |
Part2, flowchart
Part3, problem-solving ideas
a)一个程序首先要实现的是“能用”，程序能用之后就应该考虑让用户“喜欢用”，喜欢用可以通过不断的优化代码来实现，但是由于我和伙伴的还在努力学习，所以在这方面能做的有限；而程序使用的第一印象就是GUI，所以我们做好GUI的设计。
b)确定程序的基本功能：加载学生，随机点名学生；在程序的设计方面老师在课堂上讲了很多，设计分为1.DaoLayer 2.DataBase3.Entity4.DianMing四层，相互之间引用。接口是这个程序的重点，不然难以运行起来。
随机抽取学生方法：
private void timerCallName_Tick(object sender, EventArgs e)
{
Random ra = new Random();
int i = ra.Next(stuList.Count);
lblName.Text = stuList[i].Name;
label3.Text = stuList[i].Id;
}Part4、代码互审及代码规范
代码互审：代码的互审在最后真的很有用，自己有时候不管检查多少遍，都不会很快的发现问题，但是互审真的很利于发现问题，因为是一些寝室结对的，所以互审很方便也很快，互审之后得出的结论，发现我们在接口的运用不能很快的把握住重点。
代码规范：代码规范主要是结合书上和网络的知识来学习代码规范：代码规范链接
Part5、代码编写
1.按照四个层来实现程序运行
2.新增“抽取学号功能”
Part6、代码测试
代码测试这方面花了我们很久的测试，在网络上学习到有一个查覆盖率的方法，就试了一试，之后我们也进行了简单的测试。
Part7、合作及总结
下面是我们合作编写的照片。
Summary:
1. the code side also needed to be done, not very skillful application interfaces, and sometimes around the skull easy to faint.
Conclusions of what programming to consider a lot, such as assigning tasks, time planning, many aspects need to be considered in this pair programming process, the found a lot of problems; this is just the two of pair programming, after the large-scale project requires a full team to design and complete, which need to consider more aspects; through this twinning program, we should be conscious of to develop their own, to exercise this role in the project to become the PM.