| project | content |
| Course class blog link | https://edu.cnblogs.com/campus/xbsf/nwnu2020SE |
| The operational requirements Links | https://www.cnblogs.com/nwnudaizh/p/12521474.html |
| My course learning objectives | Use pair programming to complete the project, and learn to partner benefits |
| This job helped me achieve learning objectives in what areas | Pair programming is very important to have a very profound impression, agree with each other's ideas |
| Knot the other school number - Name | 201771030121- Wang Guowei |
| The blog knot the other job link | https://www.cnblogs.com/wangguow/p/12575605.html |
| The warehouse project Giyhub link address | https://github.com/18215128518wgw/diseaseManage |
I. Purpose and requirements
They (1) experience in software development cooperation, practice pair programming (Pair programming).
(2) method of operation control Github collaborative development programs.
II. Experimental details and steps
1. Read - Chapter 3-4 content "of modern software engineering Construction of Law", to understand and master the style code specification, code design specification, code reviews, pair programming concept
(1) Code specifications style: style code specification includes naming conventions, code shows the style specification (indentation, spaces, line breaks), specification and control specification code comments statements, good code style specification can let other people better understanding. Its principles are: concise, easy to read, unambiguous.
(2) Code design specifications: divided into four parts: naming conventions, style file specification, coding and programming format specification.
(3) Code review: refers to the systematic examination of computer source code, the purpose is to find and fix bugs are found in early-stage software development, and improve the technical quality of software developers.
(4) pair programming concepts: is a method of agile software development, two programmers working together on a computer, a person enter the code, and the other person to review every line of code he entered.
2. knot each other "software engineering experiment two individual events," the project results to evaluate
III. Uses two pair programming mode, combined with our teachers and students daily epidemic reporting system experience, design and development of an information system in line with the needs of epidemic prevention and control work of our school
1. Demand Analysis:
(1) understanding the health of my schools, the presence or absence of the virus to infect new crown, with or without a move back to school and so on;
(2) the secondary sector in the system each person is responsible for epidemic prevention and control work of the department staff can view summary epidemic and provide advanced query features a combination of multi-attribute query and visualization of statistical functions;
(3) The Internet is a good platform, through this platform allows managers to understand the epidemic situation of managers;
(4) the number needed to fill the more difficult to manage, so should be able to query and reporting those who did not fill, and those who did not fill timely reminder.
(5) For the query results, it should be simple and intuitive reflect the epidemic situation.
2. Software Design Description:
(1) Design: The system uses B / S structure, development model incremental model, into a series of software components, one by one member during the design development, implementation, integration and testing
(2) Design data: software re pojo layer entity class declaration database tables, using data stored ArrayList
(3) Interface Design: Mapper mybatis of using a common data manipulation, other general classes inherit the operation data mapper
(4) Process Design: springboot build web applications
3. software and core function code shows:
The software includes a user class and administrators classes, user class is used to gather disease information, management control for background log on and so on.
4. Run the program:
(1) all kinds of school staff and students can gather information epidemic
(2) each of the two departments responsible for epidemic prevention and control work of the department staff can view summary epidemic and provide advanced query features a combination of multi-attribute query and visualization of statistical functions;
(3) prevention and control of a designated person in charge of the school Login "Northwest Normal epidemic prevention and control statistical information" subsystem, you can browse a list of all persons reporting aggregated data, use [] advanced query data can be combined screening system to graphically display each college has students reporting and non-reporting statistics and key data statistics of the epidemic, [export] can query EXCEL file list;
(4) Timing furnished reminder function (SMS alerts)
The junction of the process:
Use the command git clone other projects
And establish a connection to the remote warehouse
Create a new branch and the branch pushed to GitHub
Screenshot discussion:
6. Exhibiting psp:
| psp | SUMMARY | The time required to complete the plan | The actual time required to complete | |
| Planning | plan | 30 | 30 | |
| Estimate | This task requires much time estimate and plan the steps generally work |
30 | 30 | |
| Development | Develop | 1000 | 950 | |
| Analysis | Needs analysis (including learning new technologies) | 200 | 190 | |
| Design Spec | Generate design documents | 100 | 120 | |
| Design Review | Design review (and colleagues reviewed the design documents) | 40 | 30 | |
| Coding Standard | Code specifications (development of appropriate norms for the current development) | 60 | ||
| Design | Specific design | 300 | 210 | |
| Coding | Specific coding | 300 | 200 | |
| Code Review | Code Review | 100 | 60 | |
| Test | Test (self-test, modify the code, submit modifications) | 60 | 50 | |
| Reporting | report | 30 | 50 | |
| Test Report | testing report | 50 | 40 | |
|
Computing workload | 30 | 20 | |
| Postmortem&Process Improvement Plan |
Later summarized, and process improvement plan | 60 | 50 |
7. Summary experience:
I think two people can really bring the results of cooperation 1 + 1> 2, my mate is a man of great ability hands, cooperate with each other in the course of the project, do better at their own terms, the exchange of ideas and so on with all Operators understanding. And to work with him very well, there is no conflict and other irregularities. pretty good. Strong teammate.