Journals / Ege Akademik Bakış Dergisi / 2009 / Cilt: 9 Sayı: 4

INVESTIGATION OF VARIATIONS IN THE SOFTWARE DEVELOPMENT PROCESS: A CASE STUDY

Yılmaz Gökşen(Dokuz Eylul University)
Sabri Erdem(Dokuz Eylul University)
Bilgehan Öztürk(NTX Company, İzmir)
Pages
1063–1077
Publication Date
2009-11-01
DOI
—
🏛️Bibliographic metadata and full text access for this article are provided via DergiPark.
DergiPark Record ↗
✨

AI Summary & Key Takeaways

AI Insight
⚡ TL;DR(Too Long; Didn't Read)

Our findings show that the most of the factors, that affect the software development process’ success; are understanding the customer, good communication and promises

📌 3 Key Takeaways

🎯
Objective & Hypothesis:This study employs the business software project variations in understanding the customer.
📊
Key Findings & Data:The relevant literature shows many business software implementation failures and their reasons.
💡
Conclusion & Impact:Our findings show that the most of the factors, that affect the software development process’ success; are understanding the customer, good communication and promises
🔬Design:Makale
📍Scope:Comprehensive Sample
⚙️Variables:Software development process · software project management · software project failures

Abstract

This study employs the business software project variations in understanding the customer. The relevant literature shows many business software implementation failures and their reasons. Our research is based on a real case study in Turkey and it has a potential for encountering in any location of the world as well as in Turkey. We focus on a business software implementation process and obtain observational data from project meetings and interviews. Our findings show that the most of the factors, that affect the software development process’ success; are understanding the customer, good communication and promises

🔖

Cite This Article

Gökşen, Y., Erdem, S., Öztürk, B. (2009). INVESTIGATION OF VARIATIONS IN THE SOFTWARE DEVELOPMENT PROCESS: A CASE STUDY. Ege Akademik Bakış Dergisi, Cilt: 9 Sayı: 4, 1063–1077. https://ajindex.com/articles/1476796

📄 Full Text PDF Viewer

📄

PDF görüntüleyici hazırlanıyor...

References (14)

  1. Aksoy, E. (2007). “ERP Sistemlerinde Esneklik”, http://www.ias.com.tr/enterprise/articles/20070402-erp-flexibility.html, Nisan, Access Date:June 2009.
  2. APICS (1999). www.apics.org/magazine/June 99/ERPTravis, Access Date:June 2009.
  3. Holland C. P. and Light B. (1999). “A Critical Success Factors Model For Enterprise Resource Planning Implementation”, Proceedings of the 7th European Conference on Information, available at: christopherholland.co.uk.
  4. Jones, C. (2004). “Software Project Management Practices: Failure Versus Success”, CrossTalk: The Journal of Defense Software Engineering, 5-9. available at: www.stsc.hill.af.mil
  5. Kappelman A. L., Robert M., and Lixuan Z. (2006). “Early Warning Signs of IT Project Failure: The Dominant Dozen”, Information Systems Management, 23:4, 31-36
  6. Linberg R. K. (1999). “Software developer perceptions about software project failure: a case study”, The Journal of Systems and Software, 49, 177-192.
  7. Lyytinen, K. & Robey D. (1999). “Learning failure in information systems development”, Information Systems Journal, 9, 85-101.
  8. Procaccino. D. J, June M. V., Scott P. O. and Marvin E. D. (2002). “Case study: factors for early prediction of software development success”, Information and Software Technology, 44, 53-62.
  9. Standish Group. (1994). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
  10. Standish Group. (1996). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
  11. Standish Group. (2004). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
  12. Standish Group. (2006). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
  13. Welke, R.W, (1994). “The shifting software development, paradigm”. Data Base, 25 (4), 9-16.
  14. Aksoy, E. (2007). “ERP Sistemlerinde Esneklik”, http://www.ias.com.tr/enterprise/articles/20070402-erp-flexibility.html, Nisan, Access Date:June 2009.