Home > Undergraduate > Professional Computing 3200   

  PROFESSIONAL COMPUTING (CITS3200) 2017
 
 

This unit is unlike most others you have undertaken; rather than focussing on lectures, labs and tutorials, the focus here is a significant group project. The project work is also more open-ended than you are perhaps used to. There are teams of about 5-6 people for the projects - sourced from industry and the University and wider communities. Each group generally has a distinct project, different from the other groups' projects. Team work is essential. While there is some individual assessment of how you perform in the team, projects will be marked as a whole, not as individual contributions. Therefore, unless there is strong evidence to support a contrary policy for a particular group, the default position will be that every member of a group will get the same mark.

There are no set labs, lab sheets or tutorials. There are a few lectures and you are required to attend them. You will write an essay on a topic related to Ethics of Computation.

If you enrol after the start of semester please tell me via: Michael.Wise@uwa.edu.au

Unit Co-ordinator:  Assoc. Prof. Michael Wise
Technical Enquiries:   help3200
Administrative Enquiries:   My email above
Consultation Hours:   Wednesdays 11am
  Rm 1.18, CSSE Bldg
  Other times available, just email me first, please, to arrange a mutually convenient time

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

Assessment

The assessment scheme is:
  1. a group project worth 75%, consisting of Deliverables A, B, C and D
  2. an individual essay worth 25%
Major project deliverables (excluding Deliverable D) will be submitted electonically via cssubmit and a paper copy to your project client.

In addition, Groups are expected to provide each week on Friday (but certainly no later than Sunday evening):

  • A set of Minutes for each Group meeting held that week (PDF or MS-Word doc),
  • A time-sheet summarising the work that has gone on that week (Spreadsheet) based on Booked_hours spreadsheets from Group members, and
  • A tar or zip file containing the Booked_hours spreadsheet submitted by EACH Group member.
(Minutes, TimeSheets and the Booked Hours will be discussed in the second lecture. Also see note on the Project Timetable page. The Project page has templates for the Timesheets, Minutes and Booked Hours.)

The three items are to be emailed to the unit coordinator directly.

Full participation in the project is considered essential for satisfactory progress in this unit. You must attend weekly project meetings with your team. Absences, other than sickness or emergencies, must be notified to the Unit Coordinator in advance and meetings should be free from disruptive behaviour, see UWA Guidelines for Conduct in the Workplace.

Finally, while School and University policy governs the major deliverables (and in particular late penalties), the following will apply to the aspects unique to this unit. (I really hope you won't need this information.)

  1. If a group's Minutes, Booked-hours spreadsheets file or Timesheets are later than Sunday evening, there will be a penalty of 1 mark off the total project mark for each item that is late.
  2. While it is the Group Manager's responsibility to have the 3 weekly deliverables sent to me on time, it is the responsibility of Group members to provide their Booked Hours spreadsheets to Group Managers in a timely mananer. In particular, it should not be up to Group Managers to chase Group members' Booked Hours spreadsheets, so if these have not been provided, the Group Manager will be asked to submit whatever data they have, and Group members with missing data will lose 2 marks.
  3. The weeks when there will be meetings with mentors are known well in advance. Therefore, there is no excuse other than illness or misadventure, or the unavailability of the mentor, for you not to attend a mentor meeting, so there will be penalty of 3 marks from your own total mark for each meeting missed.
  4. Minutes are expected for the Mentor meetings. If these are not provided at the end of the following week there will be a penalty of 2 marks off the project mark.


School of Computer Science & Software Engineering
The University of Western Australia

Last modified: July 17, 2017

Created by: Richard Thomas
Modified By: Michael Wise
UWA