Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
Professional Communication in Computer Science
[go: Go Back, main page]


Professional Communication in Computer Science 2004
(aka Professionel Datalogisk Kommunikation or PDK)
DAT4/F8S/SSE2/KDE2

Professional Communication in Computer Science

Warning! This page is always very much under construction! All the material on this page is tentative until further notice.

Course Tutor


What's in this "Course"?


Course Description

The goal of this n lecture course (for some as yet unspecified n greater than, or equal to, 5, but no larger than 10) is to introduce the students to the life-cycle of a scientific article, which special emphasis on the current practices in the field of Computer Science. In particular, we shall focus on the following three key questions that every novice in a scientific discipline asks oneself:

We shall devote each of the first three lectures in the course to analyze one of these questions. The last two sessions may take place later in the semester, and will be devoted to cross reviews of your own articles (based, of course, on the criteria for evaluation that will be mentioned in the course). There may be some seminar style meetings in between where we may focus on heatedly discussing some ethical and social issues which are part and parcel of scientific life. Quoting Carl Djerassi:

"Scientists operate within a very tribal culture whose rules, mores and idiosyncrasies are generally not taught through specific lectures or books, but rather are acquired through a form of intellectual osmosis in a mentor-disciple relationship. The soul and baggage of contemporary science is made up of items such as publications, priorities, the order of the authors, the choice of the journal, the collegiality and the brutal competition, the striving for academic tenure, grantsmanship, the glass ceiling for women in a male-dominated enterprise, Schadenfreude, even Nobel lust--each with its own ethical nuances."

I trust that it will be an entertaining and enlightening experience to discuss some of these issues together.

Exercise Classes: The exercises mentioned on the web page for a lecture should be solved whenever you feel that they will be useful in supporting the writing of your article.


Reading Material

Apart from the reading material specific to each lecture, I heartily recommend that you read the novel Cantor's Dilemma by Carl Djerassi (the scientist who first synthesized a steroid oral contraceptive--"the Pill"). You will learn much about the world of science and the scientists that populate it from this superbly written and entertaining book. You can buy this book from Amazon.co.uk. Enjoy it!

The booklet On Being A Scientist: Responsible Conduct In Research also has much food for thought, and we may use it as a background for some entertaining (at least I hope so!) in class discussions.

This web page has plenty of useful advice on research and writing, and is aimed primarily at computer scientists!


Lecture 1: How does one write a scientific article?

Be it for a student report, for a thesis, for a user's manual, or for a project report, we all have at one point to sit down and write something, which is often not easy at all. This lecture analyzes the goal and the means of writing a scientific paper, and identifies standard pitfalls as well as a few recipes for not doing overly badly. The main message of the lecture is concisely summarized in the following quotation:

"The preparation of a scientific paper has almost nothing to do with literary skill.
It is a question of organization."

--Robert A. Day, How to Write and Publish a Scientific Paper

Date: Friday, 6 February 2004 (10:15 in room KS 3 4.128)

Reading Material:

The following supplementary reading material is recommended for the keenest:

Some Good Books on Writing Available from AUB:
  • Steven G. Krantz. A primer of mathematical writing: Being a disquisition on having your ideas recorded, typeset, published, read and appreciated, Providence, R.I.: American Mathematical Society, 1997.
  • Norman E. Steenrod, Paul R. Halmos, Menahem M. Schiffer, and Jean Dieudonne. How to Write Mathematics, American Mathematical Society, 1981.
  • Knuth, Donald E., Larrabee, Tracy, and Roberts, Paul M. Mathematical writing, The mathematical association of America, 1989.
  • Zobel, Justin. Writing for computer science: The art of effective communication, Springer, 1997.
    Links of Possible Interest: Exercise (to be held on ????):
    1. Look back at the project you wrote last semester in light of what we discussed during the lecture. How well was your project written? Read your introduction again. Was it good? Rewrite it as suggested in this lecture.
    2. Critically read the introduction of this paper. How well does it meet the requirements for a good introduction spelled out during the lecture? Your comments are most welcome.
    3. Write an extended abstract (at most 5 pages in LaTeX article style) based on your DAT4 project. Use Day's IMRAD format and the advice presented in the slides for the course. If you already have a draft of your article (and I guess you should), we can instead discuss its organization during the exercise session. If you want any comment on your work, send your extended abstract to luca@cs.auc.dk. I will try to answer, but can't promise it!


    Lecture 2: How does one present a scientific article?

    There are many points in your career at which you will be called upon to present a paper in Computer Science, perhaps a paper written by somebody else in a graduate seminar, or your own research at a conference, departmental colloquium, or job interview. This skill is particularly important if you intend to pursue a career in academia. While research excellence is the main criterion for success as a computer scientist, your career will be assisted if you gain a reputation as a competent speaker. A competent speaker will more likely be invited to give colloquia at leading universities and invited talks at important conferences than a mediocre one, provided their research is of similar quality. The expected quality of the presentation can be the deciding factor in the selection or rejection of a controversial conference paper in cases where there is no clear consensus from the program committee.

    Date: Friday, 13 February 2004 (10:15 in room KS 3 4.128)

    Reading Material:

    Exercise (to be held on ????): Find your own "Elevator Statement".

    Definition (Elevator Statement). An elevator statement is an easily understandable and deep clarification of your work (project, article etc.) that is so short that you can tell it to a person while an elevator goes from one floor to the next.

    Use your elevator statement to prepare a five-minute presentation of the contents of your article.

    If you want any comment on your work, send your elevator statements to luca@cs.auc.dk.


    Lecture 3: How does one evaluate a scientific article?

    "Don't just read it; fight it! Ask your own questions, look for your own examples, discover your own proofs.
    Is the hypothesis necessary? Is the converse true? What happens in the classical special case?
    What about the degenerate cases? Where does the proof use the hypothesis?"

    --Paul Halmos, I Want to be a Mathematician

    The worth of ideas and results are judged within the scientific community via a mechanism that relies on peer-review. The key players in this mechanism are the editors of scientific journals, the members of program committees for conferences, and the (anonymous) referees. The role of the referees is to evaluate a paper for publication in a given journal or conference proceedings. This involves making a quality judgment as to the worth of the contribution made by the paper for the scientific community it addresses. This lecture will address some of the general issues that are involved in refereeing a paper, and in receiving a referee report for one of our own papers.

    Date: Friday, 20 February 2004 (10:15 in room KS 3 4.128)

    Reading Material:

    Links of Possible Interest:


    Lecture 4: Who should be an author?

    One of the most critical issues in science is that of authorship, and, to some extent, some of you have already dealt with such an issue in your project work. The main aim of this meeting of ours will be to discuss openly (and, I hope, heatedly) the question "Who should be an author".

    Our starting point will be the case described here. (See also the slides used in the lecture.) You should read the case before coming to the seminar, form an opinion about it, and be prepared to discuss it and defend it in plenum.

    You may also wish to read the section an authorship practices in the booklet On Being A Scientist: Responsible Conduct In Research.

    The issue of authorship, and the role it plays in the life of scientists, is also one of the main topics of the novel The Bourbaki Gambit by Carl Djerassi. You can buy this book from Amazon.co.uk. (Look here for information on the Danish edition of this book.) Enjoy it!

    Date: Friday, 27 February 2004 (10:15 in room KS 3 4.112 (Note the non-standard room!))

    Look here if you want to read about the G.H. Hardy-J.E. Littlewood's axioms for successful collaboration.


    Lecture 5: "How does one write a scientific article?" Reprise; Hands-on Example

    I have been asked by some of your colleagues to address in more detail the differences between writing an article and writing a report. Since I think that the generalities on writing an article have already been addressed in our first lecture, I propose to address the issue by having a meeting in which we'll plan the writing of an article on a concrete topic together. This should drive home the main message, namely that "the writing of a scientific article is a matter of organization". Please look at the
    slides for lecture 1 before the meeting. .

    Date: Friday, 5 March 2004 (10:15 in KS 3 4.128)


    Lecture 6: The Allocation of Credit

    In your career as students, you have actively witnessed the building of reputations --- be they good or bad, well founded or totally groundless. Indeed, the emergence of opinions and gossips about its members are part and parcel of any society, and the student and scientific communities are no exceptions. After all, as C. P. Snow once wrote, "Scientists are human beings!"

    The purpose of this meeting is discuss the role played by reputation, and the building or destruction of one, in scientific life. Our starting point will be the case described here. (See also the slides used in the lecture.) You should read the case before coming to the seminar, form an opinion about it, and be prepared to discuss it and defend it in plenum.

    Date: Friday, 12 March 2004 (10:15 in KS 3 4.128)

    Links of Possible Interest:


    Lecture 7: A Conflict of Interest

    Quoting from
    On Being A Scientist: Responsible Conduct in Research:

    "Sometimes values conflict. For example, a particular circumstance might compromise-or appear to compromise-professional judgments. Maybe a researcher has a financial interest in a particular company, which might create a bias in scientific decisions affecting the future of that company (as might be the case if a researcher with stock in a company were paid to determine the usefulness of a new device produced by the company). Or a scientist might receive a manuscript or proposal to review that discusses work similar to but a step ahead of that being done by the reviewer. These are difficult situations that require trade-offs and hard choices, and the scientific community is still debating what is and is not proper when many of these situations arise."

    The purpose of this meeting is to debate the conflict of interests issue in (computer) science. Our starting point will be the case described here. (See also the slides used in the lecture.) You should read the case before coming to the seminar, form an opinion about it, and be prepared to discuss it and defend it in plenum.

    Date: Friday, 19 March 2004 (10:15 in KS 3 4.128)


    Misconduct in Science

    Quoting from
    On Being A Scientist: Responsible Conduct in Research:

    "Beyond honest errors and errors caused through negligence are a third category of errors: those that involve deception. Making up data or results (fabrication), changing or misreporting data or results (falsification), and using the ideas or words of another person without giving appropriate credit (plagiarism)- all strike at the heart of the values on which science is based. These acts of scientific misconduct not only undermine progress but the entire set of values on which the scientific enterprise rests. Anyone who engages in any of these practices is putting his or her scientific career at risk. Even infractions that may seem minor at the time can end up being severely punished."

    We shall discuss some of these issues using the cases available here as a starting point. To see that cases of scientific misconduct do exist, and to hear the strong and thoughtful opinions of a Nobel prize winner for physics on those, I strongly recommend that you read the essay Truth, Ownership, and Scientific Tradition by Robert B. Laughlin that appeared in Physics Today, 55, No. 12 (December 2002), p. 10.


    Lectures n and n+1: Evaluation of draft articles

    The aim of this installment of the course is to give you a flavour of the peer review process by putting into practice what you heard in
    Lecture 3. As a byproduct each mini-group will receive comments on their draft articles that might help the mini-group members improve their term paper.

    The process of refereeing will occupy the first half of the day (8:30 till 11:30). You will read each other's article for at most two hours, and use the remaining hour to write a referee report of at most two pages based on your comments. Below, you'll find a list of pairs of mini-groups. Mini-groups in one pair will read and report on each other's paper.

    Date: Maybe never.

    Firm deadline for paper submission to the refereeing group: Better late than never.


    This page will be actively modified over the spring term 2004, and is currently undergoing heavy restructuring. You are invited to check it regularly during the spring term. The page is dormant in the autumn term.


    Luca Aceto, Department of Computer Science, Aalborg University.
    Last modified: Thursday, 25-Mar-2004 10:27:54 CET.