When conducting research into a topic, try to provide clear evidence that you developed new knowledge and skills while completing the assignment.
While providing references is a necessity, it's also important that you demonstrate within your discussion how and why you considered and/or adopted the approaches of others to the problem.
Make it clear why you adopted the approach you did, comparing it to the other approaches.
Make sure to search online for various approaches to the problem, including other people's attempts at solving a similar problem. Summarise the results of this search in the project documentation.
Use concepts and skills you learned in other subjects. The ability to tie all your various modules together is important.
Consider your findings from researching the problem and use them to develop a plan for the project. A good plan will be evident in the layout and organisation of your code.
Demonstrate how you made sure your software or project did what you said it would do at the start. For instance, you might consider devising some small tests that demonstrate that your submission provides the right outputs.
You should draw up a plan for completing an assignment and make the plan evident in your submission. You should try to stick to this plan, and your project timeline should clearly demonstrate your work towards it.
Consider various audiences when documenting your work. A technical audience, such as a lecturer, will require one style of description while a non-technical audience, such as a recruiter, will require another. Unfortunately, most of the time your work needs to speak to both.
submissions/assesment/guidelines.txt · Last modified: 2020/06/20 14:39 (external edit)