Concepts of product software

Xu, Lai; Brinkkemper, Sjaak

doi:10.1057/palgrave.ejis.3000703

Cited by 84 publications

(66 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The literature review filtering criteria of English-language papers will have influenced this distribution. Five concepts and themes emerged from the literature; they are: (1) maintenance of vendor software is a problem, (2) there is too little research on the topic, (3) reasons for maintenance deferral do exist, (4) deferral has consequences (5) there are reasons for maintenance implementation.…”

Section: Resultsmentioning

confidence: 99%

“…Also related to unpredictable behavior of vendors is a risk of the unforeseen, related to the impossibility of fully testing a maintenance release and its un-assessable impacts and sideeffects [2]. The risk of the unknown is implicitly common to all risks listed here, but there is a specific risk of the unforeseen, that even when everything is assessed and mitigated, something might go wrong with a concrete example of this unforeseen risk being pointed to as "Unexpected problems with file sharing in Access" in ( [7], p. 164).…”

Section: Reasons For Maintenance Deferral Do Existmentioning

confidence: 99%

“…The "dependence on critical infrastructures is increasing worldwide" ( [1], p.112) and "both the impact of software on life, and our dependence on software is rapidly increasing" ( [2], p.531). Companies requiring software capability that do not want to develop the capability in-house can choose to commission or outsource a unique build, or purchase the capability [3].…”

Section: Introductionmentioning

confidence: 99%

“…The focus of this research is on vendor-supplied standard packaged software, abbreviated hereafter to vendor software, which is considered to be generic software, pre-created by a third-party organization for the purpose of sale or licensing. Vendor software is treated as including 3 rd -party, commercial-off-the-shelf (COTS) software [5], product software [2] or packaged software [3].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A Conceptual Investigation of Maintenance Deferral and Implementation: Foundation for a Maintenance Lifecycle Model

Savage

Kautz

Clarke

2017

Complexity in Information Systems Development

View full text Add to dashboard Cite

Despite the fact that society and organizations rely heavily on Information Systems (IS) and software, the maintenance of vendor-supplied IS, in particular standard package software has gained little attention within the academic literature. This paper presents a conceptual study of the current state of research concerning the reasons for deferral and performance of vendor-supplied maintenance by the purchasing organization. These reasons have so far neither been investigated together nor from that perspective. Based on a systematic literature review and taking the purchaser's viewpoint, reasons for maintenance deferral and performance are identified from the literature. They build the groundwork and foundation for a Maintenance Lifecycle and Process Model that provides a starting point to research vendor-supplied maintenance from the customer's point of view. Disciplines Business AbstractDespite the fact that society and organizations rely heavily on Information Systems (IS) and software, the maintenance of vendor-supplied IS, in particular standard package software has gained little attention within the academic literature. This paper presents a conceptual study of the current state of research concerning the reasons for deferral and performance of vendorsupplied maintenance by the purchasing organization. These reasons have so far neither been investigated together nor from that perspective. Based on a systematic literature review and taking the purchaser's viewpoint, reasons for maintenance deferral and performance are identified from the literature. They build the groundwork and foundation for a Maintenance Lifecycle and Process Model that provides a starting point to research vendor-supplied maintenance from the customer's point of view.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Reasons For Maintenance Deferral Do Existmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Conceptual Investigation of Maintenance Deferral and Implementation: Foundation for a Maintenance Lifecycle Model

Savage

Kautz

Clarke

2017

Complexity in Information Systems Development

View full text Add to dashboard Cite

show abstract

“…companies that develop and market softwareproducts for a particular market. About 10% of the total ICT spending is spend on software products and examples of such companies are Microsoft, SAP, Oracle, and Business Objects [6]. As these companies keep the ownership of the software code and all auxiliary materials belonging to the software product, these companies create and maintain a proprietary software development method.…”

Section: Methods Fragmentsmentioning

confidence: 99%

Modularization Constructs in Method Engineering: Towards Common Ground?

Ågerfalk

Brinkkemper

González-Pérez

et al.

IFIP — The International Federation for Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract. Although the Method Engineering (ME) research community has reached considerable maturity, it has not yet been able to agree on the granularity and definition of the configurable parts of methods. This state of affairs is causing unnecessary confusion, especially with an ever increasing number of people contributing to ME research. There are several competing notions around, most significantly 'method fragments' and 'method chunks', but also 'method components' and 'process components' are used in some quarters and have also been widely published. Sometimes these terms are used interchangeably, but there appears to be important semantic and pragmatic differences. If the differences are unimportant, we should be able to come to an agreement on what construct to promote. Alternatively, the different constructs may serve different purposes and there is a need for them to coexist. If this is the case, it should be possible to pinpoint exactly how they are related and which are useful in what contexts. This panel is a step towards finding common ground in this area, which arguably is at the very core of ME.

show abstract

Energy efficiency on the product roadmap: An empirical study across releases of a software product

Jagroep

Procaccianti

Werf

et al. 2017

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

SUMMARYIn the quest for energy efficient ICT, research has mostly focused on the role of hardware. However, the impact of software on energy consumption has been acknowledged as significant by researchers in software engineering. In spite of that, due to cost and time constraints, many software producing organizations are unable to effectively measure software energy consumption preventing them to include energy efficiency in the product roadmap. In this paper, we apply a software energy profiling method to reliably compare the energy consumed by a commercial software product across two consecutive releases. We demonstrate how the method can be applied and provide an in-depth analysis of energy consumption of software components. Additionally, we investigate the added value of these measurement for multiple stakeholders in a software producing organization, by means of semi-structured interviews. Our results show how the introduction of an encryption module caused a noticeable increase in the energy consumption of the product. Such results were deemed valuable by the stakeholders and provided insights on how specific software changes might affect energy consumption. In addition, our interviews show that such a quantification of software energy consumption helps to create awareness and eventually consider energy efficiency aspects when planning software releases.

show abstract

Concepts of product software

Cited by 84 publications

References 29 publications

A Conceptual Investigation of Maintenance Deferral and Implementation: Foundation for a Maintenance Lifecycle Model

A Conceptual Investigation of Maintenance Deferral and Implementation: Foundation for a Maintenance Lifecycle Model

Modularization Constructs in Method Engineering: Towards Common Ground?

Energy efficiency on the product roadmap: An empirical study across releases of a software product

Contact Info

Product

Resources

About