Informatik
Refine
Document Type
- Conference proceeding (496)
- Journal article (186)
- Book chapter (48)
- Doctoral Thesis (10)
- Book (3)
- Report (1)
- Working Paper (1)
Has full text
- yes (745) (remove)
Is part of the Bibliography
- yes (745)
Institute
- Informatik (745)
- Technik (2)
Publisher
- Springer (131)
- Hochschule Reutlingen (95)
- IEEE (88)
- Gesellschaft für Informatik (57)
- Elsevier (41)
- ACM (33)
- IARIA (26)
- Springer Gabler (13)
- De Gruyter (11)
- MDPI (10)
Context: Organizations are increasingly challenged by high market dynamics, rapidly evolving technologies and shifting user expectations. In consequence, many organizations are struggling with their ability to provide reliable product roadmaps by applying traditional roadmapping approaches. Currently, many companies are seeking opportunities to improve their product roadmapping practices and strive for new roadmapping approaches. A typical first step towards advancing the roadmapping capabilities of an organization is to assess the current situation. Therefore, the so-called maturity model DEEP for assessing the product roadmapping capabilities of companies operating in dynamic and uncertain environments has been developed and published by the authors.
Objective: The aim of this article is to conduct an initial validation of the DEEP model in order to understand its applicability better and to see if important concepts are missing. In addition, the aim of this article is to evolve the model based on the findings from the initial validation.
Method: The model has been given to practitioners such as product managers with the request to perform a self-assessment of the current product roadmapping practices in their company. Afterwards, interviews with each participant have been conducted in order to gain insights.
Results: The initial validation revealed that some of the stages of the model need to be rearranged and minor usability issues were found. The overall structure of the model was well received. The study resulted in the development of the version 1.1 of the DEEP product roadmap maturity model which is also presented in this article.
Through increasing market dynamics, rapidly evolving technologies and shifting user expectations coupled with the adoption of lean and agile practices, companies are struggling with their ability to provide reliable product roadmaps by applying traditional approaches. Currently, most companies are seeking opportunities to improve their product roadmapping practices. As a first challenge they have to assess their current product roadmapping capabilities in order to better understand how to improve their practices and how to switch to a new approach. The aim of this article is to provide an initial maturity model for product roadmapping practices that is especially suited for assessing the roadmapping capabilities of companies operating in dynamic and uncertain market environments. Based on interviews with 15 experts from 13 various companies the current state of practice regarding product roadmapping was identified. Afterwards, the model development was conducted in the context of expert workshops with the Robert Bosch GmbH and researchers. The study results in the so-called DEEP 1.0 product roadmap maturity model which allows companies to conduct a self assessment of their product roadmapping practice.
Context: Organizations are increasingly challenged by dynamic and technical market environments. Traditional product roadmapping practices such as detailed and fixed long-term planning typically fail in such environments. Therefore, companies are actively seeking ways to improve their product roadmapping approach. Goal: This paper aims at identifying problems and challenges with respect to product roadmapping. In addition, it aims at understanding how companies succeed in improving their roadmapping practices in their respective company contexts. The study focuses on mid-sized and large companies developing software-intensive products in dynamic and technical market environments. Method: We conducted semi structured expert interviews with 15 experts from 13 German companies and conducted a thematic data analysis. Results: The analysis showed that a significant number of companies is still struggling with traditional feature based product-roadmapping and opinion based prioritization of features. The most promising areas for improvement are stating the outcomes a company is trying to achieve and making them part of the roadmap, sharing or co-developing the roadmap with stakeholders, and the establishing discovery activities.
Context: Companies in highly dynamic markets increasingly struggle with their ability to plan product development and to create reliable roadmaps. A main reason is the decreasing lack of predictability of markets, technologies, and customer behaviors. New approaches for product roadmapping seem to be necessary in order to cope with today's highly dynamic conditions. Little research is available with respect to such new approaches. Objective: In order to better understand the state of the art and to identify research gaps, this article presents a review of the scientific literature with respect to product roadmapping. Method: We performed a systematic literature review (SLR) with respect to identify papers in the field of computer science. Results: After filtering, the search resulted in a set of 23 relevant papers. The identified papers focus on different aspects such as roadmap types, processes for creating and updating roadmaps, problems and challenges with roadmapping, approaches to visualize roadmaps, generic frameworks and specific aspects such as the combination of roadmaps with business modeling. Overall, the scientific literature covers many important aspects of roadmapping but does provide only little knowledge on how to create product roadmaps under highly dynamic conditions. Research gaps address, for instance, the inclusion of goals or outcomes into product roadmaps, the alignment of a roadmap with a product vision, and the inclusion of product discovery activities in product roadmaps. In addition, the transformation from traditional roadmapping processes to new ways of roadmapping is not sufficiently addressed in the scientific literature.
Software process improvement (SPI) is around for decades, but it is a critically discussed topic. In several waves, different aspects of SPI have been discussed in the past, e.g., large scale company-level SPI programs, maturity models, success factors, and in-project SPI. It is hard to find new streams or a consensus in the community, but there is a trend coming along with agile and lean software development. Apparently, practitioners reject extensive and prescriptive maturity models and move towards smaller, faster and continuous project-integrated SPI. Based on data from two survey studies conducted in Germany (2012) and Europe (2016), we analyze the process customization for projects and practices for implementing SPI in the participating companies. Our findings indicate that, even in regulated industry sectors, companies increasingly adopt in-project SPI activities, primarily with the goal to continuously optimize specific processes. Therefore, with this paper, we want to stimulate a discussion on how to evolve traditional SPI towards a continuous learning environment.
The emergence of agile methods and practices has not only changed the development processes but might also have affected how companies conduct software process improvement (SPI). Through a set of complementary studies, we aim to understand how SPI has changed in times of agile software development. Specifically, we aim (a) to identify and characterize the set of publications that connect elements of agility to SPI, (b) to explore to which extent agile methods/practices have been used in the context of SPI, and (c) to understand whether the topics addressed in the literature are relevant and useful for industry professionals. To study these questions, we conducted an in-depth analysis of the literature identified in a previous mapping study, an interview study, and an analysis of the responses given by industry professionals to SPI related questions stemming from an independently conducted survey study. Regarding the first question, we identified 55 publications that focus on both SPI and agility of which 48 present and discuss how agile methods/practices are used to steer SPI initiatives. Regarding the second question, we found that the two most frequently mentioned agile methods in the context of SPI are Scrum and Extreme Programming (XP), while the most frequently mentioned agile practices are integrate often, test-first, daily meeting, pair programming, retrospective, on-site customer, and product backlog. Regarding the third question, we found that a majority of the interviewed and surveyed industry professionals see SPI as a continuous activity. They agree with the agile SPI literature that agile methods/practices play an important role in SPI activities but that the importance given to specific agile methods/practices does not always coincide with the frequency with which these methods/practices are mentioned in the literature.
Im Rahmen dieser Arbeit wurde eine Software-Architektur entwickelt, mit der sich Interaktionen zwischen autonomen Fahrzeugen und Passanten im Straßenverkehr in einer simulierten Umgebung untersuchen lassen. Hierbei wird das autonome Fahrzeug durch einen externen Fahrsimulator gesteuert. Der Einsatz eines Motion-Capture-Systems ermöglicht dabei die Aufzeichnung und Übertragungen der Bewegungsdaten von Passant und Fahrer in die virtuelle Umgebung. Durch den Einsatz von head-mounted Displays sollen Akteure die virtuelle Umgebung möglichst als real empfinden. Auf Basis der entwickelten Software-Architektur wurde eine Simulationsumgebung realisiert, in der Interaktionen zwischen einem Passant und einem autonomem Fahrzeug untersucht werden können. Das Projekt soll das Potential von Motion-Capture gestützten Simulationsumgebungen für die Konzeption und Entwicklung von autonomen Fahrsystemen aufzeigen.
Über die letzten Jahre nehmen die Verkehrsunfälle zwischen Fahrzeugen und Fahrrädern und Motorrädern immer weiter zu. Die Ursache ist meistens eine unachtsam geöffnete Fahrzeugtür, mit der ein anfahrender Zweiradfahrer kollidiert. Diese Unfälle können verheerende Folgen für alle Beteiligten haben. Aus diesem Grund soll der technologische Fortschritt, welcher sich durch die gesamte Automobilbranche zieht, um eine zusätzliche Komponente erweitert werden. Hierbei handelt es sich um ein System für Zweiradfahrer, welches eine sich öffnende Fahrzeugtür frühzeitig erkennen soll, den Fahrer somit frühzeitig warnen kann und gegebenenfalls Strategien zu Unfallvermeidung einleiten kann. Dieses Konzept soll die Entwicklung des Systems vorgeben und grundlegend erläutern.
Digitalization of products and services commonly causes substantial changes in business models, operations, organization structures and IT infrastructures of enterprises. Motivated by experiences and observations from digitalization projects, the paper investigates the effects of digitalization on enterprise architectures (EA). EA models serve as representation of business, information system and technical aspects of an enterprise to support management and development. By comparing EA models before and after digitalization, the paper analyzes the kinds of changes visible in the EA model. The most important finding is that newly created digitized products and the associated (product)- and enterprise architecture are no longer properly integrated into the overall architecture and even exist in parallel. Thus, the focus of this work is on showing these parallel architectures and proposing derivations for a better integration.
Die Navigation mit dem E-Bike soll eine positive Nutzerfahrung sein. Deshalb wurde im Zuge dieser Arbeit im Rahmen von Bosch E-Bike Systems ein multimodales smart User Interface (MSUI) entwickelt. Das Konzept umfasst visuelle Turn-by-Turn Signale, taktile Vibrationssignale im Lenker und eine auditive Sprachausgabe. Ziel der Arbeit ist ein Prototyp, der sich für die Evaluation von Nutzerbedürfnissen in Bezug auf verschiedene multimodale Rückmeldemöglichkeiten eignet.