WS21/22 (Layout)

(((

(% class="bodytext" style="text-align: left;" %)

The purpose of this seminar is to independently scientifically work on a layout algorithm topic. The goal is to summarize the topic in an oral presentation and a written elaboration in form of a paper. Another purpose of this seminar is to practice working in structured and time-driven workflows (e.g. for conferences or workshops). Moreover, both of these aspects are good preparation for working on your thesis. We have many theses regarding these topics available; contact us if you are interested in that.

4

5

(% class="bodytext" style="text-align: left;" %)

6

This seminar is a bachelor and master module at the same time. Compared to the bachelor seminar, we expect that master students include more related papers and therefore write a longer paper and hold a longer presentation (see below).

[[image:attach:image2016-7-7 15:43:29.png]]

[[image:attach:image2016-7-7 15:43:25.png]]

(% style="text-align: left;" %)

19

= Imprtant Dates =

20

21

(% class="wrapped" %)

22

|=(% style="text-align: right;" colspan="1" %)(% style="text-align: right;" colspan="1" %)

23

(((

24

Requirements

25

)))|(% colspan="1" %)(% colspan="1" %)

26

(((

27

//Wissenschaftliches Arbeiten// von Prof. Peters

28

)))

29

|=(% style="text-align: right;" %)(% style="text-align: right;" %)

(((

Lecturers

)))|(((

Reinhard von Hanxleden (rvh@informatik.uni-kiel.de)

34

Sören Domrös (sdo@informatik.uni-kiel.de)

35

)))

36

|=(% style="text-align: right;" %)(% style="text-align: right;" %)

(((

Block seminar day

)))|(((

TBD

)))

= Topics =

{{expand title="Klick mich, um Dinge zu sehen"}}(% class="bodytext" style="text-align: left;" %)

46

You may choose one of the following papers from the different topics. The papers marked with a are the ones that we deemed more important.

47

48

(% class="bodytext" style="text-align: left;" %)

49

The papers are assigned via //first-come-first-serve//. Already taken papers are marked. Many of the links do only work in the university network. If any problems occur feel free to contact us.

50

51

52

Some papers are not freely available. These papers are linked in an internal page in our wiki. You can log in with your Ifi-account. If any problems occur contact cds.

53

54

55

== Aesthetics and Perception ==

56

57

Lloyd, Rodgers, and Roberts. "Metro map colour-coding: effect on usability in route tracing." In International conference on Theory and Application of Diagrams, pp. 411-428. Springer, 2018. **[[PDF>>url:https://www.researchgate.net/profile/Peter_Lloyd14/publication/324279056_Metro_Map_Colour-Coding_Effect_on_Usability_in_Route_Tracing/links/5ac94b090f7e9bcd519751ae/Metro-Map-Colour-Coding-Effect-on-Usability-in-Route-Tracing.pdf||shape="rect"]]**

58

59

Burns, Carberry, Elzer, and Chester. "Automatically recognizing intended messages in grouped bar charts." In //International Conference on Theory and Application of Diagrams//, pp. 8-22. Springer, 2012. **[[PDF>>url:https://www.researchgate.net/profile/Stephanie_Schwartz9/publication/262169666_Automatically_Recognizing_Intended_Messages_in_Grouped_Bar_Charts/links/550882ff0cf26ff55f82ccee.pdf||shape="rect"]]**

60

61

== Human Computer Interaction ==

62

63

Pietriga. "A Toolkit for Addressing HCI Issues in Visual Language Environments." In //IEEE Symposium on Visual Languages and Human-Centric Computing// (VL/HCC), pp.145–152. 2015. **[[PDF>>url:https://ieeexplore.ieee.org/iel5/10093/32326/01509498.pdf||shape="rect"]]**

64

65

Green, Petre. "Usability Analysis of Visual Programming Environments - A Cognitive Dimensions Framework." In //Journal of Visual Languages and Computing//, pp. 131–174, Issue 7–2. 1996. [[**Seite mit PDF**>>url:https://www.sciencedirect.com/science/article/pii/S1045926X96900099||shape="rect"]]

66

67

Pourali, Atlee. "A Focus+Context Approach to Alleviate Cognitive Challenges of Editing and Debugging UML Models." In //ACM/IEEE 22nd International Conference on Model Driven Engineering Languages and Systems (MODELS)//, pp. 183–193. 2019. [[**PDF**>>url:https://ieeexplore.ieee.org/iel7/8894013/8906890/08906900.pdf||shape="rect"]]

68

69

Frisch, Dachselt. "Off-Screen visualization techniques for class diagrams." In //Proceedings of the 5th International Symposium on Software Visualization//, pp. 163–172. 2010. [[**PDF**>>url:https://www.researchgate.net/profile/Raimund_Dachselt/publication/220955887_Off-screen_visualization_techniques_for_class_diagrams/links/0fcfd50abd0eba0db2000000.pdf||shape="rect"]]

== Graph Drawing ==

Chevalier and Safro. "Comparison of coarsening schemes for multilevel graph partitioning." In //International Conference on Learning and Intelligent Optimization//, pp. 191-205. Springer, 2009. [[**PDF**>>url:http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.531.2924&rep=rep1&type=pdf||shape="rect"]]

74

75

Athenstädt, Hartmann, and Nöllenburg. "Simultaneous embeddability of two partitions." In //International Symposium on Graph Drawing//, pp. 64-75. Springer, 2014. [[**PDF**>>url:https://arxiv.org/pdf/1408.6019||shape="rect"]]

== Euler Diagrams ==

Bottoni, Costagliola, and Fish. "Euler diagram encodings." In //International Conference on Theory and Application of Diagrams//, pp. 148-162. Springer, 2012. [[**PDF**>>url:https://s3.amazonaws.com/academia.edu.documents/45649653/Euler_diagram_encodings20160515-26490-1rvpanx.pdf?AWSAccessKeyId=AKIAIWOWYYGZ2Y53UL3A&Expires=1532097323&Signature=0mp3Nn2fRT4GGNbTTcWS%2F3gWwR8%3D&response-content-disposition=inline%3B%20filename%3DEuler_Diagram_Encodings.pdf||shape="rect"]]

80

81

Chapman, Stapleton, Rodgers, Micallef, and Blake. "Visualizing sets: an empirical comparison of diagram types." In //International Conference on Theory and Application of Diagrams//, pp. 146-160. Springer, 2014. [[**PDF**>>url:http://eprints.brighton.ac.uk/13703/1/diagrams2014%20Visualizing%20DataREVISED.pdf||shape="rect"]]

82

83

== Other Types of Diagrams ==

84

85

Erwig and Smeltzer. "Variational Pictures." In //International Conference on Theory and Application of Diagrams//, pp. 55-70. Springer, 2018. **[[Seite mit PDF>>doc:SS20 Eingeschränkt sichtbare Paper]]**{{/expand}}\\

= Schedule =

== Dates in the semester (currently not final) ==

91

92

(% class="wrapped relative-table" style="width: 52.6894%;" %)

|=(((

Datum

)))|=(((

Meilenstein

)))

|(((

Mo., 25.10., 23:59

)))|(((

Deadline for topic

)))

|(((

Mo., 25.10., 12:00

)))|(((

Kick-off

//The kick-off will take place online. We will send you the corresponding link.//

)))

|(((

Mo., 15.11., 23:59

)))|(((

Deadline of the first draft in EasyChair

113

//Content: abstract, introduction, outline, notes for chapter contents, bibliography//

114

)))

115

|(% colspan="1" %)(% colspan="1" %)

116

(((

117

In week of above, individual dates

118

)))|(% colspan="1" %)(% colspan="1" %)

119

(((

120

Individual dates

121

//Online, as discussed with advisor

122

//

123

)))

124

|(% colspan="1" %)(% colspan="1" %)

125

(((

126

Mo., 12.12, 23:59

127

)))|(% colspan="1" %)(% colspan="1" %)

128

(((

129

Deadline of the first full version

130

//Submission-Update in EasyChair//

131

)))

132

|(% colspan="1" %)(% colspan="1" %)

133

(((

134

In week of above, individual dates

135

)))|(% colspan="1" %)(% colspan="1" %)

136

(((

137

Individual dates

138

//Online, as discussed with advisor//

139

)))

140

|(% colspan="1" %)(% colspan="1" %)

141

(((

142

Mo., 10.01., 23:59

143

)))|(% colspan="1" %)(% colspan="1" %)

144

(((

145

Deadline of the review version

146

//Submission-Update in EasyChair//

147

)))

148

|(% colspan="1" %)(% colspan="1" %)

149

(((

150

subsequently

151

)))|(% colspan="1" %)(% colspan="1" %)

(((

Review assignment

//By e-mail//**

**

)))

|(% colspan="1" %)(% colspan="1" %)

158

(((

159

Mo., 17.01., 23:59

160

)))|(% colspan="1" %)(% colspan="1" %)

(((

Deadline reviews

//In EasyChair//

)))

|(% colspan="1" %)(% colspan="1" %)

166

(((

167

tbd

168

)))|(% colspan="1" %)(% colspan="1" %)

169

(((

170

Talk on how to do talks/presentations (the talk-talk)?

171

)))

172

|(% colspan="1" %)(% colspan="1" %)

173

(((

174

In the week of Mo., 31.01.

175

)))|(% colspan="1" %)(% colspan="1" %)

176

(((

177

Individual dates for presentation slides

178

//Online, as discussed with advisor. The slides have to be available online or have been sent beforehand via e-mail.//**

179

**

180

)))

181

|(% colspan="1" %)(% colspan="1" %)

182

(((

183

Mo., 14.02., 23:59

184

)))|(% colspan="1" %)(% colspan="1" %)

185

(((

186

Deadline final version

187

//Submission-Update in EasyChair//**

188

**

189

)))

190

|(% colspan="1" %)(% colspan="1" %)

191

(((

192

TBD

193

)))|(% colspan="1" %)(% colspan="1" %)

(((

Presentations

)))

== The Final Presentations ==

199

200

Currently, it is unclear how the talks will take place. This will be influenced by the development of the pandemic. We can think of recorded videos or a live conference or other alternatives. We expect to be able to make a decision at the end of Mai.

201

202

203

= Schedule and Grading =

204

205

206

== Papers, Talks, Review ==

207

208

This seminar includes the creation of a paper, a talk, and two reviews.

=== Paper ===

The paper should provide an overview of the chosen topic. It should be written in a style that late bachelor student can understand it. The paper should be 6 (master) or 4 (bachelor) pages long, not more not less, and it should use the ACM LaTeX-style (more details below). We advise you to read the [[writing advice>>doc:RTSYS.Writing and Grading Theses||shape="rect"]] for writing a thesis.

=== Talk ===

The talk should be 40 minutes (master) or 25 minutes (bachelor) long. This is followed by 5 minutes of questions. The slides should contain page numbers to allow the participants to ask specific questions after the talk. It would be great to include a short tool demo if your topic includes some concrete implementation.\\

217

218

You can freely choose your presentation tool. The talk can be held in English or German.

=== Review ===

A review consist of two parts:

223

224

1. General comments (what do you like / not like regarding content, structure, and readability) as well as general suggestions to improve the paper

225

1. In detail remarks and corrections

226

227

The first part of the review should be at least half an A4 page long. It should be written in full text and not only consist of notes. The review content should be similar to the review you get during the individual dates, however, it should be more in detail and with a clear focus on content, structure, and readability of the paper.

228

229

It is not possible to add files in the EasyChair review form. Therefore, it is not possible to add an annotated pdf as detailed correction.

230

231

The reviews are assigned after the review-version deadline and are based on the submitted version of the papers.

== Grades ==

This seminar is graded. The grade is based on each milestone (the different versions of the paper, the reviews, the slides, the talk). For each milestone quality, timing (see dates) are graded. You may fail the seminar because of missed deadlines.

236

237

238

= Technical Details =

== LaTeX ==

Your papers should be created using LaTeX and have to be in the ACM style. You can find all necessary files in this [[archive>>attach:paper-template.zip]], including an example document that includes helpful LaTeX-hints to start with. Copy all files in some folder and begin to write your paper.

244

245

LaTeX can create a bibliography (it includes scientific publications, which are referenced to prove statements) too. The example includes a file named {{code language="none"}}myrefs.bib{{/code}}, which holds the references. ACM provides a short overview with [[examples>>url:https://www.acm.org/publications/authors/bibtex-formatting||shape="rect"]] of bibliography entries.

246

247

While writing your paper keep the following in mind:

248

249

* Think about whether you want to write your paper in German or English and make use to use the corresponding ACM-style.

250

* Graphics from your original paper should not just be screenshotted and added to your paper. Ideally, you create your own graphic (ideally as a vector graphic) to have good quality graphics.

251

* A paper always consists of an introduction, at least one main chapter, and a conclusion.

252

253

== EasyChair Tutorial ==

254

255

You can find our seminar in EasyChair [[here>>url:https://easychair.org/my/conference?conf=kielrtsyssem20ss||shape="rect"]].

256

257

[[doc:RTSYS.EasyChair Student Tutorial]]

= Ressources =

In general, it is advised to look for related work in the university network since you will get access to many online libraries. We the following search engines and web pages:

266

267

* Google Scholar: [[http:~~/~~/scholar.google.de/>>url:http://scholar.google.de/||shape="rect" class="external-link"]]

268

* dblp: [[http:~~/~~/dblp.uni-trier.de/>>url:http://dblp.uni-trier.de/||shape="rect"]]

269

* CiteSeer: [[http:~~/~~/citeseer.ist.psu.edu/>>url:http://citeseer.ist.psu.edu/||shape="rect" class="external-link"]]

270

* IEEE-Xplore: [[http:~~/~~/ieeexplore.ieee.org/Xplore/dynhome.jsp>>url:http://ieeexplore.ieee.org/Xplore/dynhome.jsp||shape="rect" class="external-link"]]

271

* ACM Digital Library: [[http:~~/~~/portal.acm.org/dl.cfm>>url:http://portal.acm.org/dl.cfm||shape="rect" class="external-link"]]

272

* Universitätsbibliothek Digitale Medien: [[http:~~/~~/www.uni-kiel.de/ub/emedien/index.html>>url:http://www.uni-kiel.de/ub/emedien/index.html||shape="rect"]]

\\

)))

(% style="display: none;" %)

279

(((

280