Decision knowledge triggers in continuous software engineering

Decision knowledge encompasses decisions and related information such as the problems the decisions address, their rationale, or alternatives. The management of decision knowledge is considered important for software development, however, it is often not integrated, since it requires additional effo...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:2018 IEEE ACM 4th International Workshop on Rapid Continuous Software Engineering (RCoSE) S. 23 - 26
Hauptverfasser: Kleebaum, Anja, Johanssen, Jan Ole, Paech, Barbara, Alkadhi, Rana, Bruegge, Bernd
Format: Tagungsbericht
Sprache:Englisch
Veröffentlicht: New York, NY, USA ACM 29.05.2018
Schriftenreihe:ACM Conferences
Schlagworte:
Conferences
Continuous Software Engineering
Data integrity
Decision Knowledge
Informatics
Knowledge engineering
Knowledge Management
Rationale
Software
Software and its engineering > Software creation and management > Software development process management > Software development methods > Agile software development
Software and its engineering > Software creation and management > Software post-development issues > Documentation
Software and its engineering > Software creation and management > Software post-development issues > Maintaining software
Software and its engineering > Software creation and management > Software post-development issues > Software evolution
Software engineering
Software Evolution
Task analysis
Trigger
decision knowledge
trigger
knowledge management
continuous software engineering
rationale
software evolution
ISBN:9781450357456, 1450357458
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:Decision knowledge encompasses decisions and related information such as the problems the decisions address, their rationale, or alternatives. The management of decision knowledge is considered important for software development, however, it is often not integrated, since it requires additional effort and developers do not perceive short-term benefits. Continuous software engineering offers new possibilities to overcome these drawbacks: During continuous software engineering, developers perform practices suitable to integrate the management of decision knowledge in their daily work. For example, developers regularly commit code and manage tasks to implement features. In this paper, we present ideas on how to trigger the developers to capture and use decision knowledge during these practices, in particular to 1) package distributed decision knowledge, 2) make tacit decisions explicit, and 3) consider consistency between decisions.
ISBN:9781450357456
1450357458
DOI:10.1145/3194760.3194765