The third convoy operations

Results team members

Full name student ID
Zhang Xu 201731024123
Tu was Sen 201731024129
Zhoucheng Jie 201731024136

Address: https://github.com/Rabbit-Tu/PairProgramming/tree/master/Rabbit-Tu/WinformControlUse
twinning partner address: https://www.cnblogs.com/Tcs199912/p/11615262.html
HTTPS: // www.cnblogs.com/shisan9527/p/11615227.html
Here Insert Picture DescriptionHere Insert Picture Description
PSP table

Personal Software Process Stages Estimated time real time
plan 30 minutes 60 minutes
Estimate how long this task 1200 minutes 1050 minutes
Develop 480 minutes 600 minutes
demand analysis 30 minutes 35 minutes
Generate design documents 10 minutes 10 minutes
Design Review 20 minutes 10 minutes
Code Specification 10 minutes 10 minutes
Specific design 60 minutes 40 minutes
Specific coding 300 minutes 120 minutes
Code Review 60 minutes 20 minutes
test 60 minutes 30 minutes
report 40 minutes 30 minutes
testing report 60 minutes 100 minutes
Computing workload 20 minutes 30 minutes
Hindsight 30 minutes 10 minutes
total 2410 minutes 2155 minutes

First, the problem-solving ideas description

Because the teacher in the class talked about this subject, and to the code, all beginning to do has a certain direction, there is not too much access to information, we decided to make changes to a part of the program on the basis of teacher, plus some features and landscaping. In the window we have added a background music and background image, adding a login system, teachers need to sign in before the roll call to be able to use.

Second, the design and implementation process

We first designed to have two window interface, a login screen, a roll call interface, there are three classes: entity classes, database, reference the class, the role of the database is to simulate SOL database, the information into our professional students, and then use the reference the class assignment information in the database to the roll call interface window, this step need to use the entity class be materialized.

REVIEW

Since we use the code given by the teacher, so basically did not encounter any problems, some problems are solved before the review. For example, insert a picture, the problem of music formats. In fact, when we write the code basically not much division of labor, each of which we are involved, we also work together to write code, but is responsible for the block there is a clear division of labor, such as I am responsible for the operation of the block I was on my computer he was responsible for operations on the block on his computer.

Fourth, Code Description

Here Insert Picture DescriptionThis is a content module, the simulation database in the database.
Here Insert Picture Description
This is a roll call system interface design when loaded
Here Insert Picture Description
This message is output on the window
Here Insert Picture Description
after logging interface window login, the login screen will hide and show a second window that is named System Interface
Here Insert Picture Description
This is the calling information of the student table
below is unit testing picture
Here Insert Picture Description
Here Insert Picture Description
## V. summary
at the junction of the task team, I always see a team in the classroom because the teacher gave us the entire mission demonstrates once, whole or in completing this task relatively easy, in the completion process, we also encountered some minor problems, some small conflicts, but we work together to solve these problems, when the results came out, we are very happy, this is probably where the fun of programming, in We experienced a variety of bug, a problem later, when their own software to run perfectly, but that happiness is incomparable.

Guess you like

Origin www.cnblogs.com/seven7k/p/11615339.html