TechSuRe - A Method for Assessing Technology Sustainability in Long Lived Software Intensive Systems

Jansen, Anton; Wall, Anders; Weiß, Roland

doi:10.1109/seaa.2011.66

Cited by 9 publications

(5 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…He proposes several quality characteristics such as maintainability, portability, modifiability and evolvability as essential NFRs for longliving software systems. Likewise, Jansen et al (2011) pay attention to the economic dimension and present a method to assess the sustainability of long-lived software-intensive systems. Their TechSuRe method defines sustainability in terms of risk and how software can stay economically viable over its entire life cycle.…”

Section: Sustainability Into Software Projectsmentioning

confidence: 99%

See 1 more Smart Citation

Incorporating sustainability into software projects: a conceptual framework

Khalifeh

Farrell

Alrousan

et al. 2020

IJMPB

View full text Add to dashboard Cite

PurposeThe paper aims to present a conceptual framework that helps in incorporating sustainability into software projects, highlights the importance of project sustainability and provides an extensive review of recent relevant contributions across various fields.Design/methodology/approachThe authors carried out a systematic bibliographic search on relevant published materials to analyse links between the two disciplines (sustainability and software projects). Furthermore, content analysis was applied to the final selected publications to identify and classify relevant triple bottom line (TBL) aspects to develop the framework.FindingsThe inclusion of TBL-related aspects is the most efficient and effective method used to incorporate sustainability into projects. Most of the relevant contributions in the software literature have focussed on either project product or project process or on one or two dimensions of sustainability rather than the three dimensions of the TBL theory. This study contributes by proposing a conceptual framework that encompasses TBL-related aspects for incorporating sustainability into processes and products of software projects.Research limitations/implicationsValidating the proposed framework empirically could be an interesting research issue. In addition, future works may focus on different types of industries, such as information systems, telecommunications and service sectors, which have seldom been studied in the literature.Practical implicationsSoftware companies – or other relevant organisations – may use the proposed framework as a measurement tool to evaluate the environmental and social impacts of their current products and project management practices. Consequently, these organisations may pay more attention to incorporating sustainability into their project management practices.Originality/valueThe proposed framework may contribute towards a more sustainable orientation by providing a unique combination of TBL-related aspects that gives academics and practitioners a better understanding of how software projects can be managed sustainably.

show abstract

Section: Sustainability Into Software Projectsmentioning

confidence: 99%

“…),Jansen et al (2011),Kocak (2013),Calero et al (2013a),Venters et al (2014a) andKoçak et al (2015), have focussed on the environmental and/or economic dimension(s) of sustainabilityalso known as green softwareand have paid almost no attention to the social dimension. On the other hand, other contributions, such asNaumann et al (2011), …”

mentioning

confidence: 99%

Incorporating sustainability into software projects: a conceptual framework

Khalifeh

Farrell

Alrousan

et al. 2020

IJMPB

View full text Add to dashboard Cite

show abstract

“…Such a preliminary encoding is done through the ontology discussed in Section IV. A similar approach is adopted in [11], where the authors address the management of risk knowledge related to technology sustainability, and create a corresponding ontology for encoding sustainability risks.…”

Section: B Related Workmentioning

confidence: 99%

Towards Software Assets Origin Selection Supported by a Knowledge Repository

Cicchetti

Borg

Sentilles

et al. 2016

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)

View full text Add to dashboard Cite

Software architecture is no more a mere system specification as resulting from the design phase, but it includes the process by which its specification was carried out. In this respect, design decisions in component-based software engineering play an important role: they are used to enhance the quality of the system, keep the current market level, keep partnership relationships, reduce costs, and so forth. For non trivial systems, a recurring situation is the selection of an asset origin, that is if going for in-house, outsourcing, open-source, or COTS, when in the need of a certain missing functionality. Usually, the decision making process follows a case-by-case approach, in which historical information is largely neglected. This solution avoids the overhead of keeping detailed documentation about past decisions, but hampers consistency among multiple, possibly related, decisions. The ORION project aims at developing a decision support framework in which historical decision information plays a pivotal role: it is used to analyse current decision scenarios, take well-founded decisions, and store the collected data for future exploitation. In this paper, we outline the potentials of such a knowledge repository, including the information it is intended to be stored in it, and when and how to retrieve it within a decision case.

show abstract

“…Sustainability risk is estimated in [1] by considering nine indicators: lifetime in production, lifetime, competence risk, technology evolution risk, risk of changing business model, market risk, lifetime certainty, complexity risk and technology evolution fitness. The output of the assessment is an indication of the expected lifetime of the technology"s sustainability.…”

Section: Sustainability Risksmentioning

confidence: 99%

A Suggested Sustainability Pattern for Online Social Networks The Facebook as a Case Study

Fawaz¹,

Mohammed²,

Noor³

2016

Fourth International Conference on Advances in Computing, Communication and Information Technology CCIT- 2016

View full text Add to dashboard Cite

Abstract-The survival of a software product for a long term is a challenging issue. Software doesn't die but it becomes obsolete. The aim of this paper is to propose a design pattern that could help maintaining the sustainability of software products. The proposed pattern could be used in the architectural engineering phase of developing an online social network system to help maintaining its sustainability. We built our work based on an agreed upon definition of software sustainability from the software engineering perspective, we discussed the main factors that lead to maintain a sustainable software product, and introduced the risks that might lead to software death. Finally, a planning phase was introduced to help analyzing the need for a sustainable software and evaluating it economically. It is highly recommended to use the proposed pattern and to consider the proposed factors due to their comprehensiveness and flexibility.

show abstract

TechSuRe - A Method for Assessing Technology Sustainability in Long Lived Software Intensive Systems

Cited by 9 publications

References 5 publications

Incorporating sustainability into software projects: a conceptual framework

Incorporating sustainability into software projects: a conceptual framework

Towards Software Assets Origin Selection Supported by a Knowledge Repository

A Suggested Sustainability Pattern for Online Social Networks The Facebook as a Case Study

Contact Info

Product

Resources

About