GUIDANCE FOR THE FEEDBACK TO THE MODULE OF THE PROJECT WORK,
PROGRAMMING IN C (Autumn 2010)
GENERAL
The group / the student doing individual project work will give
feedback from two project works.
In intranet is
file in which is told who is giving feedback from which project work.
The students who are doing the project work in a group can give the feedback
as a group. However, this requires that all group members will participate
in a feedback. If the group does not have the opportunity to provide
feedback as a group, then each group member will provide feedback independently.
The contributors will send their feedback to discussion area
as an answer to the returned module. So the students giving feedback can
consider whether they have same opinions from the code they gave feedback.
Remember to give constructive and inspiring feedback.
Also, remember that the feedback which has been sent to the discussion area
will be available to all students in the course area.
You will get one point per feedback. And the maximum is 2 points.
Write at the beginning of the feedback from whose module the feedback is
and also the name of the returned work.
Tell at the end of the feedback the name of students who gave feedback.
The feedback is given no later than Friday 15/10/2010.
Feedback
Feedback is given for the following items::
- Programming Style
Is the programming style uniform and will if
follow the guidance given in Müldner's book C for Java programmers
and whether the variables names are descriptive explaining the intended use?
Is it possible to see the type of the variable from the name of the variables?
(In particular, the pointer variables and structures.)
- Commenting
Has the commenting been done according the guidance given in Müldner's book
or in the instructions for project work?
- The module interface
Is the interface well defined in the module?
Is the division to the functions made rationally?
- Error situations
Has it been prepared for error situations in the code?
Is coding carried out in such a way that coding errors
can be detected as early as possible?
- Buffer overflows
Are there buffer overflows in the code? (Check the use
of the function scanf. Is there in the code a call to gets?
Has the progammer reserved memory also to the end of the string
(null) character.)
- Libraries
Only standard libraries may be used in project work.
Is the advice followed?
- Compiling
Compile the program using options given in the project work quidance.
If you got any errors or warnings, then list them.
- Running
If the test program has been done compile it.
Link the object files to an executable program.
Run the test program. Were you able to test the module using the test program?
Please tell the extent to which the module seemed to work correctly?
Also tell us if you find any errors.
- Suggestions for improvement
Give suggestions for improvement.
In particular, if the module interface definition has to be corrected.
- What was well done
Remember also to tell what was well done.