If we want CS accredited, we will probably have to
ensure that CS students get some exposure to these themes.
Possibility: we could make COMP4920 Professional
Issues and Ethics compulsory for CS students, and
also get them to take COMP3710 Software Project Management.
LIC Session 1 | LIC Session 2 | LIC Summer | |
COMP1001 | |||
COMP1011 | |||
COMP1711 | |||
COMP1021 | |||
COMP1721 | |||
COMP1091 | |||
COMP2011 | |||
COMP2711 | |||
COMP20yy | |||
COMP2021 | |||
COMP2041 |
Over the last year or two, I've had to repair some really sloppy marking by some of our casuals and top-up students. Particularly annoying were examples where marks had been deducted without any justifcation being provided and where the markers were unable to provide justification when pressed. (My interpretation was that the markers didn't bother to put in any effort, but wanted to give the appearance of some effort by producing a range of marks).
I presume the current standard requirement is something like:
"Xmark" makes it not too difficult to annotate project submissions so this is not imposing an unreasonable overhead.
If it's not standard practice, could we make it so? If it already is, could people remind their markers more frequently?
This problem is particularly acute for postgrad coursework students who otherwise get little feedback on their progress during semester, because we don't provide them with things like tutes/labs (in most subjects).
Another assignment-related idea that comes up reasonably frequently in course evaluations is that students would like assignment specs to be available at the start of session. I don't know how feasible it is to ask LICs to provide assignment specs at the same time as they provide Course Outlines (which everyone seems to manage to do by the end of week 1).
We need to think about what has been excised from COMP2011 (e.g.
memory management data structures, storage device characteristics)
and whether it warrants mounting COMP20yy, and how COMP20yy would
fit into CE, SE, CS, and Bioinformatics.
What the Potter
committee report said about COMP20yy:
Doing C in COMP9021 would have the advantage that we could offer
COMP9021/1021 in summer session (instead of just 1021).
The minimalist fix is to introduce BINF4903 Industrial Training (0 UoC, no
sweat), and BINF4920 Professional Issues and Ethics (3 UoC, where to fit
it in?). You can argue that they will get their professional issues and
ethics integrated into BINF1001/2001/3001, but the only mention of anything
vaguely relevant seems to be in BINF1001, where the handbook entry says, in
part:
COMP20yy will cover software development in the large, focusing
on software architecture, library design and design for reuse,
component-based development, thread-safety of components,
software deployment and configuration management. Systematic
integration-based testing will be covered. May be appropriate
to consider multiple language development (e.g. component
development + scripting).
My query a few weeks ago revealed that
none of the follow-up postgrad courses *required* Java ... the most
common request was (paraphrased) "some level of programming maturity."
UoC S1 UoC S2 6 BINF4910 Thesis Part A 12 BINF4911 Thesis Part B 6 Elective A 6 Elective B 6 Elective C 6 Elective D 3 COMP3720 Total Quality Management 3 GenEd 24 24
Structure of biotechnology industry stressing commercial,
regulatory, and intellectual property areas. Diversity of industry sector and
commercial case studies including biopharmaceuticals and gene therapy, use of
transgenic plants and animals.
School of Computer Science & Engineering The University of New South Wales Sydney 2052, AUSTRALIA Phone: +61 2 9385 6876 Fax: +61 2 9385 4071