|
Professional Computing 307 (230.307)
6 points / Semester 2
Handbook Description
The official Handbook entry Unit Aims
The unit has the following aims (developed from Clear et al 2001)
- To develop awareness of the ethical and social responsibilities of computing
professionals
- To develop experience using professional practices in a teamwork setting
- To provide a "programming in the large" experience as far as practical
- To allow for the integration of and reflection on previous computer science knowledge
- To develop student capability, confidence and maturity
- To model industrial practice regarding commercial software development, and effective client relationships
Teaching Staff
| Unit Co-ordinator |
|
|
A/Prof Richard Thomas |
Room 1.3 |
| Mentors (To be confirmed) |
|
Julie Mount |
Motorola |
|
Rodney Kirk |
Motorola |
|
Stephen Beckwith |
Motorola |
|
Richard Pragasam |
Motorola |
|
Peter Ryan |
Motorola |
|
Basavanna Gowda |
Motorola |
|
Lanny Leman |
Motorola |
|
Tjiam Nam Hong |
Motorola |
| Lecturers |
|
|
Malcolm Fialho |
Human Resources (Equity Office) |
|
Alex Reid |
Honorary Fellow |
|
Kim Heitman |
Legal |
Recommended Reading
Ian Sommerville, Software Engineering, 6th edition,
Addison-Wesley 2001.
Stevens, P & Pooley, R., Using UML : Software Engineering with Objects and Components.
Addison-Welsey 2000.
Bruegge, B & Dutoit, A., Object-oriented software engineering
Prentice Hall 2000
Spinello, Richard A., Ethical aspects of information technology
Prentice Hall, c1995 (MPSL reserve)
Edgar, Stacey L., Morality And Machines Perspectives On Computer Ethics.
Jones and Bartlett Publishers, c2003
Contact Hours
| Type |
Time |
Day |
Weeks |
| Lecture |
10-10:45 |
Tuesday |
1-4 |
| Lecture |
9-9:45 |
Wednesday |
1-4 |
|
|
|
|
See
UWA 2005 timetable for PC307
You are required to attend all lectures and mentor meetings. You must attend weekly
project meetings with your team. There are no lab sheets or supervised labs.
Assessment
The assessment scheme is:
- a team project worth 65%, consisting of Deliverables A, B, C and D
- an essay worth 25%
- an individual summary report worth 10%
and
You must obtain at least 40% in each of the essay and individual summary report
and
Full participation in the project is considered essential for satisfactory progress in this unit.
Absences, other than sickness or emergencies, must be notified to the Lecturer in advance and meetings should
be free from disruptive behaviour, see
UWA Guidelines for Conduct in the Workplace.
Unsatisfactory Progress
Any student who does not demonstrate satisfactory progress in this
unit, as defined in the FECM
Policy on Assessment Practices and Procedures, may be refused admission to the
final examinations. The final deadline for notification of unsatisfactory progress is the
last day of Week 10.
Penalties
The School of Computer Science and Software Engineering has adopted a policy on
minimum penalties for late items of assessment.
This is the default policy of all units unless indicated otherwise, in writing, by the
specific unit coordinator.
This policy shall apply to all items of continuous assessment, whether
submitted either physically or electronically. Immediately after the submission deadline for an item of continuous
assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF.
The minimum mark possible for late submission is zero. The
percentage is based on the item´s total contribution to the unit´s
assessment. For example, a project contributing 40% to the unit´s
assessment will incur a penalty of 8 marks for each day late until it is submitted or
a mark of zero results.
A more detailed description is given in this School´s Policy on
Late Submission. The Faculty does have an appeals procedure, the details of which can found at the Policy for Appeals.
All work submitted for the project assessment must be the individual
team's own work. Any instance of plagiarism will be brought to the attention of the Department Disciplinary Board
and dealt with under the Department's and Faculty's plagiarism
policies. The ethics essay must be the individual student's own work.
Plagiarism
Plagiarism is broadly defined to be when any portion
of the work presented for assessment, can be attributed
to another party. The student making the submission should acknowledge
what aspects of the presented work is not directly derived by
them. For the purposes of plagiarism it is irrelevant that you
have been given permission by someone to copy their work
and present it as your own.
You are directed to the School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism.
Faculty Scaling
Final assessment is subject to the Faculty Scaling Policy.
This information is correct as at 24-Jun-2005, but is subject
to change from time to time. In particular, The University
reserves the right to change the content and/or method of
presentation and/or the method of assessment of any unit of
study, to withdraw any unit of study or programme, and/or to
vary arrangements for any programme.
Copyright© 2005
School of Computer Science, & Software Engineering
The University of Western Australia
CRICOS Provider Code: 00126G
Last updated: 24-Jun-2005 |
