2012
DOI: 10.7494/csci.2012.13.4.165
|View full text |Cite
|
Sign up to set email alerts
|

Assessment of Risks Introduced to Safety Critical Software by Agile Practices — A Software Engineer’s Perspective

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2016
2016
2020
2020

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(2 citation statements)
references
References 19 publications
0
1
0
Order By: Relevance
“…A growing body of evidence, including industrial reports, shows that obtaining the right balance is doable and profitable especially when the companies decide to employ competent experts to develop a custom made approach. Examples of such reports can be found in [2], [3], [4], [5] and were surveyed in [6]. What is more, in 2012 FDA (Food and Drug Administration) recognized the AAMI TIR45:2012 -Guidance on the use of AG-ILE practices in the development of medical device software [7].…”
mentioning
confidence: 99%
“…A growing body of evidence, including industrial reports, shows that obtaining the right balance is doable and profitable especially when the companies decide to employ competent experts to develop a custom made approach. Examples of such reports can be found in [2], [3], [4], [5] and were surveyed in [6]. What is more, in 2012 FDA (Food and Drug Administration) recognized the AAMI TIR45:2012 -Guidance on the use of AG-ILE practices in the development of medical device software [7].…”
mentioning
confidence: 99%
“…As a consequence, one problem is the inadequate quality of the requirements specifications for existing systems. Regarding the strong demand for increasing the efficiency of software development processes (in terms of effort, user satisfaction, and time) while still respecting the safety requirements imposed by relevant standards and regulations, Gorski and Lukasiewicz (2012) affirm that many companies have incorporated agile practices into safety-critical projects. However, for engineering safety when using agile methods, most researchers prefer combining agile methods with traditional development processes that rely on safety standards, like SafeScrum (STÅL-HANE et al, 2012), XP, andIEC 61508 (THORSEN, 2002), and not much emphasis is given to addressing or considering safety aspects throughout the development process.…”
Section: Related Workmentioning
confidence: 99%