Soft Engineering Practice 2019 Fifth jobs - Programming pair programming implementation

1. Related links:

2. Specific division of labor:

  • 03702112- Blue Feipeng: requirements analysis, testing and commissioning.
  • Pair students 031702349- Wu Sihuan: coding, post updates.

3.PSP table:

PSP2.1 Personal Software Process Stages Estimated time consuming (minutes) The actual time-consuming (minutes)
Planning plan 30 30
Estimate Estimate how much time this task requires 30 30
Development Develop 40 20
Analysis Requirements Analysis (Including learning new technologies) 20 30
Design Spec Generate design documents 240 200
Design Review Design Review 100 140
Coding Standard Code specifications (development of appropriate norms for the current development) 30 20
Design Specific design 30 60
Coding Specific coding 120 150
Code Review Code Review 40 30
Test Test (Self-test, modify the code, submit modifications) 200 100
Reporting report 0 0
test repor testing report 0 0
Size Measurement Computing workload 30 20
Postmortem & Process Improvement Plan Later summarized, and process improvement plan 20 30
total 880 860

4. Design and realization solving ideas described in Description:

  • Code organization and internal implementation design (FIG class):
  • Key Description part of the algorithm and key flowchart of an implementation:
  • Posted you consider important / valuable code snippets, and explained:

5. Additional design features and display

Creative unique design, the design of sense

  • Realization of ideas:
  • Posted you consider important / valuable code snippets, and explained:
  • Achieving results show:

6. catalog descriptions and instructions for use

  • How to organize directory:
  • How testers run your website:

7. Test Unit

  • Explain your choice of testing tools, unit testing is to learn how can a copy of your own simple tutorial?
    Coverage experts winAMS , tutorials Buyer No.
  • Demonstrate the project part of unit test code, test and explain the function of
    temporarily can not display.
  • Description of test data structure of ideas, how do you consider the variety of situations? How do you make things difficult considering the future of testers?
    Uh. . .

    8. Github posted record check code:

    First put it aside.

9. code module junction or exceptions encountered difficulties and solutions.

  • Problem Description: No html + css + javascript, I do not know how front-end design.
  • What did try: surf the Internet, watch videos, and asked the students.
  • It is resolved: temporarily solved some.
  • What harvest: know the characteristics of the front-end design and related design process language.

10. Evaluation of your teammates

  • Places worth learning: There is a strong sense of responsibility-encoding capability.
  • Areas for improvement: the need for better co-ordination and communication, as well as enthusiasm for the job.

Guess you like

Origin www.cnblogs.com/L031702112/p/11704656.html