UNSW Engineering
CSE Computer Science and Engineering

SENG4921 Professional Issues and Ethics


Seminars

June 2, 2009

Week 12 (week commencing 1st June)

This seminar is concerned with Rawl’s Theory of Justice
see

also How Good is Good Enough paper of Collins, et al.

This paper is available from the Papers page of the course web site. Please study this paper before attending your seminar.

In the seminar you should consider the following:

  1. Discuss Rawls’ ethical principles. In particular:
    Two principles of fairness
    Veil of ignorance
  2. Discuss the application of these principles in the case studies discussed in How Good is Good Enough:
    • What happened?]
    • Who was involved?]
    • What went wrong?]
    • What should have happened?]
  3. Discuss the impact of this form of analysis on SE.
  4. Is this form of analysis well suited to anaysing ethical situations in computing?
  5. Revisit the Therac 25 case to see if this theory would help analyse that case.
  6. Do Rawls’ principles correspond with Stephen Cohen’s outline of the foundations of ethics?
Week 11 (week commencing 25th May)

This seminar deals with dataveillance, which is the basis of a lot of modern surveillance.

It should be an objective of this seminar —indeed all seminars— to build well structured ethical arguments. A common weakness in ethical arguments is to identify that some broad activity clearly presents ethical issues, and then the argument becomes concerned with whether the broad activity is ethical or unethical. It is rarely that simple.

Roger Clarke (ANU) coined the name ”dataveillance” in the late 1980 and he has a large website at http://www.anu.edu.au/people/Roger.Clarke/DV/ on dataveillance.

Get a copy of

More information can be found at http://www.anu.edu.au/people/Roger.Clarke/DV/.

  1. What is dataveillance?
  2. Is it immoral to collect data about other people?
  3. What personal data is currently being collected?
  4. What new opportunities are there to collect even more personal data?
  5. How can dataveillance be regulated?
  6. What advice would you give to non-specialists about safeguarding personal information?

Discuss the contents of Dataveillance — 15 Years On.

When is a Surveillance Society OK?
http://www.practicalethicsnews.com/practicalethics/2008/06/lex-orwell-when.html Lex Orwell

Week 8 (week commencing 4th May)

IP: copyright, patents, licensing, etc

Most people will have a view on these things as they can’t be avoided.

I suggest that seminars commence by discussing individual attitudes to IP:

  • do you believe in IP, that is, ownership of intellectual property?
  • how do you justify your position?
  • it is easy to arrive at a realisation that there are good arguments either way, that is you have one of these ethical dilemmas.

At that point, it will be worth looking at

This discussion drifts easily into open source development and the free software movement.

A few comments are added here on copyright and patent, as some students are unclear about the distinction.

Copyright:
is concerned with the form of expression of something. Notice that any ideas are not protected only the way it is expressed. This might be an essay, a book, a piece of music, a performance of music, a piece of software. Notice that it is “form of expression” that is protected, so translation into another language, or into machine code does not avoid the copyright, indeed it infringes the copyright. Copyright in Australia does not require any registration, nor does it require a copyright notice, although that is recommended. Copyright around the world is recognised by the Berne agreement.
Patent:
is concerned with the means of production or implementation. You cannot patent an idea, you can patent something to be produced, and you must show that it can be produced. You can’t patent “blue sky”. Notice that patenting involves publication: all patents are “world readable”. Patents do not automatically transfer to other countries: you must pay for extending to other countries and the exercise can get very expensive. DNA patents are “interesting”.
Trade secret:
is an alternative to patent. You don’t publish and there is no expiry date. You simply swear everyone to secrecy. Clearly doesn’t work for computer software.

You might like to have a look at http://progfree.org/Patents/industry-at-risk.html

and decide whether somehow software is different to other manufacturing industry to which patents have applied for 200 years.

Consider:

  • IBM holds patent #4,965,765 which covers the use of different colours to distinguish the nesting level of nested expressions.
  • Patent #5,249,290 covers assignment of client requests to the server process having the least load.
  • Patent #4,941,125 covers using a digital camera in conjunction with character recognition software to store and index documents on a CD ROM.

I’ll leave it to classes to work out issues to be discussed, but you might like to tackle the following.

On the one hand much software looks like mathematics, so should we patent mathematics? Patents were never intended to cover ideas.

But on the other hand, if we take the concept of Software Engineering seriously then surely an engineering process should allow for some patent capability?

This gets to perhaps the nub of the issue: how do we —or if you like, do we— provide for some form of ownership of invention within software engineering? Of course, you can take Brian Martin’s approach and broaden this question to all areas.

Some other possible questions:

  1. Describe situations where IP produces unfair outcomes.
  2. How much should somebody profit from their ideas?
  3. Do we have free speech in Australia?
  4. Do you believe in IP?
  5. How common/rare are good ideas?
  6. Is there such a thing as an original idea?
Week 4 (week commencing 30th March)
The seminars in Weeks 4 & 5 will be concerned with the Therac 25 case study.

Objectives

to get a clear picture of

the Therac-25 machine:
what it was; what it consisted of; and what it was used for.
the accidents:
what accidents occurred; details of each accident.
causes of the problems:
details of all causes.
context of accidents:
understand the situations of the accidents.
how the accidents were handled:
what action was taken.

In week 5, with all the above understood, the objective is to do a more thorough ethical analysis of the case.

Material for discussion

Full report of the Therac-25 case
For a full report of the Therac-25 case you should consult ”An Investigation of the Therac-25 Accidents” (see Papers/Leverson et al on this web site).
Teaching material on Therac-25
You should also look at the computingcases.org for a breakdown of the case. You will probably find this much more digestible than the Leverson report.
Wikipedia
You could also consult the Wikipedia http://en.wikipedia.org/wiki/Therac_25 .
Other material
There is also a book appendix, Medical Devices: The Therac-25.

You should bring a copies of the Leverson investigation paper to the seminar. This report has very full pages. To print, use acroread or gv and print at 90%.

You should also consult the teaching material at computingcases.org.

Week 3 (week commencing 23 March)

This week’s seminars will begin discussion of the Killer Robot story. This story consists of 9 articles that can be found here and also on the Other Sites page of the class web page . This story forms about half of the Killer Robot book, by Richard Epstein. The book contains extra material that is not online, and contains much interesting ethical discussion and references.

The seminar discussion will be based on the first 6 articles. Please read the articles and bring copies of all 9 articles to the seminar. Please come prepared.

There are some differences between the book and public version of the Killer Robot story.

If you only look at the public version, please also look at the extra prelude articles to the above .

Discuss the case as though it is real. It’s not hard to do.

Remember that this story if being revealed through newspaper reports, and therefore possess all the attributes of a real life incident and its investigation. You are not necessarily getting the truth, or at least not the whole truth.

You might pursue the following points of discussion, but facilitators can proceed however they wish:

  1. Looking at the first article, why did Bart Matthews say, ”I trust this robot”? What did he mean? It’s a strange thing to say. Perhaps he was saying this to raise his own confidence? There’s nothing definitive here; just get discussion going.
  2. Since the third and fourth articles raise the issue of charging a software developer with manslaughter, we discussed this next. Is it plausible that a software developer could be charged with manslaughter? I don’t know, but I don’t see why not. Understand that murder is killing someone with intent; manslaughter is killing without intent. In manslaughter a person has been killed in an accident. So it’s acknowledged that it is an accident, but has there been negligence, criminal negligence?

    Instruction to facilitator: This can be developed into a quite serious discussion. Any person in the class could be charged with manslaughter. Put it to them. You’ve been charged with manslaughter. How do you defend yourself? What would you need to have done to defend yourself against such a charge?

  3. Then discuss what actually happened? Collect as many details as possible.
  4. What were the potential causes that led to the software malfunction that caused Bart Matthews death?

    Each student in the class should be able to provide a potential cause. All answers can be written on the board, as for the answers to the above questions.

Try to ensure that the answers are coming from all the articles and not being concentrated on just a few articles. If the latter is happening, look for new reasons.

As well as noting the issues, carry out some discussion of the points.

Which are consequences rather than causes? Try to identify significant causes. If the consequences are undesirable, what would you do to prevent them?

Week 2 (Week commencing 16th March)

The seminar this week is concerned with Codes of Ethics and professional issues arising from such codes.

  1. The first phase is to scan the codes linked to the class website. You will find 5 codes:
    • ACM
    • ACM/IEEE Software Engineering code
    • BCS
    • ACS
    • Engineers Australia

    Scan the codes looking for any points that distinguish the codes and deserve discussion. Such items might be:

    • Codes of Conduct (CoC), as distinct from Codes of Ethics (CoE).
    • significant differences between the codes;
    • significant commonality between the codes.

    This exercise might be best done by splitting the class into, say, 5 small groups, each of which are assignment two codes.

  2. In the second part of the seminar the class discussion should be concerned with the questionable activities and procedures of a group of system developers. By questionable is intended possible breaches of professional conduct.

    To handle this part of the seminar, again it is suggested that the class splits into 5 small groups with the following roles:

    1. represents the team of system developers;
    2. represents management of the developers;
    3. represents external users of the system who have observed system malfunctions;
    4. represents a groups of observers of the discussion by the above groups.

    The chosen cases can be based on known examples or they can constructed “on the spot”, none of the discussion is intended to be prearranged, that is the discussion can be created spontaneously and the teams should defend the charges or justify their behaviour.

    Particular moral maze: The Sydney Morning Herald (SMH), Tuesday 17/03/09, reprinted an obituary on Konrad Dannenberg, first printed in The Guardian (http://www.guardian.co.uk/science/2009/mar/10/space-exploration-secondworldwar), a PDF will saved here.

    Dannenberg worked, during WW2, in Germany as a rocket scientist/engineer on the the development of V1/V2 missiles. These missiles were used on various cities in Europe, many on London and other UK cities.

    After the war Dannenberg moved to the USA where he worked on rocket development for the US space program. Finally, he was the manager of the Saturn program that produced the rocket that took the first astronauts to the moon.

    It could be interesting to examine how the CoE and CoC contribute to a discussion of the moral dilemmas to be found in Dannenberg’s case.

Week 1 (week commencing 9 March)

For the first seminar, please print the Engineering and Software Engineering .

Read the document before the seminar and bring it to the seminar. There are other linked documents and you may wish to print some of those also. In particular, the “Are Software Engineers Engineers” document should be read and perhaps printed.

This is a very wide ranging seminar. Please form your own list of topics that you would like to discuss. That way you can affect the agenda for your seminar.

We will organise the seminar discussion using the Six Thinking Hats, so please read the short summary document on that.

Please remember one thing: you are not coming to the seminar to be supplied information from you facilitator. You are coming to take part in a discussion and that should include initiating discussion.

Also, in general, there are no “right answers”. But this course is very much about your future, so there may be “right questions” for you.