| teaching home |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Multimedia Applications - Introduction.Multimedia Applications is split between two lecturers. This site covers the assignment, assessment critieria, and the parts of the module concerned with the methodical development of multimedia applications. The parts of the module concerned with the evaluation of applications is only minimally covered here, although you may find some useful links. The supporting materials for this part of the module are organised in the usual grey - green - blue scheme explained on the teaching home page. top1. Notes and Supporting Materials.top2. Lecture and Tutorial Programme.
top3. Assignment.The assignment for this strand of the module - the disciplined development process required to produce a high-quality multimedia application - is distinct from that for the 'evaluation' strand of the module. In this strand you are required to develop a prototype application and document that process carefully. The application follows on reasonably naturally from the initial familiarisation exercise; in the familiarisation exercise you will produce a fragment of a multimedia translation of a classic ghost story, in the assignment you will produce a portion of an 'annotated' classic text. It is very common for publishers to produce multimedia companions to classic stories and plays. These are useful for students and also appeal to general readers, so they have a wide market and are generally inexpensive. Your task is to produce a prototype version of a multimedia companion to a few pages of a classic text (an edited section of the opening pages of Joseph Conrad's 'Heart of Darkness'). You will be given some initial notes on the text to get you going; but apart from that the kind of treatment that you develop is very much up to you. What matters is that whatever design decisions you make are well thought-out and documented. To ensure that your design is well thought-out and documented, you should follow the step-by-step exercises included in the notes. We will work on these in lectures and tutorials, and it should be fairly easy for you to get a good mark as long as you attend and follow instructions. You may use whatever implementation technology you wish to produce your prototype (that is one of your design decisions), but I would imagine that the majority of you would be likely to produce web pages produced with Dreamweaver. You need only produce 3 or 4 (dense and fairly interactive) screenfulls/pages of your prototype - but it should be documented in not more than 2000 words and 10 pages. Use diagrams, images, etc. to get your message across in your documentation. Your prototype must fit on a 1.44Mb floppy, and both prototype and documentation must be handed in by the end of week 12. top4. Assessment Criteria.Approximately equal weighting will be given to each of the criteria below, but you should notice that they aren't fully independent. For example, you can't really produce a 'good' design for an application without a clear purpose, audience and objectives - since it isn't clear what you are trying to design. Equally, a convincing prototype can prove that an odd-looking design does actually work. Also, a prototype can't prove a design concept unless it has some substantial content - since the design exists to deliver content to the user. You should think of all of these criteria as interlinked to form something which will be judged as a package. Whilst I will treat this marking template as a checklist, there will also be some deeper assessment of coherence going on behind the checklist.
top
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| top |
|