illustrate
The assignments corresponding to the published grades are:
Week 2 Personal Assignment: WordCount Coding and Testing
If a student has any objection to the assignment score, they can appeal within 72 hours of the announcement of the score (the deadline is 0:00 on April 26), and the methods are as follows:
- In the second week of the online Q&A area of the BearingPoint platform, a grievance thread will be posted.
Scoring Rules
The total score of this assignment is 55 points, which are scored according to the program and blog. Among them, the program has a full score of 35 points and the blog has a full score of 20 points. There are two additional questions, out of 10 points. The specific details are shown in the table below.
| serial number |
Scoring item |
Scoring sub-items |
Scoring Rules |
full score |
| 1 |
Program work (35 points) |
source code management |
Points are given by the commit comment information in the source code management, the content of the incremental modification, and whether there are running instructions. |
5 points |
| correctness |
The basic correctness requirements should be met around the requirements, and the running results should be correct (it will be verified by a standard test set). |
8 points |
||
| Notes |
There should be reasonable and clear annotations in the procedure. |
2 minutes |
||
| Test case design |
The number of test cases is not less than 10 (2 points), the test case design is reasonable (8 points), and at least the test cases can be designed in combination with the methods introduced in the classroom. |
10 points |
||
| test script |
Test scripts should meet the characteristics of typicality, testability, reproducibility, independence and so on. The scripts are well designed and support good test management. |
10 points |
||
| 2 |
Blog (20 points) |
Github project address |
Github project address is given at the beginning of the article, no points for missing or wrong addresses |
1 point |
| Fill out the PSP form |
Including the estimated development time of each module before program development, and the actual development time of each mode of the program |
2 minutes |
||
| Describe problem solving ideas |
The process of how to think and how to find information after getting the topic at the beginning. |
3 points |
||
| Program design implementation process |
Including how the code is organized, for example, there will be several classes, several functions, what is the relationship between them, and the key functions should draw flowcharts. |
3 points |
||
| code description |
Show the key code of the project, and explain the ideas and notes |
4 points |
||
| test design process |
How to design test cases, which places will lead to high risk of the program, how to design test code, and evaluate your own test design in combination with the requirements of test evaluation. Can these test cases meet the requirements of the program test? |
4 points |
||
| Reference Links |
Links to all references read and referenced during the completion of the assignment are listed at the end of the blog and cited in the descriptive text corresponding to items (2) to (5) |
1 point |
||
| homework improvement |
2 points for responding to the comments of teachers and teaching assistants, including replying to comments and improving the blog; Otherwise, no points will be awarded for not responding to comments from teachers and teaching assistants, or not improving the blog, or casually perfunctory comments from teachers and teaching assistants (e.g., "ummm", "good", etc.) |
2 minutes |
||
| 3 |
Additional questions (10 points) |
Advanced function implementation |
Complete the advanced functions of WordCount and run correctly. |
5 points |
| Implementation in multiple languages |
Two languages are used for development and implementation. The program developed in one language should meet the requirements of 1 and 2 programs and blog work, and the program developed in the other language should complete the basic functions and extended functions of WordCount, and meet the requirements of source code management. requirements, and the basic correctness requirements of the program, |
5 points |
other instructions
Be careful to submit assignments on time.
l Complete and submit on time - normal grading
l Late delivery within one week - 0 points
l Late submission of more than one week or no submission - the score for this assignment will be deducted , that is, minus 55 points
l Plagiarism - the points will be deducted according to twice the full mark of this assignment , that is, minus 110 points. [All forms of plagiarism such as code and blogs are strictly prohibited! Please don't touch the bottom line, classmates, don't say it is unpredictable! 】
Explanation of terms in the grade sheet
- SM: Source Control
- CO: correctness
- RM: Notes
- TC: Test Case Design
- TS: Test Script
- GIT:github project address
- PSP: Fill out the PSP form
- SOL: Describe problem solving ideas
- DES: Program Implementation Process
- CD: Code Description
- TDP: Test Design Process
- REF: Reference Links
- IMP: Homework Improvements
- AF: Advanced Function Implementation
- ML: Multilingual Implementation
score
1505 class homework results
emphasize again:
1. For those suspected of code plagiarism and objection to their own results, please go to the second week online Q&A area of the BearingPoint platform to post an appeal!
2. Students who do not have grades in the grade sheet are because they did not see the submitted assignments in the class blog and personal blog.