Please use this identifier to cite or link to this item:
https://doi.org/10.1002/smr.237
DC Field | Value | |
---|---|---|
dc.title | Large packaged application software maintenance: A research framework | |
dc.contributor.author | Gable, G.G. | |
dc.contributor.author | Chan, T. | |
dc.contributor.author | Tan, W.-G. | |
dc.date.accessioned | 2014-12-02T08:39:23Z | |
dc.date.available | 2014-12-02T08:39:23Z | |
dc.date.issued | 2001 | |
dc.identifier.citation | Gable, G.G., Chan, T., Tan, W.-G. (2001). Large packaged application software maintenance: A research framework. Journal of Software Maintenance and Evolution 13 (6) : 351-371. ScholarBank@NUS Repository. https://doi.org/10.1002/smr.237 | |
dc.identifier.issn | 1532060X | |
dc.identifier.uri | http://scholarbank.nus.edu.sg/handle/10635/114667 | |
dc.description.abstract | This paper seeks to stimulate research on large application package software maintenance by presenting a tentative framework for future research in the area, partially instantiating that framework with examples from the papers in this special issue of the Journal of Software Maintenance and Evolution, highlighting other specific areas of research need and neglect, and posing a long list of related research questions. The user-organization-centric research framework captures relevant and interacting factors that can impact maintenance strategy, including software-source, support-source, and organizational and environmental contexts. These are viewed from the perspectives of four key stakeholders in the new distributed maintenance arrangement. In addition to the user-organization, stakeholders include the software vendor, third-party service providers, and society. Key messages from the paper include: maintenance generates benefits as well as costs; all stakeholders must have a lifecycle-wide view of maintenance costs and benefits; there is value in understanding all stakeholder perspectives; various software and related support sourcing alternatives have substantial maintenance incidence implications (incidence of costs, benefits, and responsibilities); and maintenance knowledge sourcing decisions should be made in the light of lifecycle-wide maintenance knowledge requirements. | |
dc.description.uri | http://libproxy1.nus.edu.sg/login?url=http://dx.doi.org/10.1002/smr.237 | |
dc.source | Scopus | |
dc.subject | Enterprise resource planning | |
dc.subject | Large packaged application | |
dc.subject | Maintenance | |
dc.subject | Research framework | |
dc.subject | Software lifecycle | |
dc.type | Article | |
dc.contributor.department | INSTITUTE OF SYSTEMS SCIENCE | |
dc.description.doi | 10.1002/smr.237 | |
dc.description.sourcetitle | Journal of Software Maintenance and Evolution | |
dc.description.volume | 13 | |
dc.description.issue | 6 | |
dc.description.page | 351-371 | |
dc.description.coden | JSMEC | |
dc.identifier.isiut | 000173191200001 | |
Appears in Collections: | Staff Publications |
Show simple item record
Files in This Item:
There are no files associated with this item.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.