 |
 |
 |
|
| Note: The precise requirements have been changed from 2006-7, partly as a result of student feedback |
During the year you will be asked to undertake exercises to practice and develop your skill and understanding of Java programming. Some of these exercises need to be lodged in your portfolio for this module. You will be informed which need to be included.
The portfolio will be submitted for assessment at two stages in the year (in November and February). Stage 1 is worth 15% and stage 2 is worth 20% of the module mark (35% together).
Marking of portfolios will comprise 3 aspects:
- Some marks for making a serious attempt at each exercise.
- A small number of exercises will be fully marked. The selection of these exercises won't be made until after the submission deadline.
- The quality of entries in your error log (quality not quantity) - though it is expected to contain a 'reasonable' number of entries
The portfolio will contain a record of your attempt at these exercises AND a personal error log.
It is suggested that you store evidence of your attempts into a series of Word documents ready for printing for submission. You may find it easiest to create a separate file for each 'lecture'.
The exercises can be completed with other students: they don't have to be exclusively your own work. However it is essential you personally really, fully understand their solution. Whilst the exercises can be completed collaboratively other assessments for the module must be undertaken individually. With each exercise (or set of exercises) you MUST say who you worked with. Undeclared similarity between submissions will be treated as plagiarism - cheating.
Exercise entries require you to provide sufficient and appropriate evidence to show you successfully completed the question. For a typical question this might consist of:
- the Java code written (showing sufficient of the provided code to show where yours 'fits in')
- a screen print showing the output (result) evidence
- a list of the methods (and parameter values used) in running the code (or data used to test it works)
- additionally you need to submit the relevant BlueJ project, electronically
A typical exercise entry might be:
Portfolio exercises
|
Error Log
Your error log should be submitted with your portfolio exercises. Update it as appropriate between submissions of your portfolio.
Every time a new compilation (syntax) error occurs or the Java system tells you that there's been a runtime error you need to record this in your error log (unless you've already recorded an entry for that error).
Building the error log will help you to understand Java but, even more importantly, it will help you to resolve the error next time you get the same error message.
Error log entries should include:
- The error message given
- The 'help' BlueJ provided when that error occured. Press the
button - A description of what you found the problem to be: what you'd done wrong
- How you corrected the problem
- Enough snippet(s) of code for the entry to 'make sense'
A typical error log entry might be:
|
The log should be structured to help you use it as a reference document, so think about how you order the contents.
Sometimes an error will happen and you can't work out exactly what the problem was. It is still worth recording as much evidence as possible in your log. It may help you next time.
Portfolio submission
The submitted portfolio exercises and error log must be submitted in printed form, on paper, not electronically.
You should also submit an electronic version of all relevant Java BlueJ projects. These can be provided on CD or floppy disc or USB key (not DVD please). If you submit a USB key be aware that you will not get it back for a few weeks and that it needs extra care in packaging so it does not fall out.
As with all submitted courseworks include the appropriate signed coursework coversheet.
If you wish, you can upload your module portfolio into your PebblePad PDP portfolio.