ARIN 3600 — Arts Informatics ProjectFaculty of Arts
School of English, Art History, Film and Media
March Semester 2004
Arts Informatics Project II
Unit of Study Guide ARIN3600
Teaching Staff: Kathy Cleland, Christine Crowe, John TonkinCoordinators: Christine Crowe and Kathy Cleland
This Unit of Study has been designed to allow students in the Bachelor of Arts Informatics program to apply and develop their Information systems knowledge in a project in the field of their major or, with approval, in other departments or centres in the University. The Unit includes technical workshop sessions to provide students with expert advice on the development of their projects using database and web tools.
Kathy Cleland
Room S344 John Woolley Building
9351 4721
kathy.cleland@arts.usyd.edu.au
Christine Crowe
Room 164 Mills Building
9351 3774
christine.crowe@arts.usyd.edu.auJohn Tonkin
john.tonkin@bigpond.com.au
Pat Ricketts
BAI Office
N406 John Woolley Building
9351 2226
Office hours: 10-1 and 2-4Monday - Friday
arinenquiries@arts.usyd.edu.au
Consultation times will be negotiated
For updates of information in this guide, and links to resources, please go to our website:
http://teaching.arts.usyd.edu.au/Informatics/ARIN3600/
The website will be available in Week 2
Unit of Study Structure and Organisation
Seminars: Wednesday 4-6, R. C. Mills Building 209
Technical workshops: Wednesday 4-6 Arts Computer Lab 2.
Students are required to attend the seminar sessions and technical workshops, as well as their groups’ consultations with project supervisors, as arranged throughout the semester.
At some stage during the semester we will forgo the seminar format in the Wednesday 4-6 timeslot and move to the technical workshops in CL2, again on Wednesdays 4-6.
Groups can then arrange regular consultation with their project coordinator at time suitable to both parties.
Learning Outcomes
As a result of successfully completing this unit of study you should be able to demonstrate:
the ability to apply and refine the knowledge and skills gained from your Arts and IS major in a way which demonstrates a critical understanding of the issues involved
information literacy, including the ability to recognise, locate, evaluate and use information in a range of contexts
research and inquiry skills, involving the ability to present evidence and argument in support of your own particular perspective
the development of problem-solving skills, involving the ability to identify problems, and respond effectively to unfamiliar problems in unfamiliar contexts
a critical understanding of the social and cultural contexts within which information and technological systems are used
the development of independent learning and critical thinking
the ability to work effectively towards a particular goal as part of a group
the ability to reflect upon and evaluate your own performance
oral and written communication skills
the effective use of communication and information technologies
Graduate Attributes promoted in ARIN 3600:
This unit of study has been developed to enhance graduate attributes promoted by the Faculty of Arts at the University of Sydney. The learning outcomes above, and the assessment strategies which follow, are linked to the development of these graduate attributes:
1. The development of skills for Research and Inquiry.
Graduates of the Faculty of Arts will be able to create new knowledge and understanding through the process of research and inquiry. Specifically, this Unit of Study aims to develop the ability to:
think independently and rigorously, both in creative and analytical ways;
exercise critical judgement and critical thinking to create new modes of understanding;
identify, define, investigate, and solve problems;
learn from, and build on, existing knowledge and understandings within your discipline(s);
2. Information Literacy
Graduates of the Faculty of Arts will be able to use information effectively in a range of contexts. Specifically, this UoS aims to develop the ability to:
recognise pertinent information needs;
locate relevant information efficiently and effectively;
evaluate information and its sources;
understand social and cultural issues in the use of information;
use information in critical and creative thinking;
use contemporary media and technology to access and utilise information.
3. Personal and Intellectual Autonomy
Graduates will be able to work independently and sustainably, in a way that is informed by openness, curiosity and a desire to meet new challenges. Specific to this Unit of Study:
be intellectually curious and able to sustain intellectual interest;
be capable of rigorous and independent thinking;
be open to new ideas, methods and ways of thinking;
be able to respond effectively to unfamiliar problems in unfamiliar contexts;
be independent learners who take responsibility for their own learning;
be able to work effectively in teams and other collaborative contexts;
be able to evaluate their own performance objectively;
4. Ethical, Social and Professional Understanding
Graduates of the Faculty of Arts will hold personal values and beliefs consistent with their role as responsible members of local, national, international and professional communities. Specifically, this UoS aims to develop the ability to:
recognise and honour your ethical responsibilities towards your colleagues, clients, and the wider community
5. Communication.
Graduates of the Faculty of Arts will recognise and value communication as a capacity for negotiating and creating new understanding, interacting with others, and furthering their own learning. Pertinent to this UoS is:
the recognition of the importance of continuing to develop their oral, visual, and written communication skills;
the ability to use appropriate communication technologies.
Assessing your learning:
Each assessment requirement has been designed to link to the other forms of assessment in this Unit of Study. The review and critical assessment of an informatics object, for example, should address an informatics object that is related to your group project. Your individual essay topic should again be related in a useful way to the project. This unit of study is ‘inquiry-based’ in this aspect. In other words, in the formulation of your group projects, you will need to determine what you need to know next, or what skill you need to develop next, in order to complete the project. The review and critical assessment of an informatics object, and the essay, are designed as assessment tasks that are related to the completion of your group project.
Please note that this is an 16-credit-point unit of study, and the Faculty of Arts expects that you spend, in addition to face-to-face class time, at least 18 hours per week on private and group research, completion of assessment tasks and preparation for seminars, and consultation with your group supervisor when required
ARIN3600 coversheets are available from Pat Ricketts in the Bachelor of Arts Informatics Office, N406, John Woolley Building.
Office Hours 10 - 1 and 2 - 4, Monday to Friday, phone: 9351 2226.
Assessment items are to be placed in the box outside the Arts Informatics office.
1. Attendance at workshops. Attendance at the workshops for technical instruction and trouble-shooting is compulsory.
2. Project Formulation
Word length: 1500
Due date: April 21st (week 6)
Weighting: 10%
3. Review and critical assessment of an informatics object. This can be, for example, an operating system, a web site, a specific application, a game, etc. We strongly advise that you to choose an object which relates constructively to your group project.
Word length: 1000
Due date: April 28th (week 7)
Weighting: 10%
4. Research Essay. The essay will relate to an issue which you have recognised, in the formulation of your project, as informing your group project in some way, and which you are interested in pursuing in an extended form. Essay questions must be approved in writing (email) by your supervisor
Word length: 4000
Due date: May 12th (week 9)
Weighting: 40%
5. Project Presentation. All students are to be involved in the project in its conceptualisation, formulation and presentation.
Length of time: 20 – 30 minutes
Due date: Weeks 12 and 13
Weighting: 20%
6. Project Report
The project report involves a written document which addresses the themes and issues, as well as skills developed, in the completion of the project. The report also will include a short reflective statement in which you, as a group, may, for example, discuss possible ways that you could, now that you have completed, improve upon the project, and your reflections on your participation in the group process.
Word length: 1500 words
Due date: June 9th (week 13)
Weighting: 20%
Guidelines for Assessment Tasks:
1. Review of an Informatic Object
What is an informatic object?
An informatic object is an information system or a part of an information system. It may be a piece of hardware, software or a language, a program, an application, or an accessory; it might be a protocol (including mobile, wireless or network protocols); it could be a standard or a file format, a new media platform or a particular interface; it could be a specific database, a specific network, or a specific website; it could be an online community, a listserve, a blog, a game, etc.
Choosing your object
It is advisable, though not compulsory, to select an object that has some relevance to your group project. They need not be directly related; it might be a similar sort of information system, or it might address a similar audience; it might contain similar information (content), or just raise similar issues in informatics.
If you are unsure about whether your object is suitable, contact Christine or Kathy to discuss it as soon as possible. If you plan to review an information service, a community, a network, a list, or a blog, you should join/subscribe immediately so that you have more of an experience of it to draw upon.
The content of the review must demonstrate critical engagement. This means that the review must not merely consist of simple description.
Guidelines:
state the name of the informatic object you have chosen to review;
begin with a brief description of its purpose;
give a critical assessment of its successes or failures;
demonstrate some awareness of the issues in informatics that the object raises, and the social and cultural contexts within which it is used. These issues may include ethics/politics (access, ‘freedom’ of information, etc); functionality (usability, etc); and/or aesthetics (interface design, etc).
Your review must be consistent with scholarly standards of presentation. It must be:
written in essay format (i.e. not in point form, not notes)
provide references and footnotes as required
Some items to look at for ideas:
any software or resources you typically use in your studies in the humanities;
any sites or other resources you’ve come across in your project research;
other university sites; any models or competitors for your project;
2. Project Formulation:
The project formulation is designed so that groups can receive pertinent and timely feedback as to their progress in the project.
Guidelines:
In formulating your projects bear in mind the principles that you have learned in your information system studies, with particular attention to the phases of project management
Project formulation: client profile, user profiles, needs analysis, identification of current resources;
methodology; timeline and milestones.
Design and collection of data
Implementation of system: construction of a prototype; user testing, feedback and revision
3. The Essay
We advise that your essay topic be devised in consultation with your project supervisor, and receive written (email) permission.
Like the review, the essay should be written in a scholarly form with adequate references and illustrations if necessary. Remember that the goal of an essay is to persuade the reader of a point of view, and that the typical methods of persuasion include the use of evidence from the literature and logical development of an argument.
4. The Project and Presentation
In formulating your projects bear in mind the principles that you have learned in your information system studies, with particular attention to the phases of project management
Guidelines:
Project formulation: needs analysis, user profiles; identification of current resources;
methodology; timeline and milestones.
Design and collection of data
Implementation of system: construction of a prototype; user testing, feedback and revision
Since the projects are all different, they will develop at different rates and in response to different technical and conceptual challenges, thus the timelines and milestones will vary accordingly.
Sometimes the most difficult part of a project is communicating within the group about questions of the distribution of tasks. For the purposes of this project, it is important that every member of the group be involved with the phases of the project’s development. That is, it might be that there are several solutions to a technical or design question and that the presentation of more than one may be beneficial and an advantage to the final outcome.
Remember that if you are involved in a project outside of the area of your expertise (major), you still have conceptual and critical skills to offer the project in terms of design and implementation. Your skills are those of an information systems analyst, and the specific project may or may not be in an area in which you have expertise. This is certainly the situation in the industry where you will be valued for your communication, analytic and critical skills.
Development of a successful project is not an exact science and you will be required to work closely with your client in order to ascertain their true needs in relation to the information system you will be working on— and closely with your group members in formulating the system. Be prepared to try different solutions and to experiment with different languages/applications. Some database systems work better with different file types than others. Don’t underestimate the virtue of an inspired idea that arrives as a result of dialogue, individual or group reflection.
Please feel free to consult extensively with staff outside of regular sessions. We will act as virtual clients if your real clients do not have sufficient time to consult with you regularly, or if you do not have a real client..
Project Presentation
The presentation will include a recapitulation and update of the Project Formulation including:
the purpose of the project
profile of the client and users
the analysis of needs
identification of available resources
justification of the technical solutions that the project provides
The main part of the presentation will be a demonstration of the Project Prototype. The Project Prototype may take the form of detailed story boards or a working prototype website or information system. Full implementation of the system is not required. The prototype presentations will:
take us through the site
discuss the architecture of the system
report on difficulties and issues arising in development of the prototype
The project prototypes will be assessed on the quality of the following:
realisation of the objectives defined in the project formulation
interface design
navigability
architecture of the information system
imagination
research
technical understanding and expertise
5. Project report
Guidelines for the Project report will be developed during the semester, in response to the particular types of projects undertaken. Bear in mind though, that as you proceed with the project, you should prepare for this assessment by taking note of possible alternatives which could have been undertaken had circumstances been different, such as the time frame, or the level of skills, for example, and any thoughts you have about your participation in your group.
Late Submissions and Extensions
Requests for extensions will only be considered if submitted before the due date. This includes requests based on illness or misadventure other than on the due date itself.
If no extension has been granted, the work will be penalised at a rate of 2% per day (including weekends).
Extensions will not be granted for pressures of work or competing academic commitments.
Requests for re-examination and appeals:
If you are dissatisfied with the way a piece of work has been assessed, the following procedure is to be followed:
a) you must submit an appeal in writing to a Unit of Study coordinator, giving your reasons for your appeal against the original assessment. You may wish to discuss the matter informally with your Unit of Study coordinator before submitting your written appeal;
b) requests for re-examination must be submitted within three months of the release of results for the unit of study, excepting circumstances of illness or misadventure;
c) the second examiner must complete their re-examination within 7 days;
d) if the second examiner returns a mark higher than the original mark, your examination results will be amended accordingly; if not, it will stand as originally recorded;
e) in the event that you are still dissatisfied with your result, a written appeal may be lodged with the Director of the BAI Program, Assoc. Prof, Julian Pefanis, for final determination.
Academic Honesty
You have a responsibility to be aware of the principles governing appropriate referencing and the relationship between your own written work, the work of other students, and the literature you read.
The University’s policy defines plagiarism and recycling as follows:
Plagiarism means presenting another person’s ideas, findings or work as one’s own by copying or reproducing them without due acknowledgement of the source.
Recycling means the submission for assessment of one’s own work, or of work which is substantially the same, which has previously been counted towards the satisfactory completion of another unit of study, and credited towards a university degree, and where the examiner has not been informed that the student has already received credit for that work.
Both plagiarism and recycling are contrary to the University’s accepted academic standards. The University’s policy is that
Written work which contains plagiarism will in the first place be assessed in accordance with its academic merit, and in appropriate cases may fail the assessment task. This is not a penalty for plagiarism but an evaluation of the merit of the written work in the light of the University’s expectations and standards.
Where there also appears to be evidence of an intent to deceive the examiner, you may become subject to disciplinary procedures. The Academic Board’s policy states that it will be reasonable to consider this to be the case where:
(a) substantial portions of the work submitted for assessment were copied from another student, or from the work of a former student, in a manner which clearly exceeds the boundaries of legitimate co-operation or group work;
(b) written work contains a substantial body of material copied from published work, including on the Internet, without any attribution of its source and in a manner which cannot readily be explained by poor referencing, language difficulties or lack of confidence in using one’s own words;
(c) there is evidence that the student engaged another person to write the assignment, either partly or wholly, whether for payment or otherwise;
(d) there is evidence that the student paid another person to conduct research for the assignment; and/or
(e) the student has previously received a formal warning in relation to plagiarism and the plagiarism in the work submitted for assessment cannot be explained by continuing difficulties in understanding the university’s requirements for written work. (p. 6)
The University’s policy concerning Academic Honesty in Coursework (plagiarism), including the procedures which will be followed in such cases, can be found in full on the web at:
http://policy.rms.usyd.edu.au/000002f.pdf
ARIN 3600 Timetable
Week 1 March 10
Introduction: expectations,content, structure,teaching methods, assessment,group formation
Week 2 March 17
Project brief formulation
discussion
Week 3 March 24
Project formulation
discussion
Week 4 March 31
Group work Technical Instruction
Week 5 April 7
Group work
Technical Instruction
Week 6 April 21
Group work
Technical Instruction
Week 7 April 28
Group work
Technical Instruction
Week 8 May 5
Group work
Technical Instruction
Week 9 May 12
Group work
Troubleshooting
Week 10 May 19
Group work
Troubleshooting
Week 11 May 26
Group work
Troubleshooting
Week 12 June 2
Project presentations
Troubleshooting
Week 13 June 9
Project presentations
Troubleshooting