Professional Documents
Culture Documents
Software Engineering
Kai Koskimies
SoSE paper project course
Spring 2009
• Tool as contribution
Present your existing tool and show how it can be used to solve a problem
Correction: Present the problem and solution on an abstract level, and use
your tool only in the implementation part, as part of the evaluation
• Formalism as contribution
Show how a certain aspect of software engineering can be formalized
Correction: Present the formalism as a tool to achieve some advantages or
solve some problem in software engineering
intro beef
bad good
• Do not write for your project team, for your supervisor, for a narrow
community
• Avoid metatext, research process text when not essential, just
concentrate on the result (research methodological issues may be
relevant, though)
• Avoid lists of paragraphs (-> bullet list), still paragraphs are an
important means of structuring
• Beware of the Lemminkäinen effect (”Tiedänpä vielä tämänkin”, I
know this, too. Or: ”There is this additional feature in the tool, too.”)
• The art of removing and compressing text, without affecting the main
message
• Language is a powerful tool – and unreliable. Aim at simple
expressions and sentences (e.g. avoid ”very”)
Other conferences
- often questionable merit
- some conferences may have special hidden agenda
- acceptance rate unknown (possibly 100%)
- publication as separate proceedings of small publisher
- PC consists of unknown persons
- avoid, if no particular reason to attend