UCL DEPARTMENT OF ELECTRONIC AND ELECTRICAL ENGINEERING

UCL logo

Obtaining Programs from the Internet

On using
the internet
in general
Identifying
a reliable
web source
Citing
the web
Using
another's
program
SUN's Java
Tutorial
SUN's Java
Documentation
Downloading
the Java
Platform
M T Flanagan's
Java Library

On using the internet in general

The internet is an extremely valuable asset, particularly if you are looking for Java programs. Use it, BUT use it with care because:
  1. it contains
    • many pages that contain errors of fact
    • some pages that contain errors in mathematical derivations
    • countless examples of sloppily written and/or badly documented programs
    • a large number of pages that are total rubbish however attractively presented
  2. copying directly from the internet into your coursework, without obtaining any necessary permission and without an appropriate citation is plagiarism, and a form of plagiarism that is quite easy to detect, as several students have found to their cost. Use the internet to learn more about your subject; not to bypass learning about your subject.

Hints on identifying a reliable web source

These have been adapted, for Engineering Students, from the Mayfield Web Tutorial, a site that is well worth visiting for more detailed advice.
  • Who is the author or sponsor of the page?
    Check the url. If it contains the extension .edu or .ac it is an academic and/or educational institution but this does not guarantee quality. Check if the web page is part of a course and whether it has been written by the lecturer. If not, remember that many universities allow their students to post what ever they wish on their personal web sites as long as it is not illegal, immoral or libellous. You may be reading part of the work of a student who knows even less about the subject than you do. On the page you are citing, or on a page linked to it, the authoring individual or organization should be identified, that individual's qualifications should be apparent, and other avenues of verification should be open to you. An example of a reliably documented source may be seen in my own Java library web page http://www.ee.ucl.ac.uk/~mflanaga/java. A page created by a person or an organization that does not provide this information is not a good source to cite.
  • Is contact information provided?
    If no identification is given or the only identification available is so cryptic as to be meaningless, e.g. "Society for less than integrated circuits", you should suspicious of the page's reliability. If the page is sponsored by a reputable person or organization, there should be some other way to verify that reputation, such as an e-mail or postal address. (Note that a tilde [~] in the page's address usually indicates a personal home page and may require more searching for reliability.)
  • What is the purpose of the page?
    Why is this information being posted - as information, as a public service, as a news source, as a research tool for academics, as an advertisement, as a personal axe to grind, or as a way to gain attention?
    Company web sites can be a very valuable source of information about their products but, obviously, will generally rate their product as superior to that of a competing company and may be less forthcoming about any adverse environmental consequences of the use of their products.
  • Can you verify the information on the Web page some other way?
    For example, can you check the page's bibliography (if there is one) against your library's holdings or check the information against a source in the library? Indeed a web search can often be a useful and rapid way of identifying more conventional sources of information.

Citing a web page in your reference list

The conventions for citing electronic sources are still somewhat fluid, differing slightly between the UK and the US, but all involve quoting the author/s (surname, forename or initial) if available or the organisation responsible for the web site, title of the article or of the web page, date of the creation or update of the web site if available, date on which you accessed the web site and the url of the web site. Examples, using the British Standard, follow:

  • Authors known and the date that the web page was posted known
      1.  Danecek, Jiri and Slavik, Pavel. Teaching Java at CTU Prague. 7th October 1999. Retrieved on 4th August 2004 from the World Wide Web:
    http://www.ulst.ac.uk/cticomp/monitor12/jdanecek.html
  • Author/s not known but authoring organisation, The Wikipedia Free Encyclopedia, known
      2.  Wikipedia. Fast Fourier transform. 10 August 2004. Retrieved on 12th August 2004 from the World Wide Web:
    http://en.wikipedia.org/wiki/Fast_Fourier_transform
  • Author/s not known but authoring company, Microstar Laboratories, known
    Date that the web page was posted not known
      3.  Microstar laboratories. Process Control. No date. Retrieved on 7th August 2004 from the World Wide Web:
    http://www.mstarlabs.com/adwds/adpid02.html

Using another's program

Using another's program/s, method/s or procedure/s without permission and/or acknowledgment is academic plagiarism and may qualify as copyright infringement. The following requirements apply not only to programs discovered on the web but to any program that you may wish to use, e.g. if the program is one written as part of an earlier third year project upon which your project may be building.

If you discover a program, e.g. on the web, that you would like to use as part of your own work you must check the source code and accompanying documentation for permissions to use and/or copyright restrictions.
If copying for use is allowed:
  • Follow the conditions of use strictly. Typical conditions of use may be seen at the top of any of my own Java library programs, e.g. Db.java, or any Sun Java example program, e.g. Animator.java. This usually involves including an acknowledgement (see below) and/or retaining the copyright or permission to use paragraph in your copy. They almost always exclude copying for commercial use.
  • Email or write to the author/s thanking them for the use of the program and give a very brief description of your use of the program.
  • Additionally
    • If you are including the copied program as part of your own larger program, e.g. just as one class in several in a Java application:
      • include an acknowledgement in the documentation (comment) lines at the top of the full listing. This should be there even if not requested by the original author/s. It should either take the form required by the original authors or, if this not provided, give details of the original source (see Citing the Web above for the correct method of citing a web source);
      • include a similar acknowledgement in the documentation lines at the top of the listing of copied program itself. This should be there even if not requested by the original author/s;
      • the above acknowledgements and citations should be mirrored in any documentation, additional to that within the source code, describing the program.
    • If you are including a copied method or procedure as part of your own program:
      • include an acknowledgement in the documentation (comment) lines at the top of the full listing. This should be there even if not requested by the original author/s. It should either take the form required by the original authors or, if this not provided, give details of the original source (see Citing the Web above for the correct method of citing a web source).
      • identify and acknowledge the copied method in the comment line/s immediately above the method;
      • similar acknowledgements should be included if the copied method has been used as the basis of a very similar method, e.g. conversion from C to Java. An example of the documentation and acknowledgement of this type can be seen in my program FourierTransform.java;
      • the above acknowledgements and citations should be mirrored in any documentation, additional to that within the source code, describing the program.
    • If using the copied program as a stand alone program:
      • ensure that the originators conditions of use are met and correctly documented and referenced;
      • ensure that it is clear in any relevant coursework or project report that this is not your own program and acknowledge and cite the source.
If it is not clear whether you may copy a program contact the authors, explaining briefly why you wish to copy their program, and ask their permission to copy their program.

Further advice on documenting a program may be found on Documenting your Program.

SUN's Java Tutorial and Java Platform Downloading Instructions

SUN have an excellent on-line Java tutorial that will not only get you started in writing a Java application or applet but gives clear instructions on how to download and install the SUN Java Platform (the Java compiler, interpreter etc) on your home machine if you wish to do so. The tutorial and download instructions may be found through http://java.sun.com/docs/books/tutorial/getStarted/cupojava/ . Downloading the Java Platform onto your home computer is NOT a course requirement for any departmental course but many students, especially if using Java in a third year project, find it convenient to do so (Installing and running Java on a PC). The Java platform has been installed on the Departmental Network and Java programs can be run on the Departmental Sun work stations (see Running a Java Program on a Sun Work Station for details).

SUN's Java Documentation

SUN provide extensive documentation in support of the Java Platform. A useful index to this documentation is provided on http://java.sun.com/j2se/1.4.2/docs/api/index-files/index-1.html.

Typical Sun Java documentation pages:


    Math Class        link: http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Math.html/
    Double Class        link: http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html/
    System Class        link: http://java.sun.com/j2se/1.4.2/docs/api/java/lang/System.html/



Departmental home page


      This page is maintained by Michael Thomas Flanagan    -    last update: February 2009
      Department of Electronic and Electrical Engineering, University College London - Torrington Place - London - WC1E 7JE - Telephone: +44 (0)20 7679 7306 - Copyright © 1999-2007 UCL
      Disclaimer | Advanced Search |