Refine
Document Type
- Journal article (992)
- Conference proceeding (904)
- Book chapter (222)
- Working Paper (35)
- Book (30)
- Doctoral Thesis (24)
- Report (23)
- Issue of a journal (17)
- Review (6)
- Anthology (2)
Has full text
- yes (2257) (remove)
Is part of the Bibliography
- yes (2257)
Institute
- Informatik (747)
- ESB Business School (698)
- Technik (373)
- Life Sciences (274)
- Texoversum (137)
- Zentrale Einrichtungen (14)
Publisher
- Springer (367)
- IEEE (251)
- Elsevier (189)
- Hochschule Reutlingen (176)
- MDPI (99)
- Gesellschaft für Informatik e.V (66)
- Wiley (62)
- De Gruyter (51)
- Association for Computing Machinery (45)
- IARIA (26)
The blockchain technology enables a common data basis between the participants. Entries are logged and the authenticity of the participants is guaranteed. In the case of a relationship between customers and producers, this would lead to verifiable cooperation, which would be a major step as companies enter into service contracts based on the flow of many small transactions through communication. This paper proposes an architecture that enables the creation and processing of orders between the customer and producers via a blockchain based production network. The handling of larger files which are traceable via the blockchain is also shown and the use of a public or permissioned blockchain for an application case is also considered.
Der Einsatz von Data Science in der Produktion ermöglicht eine neue Art der Optimierung von Prozessen und Systemen. Die Bedeutung der datengetriebenen Produktionsoptimierung wächst zunehmend im produzierenden Gewerbe. Im Gegensatz zu konventionellen Ansätzen, wie z. B. die des Lean Managements, basiert dieser anhaltende Trend auf der steigenden Verfügbarkeit von Daten im Zuge der digitalen Transformation. Vor allem kleine und mittlere Unternehmen stehen vor der Herausforderung abzuwägen, welche Maßnahmen hierfür ergriffen werden sollten und welche Nutzenpotenziale sich daraus ergeben. Diese Arbeit stellt einen strukturierten Leitfaden zur Vorgehensweise bei Datenanalyseprojekten bezogen auf einen spezifischen Anwendungsfall im Kontext einer frühen Fehlerdetektion und -prävention dar.
The halo effect in sports
(2018)
A halo effect can lead to significantly biased and distorted judgments in numerous situations and settings in daily life. However, its impact has barely been researched in the sporting environment, although it might help a great deal in understanding how sport fans think and behave. This paper provides an international literature review on the halo effect in different research fields. Built upon this state of the art, an empirical study based on two German soccer clubs, VfB Stuttgart and FC Bayern Munich, analyzes the presence of halo effects explained by social identity theory. The study shows that supporters rate aspects of the respective team, for example the president’s competency, more favorable than common sport spectators, and this effect even increases with a higher level of team identification.
Lessons from sports : what corporate managers can learn from international professional sports
(2018)
Although sports is generally defined as motor activity, it has always been much more than that. Since management and sports follow the same objective of achieving highest performance, correlations between these two fields nowadays become increasingly interesting in terms of corporate strategy. This paper aims to point out how organisations as well as individuals can benefit from the general and psychological values and strategies of international professional sports, by first looking at the general framework of professional sports and further applying approaches from various types of sports directly to certain business functions like general management, human resource management and marketing management.
An assessment model to foster the adoption of agile software product lines in the automotive domain
(2018)
A software product line is commonly used for the software development in large automotive organizations. A strategic reuse of software is needed to handle the increasing complexity of the development and to maintain the quality of numerous software variants. However, the development process needs to be continuously adapted at a fast pace to satisfy the changing market demands. Introducing agile software development methods promise the flexibility to react on customers’ change requests and market demands to deliver high quality software. Despite this need, it is still challenging to combine agile software development and product lines. The maturity of an agile adoption is often hard to determine. Assessing the current situation regarding the combination is a first step towards a successful inclusion of agile methods into automotive software product lines. Based on an interview study with 16 participants and a literature review, we build the so-called ASPLA Model allowing self-assessments within the team to determine the current state of agile software development in combination with software product lines. The model comprises seven areas of improvement and recommends a possibility to improve the current status.
Software engineering courses have to deliver theoretical and technical knowledge and skills while establishing links to practice. However, due to course goals or resource limitations, it is not always possible or even meaningful to set up complete projects and let students work on a real piece of software. For instance, if students shall understand the impact of group dynamics on productivity, a particular software to be developed is of less interest than an environment in which students can learn about team-related phenomena. To address this issue, we use experimentation as a teaching tool in software engineering courses. Experiments help to precisely characterize and study a problem in a systematic way, to observe phenomena, and to develop and evaluate solutions. Furthermore, experiments help establishing short feedback and learning cycles, and they also allow for experiencing risk and failure scenarios in a controlled environment. In this paper, we report on three courses in which we implemented different experiments and we share our experiences and lessons learned. Using these courses, we demonstrate how to use classroom experiments, and we provide a discussion on the feasibility based on formal and informal course evaluations. This experience report thus aims to help teachers integrating small- and medium sized experiments in their courses.
The need for creating digitally enhanced products, services, and experiences as well as the emergence of new or modified business models has a significant impact on the automotive domain. Innovative solutions and new topics such as Smart Mobility or Connectivity require current automotive development processes to undergo major changes. They need to be redesigned in a way that it is possible to learn and adapt continuously at a fast pace. Agile methods are promising approaches to address these new challenges. However, agile methods are not tailored to the specific characteristics of the automotive domain such as software product line (SPLs) development. Although, there have been efforts to apply agile methods in the automotive domain, widespread adoptions have not yet taken place.
Software engineering education is supposed to provide students with industry-relevant knowledge and skills. Educators must address issues beyond exercises and theories that can be directly rehearsed in small settings. A way to experience such effects and to increase the relevance of software engineering education is to apply empirical studies in teaching. In our article, we show how different types of empirical studies can be used for educational purposes in software engineering. We give examples illustrating how to utilize empirical studies, discuss challenges, and derive an initial guideline that supports teachers to include empirical studies in software engineering courses.
Software and system development faces numerous challenges of rapidly changing markets. To address such challenges, companies and projects design and adopt specific development approaches by combining well-structured methods and flexible agile practices. Yet, the number of methods and practices is large and the actual process composition is often carried out in an ad-hoc manner. This paper reports on a survey on hybrid software development approaches. We study which approaches are used in practice, how different approaches are combined, and what contextual factors influence the use and combination of hybrid software development approaches.
Back to the future: origins and directions of the “Agile Manifesto” – views of the originators
(2018)
In 2001, seventeen professionals set up the manifesto for agile software development. They wanted to define values and basic principles for better software development. On top of brought into focus, the manifesto has been widely adopted by developers, in software-developing organizations and outside the world of IT. Agile principles and their implementation in practice have paved the way for radical new and innovative ways of software and product development. In parallel, the understanding of the manifesto’s underlying principles evolved over time. This, in turn, may affect current and future applications of agile principles. This article presents results from a survey and an interview study in collaboration with the original contributors of the manifesto for agile software development. Furthermore, it comprises the results from a workshop with one of the original authors. This publication focuses on the origins of the manifesto, the contributors’ views from today’s perspective, and their outlook on future directions. We evaluated 11 responses from the survey and 14 interviews to understand the viewpoint of the contributors. They emphasize that agile methods need to be carefully selected and agile should not be seen as a silver bullet. They underline the importance of considering the variety of different practices and methods that had an influence on the manifesto. Furthermore, they mention that people should question their current understanding of "agile" and recommend reconsidering the core ideas of the manifesto.