Maintaining ERP packaged software – a revelatory case study created by Celeste See-Pui Ng and Guy G Gable
Material type:
- text
- unmediated
- volume
- 02683962
- T58.5 JOU
Item type | Current library | Call number | Vol info | Copy number | Status | Notes | Date due | Barcode | |
---|---|---|---|---|---|---|---|---|---|
![]() |
Main Library Journal Article | T58.5 JOU (Browse shelf(Opens below)) | Vol. 25, no. 1 (pages 65-90) | SP4287 | Not for loan | For in house use |
Browsing Main Library shelves, Shelving location: Journal Article Close shelf browser (Hides shelf browser)
For 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.
There are no comments on this title.