Software Development under Stringent Hardware Constraints: Do Agile Methods Have a Chance?

Ronkainen, Jussi; Abrahamsson, Pekka

doi:10.1007/3-540-44870-5_10

Cited by 50 publications

(35 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Ronkainen and Abrahamsson [27] identified four main characteristics that would affect adoption of agile methods under strict hardware constraints, typical of most embedded systems:…”

Section: Agile Development Of Embedded Softwarementioning

confidence: 99%

See 1 more Smart Citation

Industrial Challenges of Scaling Agile in Mass-Produced Embedded Systems

Eklund

Olsson

Strøm

2014

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

When individual teams in mechatronic organizations attempt to adopt agile software practices, these practices tend to only affect modules or sub-systems. The short iterations on team level do not lead to short lead-times in launching new or updated products since the overall R&D approach on an organization level is still governed by an overall stage gate or single cycle V-model. This paper identifies challenges for future research on how to combine the predictability and planning desired of mechanical manufacturing with the dynamic capabilities of modern agile software development. Scaling agile in this context requires an expansion in two dimensions: First, scaling the number of involved teams. Second, traversing necessary systems engineering activities in each sprint due to the co-dependency of software and hardware development.

show abstract

“…Ronkainen and Abrahamsson [27] identified four main characteristics that would affect adoption of agile methods under strict hardware constraints, typical of most embedded systems:…”

Section: Agile Development Of Embedded Softwarementioning

confidence: 99%

“…However, existing large-scale agile methodology frameworks such as these do not address the challenges particular to the embedded domain (identified by e.g. [27]), and especially not all system engineering challenges regarding large-scale manufacturing.…”

Section: Challenge Of Scaling the Number Of Involved Teamsmentioning

confidence: 99%

Industrial Challenges of Scaling Agile in Mass-Produced Embedded Systems

Eklund

Olsson

Strøm

2014

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…Similarly, issues with refactoring are highlighted, such as the potential to invalidate earlier certification (credit) [12], or to introduce timing issues [24]. A workable configuration management system combined with relentless testing can help.…”

Section: Some Issues Encounteredmentioning

confidence: 99%

Lean/Agile Software Development Methodologies in Regulated Environments – State of the Art

Cawley

Wang

Richardson

2010

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Choosing the appropriate software development methodology is something which continues to occupy the minds of many IT professionals. The introduction of "Agile" development methodologies such as XP and SCRUM held the promise of improved software quality and reduced delivery times. Combined with a Lean philosophy, there would seem to be potential for much benefit. While evidence does exist to support many of the Lean/Agile claims, we look here at how such methodologies are being adopted in the rigorous environment of safety-critical embedded software development due to its high regulation. Drawing on the results of a systematic literature review we find that evidence is sparse for Lean/Agile adoption in these domains. However, where it has been trialled, "out-of-the-box" Agile practices do not seem to fully suit these environments but rather tailored Agile versions combined with more planbased practices seem to be making inroads.

show abstract

“…The main reason to propose this semiformal development methodology is to cover the gaps identified by Ronkainen and Abrahamsson, 2003). Therefore, the main motivations of the proposed methodology fall into the following categories: (i) full lifecycle coverage, (ii) project management activities, (iii) flexibility, (iv) means to address the non-functional requirements, (v) a software driven hardware development approach, (vi) concrete guidance of the processes, and (vii) experimental results.…”

Section: Towards a Semiformal Development Methodology For Embedded Symentioning

confidence: 99%

Towards a Semiformal Development Methodology for Embedded Systems

Cordeiro

Barreto²,

Oliveira

2008

Proceedings of the Third International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract:In recent days, the amount of functions has increased significantly in embedded products so that systems development methodologies play an important role to ensure the product's quality, cost, and time. Furthermore, this complexity coupled with constantly evolving specifications, has led to propose a semiformal development methodology to support the building of embedded real-time systems. A platform-based design approach has been used to balance costs and time-to-market in relation to performance and functionality constraints. We performed three expressive case studies and we concluded that the proposed methodology significantly reduces design time and improves software modularity and reliability.

show abstract

Software Development under Stringent Hardware Constraints: Do Agile Methods Have a Chance?

Cited by 50 publications

References 5 publications

Industrial Challenges of Scaling Agile in Mass-Produced Embedded Systems

Industrial Challenges of Scaling Agile in Mass-Produced Embedded Systems

Lean/Agile Software Development Methodologies in Regulated Environments – State of the Art

Towards a Semiformal Development Methodology for Embedded Systems

Contact Info

Product

Resources

About