20172313 Pair Programming Project-Four Algorithms First Week Phase Summary

20172313 Pair Programming Project-Four Algorithms First Week Phase Summary

paired object

• Student ID 20172332 20172326
• Name Yu Xinyue Kang Haoyue
• Buddy Week 1 Blog:
• Take on the role:
  • Driver: Yu Kunpeng
  • Driver: Yu Xinyue
  • Driver: Kang Haoyue
    (everyone takes turns "driving", expresses their own opinions, and has devoted their own efforts and efforts to this project operation, there is no situation of who is the driver and who is the co-pilot)

demand analysis

• It can automatically generate four arithmetic questions for elementary school (including addition, subtraction, multiplication and division) according to different difficulty requirements.
• Can support whole numbers and true fractions
• Can support multiple operators mixed operation
• Ability to generate parentheses to change the order in which expressions are evaluated sequentially from left to right
• Able to judge whether the result entered by the user is correct
• Expansion requirements
  • Multi-language support: Simplified Chinese, Traditional Chinese, English
  • Deduplication of generated topics
  • Statistics on the correct rate of user calculations

Design ideas

• UML graphics
• Ideas:
• Create a number generation class (including true fractions and integers)
• Create a symbol class (addition, subtraction, multiplication and division and parentheses)
• Create a class that generates expressions
• Create a conversion class that converts infix expressions to postfix expressions (using stacks)
• Create a class that evaluates postfix expressions
• Create test class

PSP time statistics:

PSP2.1	Personal Software Process Stages	Estimated time (minutes)	Actual time (minutes)
Planning	plan	1
Estimate	Estimate how long this task will take	1
Development	develop	6
Analysis	Requirements analysis (including learning new technologies)	1
Coding Standard	Code Specifications (to develop appropriate specifications for current development)	1
Design UML	Design project UML class diagram	1.5
Coding	specific code	6
Code Review	code review	2
Test	Testing (self-testing, modifying code, committing changes)	2
Size Measurement	Computational workload (actual time)	2
Postmortem & Process Improvement Plan	Post-event summary, and propose a process improvement plan	1
	total	26.5