Software Release Patterns When is it a good time to update a software component? | Zendy

Solomon Berhe | Zendy; Marc Maynard | Zendy; Foutse Khomh | Zendy

AI Assistant Blog Pricing

Home ZAIA Blog

Open Access

Software Release Patterns When is it a good time to update a software component?

Author(s) -

Solomon Berhe,

Marc Maynard,

Foutse Khomh

Publication year - 2020

Publication title -

procedia computer science

Language(s) - English

Resource type - Journals

SCImago Journal Rank - 0.334

H-Index - 76

ISSN - 1877-0509

DOI - 10.1016/j.procs.2020.03.142

Subject(s) - computer science , backporting , software sizing , software , software construction , component based software engineering , software development , software release life cycle , software engineering , component (thermodynamics) , package development process , operating system , physics , thermodynamics

Over the past decade the industry 4.0 witnessed a trend towards an increasing number of software components, dependencies towards third party software components, and software component release cycles. Industry 4.0 teams building software products are more frequently impacted by third party software component updates. Due to this dependency, updating a single third party software component can break an entire software product. Reasons include parallel conflicting updates of third party software components, updating to an unstable version, or updating to a major stable version without an impact analysis. The objective of this paper is to reduce the risk of breaking updates by reviewing software release patterns and proposing update scheduling recommendations.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.

Having issues? You can contact us here

Accelerating Research