Refine
Year of publication
Document Type
- Article (54) (remove)
Has Fulltext
- yes (54)
Is part of the Bibliography
- no (54)
Keywords
- OSGi (3)
- SOA (3)
- complex event processing (3)
- mobile health (3)
- Akzeptanz (2)
- Arbeitsqualität (2)
- CEP (2)
- Computersicherheit (2)
- ECA (2)
- Empfehlungssystem (2)
- Ereignisgesteuerte Programmierung (2)
- Otto (GmbH & Co KG) (2)
- Patient (2)
- Security (2)
- Serviceorientierte Architektur (2)
- Smart Device (2)
- Telearbeit (2)
- Verarbeitung komplexer Ereignisse (2)
- Versicherung (2)
- Virtuelle Realität (2)
- acceptance (2)
- digital divide (2)
- event-driven architecture (2)
- general practitioners (2)
- mHealth (2)
- tablet (2)
- Abschlussarbeit (1)
- Ad-hoc-Netz (1)
- Adaptives Verfahren (1)
- Agent <Informatik> (1)
- Agile Softwareentwicklung (1)
- Agile software development (1)
- Allgemeinarzt (1)
- Android (1)
- Angst (1)
- Arbeitsbelastung (1)
- Arbeitsklima (1)
- Arbeitswelt (1)
- Arbeitszufriedenheit (1)
- BLAST algorithm (1)
- Bacterial genomics (1)
- Bankruptcy costs (1)
- Bat algorithm (1)
- Berufsleben (1)
- Berufsziel (1)
- Berufszufriedenheit (1)
- Betriebsorganisation (1)
- Biometrie (1)
- Business Plan (1)
- Business model (1)
- CI/CD (1)
- COBIT (1)
- CRM in Hochschulen (1)
- Checkliste (1)
- Code quality (1)
- Complex Event Processing (CEP) (1)
- Complex event processing (1)
- Compliance (1)
- Consumerization (1)
- Context-aware recommender systems (1)
- Continuous Delivery (1)
- Cross-holdings (1)
- Crowdsourcing (1)
- Customer channel (1)
- Cyber Insurance (1)
- Cyber Risks (1)
- Cyber-Versicherung (1)
- Damage claims (1)
- Datenstrom (1)
- Delphi (1)
- Delphi method characteristics (1)
- Delphi method variants (1)
- Depression (1)
- Design Thinking (1)
- DevOps (1)
- Dienstgüte (1)
- Distributed file systems (1)
- Dyadisches Gitter (1)
- Dünnes Gitter (1)
- E-Health (1)
- E-Learning (1)
- Echtzeitsimulation (1)
- Eindringerkennung (1)
- Eingebettetes System (1)
- Einzelfertigung (1)
- Endredaktion (1)
- Entrepreneurship (1)
- Event Admin (EA) (1)
- Event monitoring (1)
- Explainability (1)
- Fault tolerance (1)
- Fehlerverhütung (1)
- Financial contagion (1)
- Financial network (1)
- Finanzplanung (1)
- Fire sales (1)
- Frauenquote (1)
- Gender Mainstreaming (1)
- Genomic databases (1)
- Geschäftsmodell (1)
- Gesichtserkennung (1)
- Gleichberechtigung (1)
- Graph embeddings (1)
- Gute Arbeit (1)
- Hausarzt (1)
- Hochschullehre (1)
- IDS (1)
- ISO 27 K (1)
- ISO 27000 (1)
- ISO 27001 (1)
- ISO 27002 (1)
- ISO/IEC 27000 (1)
- IT Risk (1)
- IT Risk Management (1)
- IT Security Risk (1)
- Idiosyncratic Risk (1)
- Indicator Measurement (1)
- Information systems research (1)
- Instrument (1)
- Insurance (1)
- Internationalisierung (1)
- Kardiovaskuläre Krankheit (1)
- Knowledge graphs (1)
- Kontextfaktor (1)
- Kontinuierliche Integration (1)
- Kreatives Denken (1)
- Kreativität (1)
- Künstliche Intelligenz (1)
- LightSabre (1)
- Liquidität (1)
- Liquiditätsplan (1)
- Liquiditätsplanung (1)
- Location-based systems (1)
- Lymphknoten (1)
- MANET (1)
- Machine-to-Machine-Kommunikation (1)
- Magnetometer (1)
- Management (1)
- MapReduce algorithm (1)
- Maps (1)
- Metagenomics (1)
- Metakognitive Therapie (1)
- Mobile Applications (1)
- Mobile Device (1)
- Music recommender (1)
- Musik (1)
- Neuronales Netz (1)
- NoSQL databases. (1)
- Notfallmedizin (1)
- OECD datasets (1)
- Offenes Kommunikationssystem (1)
- Online services (1)
- Online-Dienst (1)
- Online-Portal (1)
- Ontologies (1)
- Open Source (1)
- Open systems (1)
- Optimalliquidität (1)
- PC-gestützt (1)
- Plan (1)
- Problemlösen (1)
- Prostatakrebs (1)
- Prüfungsangst (1)
- Psychische Gesundheit (1)
- Psychokardiologie (1)
- Psychologie (1)
- Quality of Service (QoS) (1)
- Quality perception (1)
- Qualität (1)
- Quellcode (1)
- Quotierung (1)
- Rationalität (1)
- Real-time simulation (1)
- Recommender systems (1)
- Remote work (1)
- Rendering (1)
- Rendering (computer graphics) (1)
- Risiko (1)
- Rule learning (1)
- SEM (1)
- SIEM (1)
- SOAP (1)
- SPION (1)
- Schadensersatzanspruch (1)
- Semantic Web (1)
- Semi-structured interviews (1)
- Sensor (1)
- Sensorsystem (1)
- Sentinel-Lymphknoten (1)
- Sequence alignment (1)
- Service Lifecycle (1)
- Service Management (1)
- Service Monitoring (1)
- Service Registry (1)
- Service Repository (1)
- Service Semantics (1)
- Service-orientation (1)
- Simulation (1)
- Smartphone (1)
- Soft Skills (1)
- Software Engineering (1)
- Software development (1)
- Soll-Ist-Vergleich (1)
- Sonnenfinsternis (1)
- Source code properties (1)
- Spheres (1)
- Standortbezogener Dienst (1)
- Strategie (1)
- Streaming <Kommunikationstechnik> (1)
- Strukturgleichungsmodell (1)
- Studienarbeit (1)
- Studiengangfinder (1)
- Swarm algorithm (1)
- Systematic Risk (1)
- Systemic risk (1)
- Taxonomy (1)
- Technology acceptance (1)
- Unternehmen (1)
- Unternehmensgründung (1)
- Versicherungsbetrieb (1)
- Verwaltung (1)
- Virtual reality (1)
- WS-Security (1)
- Web service (1)
- Web services (1)
- Web-Portal (1)
- Wirtschaftsinformatik (1)
- Wissensgraph (1)
- Work quality (1)
- Workload (1)
- XML-Model (1)
- XML-Schema (1)
- Zentriertes Interview (1)
- Zufriedenheit (1)
- ad-hoc networks (1)
- adaptive methods (1)
- agents (1)
- anaphylaxis (1)
- anxiety (1)
- architecture (1)
- asynchronous messaging (1)
- build automation (1)
- build server (1)
- cardiovascular disease (1)
- cashing (1)
- cloud computing (1)
- clustering on countries (1)
- collaborative coordination (1)
- complex event processing (CEP) (1)
- creativity (1)
- data protection (1)
- data stream learning (1)
- depression (1)
- digital intervention (1)
- distributed environments (1)
- distributed evacuation coordination (1)
- dyadic grid (1)
- e-learning (1)
- educational virtual realities (1)
- eigenface (1)
- emergency medicine (1)
- enterprise apps (1)
- evacuation guidance (1)
- evaluation (1)
- event models (1)
- events (1)
- examination (1)
- face recognition (1)
- fear (1)
- financial planning (1)
- forecasting models on countries (1)
- head-mounted display (1)
- health care (1)
- immersive media (1)
- kreativität (1)
- large scale systems (1)
- load balancing (1)
- lymphadenectomy (1)
- machine learning (1)
- machine-to-machine communication (1)
- magnetometer (1)
- market-based coordination (1)
- mental health (1)
- metacognitive therapy (1)
- multi-dimensional data (1)
- multiagent systems (1)
- ontology (1)
- patients (1)
- presence experience (1)
- privacy (1)
- prostate cancer (1)
- psychocardiology (1)
- rationalität (1)
- real-time routing (1)
- reliable message delivery (1)
- rollierend (1)
- security (1)
- semantic web application (1)
- sentinel lymph node dissection (1)
- shopping cart system (1)
- simulation training (1)
- situation aware routing (1)
- smart cities (1)
- smartphone (1)
- solid waste management (1)
- sparse grid (1)
- student project (1)
- superparamagnetic iron oxide nanoparticles (1)
- teaching entrepreneurship (1)
- training effectiveness (1)
- underprivileged adolescents (1)
- user training (1)
- vermeidbare Fehler (1)
- virtual emergency scenario (1)
- virtual patient simulation (1)
- virtual reality (1)
- web services (1)
- Übung (1)
Institute
- Fakultät IV - Wirtschaft und Informatik (54) (remove)
Objective: The study’s objective was to assess factors contributing to the use of smart devices by general practitioners (GPs) and patients in the health domain, while specifically addressing the situation in Germany, and to determine whether, and if so, how both groups differ in their perceptions of these technologies.
Methods: GPs and patients of resident practices in the Hannover region, Germany, were surveyed between April and June 2014. A total of 412 GPs in this region were invited by email to participate via an electronic survey, with 50 GPs actually doing so (response rate 12.1%). For surveying the patients, eight regional resident practices were visited by study personnel (once each). Every second patient arriving there (inclusion criteria: of age, fluent in German) was asked to take part (paper-based questionnaire). One hundred and seventy patients participated; 15 patients who did not give consent were excluded.
Results: The majority of the participating patients (68.2%, 116/170) and GPs (76%, 38/50) owned mobile devices. Of the patients, 49.9% (57/116) already made health-related use of mobile devices; 95% (36/38) of the participating GPs used them in a professional context. For patients, age (P<0.001) and education (P<0.001) were significant factors, but not gender (P>0.99). For doctors, neither age (P¼0.73), professional experience (P>0.99) nor gender (P¼0.19) influenced usage rates. For patients, the primary use case was obtaining health (service)-related information. For GPs, interprofessional communication and retrieving information were in the foreground. There was little app-related interaction between both groups.
Conclusions: GPs and patients use smart mobile devices to serve their specific interests. However, the full potentials of mobile technologies for health purposes are not yet being taken advantage of. Doctors as well as other care providers and the patients should work together on exploring and realising the potential benefits of the technology.
Decision support systems for traffic management systems have to cope with a high volume of events continuously generated by sensors. Conventional software architectures do not explicitly target the efficient processing of continuous event streams. Recently, event-driven architectures (EDA) have been proposed as a new paradigm for event-based applications. In this paper we propose a reference architecture for event-driven traffic management systems, which enables the analysis and processing of complex event streams in real-time and is therefore well-suited for decision support in sensor-based traffic control sys- tems. We will illustrate our approach in the domain of road traffic management. In particular, we will report on the redesign of an intelligent transportation management system (ITMS) prototype for the high-capacity road network in Bilbao, Spain.
Heterogeneity has to be taken into account when integrating a set of existing information sources into a distributed information system that are nowadays often based on Service- Oriented Architectures (SOA). This is also particularly applicable to distributed services such as event monitoring, which are useful in the context of Event Driven Architectures (EDA) and Complex Event Processing (CEP). Web services deal with this heterogeneity at a technical level, also providing little support for event processing. Our central thesis is that such a fully generic solution cannot provide complete support for event monitoring; instead, source specific semantics such as certain event types or support for certain event monitoring techniques have to be taken into account. Our core result is the design of a configurable event monitoring (Web) service that allows us to trade genericity for the exploitation of source specific characteristics. It thus delivers results for the areas of SOA, Web services, CEP and EDA.
This article discusses event monitoring options for heterogeneous event sources as they are given in nowadays heterogeneous distributed information systems. It follows the central assumption, that a fully generic event monitoring solution cannot provide complete support for event monitoring; instead, event source specific semantics such as certain event types or support for certain event monitoring techniques have to be taken into account. Following from this, the core result of the work presented here is the extension of a configurable event monitoring (Web) service for a variety of event sources. A service approach allows us to trade genericity for the exploitation of source specific characteristics. It thus delivers results for the areas of SOA, Web services, CEP and EDA.
Mobile crowdsourcing refers to systems where the completion of tasks necessarily requires physical movement of crowdworkers in an on-demand workforce. Evidence suggests that in such systems, tasks often get assigned to crowdworkers who struggle to complete those tasks successfully, resulting in high failure rates and low service quality. A promising solution to ensure higher quality of service is to continuously adapt the assignment and respond to failure-causing events by transferring tasks to better-suited workers who use different routes or vehicles. However, implementing task transfers in mobile crowdsourcing is difficult because workers are autonomous and may reject transfer requests. Moreover, task outcomes are uncertain and need to be predicted. In this paper, we propose different mechanisms to achieve outcome prediction and task coordination in mobile crowdsourcing. First, we analyze different data stream learning approaches for the prediction of task outcomes. Second, based on the suggested prediction model, we propose and evaluate two different approaches for task coordination with different degrees of autonomy: an opportunistic approach for crowdshipping with collaborative, but non-autonomous workers, and a market-based model with autonomous workers for crowdsensing.
In service-oriented architectures the management of services is a crucial task during all stages of IT operations. Based on a case study performed for a group of finance companies the different aspects of service management are presented. First, the paper discusses how services must be described for management purposes. In particular, a special emphasis is placed on the integration of legacy/non web services. Secondly, the service lifecycle that underlies service management is presented. Especially, the relation to SOA governance and an appropriate tool support by registry repositories is outlined.
End users urgently request using mobile devices at their workplace. They know these devices from their private life and appreciate functionality and usability, and want to benefit from these advantages at work as well. Limitations and restrictions would not be accepted by them. On the contrary, companies are obliged to employ substantial organizational and technical measures to ensure data security and compliance when allowing to use mobile devices at the workplace. So far, only individual arrangements have been presented addressing single issues in ensuring data security and compliance. However, companies need to follow a comprehensive set of measures addressing all relevant aspects of data security and compliance in order to play it safe. Thus, in this paper at first technical architectures for using mobile devices in enterprise IT are reviewed. Thereafter a set of compliance rules is presented and, as major contribution, technical measures are explained that enable a company to integrate mobile devices into enterprise IT while still complying with these rules comprehensively. Depending on the company context, one or more of the technical architectures have to be chosen impacting the specific technical measures for compliance as elaborated in this paper. Altogether this paper, for the first time, correlates technical architectures for using mobile devices at the workplace with technical measures to assure data security and compliance according to a comprehensive set of rules.
Eine Unternehmensgründung ist ein komplexes Vorhaben, dessen Risiken soweit wie möglich vermieden bzw. minimiert werden sollten. Dabei hilft eine sorgfältige Planung und Vorbereitung. Der Gründungsprozess lässt sich — von der Prüfung der Grundvoraussetzungen über den Business Plan, die Vorbereitung der Gründung sowie deren Realisierung bis zur Stabilisierung des Unternehmens — in fünf Phasen einteilen.
Durch die Covid-19-Pandemie und die damit einhergehenden Effekte auf die Arbeitswelt ist die Belastung der Mitarbeitenden in einen stärkeren Fokus gerückt worden. Dieser Umstand trifft unter anderem durch den umfassenden Wechsel in die Remote Work auch auf agile Software-Entwicklungsteams in vielen Unternehmen zu. Eine zu hohe Arbeitsbelastung kann zu diversen negativen Effekten, wie einem erhöhten Krankenstand, mangelndem Wohlbefinden der Mitarbeitenden oder reduzierter Produktivität führen. Es ist zudem bekannt, dass sich die Arbeitsbelastung in der Wissensarbeit auf die Qualität der Arbeitsergebnisse auswirkt. Dieser Forschungsbeitrag identifiziert potenzielle Faktoren der Arbeitsbelastung der Mitglieder eines agilen Software-Entwicklungsteams bei der Otto GmbH & Co KG. Auf der Grundlage der Faktoren präsentieren wir Maßnahmen zur Reduzierung von Arbeitsbelastung und erläutern unsere Erkenntnisse, die wir im Rahmen eines Experiments validiert haben. Unsere Ergebnisse zeigen, dass bereits kleinteilige Maßnahmen, wie das Einführen von Ruhearbeitsphasen während des Arbeitstages, zu positiven Effekten bspw. hinsichtlich einer gesteigerten Konzentrationsfähigkeit führen und wie sich diese auf die Qualität der Arbeitsergebnisse auswirken.
There are many aspects of code quality, some of which are difficult to capture or to measure. Despite the importance of software quality, there is a lack of commonly accepted measures or indicators for code quality that can be linked to quality attributes. We investigate software developers’ perceptions of source code quality and the practices they recommend to achieve these qualities. We analyze data from semi-structured interviews with 34 professional software developers, programming teachers and students from Europe and the U.S. For the interviews, participants were asked to bring code examples to exemplify what they consider good and bad code, respectively. Readability and structure were used most commonly as defining properties for quality code. Together with documentation, they were also suggested as the most common target properties for quality improvement. When discussing actual code, developers focused on structure, comprehensibility and readability as quality properties. When analyzing relationships between properties, the most commonly talked about target property was comprehensibility. Documentation, structure and readability were named most frequently as source properties to achieve good comprehensibility. Some of the most important source code properties contributing to code quality as perceived by developers lack clear definitions and are difficult to capture. More research is therefore necessary to measure the structure, comprehensibility and readability of code in ways that matter for developers and to relate these measures of code structure, comprehensibility and readability to common software quality attributes.