Refine
Year of publication
- 2018 (47) (remove)
Document Type
- Book chapter (23)
- Journal article (11)
- Conference proceeding (10)
- Book (2)
- Anthology (1)
Is part of the Bibliography
- yes (47)
Institute
- Informatik (19)
- Texoversum (15)
- ESB Business School (8)
- Life Sciences (3)
- Technik (2)
Publisher
- Springer (47) (remove)
Rapid prototyping platforms reduce development time by allowing quick prototyping of a prototype idea and achieve more time for actual application development with user interfaces. This approach has long been followed in technical platforms, such as the Arduino. To transfer this form of prototyping to wearables, WearIT is presented in this paper.WearIT consists of four components as a wearable prototyping platform: (1) a vest, (2) sensor and actuator shields, (3) its own library and (4) a motherboard consisting of Arduino, Raspberry Pi, a board and a GPS module. As a result, a wearable prototype can be quickly developed by attaching sensor and actuator shields to the WearIT vest. These sensor and actuator shields can then be programmed through the WearIT library. Via Virtual Network Computing (VNC) with a remote computer, the screen contents of the Raspberry Pi can be accessed and the Arduino be programmed.
Context: Software product lines are widely used in automotive embedded software development. This software paradigm improves the quality of software variants by reuse. The combination of agile software development practices with software product lines promises a faster delivery of high quality software. However, the set up of an agile software product line is still challenging, especially in the automotive domain. Goal: This publication aims to evaluate to what extend agility fits to automotive product line engineering. Method: Based on previous work and two workshops, agility is mapped to software product line concerns. Results: This publication presents important principles of software product lines, and examines how agile approaches fit to those principles. Additionally, the principles are related to one of the four major concerns of software product line engineering: Business, Architecture, Process, and Organization. Conclusion: Agile software product line engineering is promising and can add value to existing development approaches. The identified commonalities and hindering factors need to be considered when defining a combined agile product line engineering approach.
Unternehmen, die gesellschaftliche Verantwortung für die Auswirkungen ihrer Geschäftstätigkeit übernehmen, stehen vor der Herausforderung, CSR und Compliance systematisch und umfassend in ihr Unternehmen zu integrieren und kontinuierlich umzusetzen. Dieser Beitrag zeigt vor diesem Hintergrund auf, wie Unternehmen durch die Etablierung von Wertemanagementsystemen sowie PDCA-Zyklen (Plan-Do-Check-Act) CSR- und Compliancemanagementsysteme integrieren und umsetzen können. Des Weiteren werden Instrumente, die relevant für die Entwicklung, Implementierung und Umsetzung von effektiven und effizienten CSR- und Compliancemanagementsysteme sind, aufgelistet.
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.
The relative pros and cons of using students or practitioners in experiments in empirical software engineering have been discussed for a long time and continue to be an important topic. Following the recent publication of “Empirical software engineering experts on the use of students and professionals in experiments” by Falessi, Juristo, Wohlin, Turhan, Münch, Jedlitschka, and Oivo (EMSE, February 2018) we received a commentary by Sjøberg and Bergersen. Given that the topic is of great methodological interest to the community and requires nuanced treatment, we invited two editorial board members, Martin Shepperd and Per Runeson, respectively, to provide additional views.
Die hohen Schulden in einigen Staaten der Europäischen Wirtschafts- und Währungsunion lassen nach wie vor staatliche Insolvenzen befürchten. Um die bereits entstandenen Probleme zu bewältigen, aber auch damit eine solche Situation künftig gar nicht erst eintritt, ist eine staatliche Insolvenzordnung erforderlich.
Container virtualization evolved into a key technology for deployment automation in line with the DevOps paradigm. Whereas container management systems facilitate the deployment of cloud applications by employing container based artifacts, parts of the deployment logic have been applied before to build these artifacts. Current approaches do not integrate these two deployment phases in a comprehensive manner. Limited knowledge on application software and middleware encapsulated in container-based artifacts leads to maintainability and configuration issues. Besides, the deployment of cloud applications is based on custom orchestration solutions leading to lock in problems. In this paper, we propose a two-phase deployment method based on the TOSCA standard. We present integration concepts for TOSCA-based orchestration and deployment automation using container-based artifacts. Our two-phase deployment method enables capturing and aligning all the deployment logic related to a software release leading to better maintainability. Furthermore, we build a container management system, which is composed of a TOSCA-based orchestrator on Apache Mesos, to deploy container-based cloud applications automatically.
Die Einführung CSR- und wertebasierter Unternehmensziele und Managementmethoden wird von Führungskräften und Mitarbeitern häufig als Überforderung empfunden und löst Bedenken und teilweise Ängste aus. Diesem Phänomen kann alleine durch eine gelungene Schulung in den Theorien und Methoden entgegengetreten werden. Das hier vorgeschlagene Sechs-Schritte-Programm zur Schulung dieser Theorien und Methoden weckt das Bewusstsein für die Notwendigkeit eines Paradigmenwechsels und vermittelt den betroffenen Individuen die erforderlichen Kenntnisse und Werkzeuge, sich dieser Herausforderung zu stellen. In sechs Arbeitsschritten wird von der Phänomenologie der derzeitigen Unternehmenswelt über die theoretische Analyse der Situation bis hin zur Vorstellung geeigneter Tools und der möglichen Risiken ein Weg zur erfolgreichen Schulung gezeigt.
Unternehmertum ist ein integraler Bestandteil des Ernuerungsprozesses von Wirtschaft und Gesellschaft. Die Erneuerer sind nicht Politik oder Management, es sind einzelne Persönlichkeiten, die wagen, mit etwas zu beginnen, dessen Ausgang ungewiss ist, die ungebremst Kraft und Fähigkeiten einsetzen, mit der Folge, dass am Ende etwas Neues erschaffen worden ist. Wenn in wirtschaftlichen, kirchlichen, staatlichen, wissenschaftlichen und politischen Bereichen wirksam und innovativ gearbeitet wird, sind möglicherweise die gleichen personalen Talente und Gaben wirksam...Oft ist es eine Idee, ein motivierendes Bedürfnis, das sich Ausdruck verschafft in Handlungen, fast unabhängig von der Ausbildung oder einem begonnenen Studium. Man kann methodisches Know-how aufbauen, jedoch nicht Unternehmertum lernen.