The Human Factor in Software Engineering

Am 28.-29.11.2013 findet das GI-Fachgruppentreffen Requirements Engineering in Ilmenau statt. Ich bin natürlich wieder als Mitorganisatorin und Vortragende dort.

CreaRE 2014: Fourth International Workshop on Creativity in Requirements Engineering

http://www.se.uni-hannover.de/events/creare-2014

*** Workshop topic, background and motivation ***
Requirements Engineering (RE) not only demands a systematic approach for eliciting, documenting, and validating requirements, but it also is a creative activity. It demands that stakeholders create visions of future software systems and to imagine all their implications. Creativity techniques that have been developed and used in other disciplines and areas of problem-solving, have the potential to be adapted and adopted in today’s RE, becoming the foundation for innovative RE processes addressing both problem analysis and solution design.

*** Goals of the workshop ***

The CreaRE series of workshops brings together RE practitioners and researches who are interested in discussing the role of creativity in RE, the array of creativity techniques that can be applied to RE, and the ways in which creativity techniques from other disciplines can be leveraged in RE. Drawing upon the previous workshop editions, the intended purpose of the CREARE’14 workshop is to be a forum for the exchange of emerging ideas, experience and research results. It also aims at raising awareness in the RE community of the importance of creativity and creativity techniques.

The unique goal of the CreaRE 2014 workshop is to foster collaborative brainstorming and exchange of research designs, and possibly results from studies on using game-based techniques for RE. To this end, we plan to create a game for and with the workshop participants, and experiment with it during the REFSQ’14 conference.

*** Important Dates ***
• Jan 5, 2014: paper submission deadline
• Jan 30, 2014: author notification
• Feb 18, 2014: submission of camera-ready papers
• April 7, 2014: workshop date

*** Workshop topics ***
Workshop topics include, but are not restricted to:
• The interplay of requirements and creativity (e.g. between RE and the creative process of game design)
• Theories for creativity that fit RE
• The application of known creativity techniques in RE activities
• Emerging ideas for new/adapted creativity techniques for RE activities
• Tool support for creativity-enhancement
• Context-dependency of creativity and creativity techniques
• Industry experiences with creativity techniques in RE
• Relation of creativity to innovation
• RE techniques that enable or support creativity
• Skill-sets for creativity in RE
• Creativity via reuse: trading off innovation and efficient production
• Thought reading: understanding the other perspective/ person
• Creativity in RE for entertainment applications (e.g. games, online learning systems)


*** paper submission and selection process ***
We invite two types of submissions: position papers and full papers. Both types should treat a topic from the workshop themes.
- Position papers (3-6 pages): Short papers, stating the position of the author(s) on any of the workshop topics. For example, position papers could describe an experiment or a case study in industry. These papers will be evaluated on their potential for generating discussion, on practical relevance and on the originality of the positions stated. Position papers can also be used to describe emerging ideas on how creativity should be performed. These papers will be evaluated based on their relevance, originality and sound argumentation.
- Full papers (8-10 pages): Full papers evaluating an experience (in industry) or describing the results of a research effort. Full papers will be evaluated for innovativeness of the proposed ideas and for technical soundness.

Submissions will be accepted via E-Mail at herrmann@herrmann-ehrlich.de. All paper submissions should be in the LNCS format (see http://www.springer.com/computer/lncs?SGWID=0-164-12-73062-0).
The papers will be published in the REFSQ workshop proceedings.
All submissions will be reviewed by three members of the Program Committee.
Workshop agenda
We plan for a half day workshop that includes a key note, a paper presentation session, a game with the workshop participants, and a closing discussion.

*** Past editions of the workshop ***
8 April 2013 at REFSQ 2013: http://www.se.uni-hannover.de/events/creare-2013
organizers were Maya Daneva, Andrea Herrmann, Anne Hoffmann, Kurt Schneider
19 March 2012 at REFSQ 2012: http://www.se.uni-hannover.de/events/creare-2012
organizers were Maya Daneva, Joerg Doerr, Andrea Herrmann, Kurt Schneider
29 June 2010 at REFSQ 2010: https://sites.google.com/site/creare2010/
organizers were Joerg Doerr, Andrea Herrmann, Klaus Schmid, Kurt Schneider

*** Program Committee ***

Sebastian Adam Fraunhofer Institut IESE, Germany
Dan Berry University of Waterloo, Canada
Hans Hartmann OBJENTIS Software Integration GmbH, Austria
Thomas Herrmann Ruhr-University of Bochum, Germany
Eric Knauss Chalmers | University of Gothenburg, Sweden
Anitha PC Siemens Information Systems Ltd., Bangalore, India
Chris Rupp Sophist Group, Germany
Klaus Schmid University of Hildesheim, Germany
Roel Wieringa University of Twente, The Netherlands
Konstantinos Zachos City University London, UK

*** Workshop organizers ***

Andrea Herrmann, Herrmann & Ehrlich, Germany
Maya Daneva, University of Twente, The Netherlands
Joerg Doerr, Fraunhofer IESE, Germany
Anne Hoffmann, Siemens AG, Germany
Kurt Schneider, Leibniz University Hannover, Germany

It is very instructional, and in my opinion even essential to change roles now and then and to walk a mile or two in my customers´ boots. Therefore, I am currently studying historical fiction and songwriting at Coursera. It would be boring for me to attend a course about software engineering, in fact, because there is not much new to learn for me on college level.

But I am highly motivated and already had a lot of fun reading articles about historical novels. In the songwriting course, the professor (Pat Pattison) is telling us stories in order to teach us simple truths about song lyrics. However, the challenge is not to understand these principles, but to apply them artistically. I feel so great, when I manage to answer to the quiz about the learning stuff successfully. I get direct feedback that I understood everything right. Later course units will then demand me to apply what I learned by writing a song. And singing. :-)

Let´s see how far I get. My objective is to end with a great song. I have been keeping my eyes open for a topic. And immediately found one: A pigeon on the rail tracks, pecking a bread roll. When the train was approaching, the pigeon was torn between continuing its breakfast as long as possible, and fleeing from the deadly threat. It carefully observed the train and managed to find the right moment to leave. However: What if not? What if the pigeon every day leaves a second later? Aren´t we in life sometimes also hesitating to leave a good piece of bread even when we know it is dangerous?

In fact, I do not have any time for taking courses. So, I wondered whether I would survive the first week. And I have missed the short deadline of one of the homework. Fortunately, I was not thrown out of the course, only got a penalty on my grading. In constrast to real students, I do not need a good grading. I study just for fun. So, this is OK. Apart from this, I find amazingly many occasions to listen to the 12-minutes video lectures during breakfast or boring work, and it is a nice leasure-time activity to answer quizzes about historical fiction and songwriting. A minute ago, I listened to a lecture while printing out course material for my own lecture. So, maybe I will finish the courses successfully despite all the hectic at work.

Unfortunately, the Camp David Expedition takes place without me: "Leider müssen wir Dir mitteilen, dass Du nicht dabei bist und wir an Dich, trotz Deiner sportlichen Fähigkeiten, keinen Startplatz für die Qualifikationsveranstaltung vergeben können – Deine Mitbewerber/innen haben unsere Jury mehr überzeugt."
This is a pity. But I will keep touring in Germany. Anyway, I had started having strange dreams with Joey Kelly and me at -20°C in a snow storm, climbing up a vertical cliff. This is probably a very realistic nightmare. Next time, Joey! I keep training!

So far, universities owned the monopoly on assigning ECTS points to students. And they did so only for traditional lectures, which are much like the lectures in the Middle Ages. Now, for the first time, ECTS points can be obtained by successfully attending an online course at iversity.
For reading more:

• Deutsch
• English

Jeder von uns kann das Opfer von Spionage werden, denn wir sind ja alle sooo interessant. Und die NSA (und andere Geheimdienste) haben unglaubliche Möglichkeiten. Gestern Abend war ich bei einem Vortrag des Chaos Computer Clubs zu diesem Thema: Stefan Leibfarth: "Prism, Tempora und Co. - Wie wir überwacht werden und wie wir uns verteidigen können".

Wie wir überwacht werden, können Sie hier und hier nachlesen.

Was aber tun, um sich und seine Daten zu schützen? Stefan Leibfarth empfahl die folgenden Maßnahmen:

• demonstrieren
• die richtige Partei wählen (bald sind Wahlen!)
• mit Ihrem Abgeordneten sprechen
• Open Source Software benutzen (in kommerzieller Software sind mit höherer Wahrscheinlichkeit Hintertüren eingebaut)
• Meiden Sie US-basierte Anbieter von Software und Dienstleistungen
• Datensparsamkeit: Nicht alle Kommunikation muss elektronisch erfolgen und Sie müssen in Formularen nicht alle Felder (korrekt) ausfüllen.
• raus aus der Cloud: Benutzen Sie keine Online-Speicherdienste
• Verwenden Sie ein sicheres Betriebssystem, z.B. Linux.
• Verschlüsseln Sie Dateien und E-Mails. Für die E-Mail-Verschlüsselung gibt es PGP-Plugins für Ihren E-Mail-Client, z.B. Enigmail für Thunderbird.
• Surfen Sie anonym, z.B. über Tor
• Verwenden Sie Ad-Blocker wie ABE
• Verwenden Sie einen Virenscanner. Für Linux gibt es ClamAV.
• Verwenden Sie die anonyme Suchmaschine DuckDuckGo
• Auf gar keinen Fall kapitulieren! Alles was Sie tun, ist besser als nichts.

Doing research alone is most efficient: You design your study as you always do, make fast decisions and let routine do the rest.
However, this approach can lead you on the street of overconfidence. Experts very fast believe to control even complex situations and that solutions that worked before will work in the next project, too. When reading Kahneman´s "Thinking fast, thinking slow", I applied what I read on the work of scientists. Of course, scientists are trained to think objectively, to separate facts from interpretation, to know how definitive a certain piece of information is. However, we are still humans with the related limitations of our brains. Being experts and knowing methods, having been successful, can make us trust our expertise too much, like this is the case for other experts, too.
Therefore, the more experience I have with research, the more I believe that a researcher should never work alone. Working in a team forces the researcher to justify all decisions when they are made (and not when a journal reviewer demands more clarification, what can lead to artificial posteriori justifications), all material is reviewed, potential misunderstandings by interviewed persons and experiment objects can be foreseen by a partner.
The research partner needs not be more experienced than you. Even students can be great partners, because you need to explain them every step and they ask questions which are even better than they themselves believe them to be. Encourage them to ask and doubt, and they will. It is interesting for them to see how difficult good research is and how important details can be. So, the discussions become part of their learning process.

Gestern also fand in unserer GI-Regionalgruppe der Vortrag "ISO this *" von Jörg Simon statt.
Das Sternchen steht übrigens für ein beliebiges Schimpfwort. Es wendet sich gegen die Unart, echte Sicherheit durch Compliance zu ersetzen. Grundsätzlich widersprechen Compliance und Sicherheit einander nicht, sondern unterstützen einander. Aber im Einzelfall muss man sich eventuell entscheiden.

Was ist nochmal Sicherheit? Security bedeutet, den zu schützenden Wert (Asset) von der Bedrohung zu trennen. Leider funktioniert dann das Business meist nicht mehr. Es ist also ein gewisses Maß an Öffnung (Porosity) nötig, was Angriffsflächen erschafft. Safety ist dann die Kontrolle dieser Öffnung. Für die Öffnung gilt: Porosity = Visibility + Access + Trust, d.h. Sichtbarkeit + Zugang + Vertrauen.

Jörg Simon berichtete uns lebhaft aus verschiedenen Projekten, wie und wo dort Sicherheit gemacht wird:
Fedora ist ein Open Source Betriebssystem und unterstützt durch das Fedora Security Lab das praktische Erlernen von Security-Testing in der Lehre, indem es Ziele für Angriffe anbietet.
Das OSSTMM Open Source Security Testing Methodology Manual ist ein Handbuch fürs Sicherheitstesten.
Kurse zum Thema Sicherheitstesten gibt es in der Hacker Highschool. Auch wir lernten nun die verschiedenen Artren von Teststrategien und Phasen eines Angriffs kennen.