Advertisement

Integration assessment ofan individually developed application vs. software packages from the market - an experience report

  • Oliver Skroch

Abstract

The following research article presents the examination of the results from an IT strategy project performed by a team of consultants [Tom the software engineering sector for a large client in the communications business. The client requirements sketched a highly integrated, inter-organizational business support system. The examination of the project results focus on the “make-or-buy” assessment of individual application software development, as compared to alternative courses of action based on the reuse and integration of software packages and components which are available on the market.

Keywords

Integration Assessment Individual Solution Integration Scenario Telecom Provider Component Competence 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Bayerlein, W. (2008), Praxishandbuch Sachverständigenrecht, 4th edn, Beck, Munich.Google Scholar
  2. BGH (2003), Bundesgerichtshof,decision of 16 Dec. 2003, X ZR 129/01, accessed on 26 Jan. 2009, http://www.bundesgerichtshof.de.Google Scholar
  3. DeMarco, T. (1997), Warum ist Software so teuer? Und andere Rätsel des Informationszeitalters, Hanser, Munich.Google Scholar
  4. Grollius, T.; Lonthoff J.; Ortner, E. (2007), “Softwareindustrialisierung durch Komponentenorientierung und Arbeitsteilung”, HMDPraxis der Wirtschaftsinformatik, 43 (256): 37–45.Google Scholar
  5. Gsell, B.; Overhage, S.; Turowski, K. (2008), “Unzureichende Leistungsbeschreibung bei der Softwareentwicklung und die Rolle von Standardverträgen”, in Möllers, T. (ed.), Standardisierung durch Markt und Recht, Nomos, Baden-Baden: 23–48.Google Scholar
  6. Jäger, K.; Lenzer, J.; Scheider, J.; Wißner, B (2003), Begutachtung und rechtliche Bewertung von EDV- Mängeln. Wißner-Verlag, Augsburg.Google Scholar
  7. Mertens, P. (2009), “Schwierigkeiten mit IT-Projekten der öffentlichen Verwaltung”, Informatik-Spektrum, 32 (1): 42–49.CrossRefGoogle Scholar

References

  1. Aspray, W.; Mayadas, F.; Vardi, M. (eds) (2006), “Globalization and offshoring of software: A report of the ACM job migration task force: The executive summary, findings, and overview of a comprehensive ACM report on the offshoring of software worldwide”, ACM, New York, USA.Google Scholar
  2. Becker, J.; Rosemann, M.; Schütte, R. (1995), “Grundsätze ordnungsgemäßer Modellierung”, Wirtschaftsinformatik, 37 (5): 435–445.Google Scholar
  3. Bensberg, F. (2008), “Nutzwertanalyse”, in Kurbel, K.; Becker, J.; Gronau, N.; Sinz, E.; Suhl, L. (eds) (2008), Enzyklopädie der Wirtschaftsinformatik – Online-Lexikon, Oldenbourg. Munich.Google Scholar
  4. Berenbach, B.; Borotto, G. (2006), “Metrics for model driven requirements development”, Proceedings of the 28th international nce on software engineering, ACM, 20-28 May 2006, Shanghai, China: 445–451.Google Scholar
  5. Bhat, J.; Mayank, G.; Murthy, S. (2006), “Overcoming requirements engineering challenges: Lessons from offshore outsourcing”, IEEE Software, 23 (5): 38–44.CrossRefGoogle Scholar
  6. Boos, E.; Iesalnieks, J.; Keller, F.; Moczadlo, R.; Rathgeb, K.; Rohlfes, M.; Schmidt, C.; Stimmer, J. (2005), Leitfaden Offshoring, Bundesverband Informationswirtschaft, Telekommunikation und neue Medien e.V., Berlin.Google Scholar
  7. Brown, A. (2000), Large-scale, component-based development, Prentice Hall, Upper Saddle River, USA.Google Scholar
  8. Christiansen, H. (2007), “Meeting the challenge of communication in offshore software development”, Proceedings of the first international nce on software engineering approaches for offshore and outsourced development, Lecture Notes in Computer Science 4716, Springer, 5-7 Feb. 2007, Zurich, Switzerland: 19–26.CrossRefGoogle Scholar
  9. Coase. R. (1937), “The nature of the firm”, Economica, 4 (16): 386–405.CrossRefGoogle Scholar
  10. Corriveau, J. (2007), “Testable requirements for offshore outsourcing”, Proceedings of the first international nce on software engineering approaches for offshore and outsourced development, Lecture Notes in Computer Science 4716, Springer, 5-7 Feb. 2007, Zurich, Switzerland: 27–43.CrossRefGoogle Scholar
  11. Cusick, J.; Prasad, A. (2006), “A practical management and engineering approach to offshore collaboration“, IEEE Software, 23 (5): 20–29.CrossRefGoogle Scholar
  12. D'Souza, D.; Wills, A. (1999), Objects, components, and frameworks with UML: The catalysis approach, Addison Wesley, Upper Saddle River, USA.Google Scholar
  13. Davenport, T. (2004), “What stays and what goes? Sourcing processes and jobs in the global economy”, Offshore oursourcing - risks and rewards: Symposium conclusions paper, CFO Publishing, 17 Jun. 204, New York, USA: 3–4.Google Scholar
  14. Davis, A. (1993), Software requirements: Objects,functions, and states, Prentice Hall, Englewood Cliffs, USA.Google Scholar
  15. Dibbern, J.; Goles, T.; Hirschheim, R.; Jayatilaka, B. (2004), “Information systems outsourcing: A survey and analysis of the literature”, The DATA BASE for Advances in Information Systems, 35 (4): 6–102.Google Scholar
  16. Dibbern, J.; Winkler, J.; Heinzl, A. (2008), “Explaining variations in client extra costs between software projects offshored to India”, MIS Quarterly, 32 (2): 333–366.Google Scholar
  17. Erber, G.; Sayed-Ahmed, A. (2008), “Offshore outsourcing: A global shift in the present IT industry”, Intereconomics, 40 (2): 100–112.CrossRefGoogle Scholar
  18. Gefen, D.; Wyss, S.; Lichtenstein, Y. (2008), “Business familiarity as risk mitigation in software development outsourcing contracts”, MIS Quarterly, 32 (3): 531–551.Google Scholar
  19. Gsell, B.; Overhage, S.; Turowski, K. (2008), “Unzureichende Leistungsbeschreibung bei der Softwareentwicklung und die Rolle von Standardverträgen”, in Möllers, T. (ed.), Standardisierung durch Markt und Recht, Nomos, Baden-Baden: 23–48.Google Scholar
  20. Hall, A. (1990), “Seven myths of formal methods”, IEEE Software, 7 (5): 11–19.CrossRefGoogle Scholar
  21. Hansen, H.; Neumann, G. (2009), Wirtschaftsinformatik 1: Grundlagen und Anwendung, 10th edn, Lucius & Lucius, Stuttgart.Google Scholar
  22. Heeks, R.; Krishna, S; Nicholson, B.; Sahay, S. (2001), “Synching or sinking: Global software outsourcing relationships”, IEEE Software, 18 (2): 54–60.CrossRefGoogle Scholar
  23. Heindl, M.; Biffl, S. (2006), “Risk management with enhanced tracing of requirements rationale in highly distributed projects”, Proceedings of the 2006 international workshop on global software development for the practitioner, ACM, Shanghai, China: 20–26.Google Scholar
  24. Hevner, A.; March, S.; Park, J.; Ram, S. (2004), “Design science in information systems research”, MIS Quarterly, 28 (1): 75–105.Google Scholar
  25. Hofstede, G. (2002), Culture's consequences: Comparing values, behaviors, institutions, and organizations across nations, 2nd edn, Sage, Thousand Oaks, USA.Google Scholar
  26. IEEE (1998), IEEE recommended practice for software requirements specifications: IEEE standard 830–1998, IEEE, New York, USA.Google Scholar
  27. King, W.; Torkzadeh, G. (2008), “Information systems offshoring: Research status and issues”, MIS Quarterly, 32 (2): 205–225.Google Scholar
  28. Klein, R.; Scholl, A. (2004), Planung und Entscheidung: Konzepte, Modelle und Methoden einer modernen betriebswirtschaftlichen Entscheidungsanalyse, Vahlen, Munich.Google Scholar
  29. Kobitzsch,W.; Rombach, D.; Feldmann, R. (2001), “Outsourcing in India”, IEEE Software, 18 (2): 78–86.CrossRefGoogle Scholar
  30. Kojima, S.; Kojima, M. (2007), “Making IT offshoring work for the Japanese indusustries”, Proceedings of the first international nce on software engineering approaches for offshore and outsourced development, Lecture Notes in Computer Science 4716, Springer, 5-7 Feb. 2007, Zurich, Switzerland: 67–82.Google Scholar
  31. Krogstie, J. (1998), “Integrating the understanding of quality in requirements specifications and conceptual modeling”, ACMSIGSOFT Software Engineering Notes, 23 (1): 86–91.CrossRefGoogle Scholar
  32. van Lamsweerde, A. (2009), Requirements engineering: From system goals to UML models to software specifications, Wiley, Hoboken, USA.Google Scholar
  33. Liskov, B.; Berzins, V. (1986), “An appraisal of program specifications”, in Gehani, N.; McGettrick, A. (eds), Software specification techniques, Addison Wesley, wokingham, UK: 3–24.Google Scholar
  34. MacGregor, E.; Hsieh, Y.; Kruchten, P. (2005), “Cultural patterns in software process mishaps: Incidents in global projects”, ACM SIGSOFT Software Engineering Notes, 30 (4): 1–5.CrossRefGoogle Scholar
  35. Moczadlo, R. (2002), “Chancen und Risiken des Offshore-Development: Empirische Analyse der Erfahrunge deutscher Unternehmen”, accessed on 14 Jul. 2009, http://www.competence-site.de.Google Scholar
  36. Morris, C. (1970), Foundation of the theory of signs, University of Chicago Press, Chicago, USA.Google Scholar
  37. Nevo, S.; Wade, M.; Cook, W. (2006), “An examination of the trade-off between internal and external IT capabilities”, Journal of Strategic Information Systems, 16 (1): 5–23.CrossRefGoogle Scholar
  38. Overby, S. (2003), “Offshore outsourcing the money: Moving jobs overseas can be a much more expensive proposition than you may think”, CIO, 16 (22): 60–66.Google Scholar
  39. Overhage, S. (2006), “Vereinheitlichte Spezifikation von Komponenten: Grundlagen, UnSCom Spezifikationsrahmen und Anwendung“, Dissertation, Universität Augsburg, Augsburg.Google Scholar
  40. Overhage, S.; Thomas, P. (2005), “WS-Specification: Ein Spezifikationsrahmen zur Beschreibung von Web-Services auf Basis des UDDI-Standards”, eEconomy, eGovernment, eSociety: Proceedings Wirtschaftsinformatik 2005, Physica, 23-25 Feb. 2005, Bamberg: 1539–1558.CrossRefGoogle Scholar
  41. Pruß, M.; Skroch, O. (2008), “Kritische Defizite bei der Leistungsvereinbarung in Softwareverträgen: Ein Bericht aus der Praxis”, in Möllers, T. (ed.), Vielfalt und Einheit: Wirtschaftliche und rechtliche Rahmenbedingungen von Standardbildung, Nomos, Baden-Baden: 263–278.Google Scholar
  42. Pryor, B.; Keane, B. (2004), “Critical success factors in outsourcing”, Offshore oursourcing - risks and rewards: Symposium conclusions paper, CFO Publishing, 17 Jun. 2004, New York, USA: 11–13.Google Scholar
  43. Remus, U.; Wiener, M. (2009), “Critical success factors for managing offshore software development projects”, Journal of Global Information Technology Management, 12 (1): 6–29.Google Scholar
  44. Sakthivel, S. (2007), “Managing risk in offshore systems development”, Communications of the ACM, 50 (4): 69–75.CrossRefGoogle Scholar
  45. Scheffczyk, J.; Stutz, C.; Borghoff, U.; Siedersleben, J. (2004), “Formale Konsistenzsicherung in informellen Software-Spezifikationen”, Informatik Forschung und Entwicklung, 19 (1): 17–29.CrossRefGoogle Scholar
  46. Schienmann, B. (1997), Objektorientierter Fachentwurf: Ein terminologiebasierter Ansatz für die Konstruktion von Anwendungssystemen, Teubner, Stuttgart.Google Scholar
  47. Setamanit, S.; Raffo, D. (2008), “Identifying key success factors for globally distributed software projects using simulation: A case study”, Proceedings of the international nce on software processes, Lecture Notes in Computer Science 5007, Springer, 10-11 May 2008, Leipzig: 320–332.Google Scholar
  48. Siakas, K.; Maoutsidis, D.; Siakas, E. (2006), “Trust facilitating good software outsourcing relationships”, Proceedings of the 13th European nce on software process improvement, Lecture Notes in Computer Science 4257, Springer, 11-13 Oct 2006, Joensuu, Finland: 171–182.CrossRefGoogle Scholar
  49. Steimle, T. (2007), Softwareentwicklung im Offshoring: Erfolgsfaktoren für die Praxis, Springer, Heidelberg.Google Scholar
  50. Takeda, H.; Veerkamp, P.; Tomiyama, T.; Yoshikawa, H. (2007), “Modeling design processes”, AI Magazine,11 (4): 37–48.Google Scholar
  51. Tsuji, H.; Sakurai, A.; Yoshida, K.; Tiwana, A.; Bush, A. (2007), “Questionnaire-based risk assessment scheme for Japanese offshore software outsourcing”, Proceedings of the first international nce on software engineering approaches for offshore and outsourced development, Lecture Notes in Computer Science 4716, Springer, 5-7 Feb. 2007, Zurich, Switzerland: 114–127.Google Scholar
  52. Vlaar, P.; van Fenema, P.; Tiwari, V. (2008), “Cocreating understanding and value in distributed work: How members of onsite and offshore vendor teams give, make, demand and break sense”, MIS Quartery, 32 (2): 227–255.Google Scholar
  53. Wada, Y.; Nakahigashi, D.; Tsuji, H. (2007), “An evaluation method for offshore software development by structural equation modeling”, Proceedings of the first international nce on software engineering approaches for offshore and outsourced development, Lecture Notes in Computer Science 4716, Springer, 57 Feb. 2007, Zurich, Switzerland: 128–140.CrossRefGoogle Scholar
  54. Wehrmann, A.; Gull, D. (2006), “Ein COCOMO-basierter Ansatz zur Entscheidungsunterstützung beim Offshoring von Softwareentwicklungsprojekten”, Wirtschaftsinformatik, 48 (6): 407–417.CrossRefGoogle Scholar
  55. Winkler, J.; Dibbern, J.; Heinzl, A. (2007), “Der Einfluß kultureller Uaterschiede beim IT-Offshoring: Ergebnisse aus Fallstudien zu deutsch-indischen Anwendungsentwickungsprojekten”, Wirtschaftsinformatik, .49 (2): 95–103.CrossRefGoogle Scholar
  56. Zangemeister, C. (1976), Nutzwertanalyse in der Systemtechnik – Eine Methodik zur multidimensionalen Bewertung undAuswahl von projektalternativen, 4th edn, Wittemann, Munich.Google Scholar

Copyright information

© Gabler Verlag | Springer Fachmedien Wiesbaden GmbH 2010

Authors and Affiliations

  • Oliver Skroch

There are no affiliations available

Personalised recommendations