2010 Agile Conference 2010
DOI: 10.1109/agile.2010.10
|View full text |Cite
|
Sign up to set email alerts
|

An Iterative Approach for Development of Safety-Critical Software and Safety Arguments

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
54
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 50 publications
(59 citation statements)
references
References 6 publications
0
54
0
Order By: Relevance
“…This examination revealed that none of the Scrum practices contradict regulatory requirements. To further reinforce the decision to adopt Scrum practices, the findings of the mapping study revealed that where agile practices have been adopted when developing medical device software, they have typically been Scrum practices [14][15][16][17][18].…”
Section: Identification Of Applicable Agile Practicesmentioning
confidence: 99%
“…This examination revealed that none of the Scrum practices contradict regulatory requirements. To further reinforce the decision to adopt Scrum practices, the findings of the mapping study revealed that where agile practices have been adopted when developing medical device software, they have typically been Scrum practices [14][15][16][17][18].…”
Section: Identification Of Applicable Agile Practicesmentioning
confidence: 99%
“…In [16] presented an approach on how incremental methods can be used in safety critical development. They claimed that agile methods can provide benefits, but the methods are not directly applicable in regulated areas.…”
Section: Adopting Agile Methods For Safety-critical Systemsmentioning
confidence: 99%
“…In another study Ge and et al, propose an iterative approach for developing safety-critical software [7]. First they address the notion of up-front design in safety critical software development, and describe the characteristics of an up-front design that is minimal from perspective of achieving safety objectives.…”
Section: Test Driven Developmentmentioning
confidence: 99%