목차
The Trouble with Enterprise Software – Cynthia Rettig
Claim 1
Claim 2
Claim 3
Claim 4
Claim 5
Claim 6
Claim 7
Claim 8
Claim 9
Claim 10
Claim 11
Claim 12
Conclusion
Implication of Cisco – The model student for us.
Claim 1
Claim 2
Claim 3
Claim 4
Claim 5
Claim 6
Claim 7
Claim 8
Claim 9
Claim 10
Claim 11
Claim 12
Conclusion
Implication of Cisco – The model student for us.
본문내용
The software itself is not developed by new technology, as the hardware is. The hardware is newly developed and invented but the software is evolved by human’s creativity which becomes innovation. By adoption and adaptation of different types and functions from different fields, the software is recreated. For example, ERP system is recreated and evolved system integrating inventory, human resources, procurement, production, CRM, SCM, finance, sales, etc (as taught in Session 5). But the integration also brings the complexity which makes the implementation too difficult. But the modular concept may help firms to decrease complexity.
Claim 3
Business users and management always want to customize their software to fit their own needs without proper knowledge for the system. “Software is infinitely malleable,” says computer historian Martin Campbell-Kelly. However, as enterprise software becomes increasingly comprehensive and complex, the costs and risks involved in changing it increase as well. No single person within an organization could possibly know how a change in one part of the software will affect its functioning elsewhere. And customizing could lead to in-house bugs and glitches that were hard to foresee and expensive to fix.
Evaluation and Critique
There is a forked road. Standardization or Customization. The customization is modifying software to fit the company’s needs and market. As taught in Session 5, technical failure from customization is the one of the key risks of ERP implementation. The package is proved with long time testing but complex. Customizing the package software may bring bugs and errors unknown, especially when customization is done without enough knowledge about the system.
Claim 3
Business users and management always want to customize their software to fit their own needs without proper knowledge for the system. “Software is infinitely malleable,” says computer historian Martin Campbell-Kelly. However, as enterprise software becomes increasingly comprehensive and complex, the costs and risks involved in changing it increase as well. No single person within an organization could possibly know how a change in one part of the software will affect its functioning elsewhere. And customizing could lead to in-house bugs and glitches that were hard to foresee and expensive to fix.
Evaluation and Critique
There is a forked road. Standardization or Customization. The customization is modifying software to fit the company’s needs and market. As taught in Session 5, technical failure from customization is the one of the key risks of ERP implementation. The package is proved with long time testing but complex. Customizing the package software may bring bugs and errors unknown, especially when customization is done without enough knowledge about the system.
키워드
추천자료
- 경영정보_가치 지향적인 정보시스템의 구축(BGSoft)
- 정보시스템 조직 및 인력관리(경영정보학 개론)
- 경영정보시스템(EIS)의 필요성과 의미
- 경영정보시스템(EIS)의 하드웨어
- 경영전략과 경영정보시스템의 활용(개념, 의의, 기능)
- [경영정보시스템]_시스템개발수명주기방법의단점을보안하기위한방법
- CRM 효과 및 성공사례 - 경영정보시스템,마케팅,브랜드,브랜드마케팅,기업,서비스마케팅,글로...
- [경영정보시스템]기업_내_지식경영의_사례
- [경영정보시스템]_경영혁신기법
- [경영] 경영정보시스템에 대한 이해
- [경영정보시스템] 기업포탈시스템에 대해
- [경영정보] 조직구조에서 정보시스템 구축 사례 (국내외 CRM 도입 성공/실패 사례 분석, 분석...
- [경영정보시스템] 기업 경영혁신에 관해서
- 경제 마케팅문제 정리 - 경영정보시스템, 경제학개론, 국제경영, 마케팅원론 4문제