Presentation is loading. Please wait.

Presentation is loading. Please wait.

Seminar: Softwareproduktlinien Marko Rosenmüller Norbert Siegmund Christian Kästner Gunter Saake 2008 / 2009.

Similar presentations


Presentation on theme: "Seminar: Softwareproduktlinien Marko Rosenmüller Norbert Siegmund Christian Kästner Gunter Saake 2008 / 2009."— Presentation transcript:

1 Seminar: Softwareproduktlinien Marko Rosenmüller Norbert Siegmund Christian Kästner Gunter Saake 2008 / 2009

2 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 2 Outline Aufbau eines Papers Bewertung

3 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 3 Why to write a paper Communicate new findings publication = ultimate result of scientific research research is never finished until it's published To let the community know about your work Recognition Contacts, fruitful collaborations Get feedback from peers external, independent, frank (anonymous)

4 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 4 What to write in a paper Write the paper for readers As communication between you and readers Consider their backgrounds With evaluation criteria in mind Original contribution Significant problem Significant solution Sound results High-quality presentation

5 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 5 Anatomy of a paper Title Abstract Introduction (Background) (Problem Statement) Body Evaluation Discussion Related Work Conclusion + Future Work References

6 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 6 Abstract Very brief summary of the paper Why is this work important, what was the motivation? Main contents, main results Typically one of the last things to write => Is this paper relevant for the reader?

7 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 7 Introduction What is the general problem? Why is it important? What is the specific problem? Why should the reader care? How is it different from prior work? What was the motivation for this work? What are the objectives/contributions? How is it new? What is the general approach/outline? Keep it short (approx. 1 column)

8 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 8 Background (if necessary) What is the necessary background to understand this work? In scientific papers usually very short. Know your audience! Only background that is really necessary!

9 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 9 Problem statement (if necessary) What is the specific problem? Why is it important? Example if necessary Sometimes necessary to tell the reader that there is a problem

10 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 10 The contribution Main part of the paper Describes the own approach, the innovation Readable, verifiable! Examples where necessary!

11 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 11 Evaluation / Proof Evaluation critical What is the evaluation criteria? Case studies? Empirical studies? Does your innovation scale up? Does it solve real problems? Report experience Readable, verifiable! Can be assessed and replayed Separate data from interpretation

12 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 12 Discussion (if appropriate) Interpret results Advantages and Disadvantages (Comparison to related approaches) Threats to validity

13 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 13 Related Work What are others doing? How is this work different? Common reviewer comments: The paper omits important related work The authors describe the related work but don't compare their work

14 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 14 Conclusion and Future Work Summary Results, what has been achieved What's missing? New research questions? Bigger context, long-term goals?

15 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 15 References Give credits to previous and contextual work Reference quotes, claims, previous results References must include Name of authors Title Journal, Conference, Publisher Volume, Edition, Pages Year

16 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 16 Für dieses Seminar Ausarbeitung über den aktuellen Stand und zukünftige Herausforderungen Überblick über das Themengebiet Verständlich für alle Teilnehmer des Seminars Gegebenenfalls Vergleich verschiedener Lösungen Pro/Contra Argumentation Offene Probleme / zukünftige Herausforderungen Aufbau: Einleitung, (Grundlagen), (Problembeschreibung), Hauptteil, offene Probleme, Zusammenfassung

17 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 17 Finding literature Library: Journals scholar.google.com ACM Digital Library CiteSeer dblp.uni-trier.de

18 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 18 Style Cohesion (Roter Faden) Line of thoughts Self-contained Say what you're saying before saying it Avoid mere description

19 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 19 Typical Problems missing motivation (why is it important?) unclear goal, unclear contribution missing reasoning (thats the way I did it) dead-end discussions, unused background missing cohesion bigger picture missing (just details) missing conclusions or results jargon, background missing related work missing

20 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 20 Typical comment patterns the objectives are unclear too little beef the authors seem to ignore so what? the paper fails to deliver what is promises unsubstantiated claims opinion paper... premature... the paper provides little evidence that the results do apply in real settings, scaleability is questionable, etc evaluation is weak

21 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 21 Evaluation Criteria Paper Does the paper match the chosen topic? Do title and abstract reflect the content of the paper? Is the paper well structured? Is the motivation clear? Do sections contain the content promised in section titles? Is there a consistent recurring theme or does the author jump from idea to idea? Are all background information necessary for understanding the paper provided? Are there any unnecessary information/sections? Are arguments well supported by references? Are references complete and suited? Are examples/figures/tables used adequately to support understanding the paper? Is the reasoning of the paper correct? Is the paper well written (language, style)?

22 Rosenmüller / Siegmund / Kästner / Saake Seminar Softwareproduktlinien 22 Evaluation Criteria Presentation Allgemeiner Eindruck (Körperhaltung, Blickkontakt, Sprechgeschwindigkeit, - lautstärke, Auftreten, Vorbereitung) Verständlichkeit Motivation Zielgruppengerecht Abgeschlossen Schlüssigkeit Detail vs. Big Picture (Tiefe vs. Breite) Roter Faden Folien (Klarheit, Formatierung, Text-, Code-, Formelmenge, Visualisierung) Zeit Fragestunde


Download ppt "Seminar: Softwareproduktlinien Marko Rosenmüller Norbert Siegmund Christian Kästner Gunter Saake 2008 / 2009."

Similar presentations


Ads by Google