000			02083nam a22002537a 4500
003			ZW-GwMSU
005			20240830111151.0
008			240830b |||||||| |||| 00| 0 eng d
022			_a02683962
040			_aMSU _bEnglish _cMSU _erda
050	0	0	_aT58.5 JOU
100	1		_aSee-Pui Ng, Celeste _eauthor
245	1	0	_aMaintaining ERP packaged software – _ba revelatory case study _ccreated by Celeste See-Pui Ng and Guy G Gable
264	1		_aLondon: _bPalgrave, _c2010
336			_2rdacontent _atext _btxt
337			_2rdamedia _aunmediated _bn
338			_2rdacarrier _avolume _bnc
440			_aJournal of Information Technology _vVolume 25, number 1
520	3		_aFor many organizations, maintaining and upgrading enterprise resource planning (ERP) systems (large packaged application software) is often far more costly than the initial implementation. Systematic planning and knowledge of the fundamental maintenance processes and maintenance-related management data are required in order to effectively and efficiently administer maintenance activities. This paper reports a revelatory case study of Government Services Provider (GSP), a high-performing ERP service provider to government agencies in Australia. GSP ERP maintenance-process and maintenance-data standards are compared with the IEEE/EIA 12207 software engineering standard for custom software, also drawing upon published research, to identify how practices in the ERP context diverge from the IEEE standard. While the results show that many best practices reflected in the IEEE standard have broad relevance to software generally, divergent practices in the ERP context necessitate a shift in management focus, additional responsibilities, and different maintenance decision criteria. Study findings may provide useful guidance to practitioners, as well as input to the IEEE and other related standards.
650			_aSoftware engineering standard _vMaintenance management _xMaintenance measurement
700			_aGable, Guy G _eco-author
856			_uhttps://doi.org/10.1057/jit.2009.8
942			_2lcc _cJA
999			_c166970 _d166970