600 Technik, Technologie
Refine
Year of publication
Document Type
- Conference Proceeding (3)
- Part of a Book (2)
- Master's Thesis (2)
- Article (1)
- Article trade magazine (1)
- Bachelor Thesis (1)
- Diploma Thesis (1)
- Workingpaper / Report (1)
- Study Thesis (1)
Keywords
- FHD (2)
- Künstliche Intelligenz (2)
- Academic Software (1)
- Architecture Erosion (1)
- BestHeatNet (1)
- Cross-Platform-Development (1)
- Cross-Plattform Entwicklung (1)
- Digitalisierung (1)
- Diplomarbeit (1)
- Entwicklung (1)
Department/institution
Feldspritzen verfügen über entlang eines Spritzgestänges angebrachte Düsen, die ein Pflanzenschutzmittel-(PSM-)Trägerflüssigkeits-Gemisch verteilen. Da die Düsen nur ein PSM-Gemisch applizieren und häufig nicht einzeln ansteuerbar sind, wird nicht bedarfsgerecht verteilt und u. U. stellenweise zu wenig, zu viel oder nicht das optimale PSM appliziert. Dieser Beitrag stellt das Labormodell einer High-Speed-Dosiereinheit zur Vermischung dreier PSM mit der Trägerflüssigkeit vor, mit der Pflanzen individuell und mit der minimal nötigen PSM-Menge behandelt werden. Sie arbeitet unabhängig vom hydraulischen System der Trägerflüssigkeit, ist reaktionsschnell und überaus dosiergenau. Basierend auf einer Applikationskarte, die den Pflanzenstatus enthält, und der GPS-Position werden Ausbringvolumen, -zeitpunkt, -position und PSM-Art in einem ISOBUS-Terminal bestimmt und an ein Steuergerät weitergegeben, das die Dosiereinheit ansteuert. Neben der neuentwickelten Hardware und Steuerung werden erste Prüfstandergebnisse vorgestellt.
Background
Digital technologies are increasingly used in healthcare. In this context, perceived safety plays a critical role in their acceptance and implementation. Previous research had focused more on data security or specific digital technologies. There has also been a lack of participatory approaches to consider and empower healthcare recipients (and relatives), providers, and technology experts to broaden the phenomenon.
Objective
The aim of this study was to present a comprehensive perspective on the needs, influencing factors and related outcomes in the context of feeling safe with digital technologies in healthcare.
Method
A qualitative, exploratory, and participatory methodology was used with five guide-based focus group workshops. Each workshop explored one of five digital technology demonstrations provided at the beginning: (1) electronic health records (EHR), (2) robotics, (3) artificial intelligence (AI), (4) smart home, and (5) smart hospital. All participants were invited for a guide-based discussion. The study focused on the levels of ‘involvement’ and ‘collaboration’ by also empowering participation. The workshop target groups were actively involved in the development and execution of the workshops and were empowered. The data were analysed via a content analysis approach, with a mostly inductive procedure.
Results
Feeling safe was found to affect thoughts, emotions, and actions. For example, a higher level of perceived safety increased the acceptance of digital technologies, whereas a lower level of perceived safety decreased it. The corresponding needs and influencing factors differed in terms of their scope and focus depending on the context. The aspect of ‘control’ was most frequently addressed by all the target groups and was viewed as relevant in all the workshops. In general, digital technologies were viewed as supplements rather than substitutes for healthcare providers.
Conclusion
This study extends beyond the current state of research on perceived safety and the use of digital technologies in healthcare by providing a comprehensive overview of the corresponding needs and influencing factors at various levels, such as the individual, community-organizational, and system-society levels. The perceived safety of healthcare recipients and providers related to digital technologies should be taken into consideration to achieve positive implementation outcomes.
Sustainable software architecture is crucial for the success of an evolving system that is affected by its context and environment. However, deviations between software design and implementation are often uncontrolled and induce architectural erosion. The literature describes several symptoms and observes this phenomenon in open source software. Prominent reasons for the occurrence of architectural erosion include a rushed evolution, recurring changes, a lack of developers' awareness, time pressures, and the accumulation of design decisions. Architectural erosion is also prevalent in academic projects, but it still needs to be researched in-depth in a real-life setting.
In this work, a single case study investigates the symptoms and reasons for architectural erosion in open source software originating from academia by employing a mixed-methods approach. Architectural metrics from a static code analysis using ARCADE Core are contrasted with developers' perspectives sourced from semistructured interviews. The investigated project is JackTrip, a cross-platform application for realtime networked music performances and Internet reverberation research.
The first research question aims at assessing the trend of structural symptoms for architectural erosion in JackTrip. The results show a significant increase in link overload smells in the course of the evolution, which reached 11 as of version 1.6.2. This supports the developers' perception of a rushed evolution corresponding to the second research question, which asks to what extent prominent causes for architectural erosion apply. Additionally, the interview data evince time constraints related to tight research funding and the commercialization of the project. Research question 3 investigates how the academic environment and the problem domain relate to the symptoms and reasons for architecture erosion. It has been found that these influences shape the development approach and impact contributor selection.
In relation to a certain inexperience and lack of commitment of open source developers as a reason for architectural erosion, the results suggest further studies and opt for ending the discussion regarding skills. Currently, the role of an architect or dedicated architectural work does not seem to be present in the JackTrip project. However, structural issues described in this work should not be considered as categorical statements about its software architecture as they would need to be confirmed on a code level.
SOLAR DECATHLON EUROPE - TEAM MIMO DER HSD STELLT SICH DER AUFSTOCKUNG SAMT SANIERUNG DES CAFÉS ADA
(2021)
Die im Laufe des Jahres veröffentlichten Passwörter auf der Plattform "Have I been pwnd" zeigen deutlich, dass Nutzer aufgrund von besserer Merkbarkeit schwache Passwörter wählen. Dies hat zur Folge, dass die sensiblen Daten der Nutzer nur unzureichend geschützt sind. Aus diesem Grund gewinnt das Themengebiet der IT-Sicherheit zunehmend an Bedeutung. Passwortmanager stellen für dieses Szenario eine mögliche Lösung dar.
Der im Rahmen dieser Masterthesis entwickelte Passwortmanager "Safeword" ermöglicht, sensitive Daten, die mittels adäquaten kryptografischen Verfahren geschützt werden, zentral an einer Stelle abzulegen und sukzessive unsichere Passwörter durch starke zufällige Passwörter zu ersetzen. Der Nutzer muss sich nur ein starkes Hauptkennwort merken, mit dem er sich bei dem Passwortmanager authentisiert und anschließend die gespeicherten Passwörter abrufen kann. Der Passwortmanager bietet zahlreiche Funktionen, die die Nutzung der Anwendung erleichtern, wie die simple und moderne Oberfläche, einen Passwort-Generator, der kryptografisch sichere Zufallspasswörter erstellt, oder Funktionen zur besseren Handhabung von Passwörtern, beispielsweise Label oder Notizen.
Safeword basiert auf einer modularen und erweiterbaren Architektur, die auf Code-Sharing setzt. Das Code-Sharing vereinfacht die Wartung der Anwendung und ermöglicht bei Schwachstellen eine schnellere Behebung. Die Ergebnisse aus dem Vergleich existierender Passwortmanager flossen direkt in die Entwicklung von Safeword ein, sodass aus Fehlern anderer Mitbewerber gelernt werden konnte. Um den Beitrag zur Open-Source-Welt sicherzustellen, wird Safeword unter der GPLv3-Lizenz bereitgestellt, sodass auch in Zukunft viele Nutzer von dem Passwortmanager profitieren können.
Voraussetzung für den Produktiveinsatz von Safeword ist die Entwicklung noch fehlender Funktionen und die Prüfung des Quelltexts nach aktuellen Standards der IT-Sicherheit.
Progressive web applications (PWAs) seem to be the next big thing in the mobile landscape. These are web applications with “super-powers” which are meant to provide the kinds of user experiences previously only native mobile applications could. Therefore they are able to match native applications in their capabilities but still thrive on the reachability of the web. They achieve this by implementing certain characteristics which originate from innovative standards and sophisticated best practices. Conveniently, as it is the web, PWAs are working seamlessly cross-platform. One of the closest things to a PWA so far may be an application created with the NativeScript framework. Such an application is also developed with web technologies yet able to use any native interface directly. This is made possible by using a designated runtime for mediating between JavaScript and the mobile system. Eventually, NativeScript is able to offer a high degree nativity yet also of convenient abstraction during development. This paper is set out to deliver further insight into both approaches by contrasting them based on the characteristics of PWAs. For this purpose, these characteristics are elaborated and adjusted to be applicable to native mobile applications. Hence a reasonable basis for what to expect from a native application is derived. Then NativeScript is assessed on this basis by the means of transferable concepts and technologies as well as a prototypic mobile application. Finally, an informed discussion and conclusion is performed based on the results. The comprehensive characteristics of PWAs resolve previous shortcomings with well thought out concepts and new technologies. These are transferable to native mobile applications to a far extent and may also be put into practice with NativeScript. The framework’s approach may be very well called ingenious, however, in the long run it might fall short of the innovative concept of PWAs. Having said this, it is still able to serve as a practical measure for creating appealing user experiences for multiple systems with arguably little effort. Due to large overlap a transformation between the two application types is a realistic option. Either way, web technologies are far from what they used to be and it is exciting to see how the mobile and web landscape will evolve in the future.