Refine
H-BRS Bibliography
- no (68) (remove)
Departments, institutes and facilities
Document Type
- Article (27)
- Conference Object (19)
- Part of a Book (8)
- Lecture (6)
- Book (monograph, edited volume) (5)
- Conference Proceedings (1)
- Master's Thesis (1)
- Patent (1)
Year of publication
- 2013 (68) (remove)
Has Fulltext
- no (68)
Keywords
- Amiloride (2)
- Mal d 1 (2)
- Molecular dynamics (2)
- apple allergy (2)
- cystic fibrosis (2)
- end user development (2)
- 1-Methycyclopropene (1)
- Adaptive resolution schemes (1)
- Airway surface liquid (1)
- Analysis (1)
Kommentierung zu § 39 BDSG
(2013)
In Software development, the always beta principle is used to successfully develop innovation based on early and continuous user feedback. In this paper we discuss how this principle could be adapted to the special needs of designing for the Smart Home, where we do not just take care of the software, but also release hardware components. In particular, because of the 'materiality' of the Smart Home one could not just make a beta version available on the web, but an essential part of the development process is also to visit the 'beta' users in their home, to build trust, to face the real world issues and provide assistance to make the Smart Home work for them. After presenting our case study, we will then discuss the challenges we faced and how we dealt with them.
The Java Virtual Machine (JVM) executes the compiled bytecode version of a Java program and acts as a layer between the program and the operating system. The JVM provides additional features such as Process, Thread, and Memory Management to manage the execution of these programs. The Garbage Collection (GC) is part of the memory management and has an impact on the overall runtime performance because it is responsible for removing dead objects from the heap. Currently, the execution of a program needs to be halted during every GC run. The problem of this stop-the-world approach is that all threads in the JVM need to be suspended. It would be desirable to have a thread-local GC that only blocks the current thread and does not affect any other threads. In particular, this would improve the execution of multi-threaded Java programs. An object that is accessible by more than one thread is called escaped. It is not possible to thread-locally determine if escaped objects are still alive so that they cannot be handled in a thread-local GC. To gain significant performance improvements with a thread-local GC, it is therefore necessary to determine if it is possible to reliably predict if a given object will escape. Experimental results show that the escaping of objects can be predicted with high accuracy based on the line of code the object was allocated from. A thread-local GC was developed to minimize the number of stop-the-world GCs. The prototype implementation delivers a proof-of-concept that shows that this goal can be achieved in certain scenarios.
PhD Project Management
(2013)