"Better! Cheaper! Faster!" is a battle cry in today's economy that sounds across many lines of businesses, from the investors' desks through executive management levels down to operational projects (Brandon 2006, p. 4). The three cardinal challenges of this objective are depicted in the structure of the "triple constraint" triangle illustrated in Figure I-1 (Rosenau 1981, pp.15–18). Some difficulties, however, arise from the dynamics of the "triple constraint", from the challenges associated with achieving all three dependent conditions simultaneously: "Unfortunately, the Triple Constraint is very difficult to satisfy because most of what occurs during a project conspires to pull the performance below specification and to delay the project so it falls behind schedule, which makes it exceed the budget." (Rosenau 1981, p. 15).


Software Development Software Engineering Business Process Model Software Reuse Software Development Project 
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.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. Alper, P.; Grob, H.; Weimann, P.; Winter, R. (2008), Anwendungsorientierte Wirtschaftsinformatik. Strategische Planung, Entwickung and Nutzung von Informations- und Kommumikationssystemen,5th edn, Vieweg, Wiesbaden.Google Scholar
  2. Atkinson, C; Bunse, C; Groβ, H.; Kühne, T. (2002), "Towards a general component model for Web-based applications",Annals of Software Engineering, 13 (1): 35–69.CrossRefGoogle Scholar
  3. Biggerstaff, T.; Richter, C (1987), “Reusability framework, assessment, and directions”, IEEE Software, 4 (2): 41–49.CrossRefGoogle Scholar
  4. Boehm, B. (1986), Wirtschaftliche Software-Produtaion, Forkel, Wiesbaden.Google Scholar
  5. Brandon, D. (2006), Project management for modern information systems, IRM Press, Hershey, USA.Google Scholar
  6. Brooks, F. (1987), "No sliver bullet: Essence and accidents of software engineering", IEEE Computer. 20 (4): 10–19.CrossRefGoogle Scholar
  7. Brown, A. (2000), Large-scale, component-based development, Prentice Hall, Upper Saddle River, USA.Google Scholar
  8. Chatzoglou, P. (1997), “Factors affecting completion of the requirements capture stage of projects with different characteristics”, Information and Software Technology, 39 (9): 627–640.CrossRefGoogle Scholar
  9. DeMarco, T. (1997), Warum ist Software so teuer? Und andere Rätsel des Informationszeitalters, Hanser, Munich.Google Scholar
  10. Dahl, O.; Nygaard, K. (1966), “SIMULA – an ALGOL-based simulation language”, Communications of the ACM, 9 (9): 671–678.CrossRefGoogle Scholar
  11. Dijkstra, E. (1972), “The humble programmer”, Communications of the ACM, 15 (10): 859–866.CrossRefGoogle Scholar
  12. Ferstl, O.; Sinz, E. (2008), Grundlagen der Wirtschaftsinformatik, 6th edn, Oldenbourg, Munich.Google Scholar
  13. Fröschle, H.; Reinheimer, S. (eds) (2007), “Serviceorientierte Architekturen”, HMD - Praxis der Wirtschaftsinfomatik, 43 (253).Google Scholar
  14. Garlan, D.; Allen, R.; Ockerbloom, J. (1995), “Architectural mismatch: Why reuse is so hard”, IEEE Software, 12 (6): 17–26.CrossRefGoogle Scholar
  15. Glass, R. (1996), “Study supports existence of software crisis: Management issues appear to be prime cause”, Journal of Systems and Software, 32 (3): 83–184.CrossRefGoogle Scholar
  16. Glass, R. (2005),“’Silver bullet’ milestones in software history”, Communications of the ACM, 48 (8): 15–18.CrossRefGoogle Scholar
  17. Glass, R. (2006), “Looking into the challenges of complex IT projects”, Communications of the ACM, 49 (11): 15–17.CrossRefGoogle Scholar
  18. Hansen, H.; Neumann, G. (2009), Wirschaftsinformatik 1: Grundlagen und Anwendung, 10th edn, Lucius & Lucius, Stuttgart.Google Scholar
  19. Heinrich, L.; Heinzl, A.; Roithmayr, F. (2007), Wirtschaftsinformatik: Einführung und Grundlegung,3rd edn, Oldenbourg, Munich.Google Scholar
  20. Heinrich, L.; Lehner, F. (2005), Informationsmanagement. 8th edn, Oldenbourg, Munich.Google Scholar
  21. Henderson, J.; Venkatraman, N. (1993), “Strategic alignment: Leveraging information technology for transforming organizations”,IBM Systems Journal, 32 (1): 4–16.CrossRefGoogle Scholar
  22. Martin, R.; Chang, C. (1994), “How to solve the management crisis”, IEEE Software, 11 (6): 14–15.CrossRefGoogle Scholar
  23. Mertens, P.; Bodendorf, F.; König, W.; Picot, A.; Schumann, M.; Hess, T. (2005), Grundzüge der Wirtschaftsinformatik; 9th edn, Springer, Berlin.Google Scholar
  24. Meyer, B. (1990), Objektorientierte Softwareentwicklung, Hanser, Munich.Google Scholar
  25. Mili, H.; Mili, F.; Mili, A. (1995), “Reusing software: Issues and research directions”, IEEE Transactions on Software Engineering, 21 (6): 528–562.CrossRefGoogle Scholar
  26. Moore, G. (1965), “Cramming more components onto integrated circuits”, Electronics Magazine, 38 (8): 114–117.Google Scholar
  27. Naur, P.; Randell, B. (Hrsg.) (1969), Software engineering: Report on a conference sponsored by the NATO Science Committee, NATO Scientific Affairs Division, Brussels, Belgium.Google Scholar
  28. Neighbors, J. (1984), “The draco approach to constructing software from reusable components”, IEEE Transactions on Software Engineering, 10 (5):564–574.CrossRefGoogle Scholar
  29. Ortner, E. (1998), “Ein Multipfad-Vorgehensmodell für die Entwicklung von Informationssystemen–dargestellt am Beispiel von Workflow-Management Anwendungen”, Wirtschaftsinformatik, 40 (4): 329–337.Google Scholar
  30. Overhage, S. (2006), “Vereinheitlichte Spezifikation von Komponenten: Grundlagen, UnSCom Spezifikationsrahmen und Anwendung”, Dissertation, Universität Augsburg, Augsburg.Google Scholar
  31. Overhage, S.; Turowski, K. (2008), “Ingenieurmäβige Entwicklung von Komponenten, Services und Anwendungssystemen: Zum Aufbau einer Konstruktionslehre für die (Wirtschafts-)Informatik”, in Heinemann, E. (ed.), Anwendungsinformatik: Die Zukunft des Enterprise Engineering, Nomos, Baden-Baden: 105–119.Google Scholar
  32. Pahl, G.; Beitz, W.; Feldhusen, J.; Grote, K. (2003), Konstruktionslehre: Grundlagen erfolgreicher Produktentwicklung: Methoden und Anwendung, 5th edn, Springer, Berlin.Google Scholar
  33. Parnas, D. (1985), “Software aspects of strategic defense systems”, Communications of the ACM, (28) 12: 1326–1335.CrossRefGoogle Scholar
  34. Potok, T., Vouk, M.; Rindos, A. (1999), “Productivity analysis of object-oriented software developed in a commercial environment”, Software Practice and Experience, 29 (10): 833–847.CrossRefGoogle Scholar
  35. Poulin, J. (1997), Measuring software reuse: Principles, practices, and economic models, Addison Wesley, Reading, USA.Google Scholar
  36. Raymond, E. (1998), “The cathedral and the bazaar”, First Monday, 3 (3).Google Scholar
  37. Rosenau, M. (1981), Successful project management: A step-by-step approach with practical examples, Van Nostrand Reinhold, New York, USA.Google Scholar
  38. Rost, J. (1997), “Wiederverwendbare Software”, Wirtschaftsinformatik, 39 (4): 357–365.Google Scholar
  39. Rumbaugh, J.; Blaha, M.; Premerlami, W.; Eddy, F.; Lorensen, W (1993), Objektorientiertes Modellieren und Entwerfen, Hanser, Munich.Google Scholar
  40. Sackman, H.; Erikson, W.; Grant, E. (1968), “Exploratory experimental studies comparing online and offline programming performance”, Communications of the ACM, (11) 1: 3–11.CrossRefGoogle Scholar
  41. Sametinger, J. (1997), Software engineering with reusable components, Springer, Berlin.Google Scholar
  42. Schulte, R. (1996), “’Service oriented’ architectures, part 2”, Gartner Research ID Number SPA-401-069, Gartner, Stamford, USA.Google Scholar
  43. Schulte, R.; Natis, Y. (1996), “’Service oriented’ architectures, part 1”, Gartner Research ID Number SPA-401-068, Gartner, Stamford, USA.Google Scholar
  44. Sommerville, I. (2001), Software engineering, 6th edn, Pearson, Munich.Google Scholar
  45. Szyperski, C. (1998), Component software: Beyond object-oriented programming, Addison Wesley, Harlow, UK.Google Scholar
  46. Teubner, A. (2006), “IT/business alignment”, Wirtschaftsinformatik, 48 (5): 368–371.CrossRefGoogle Scholar
  47. Turowski, K. (2003), Fachkamponenten: Komponentenbasierte betriebliche Anwendungssysteme, Shaker, Aachen.Google Scholar
  48. Voas, J. (2001), “Faster, better, and cheaper”, IEEE Software, 18 (3): 96–97.CrossRefGoogle Scholar
  49. Wassermann, A.; Gutz, S. (1982), “The future of programming”, Communications of the ACM, 25 (3): 196–206.CrossRefGoogle Scholar
  50. Wikipedia (2009), “Observable universe”, accessed on 17 Jul 2009,
  51. Wissenschaftliche Kommission Wirtschaftsinformatik (1994), “Profil der Wirtschaftsinformatik”, Wirtschaftsintormatik, 36 (1): 80–81Google Scholar
  52. Wissenschaftliche Kommission Wirtschaftsinformatik (2003), Rahmenempfehlung für die Universitätsausbildung in wirtschaftsinformatik, Gesellschaft für Informatik, Bonn.Google Scholar

Copyright information

© Gabler Verlag | Springer Fachmedien Wiesbaden GmbH 2010

Authors and Affiliations

  • Oliver Skroch

There are no affiliations available

Personalised recommendations