| 1. |
- Gren, Lucas, 1984, et al.
(författare)
-
Agility is responsiveness to change: An essential definition
- 2020
-
Ingår i: 24th Conference on Evaluation and Assessment in Software Engineering (EASE2020). - New York, NY, USA : Association for Computing Machinery. - 2153-1633.
-
Konferensbidrag (refereegranskat)abstract
- There is some ambiguity of what agile means in both research and practice. Authors have suggested a diversity of different definitions, through which it is difficult to interpret what agile really is. The concept, however, exists in its implementation through agile practices. In this vision paper, we argue that adopting an agile approach boils down to being more responsive to change. To support this claim, we relate agile principles, practices, the agile manifesto, and our own experiences to this core definition. We envision that agile transformations would be, and are, much easier using this definition and contextualizing its implications.
|
|
| 2. |
- Lenberg, Per, 1976, et al.
(författare)
-
Behavioral Aspects of Safety-Critical Software Development
- 2020
-
Ingår i: Proceedings - 2020 IEEE/ACM 42nd International Conference on Software Engineering Workshops, ICSEW 2020. - New York, NY, USA : ACM. ; , s. 173-176
-
Konferensbidrag (refereegranskat)abstract
- We are becoming increasingly dependent on software systems also for highly critical tasks in society. To minimize the risk of failures, regulatory institutions define standards that software organizations must meet. However, the quality of the safety-critical software is, ultimately, determined by the software engineers' behavior. Even though previous studies have recognized the significance of such behavioral aspects, research that studies them is limited. The aim of this initial study was, therefore, to identify how and in what way, behavioral aspects affect the quality of safety-critical software. Thematic analysis of interviews with six software engineers identified four themes linking developer behavior to safety. Our analysis suggests that developing safety-critical systems imposes stress on software engineers and that to reduce such pressure it is critical to enhance organizational trust. It also indicates that the agile way-of-working has the potential to improve safety by facilitating the sharing of domain knowledge. Our findings provide directions for future studies into these important aspects and can be of wider relevance, in particular for the development of secure software, but potentially also for general software engineering.
|
|
