This module builds heavily on top of what you have been studying during your year 1.
You will be already familiar with HTML, CSS, the general principles of Object Oriented Programming and the basics of computer networks.
The module team will support you in class and review your assignment in class, on a week by week bases. The module team will NOT review your assignment after the last lab.
Be wise, and start your assignment as soon as possible.
No unproved statement should EVER be in your assignments. Every single statement in your assignments has to be either:
A number of different references style are in use in the academic community.
UEL is using the Harvard style.
The Free Software movement advocates the development and use of software that is free to use, free to modify and free to redistribute, on both pragmatic (Stallman, 2002) and philosophical (Stallman, 2004) grounds. The Free Software movement shares many points of contact with the Open Source movement (Perence, 1999), and they are often commonly referred together, as FLOSS (Free/Libre and Open Source Software) (FLOSS project, 2002), FOSS (Free and Open Source Software) (Bollinger, 2003) or F/OSS (MIT Open Source Group, 2002). [...]
Stallman, R. (2004) The Free Software Definition, Free Software Foundation. Available from http://www.fsf.org/philosophy/free-sw.html (Accessed 1 September 2009)
Feel free to incorporate pictures and graphics and media in general into your work, but make sure that you understand the copyright implications.
Creative Commons licenses have been created ad hoc for content. There are six major Creative Commons licenses:
Want to use images for your web site/application? Here are some starting points:
In some cases there are copyright exceptions for academic use. The breath of these exceptions is questionable and untested in trial.
For this module, you will have to work within the same legal context of a IT professional - without any of the academic exceptions.
You are encouraged to use Open Source third-party libraries.
Use what you need. Some examples include:
If you have any resources (code or images) that you have not created yourself, you must include an appendix labelled "List of resources".
It will list all the resources that you have not developped, their name, authors, original URL and where did you use them in your application.
You can include Open Source or public domain resources only, and you cannot include anything without a URL.
Plagiarism is using someone else’s material without attribution and is dealt with through a “Breach of Regulations” hearing.
Repeated Breach of Regulations are grounds for expulsion.
If you do not write any original content, but just “reference” external material, you will not pass this module.
Plagiarism applies both to text and code; any code that you have not produced (e.g. from software or books) but that features in your work without attribution constitutes plagiarism.