20172327 Pair programming project - four arithmetic operations first week phase summary
Pair programming project - four arithmetic operations first week output stage summary blog
Pairing objects:
| Student ID: 20172317 Name: Jiang Zixing Partner blog address for the first week: |
| Student ID: 20172320 Name: Li Wenzhou Partner blog address for the first week: |
Role: Driver: Jiang Zixing Passenger: Li Wenzhou and Ma Ruifan |
demand analysis:
| **1. Automatically generate questions** It can be used independently (it can realize the function of writing test classes to generate questions independently), and can generate questions of different levels, similar to: Level 1 questions: 2 + 5 = 10 - 5 = and so on. Number of questions, an operator's question**2. Question operation (judgment)** - can be used independently - convert infix expressions into postfix expressions and calculate - judge whether the user's answer is correct or not, and output the correct result**3 .Support true fractions** - can be used independently - realize the calculation of fractional formulas |
- analyze:
To generate questions, we classify the difficulty by adjusting the symbols and numbers.
1. Difficulty 1 is an operation between two integers
2. The probability of a true score in Difficulty 2 and Difficulty 3 is determined by a random number, and The position of this
score is fixed
Design ideas:
UML class:
picture
Ideas:
Create a true score generation class
Create three difficulty classes
Create an infix-to-suffix class Create a class that
calculates suffix expressions
Rate)
Code implementation (key code explanation)
- True Score Class:
- analyze:
- Difficulty 1, 2, 3:
- analyze:
Code hosting address:
- Source code link:
- commit commit information:
Comment on paired partners:
PSP time statistics:
| PSP2.1 | Personal Software Process Stages | Estimated time (minutes) | Actual time (minutes) | |
|---|---|---|---|---|
| Planning | plan | 60 | 60 | |
| Estimate | Estimate how long this task will take | 100 | 100 | |
| Development | develop | 800 | ||
| Analysis | Requirements analysis (including learning new technologies) | 100 | ||
| Coding Standard | Code Specifications (to develop appropriate specifications for current development) | 30 | ||
| Design UML | Design project UML class diagram | 50 | ||
| Coding | specific code | 30 | ||
| Code Review | code review | 50 | ||
| Test | Testing (self-testing, modifying code, committing changes) | 30 | ||
| Size Measurement | Computational workload (actual time) | 30 | ||
| Postmortem & Process Improvement Plan | Post-event summary, and propose a process improvement plan | 30 | ||
| total | 1240 |
---End of recovery content---