
Quality of Experience – Why Bother?
15. Oktober 2014

WHO:
WHEN:
WHERE:
WHY: To do cool things that matter!
DETAILS:
What is Content ID?
Copyright owners can use a YouTube specific system called Content ID to easily identify and manage their content on YouTube. Videos uploaded to YouTube are scanned against a database of files that have been submitted by content owners. Copyright owners get to decide what happens when content in a video on YouTube matches a work they own. When this happens, the video gets a Content ID claim.
About Thomas (Bio)
Der Rückblick zum TEWI-Kolloquium von Dr. Fabian Beck am 03.09.2014 beinhaltet die Videoaufzeichnung sowie die Folien:
Video
[iframe height=“350″ src=“http://video.aau.at/video.php?video=ftf_beck.mp4″]
Slides
[iframe src=“http://www.slideshare.net/slideshow/embed_code/38904796″ width=“476″ height=“400″ frameborder=“0″ marginwidth=“0″ marginheight=“0″ scrolling=“no“]
Abstract
Abstract: Software visualization addresses the visual representation of software systems, their dynamic execution, and their development process. In this context, diagrams can help software developers, software architects, or researchers understand and analyze the system, to finally improve the software and development process. Those different roles, however, come along with different perspectives and requirements for visualization tools. In my talk, I will give recent examples from my own work how those diverging perspectives can be addressed: On the one hand, high-level visualizations showing complete software systems and their evolution might be leveraged by architects and researchers. On the other hand, small visualizations embedded in the code could support developers in their daily work extending and optimizing the code. Finally, I want to conclude by giving an outlook on future perspectives on software visualization.
Biography
Fabian Beck is a postdoctoral researcher at VISUS, University of Stuttgart, Germany. In 2013, he obtained his Dr. rer. nat. (PhD) degree in computer science from University of Trier. In his dissertation, he investigated multi-dimensional coupling graph structures of software systems. In general, most of his research is focused on methods for visualizing and comparing large and dynamic graphs and hierarchies, often in the context of software systems and their evolution. In recent projects, he also studies the use of word-sized visualizations embedded in source code and text.
Abstract: Software visualization addresses the visual representation of software systems, their dynamic execution, and their development process. In this context, diagrams can help software developers, software architects, or researchers understand and analyze the system, to finally improve the software and development process. Those different roles, however, come along with different perspectives and requirements for visualization tools. In my talk, I will give recent examples from my own work how those diverging perspectives can be addressed: On the one hand, high-level visualizations showing complete software systems and their evolution might be leveraged by architects and researchers. On the other hand, small visualizations embedded in the code could support developers in their daily work extending and optimizing the code. Finally, I want to conclude by giving an outlook on future perspectives on software visualization.
Biography: Fabian Beck is a postdoctoral researcher at VISUS, University of Stuttgart, Germany. In 2013, he obtained his Dr. rer. nat. (PhD) degree in computer science from University of Trier. In his dissertation, he investigated multi-dimensional coupling graph structures of software systems. In general, most of his research is focused on methods for visualizing and comparing large and dynamic graphs and hierarchies, often in the context of software systems and their evolution. In recent projects, he also studies the use of word-sized visualizations embedded in source code and text.
Janusz Konrad | ECE Department, Boston University | July 21 th, 2014, 14:00 CET | Lakeside Labs, Room L4.1.114
Abstract: How many times per day do you need to prove your identity? Perhaps 5, maybe 10 or even 20. Try to access your smartphone and you need a 4-digit PIN at minimum. Need to check email at work and you have to provide username and password. Want to enter a lab and you need to punch in a code, swipe a magnetic card or wave an RFID tag. While cards and tags can be easily lost, codes and passwords are difficult to remember once we have too many of them, and we all do! One answer to this dilemma is to use biometrics such as fingerprints, irises or facial characteristics, but should they be compromised there is no way to replace them. In this talk, I will describe our recent work on using soft biometrics jointly with gestures to authenticate a user. We implicitly use rough proportions of human body shape from skeleton data captured by Kinect camera. Should these soft biometrics become compromised, a user can easily change his/her gesture and prevent the loss of identity. I will describe details of our approach and some experimental results in which we have attained a 1-2% equal error rate on a database of 40 users. We believe this level of performance shows promise for swinging your way to security in a not-too-distant future.
Bio: Janusz Konrad earned the M.Eng. degree from the Technical University of Szczecin, Poland, and the Ph.D. degree from McGill University, Montreal, Canada. From 1989 to 2000 he was with INRS-Telecommunications, Montreal, and since 2000 with Boston University. He has been on Editorial Boards of various IEEE and EURASIP journals related to signal, image and video processing. He was the General Chair of AVSS-2013, a Technical Program Co-Chair of ICIP-2000 and AVSS-2010, and Tutorials Co-Chair of ICASSP-2004. He is a co-recipient of the 2001 Signal Processing Magazine Award, the 2004-05 EURASIP Image Communications Best Paper Award, the AVSS-2010 Best Paper Award and a co-winner of the Semantic Description of Human Activities Contest at ICPR-2010. His research interests include image and video processing, stereoscopic and 3D displays, human-computer interfaces and visual sensor networks.
Während Softwareproduktlinien auf die Entwicklung von Softwarevarianten innerhalb einer Organisation zielen und einen längst etablierten Softwareentwicklungsansatz darstellen, wendet sich aktuell das Augenmerk verstärkt Software-Ökosystemen zu.
In diesem Entwicklungsmodell gibt es keine zentrale Koordination und die Eigenschaften des Systems werden erst zur Laufzeit beim Endanwender bestimmt.
Dies bringt eine Vielzahl neuer wissenschaftlicher und technischer Herausforderungen mit sich, die in diesem Vortrag dargestellt werden.
In meiner Arbeitsgruppe Software Systems Engineering an der Universität Hildesheim wurde ein Ansatz geschaffen, um die Entwicklung von Softwareproduktlinien und Software-Ökosystemen zu unterstützen. Grundlage dafür ist ein umfassender und flexibler Ansatz zur Unterstützung von Variabilität, sowie darauf aufbauend ein flexibler Ansatz zur effizienten Ableitung von Produktlinieninstanzen. Die Produktableitung wird dabei als (Modell-)transformations¬problem betrachtet.
In diesem Vortrag möchte ich insbesondere auf die besonderen Schwierigkeiten von Software-Ökosystemen eingehen, die über die üblichen Herausforderungen von Softwareproduktlinien hinausgehen. Hierzu zählen der Umgang mit Offenheit der Variation und als Konsequenz die Schwierigkeit die Vollständigkeit der Konfiguration und die Konsistenz und Vollständigkeit der Implementierung zu gewährleisten.
Qualitativ mangelhafte Softwaresysteme wie jüngst die Steuerungssoftware der Boeing 747-8 geraten immer wieder in die Schlagzeilen. Wie weit Softwaremetriken bei der Erkennung solcher Probleme helfen können, ist noch weitgehend ungeklärt. In diesem Vortrag werde ich jüngste Forschungsergebnisse nach denen Refactorings Metrikmesswerte oftmals negativ beeinflussen, diskutieren und zeigen, wie Kombinationen von Metriken und Code-Analyse zur Erkennung von “Design-Smells“ verwendet werden können. Abschließend werde ich skizzieren, wie ich zukünftig die Abschätzung von Änderungsaufwänden mit Hilfe von Metriken verbessern möchte.
Software systems, like many other systems, need to change in order to stay successful on the market. As has been described by Lehman’s Laws of Software Evolution, these changes cause software systems to become larger in size and more complex. As a consequence, more resources are needed to maintain, or in general, evolve a software system. Evolving software systems is therefore mastering change and system complexity. In this presentation, I show how the various data recorded for software projects can be used to identify critical parts of a software system and to help steering the evolution of software systems. Furthermore, I show how visualization techniques can be used to help software engineers to comprehend the implementation of large, complex software systems including large spreadsheets.
Research on automated software engineering aims to improve software development by automating tedious or error prone manual activities. We can now automatically produce tests, models, patches – and even software itself. But can we ultimately remove the human from software engineering, and is this even desirable? In this talk, I exemplify in the domain of automated software testing that software engineering depends on human software engineers, and discuss implications this has on automation research. Automated techniques need to be developed for software engineers, not to replace them. We can, however, utilise both, explicit and implicit human intelligence, to take automated software engineering to the next level.
Cyperphysical systems (CPS) are on the horizon to challenge the way we see and develop computer systems. CPS provide the integration of embedded computing, real-time computing, distributed computing, parallel computing, mobile computing, and server systems, resulting in completely new application domains. On one side the arise of CPS is just the natural consequence of various incremental improvements of enabling technologies. But from the software engineering side it creates big challenges for software engineering. CPS will result in significant rise of system complexities. At the same time there are serious security and safety challenges as it requires to combine subsystems with closed-world assumptions and those with open-world assumptions, requiring new interfacing solutions. In this talk we present the research towards the development of a programming model that is aimed to withstand the CPS challenge. This programming model will provide support for mixed-criticality systems and adaptability. As a fundamental change in software engineering we present a computing model that unifies the non-real time, soft-real time and hard real-time paradigms. An important mechanism included in this computing model are tolerance ranges, which allow to adapt the system when necessary. Such adaptation scenarios include fault-tolerance with reconfiguration and optimisation of resources like processing time or power consumption.