Sustainability guidelines for long-living software systems

Durdik, Zoya; Klatt, Benjamin; Koziolek, Heiko; Krogmann, Klaus; Stammel, Johannes; Weiß, Roland

doi:10.1109/icsm.2012.6405316

Cited by 48 publications

(35 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…al. point out that "in many software development projects, sustainability is treated as an afterthought, as developers are driven by time-to-market pressure and are often not educated to apply sustainability-improving techniques" [15], and they call for better guidance for software practice.…”

Section: Software Systems and Sustainabilitymentioning

confidence: 99%

Sustainability Design and Software: The Karlskrona Manifesto

Becker

Chitchyan

Duboc

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

155

163

View full text Add to dashboard Cite

Abstract-Sustainability has emerged as a broad concern for society. Many engineering disciplines have been grappling with challenges in how we sustain technical, social and ecological systems. In the software engineering community, for example, maintainability has been a concern for a long time. But too often, these issues are treated in isolation from one another. Misperceptions among practitioners and research communities persist, rooted in a lack of coherent understanding of sustainability, and how it relates to software systems research and practice. This article presents a cross-disciplinary initiative to create a common ground and a point of reference for the global community of research and practice in software and sustainability, to be used for effectively communicating key issues, goals, values and principles of sustainability design for software-intensive systems. The centrepiece of this effort is the Karlskrona Manifesto for Sustainability Design, a vehicle for a much needed conversation about sustainability within and beyond the software community, and an articulation of the fundamental principles underpinning design choices that affect sustainability. We describe the motivation for developing this manifesto, including some considerations of the genre of the manifesto as well as the dynamics of its creation. We illustrate the collaborative reflective writing process and present the current edition of the manifesto itself. We assess immediate implications and applications of the articulated principles, compare these to current practice, and suggest future steps.

show abstract

Section: Software Systems and Sustainabilitymentioning

confidence: 99%

Sustainability Design and Software: The Karlskrona Manifesto

Becker

Chitchyan

Duboc

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

155

163

View full text Add to dashboard Cite

show abstract

“…Our survey (see section 5) showed that 90% of the software engineers have encountered various problems while applying patterns, with already applied patterns or with their documentation. Moreover, practitioners desire a compact description of the material, as we discovered during several industrial projects [6]. These findings indicate a need for an improved pattern description and support for application and documentation.…”

Section: Purposementioning

confidence: 83%

On the appropriate rationale for using design patterns and pattern documentation

Durdik

Reussner

2013

Proceedings of the 9th International ACM Sigsoft Conference on Quality of Software Architectures

Self Cite

View full text Add to dashboard Cite

Software design patterns are proven solutions for recurring design problems. Decisions on the use of a pattern in a software design form a specific but important class of design decisions. However, despite their importance, these design decisions are often mistaken and rarely documented. In our survey, about 90% of the participants confirmed to have experienced such problems. Therefore, we propose an approach that supports the appropriate use of design patterns and documentation of such decisions. The main idea is to create a pattern catalogue, where a pattern (as part of its catalogue entry) is annotated with general questions on the appropriateness of the use of the pattern. The envisioned benefits of this approach are a more appropriate use of design patterns, and documented design decisions on the use of patterns with positive effects on evolution. In this paper, we present the enriched pattern catalogue, and results of a survey with 21 software engineers as a validation of some entries of the pattern catalogue.

show abstract

“…These trends require more advanced aPS [3], which support changes in the physical layout of the aPS including extensive technical updates, since aPS often have a life-span of more than 10 years [4]. The complexity of the aPS, including automation hardware and automation software (called software henceforth), is rising.…”

Section: Introductionmentioning

confidence: 99%

Challenges for maintenance of PLC-software and its related hardware for automated production systems: Selected industrial Case Studies

Vogel‐Heuser

Fischer

Rösch

et al. 2015

2015 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

The specific challenges for maintenance of software and its related hardware for the domain of automated Production Systems is discussed. Presenting four industrial case studies from renowned and world market leading German machine and plant manufacturing companies, these challenges and different solution approaches are introduced with a focus on software architectures to support modularity as a basis for maintaining long-living automated Production Systems. Additionally, most critical aspects hindering classical approaches from software engineering to be successful, e.g., modes of operation and fault handling, are discussed. In the last decades, research in the field of software engineering for automated Production Systems (aPS) has been focusing on developing domain specific model-driven engineering approaches supporting the development process, but mostly neglecting the operation, maintenance and re-engineering aspects. However, the success of model-driven engineering in aPS industry has been limited because the effort to introduce model-driven engineering and to change the entire existing legacy software is estimated as too high and the benefit as too low against the background of customer specific solutions expecting a low degree of reuse.

show abstract

Sustainability guidelines for long-living software systems

Cited by 48 publications

References 15 publications

Sustainability Design and Software: The Karlskrona Manifesto

Sustainability Design and Software: The Karlskrona Manifesto

On the appropriate rationale for using design patterns and pattern documentation

Challenges for maintenance of PLC-software and its related hardware for automated production systems: Selected industrial Case Studies

Contact Info

Product

Resources

About