Software Engineering – Processes and Tools

  • Gerhard Weiß
  • Gustav Pomberger
  • Wolfgang Beer
  • Georg Buchgeher
  • Bernhard Dorninger
  • Josef Pichler
  • Herbert Prähofer
  • Rudolf Ramler
  • Fritz Stallinger
  • Rainer Weinreich


Software engineering traditionally plays an important role among the different research directions located in the Software Park Hagenberg, as it provides the fundamental concepts, methods and tools for producing reliable and high quality software. Software engineering as a quite young profession and engineering discipline is not limited to focus on how to create simple software programs, but in fact introduces a complex and most of the time quite costly lifecycle of software and derived products. Some efforts have been made to define software engineering as a profession and to outline the boundaries of this emerging field of research [PP04, Som04]. Several different definitions of the term software engineering appeared since its first mentioning on a NATO Software Engineering Conference in 1968.


Software Engineering Software Process Software Architecture Software Quality Software Product Line 
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. [ABD+04]
    Alain Abran, Pierre Bourque, Robert Dupuis, James W. Moore, and Leonard L. Tripp. Guide to the Software Engineering Body of Knowledge - SWEBOK. IEEE Press, Piscataway, NJ, USA, 2004 version edition, 2004.Google Scholar
  2. [AGM05]
    Paris Avgeriou, Nicolas Guelfi, and Nenad Medvidovic. Software architecture description and uml. pages 23–32. 2005.Google Scholar
  3. [AMS08]
    Lennart Augustsson, Howard Mansell, and Ganesh Sittampalam. Paradise: a two-stage dsl embedded in haskell. In ICFP ’08: Proceeding of the 13th ACM SIGPLAN international conference on Functional programming, pages 225–228, New York, NY, USA, 2008. ACM.Google Scholar
  4. [BA04]
    Kent Beck and Cynthia Andres. Extreme Programming Explained: Embrace Change (2nd Edition). Addison-Wesley Professional, 2 edition, November 2004.Google Scholar
  5. [BAB+05]
    Stefan Biffl, Aybüke Aurum, Barry Boehm, Hakan Erdogmus, and Paul Grünbacher. Value-Based Software Engineering. Springer Verlag, oct 2005.Google Scholar
  6. [Bac97]
    James Bach. Good enough quality: Beyond the buzzword. Computer, 30(8):96–98, 1997.CrossRefGoogle Scholar
  7. [BCK03]
    Len Bass, Paul Clements, and Rick Kazman. Software Architecture in Practice, Second Edition. Addison-Wesley Professional, April 2003.Google Scholar
  8. [BD04]
    Pierre Bourque and Robert Dupuis, editors. SWEBOK - Guide to the Software Engineering Body of Knowledge, 2004 Version. IEEE Computer Society, 2004 version edition, 2004.Google Scholar
  9. [Bec02]
    Kent Beck. Test Driven Development: By Example. Addison-Wesley Professional, November 2002.Google Scholar
  10. [Bei90]
    Boris Beizer. Software Testing Techniques 2E. International Thomson Computer Press, 2nd edition, June 1990.Google Scholar
  11. [BG00]
    Kent Beck and Erich Gamma. More Java Gems, chapter Test-infected: programmers love writing tests, pages 357–376. Cambridge University Press, 2000.Google Scholar
  12. [Boe76]
    B. W. Boehm. Software engineering. Transactions on Computers, C-25(12):1226–1241, 1976.CrossRefGoogle Scholar
  13. [Boe88]
    B. W. Boehm. A spiral model of software development and enhancement. Computer, 21(5):61–72, May 1988.CrossRefGoogle Scholar
  14. [BR08]
    Armin Beer and Rudolf Ramler. The role of experience in software testing practice. In Proceedings of the 34th EUROMICRO Conference on Software Engineering and Advanced Applications, pages 258–265, Parma, Italy, 2008. IEEE Computer Society.Google Scholar
  15. [Bru01]
    H. Bruyninckx. Open robot control software: the OROCOS project. In Robotics and Automation, 2001. Proceedings 2001 ICRA. IEEE International Conference on, volume 3, pages 2523–2528 vol.3, 2001.Google Scholar
  16. [BW08]
    Georg Buchgeher and Rainer Weinreich. Integrated software architecture management and validation. In Software Engineering Advances, 2008. ICSEA ’08. The Third International Conference on, pages 427–436, 2008.Google Scholar
  17. [BWK05]
    Stefan Berner, Roland Weber, and Rudolf K. Keller. Observations and lessons learned from automated testing. In Proceedings of the 27th international conference on Software engineering, pages 571–579, St. Louis, MO, USA, 2005. ACM.Google Scholar
  18. [CBB+02]
    Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Robert Nord, and Judith Stafford. Documenting Software Architectures: Views and Beyond. Addison-Wesley Professional, September 2002.Google Scholar
  19. [CEC00]
    Krzysztof Czarnecki, Ulrich Eisenecker, and Krzysztof Czarnecki. Generative Programming: Methods, Tools, and Applications. Addison-Wesley Professional, June 2000.Google Scholar
  20. [CH03]
    Krzysztof Czarnecki and Simon Helsen. Classification of model transformation approaches. In Proceedings of the 2nd OOPSLA Workshop on Generative Techniques in the Context of MDA, 2003.Google Scholar
  21. [Cha05]
    R. N. Charette. Why software fails. IEEE Spectrum, 42(9):42–49, September 2005.CrossRefGoogle Scholar
  22. [Chr92]
    Gerhard Chroust. Modelle der SoftwareEntwicklung. Oldenbourg Verlag München Wien, 1992. in German.Google Scholar
  23. [CJKW07]
    Steve Cook, Gareth Jones, Stuart Kent, and Alan C. Wills. Domain Specific Development with Visual Studio DSL Tools (Microsoft .Net Development). Addison-Wesley Longman, Amsterdam, May 2007.Google Scholar
  24. [CKK02]
    Paul Clements, Rick Kazman, and Mark Klein. Evaluating Software Architectures: Methods and Case Studies. Addison-Wesley Professional, January 2002.Google Scholar
  25. [Cle95]
    Paul Clements. Formal methods in describing architectures. In Monterey Workshop on Formal Methods and Architecture, September 1995.Google Scholar
  26. [Cle96]
    Paul C. Clements. A survey of architecture description languages. In IWSSD ’96: Proceedings of the 8th International Workshop on Software Specification and Design, Washington, DC, USA, 1996. IEEE Computer Society.Google Scholar
  27. [CMM06]
    CMMI for development, version 1.2. Technical report CMU/SEI-2006-TR-008, Carnegie Mellon University, Software Engineering Institute, Pittsburgh, PA 15213-3890, August 2006.Google Scholar
  28. [CN02]
    P. Clements and L. N. Northrop. Software Product Lines: Practices and Patterns. Addison Wesley Professional Series: The SEI Series in Software Engineering. Addison Wesley, 2002.Google Scholar
  29. [Cop04]
    Lee Copeland. A Practitioner’s Guide to Software Test Design. Artech House Publishers, 2004.Google Scholar
  30. [Cza05]
    Krzysztof Czarnecki. Overview of generative software development. pages 326–341. 2005.Google Scholar
  31. [DeM86]
    T. DeMarco. Controlling Software Projects: Management, Measurement, and Estimates. Prentice Hall PTR, Upper Saddle River, NJ, USA, 1986.Google Scholar
  32. [Dio93]
    R. Dion. Process improvement and the corporate balance sheet. IEEE Software, pages 28–35, July 1993.Google Scholar
  33. [DN02]
    L. Dobrica and E. Niemela. A survey on software architecture analysis methods. Software Engineering, IEEE Transactions on, 28(7):638–653, 2002.CrossRefGoogle Scholar
  34. [Dor93]
    Alec Dorling. Software Process Improvement and Capability Determination. Software Quality Journal, 2(4):209–224, December 1993. also in: Information and Software Technology, vol. 35, no. 6/7, June 1993, p. 404.Google Scholar
  35. [Dor09]
    Bernhard Dorninger. ProMoRTE: A process model runtime environment based on OSGi. 2009. accepted for publication at 7th IEEE International Conference on Industrial Informatics (INDIN 2009).Google Scholar
  36. [Dou02]
    Bruce Powell Douglass. Real-Time Design Patterns: Robust Scalable Architecture for Real-Time Systems. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 2002.Google Scholar
  37. [DW06]
    Patricia Derler and Rainer Weinreich. Models and tools for soa governance. In International Conference on Trends in Enterprise Application Architecture. Springer Lecture Notes on Computer Science (LNCS), December 2006.Google Scholar
  38. [Eck05]
    Wayne W. Eckerson. Performance Dashboards: Measuring, Monitoring, and Managing Your Business. Wiley, October 2005.Google Scholar
  39. [EJB06]
    Enterprise javabeans 3.0 specification, 2006.Google Scholar
  40. [EK07]
    Andrew D. Eisenberg and Gregor Kiczales. Expressive programs through presentation extension. In AOSD ’07: Proceedings of the 6th international conference on Aspect-oriented software development, pages 73–84, New York, NY, USA, 2007. ACM.Google Scholar
  41. [FG99]
    Mark Fewster and Dorothy Graham. Software Test Automation. Addison-Wesley Professional, September 1999.Google Scholar
  42. [FJ99]
    Mohamed Fayad and Ralph Johnson. Domain-Specific Application Frameworks: Frameworks Experience by Industry. John Wiley & Sons, October 1999.Google Scholar
  43. [FPC97]
    William A. Florac, Robert E. Park, and Anita D. Carleton. Practical software measurement: Measuring for process management and improvement. Guidebook CMU/SEI-97-HB-003, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213, April 1997.Google Scholar
  44. [Gar84]
    David A. Garvin. What does product quality really mean? Sloan Management Review, 26(1):25–45, Fall 1984.Google Scholar
  45. [Gar00]
    David Garlan. Software architecture: a roadmap. In ICSE ’00: Proceedings of the Conference on The Future of Software Engineering, pages 91–101, New York, NY, USA, 2000. ACM Press.Google Scholar
  46. [GBU08]
    Thomas Goldschmidt, Steffen Becker, and Axel Uhl. Classification of concrete textual syntax mapping approaches. pages 169–184. 2008.Google Scholar
  47. [GJ96]
    Pankaj K. Garg and Mehdi Jazayeri, editors. ProcessCentered Software Engineering Environments. IEEE Computer Society Press, 1996.Google Scholar
  48. [Gre07]
    J. Grenning. Applying test driven development to embedded software. Instrumentation & Measurement Magazine, IEEE, 10(6):20–25, 2007.CrossRefGoogle Scholar
  49. [Ham04]
    Paul Hamill. Unit Test Frameworks. O’Reilly Media, Inc., October 2004.Google Scholar
  50. [HB06]
    LiGuo Huang and Barry Boehm. How much software quality investment is enough: A Value-Based approach. IEEE Software, 23(5):88–95, 2006.CrossRefGoogle Scholar
  51. [HCR+94]
    James Herbsleb, Anita Carleton, James Rozum, Jane Siegel, and David Zubrow. Benefits of CMM-based software process improvement: Initial results. Technical Report CMU/SEI-94-TR-013, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania 15213, August 1994.Google Scholar
  52. [Hel07]
    Hello2morro. Sonarj., 2007.Google Scholar
  53. [HHK+08]
    Walter Hargassner, Thomas Hofer, Claus Klammer, Josef Pichler, and Gernot Reisinger. A script-based testbed for mobile software frameworks. In Proceedings of the First International Conference on Software Testing, Verification and Validation, pages 448–457. IEEE, April 2008.Google Scholar
  54. [HNS99]
    Christine Hofmeister, Robert Nord, and Dilip Soni. Applied Software Architecture. Addison-Wesley Professional, November 1999.Google Scholar
  55. [Hof05]
    Christine Hofmeister. Architecting session report. In WICSA ’05: Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA’05), pages 209–210, Washington, DC, USA, 2005. IEEE Computer Society.Google Scholar
  56. [HSSL02]
    B. Henderson-Sellers, F. Stallinger, and B. Lefever. Bridging the gap from process modelling to process assessment: the OOSPICE process specification for component-based software engineering. In Proceedings of the 28th Euromicro Conference, pages 324–331. IEEE Computer Society, 2002.Google Scholar
  57. [HT06]
    Brent Hailpern and Peri Tarr. Model-driven development: The good, the bad, and the ugly. IBM Systems Journal, 45(3):451–461, July 2006.CrossRefGoogle Scholar
  58. [Hum89]
    W. Humphrey. Managing the Software Process. AddisonWesley Reading Mass., 1989.Google Scholar
  59. [Hum95]
    W. Humphrey. A Discipline for Software Engineering. SEI Series in Software engineering. AddisonWesley, 1995.Google Scholar
  60. [IEE90]
    IEEE Std 610.12-1990: IEEE standard glossary of software engineering terminology, 1990.Google Scholar
  61. [IMP05]
    P. Inverardi, H. Muccini, and P. Pelliccione. Dually: Putting in synergy uml 2.0 and adls. In WICSA ’05: Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture, pages 251–252, Washington, DC, USA, 2005. IEEE Computer Society.Google Scholar
  62. [Int08]
    International Organization for Standardization (ISO). Systems and software engineering - architectural description working draft 3, 2008.Google Scholar
  63. [ISO95]
    ISO/IEC 12207:1995, Information technology - Software life cycle processes, 1995. Amd.1:2002; Amd.2:2004.Google Scholar
  64. [ISO98]
    ISO/IEC TR 15504-7:1998(e), Information technology - Software process assessment - Part 7: Guide for use in process improvement, 1998.Google Scholar
  65. [ISO01]
    ISO/IEC 9126-1:2001, Software engineering - Product quality - Part 1: Quality model, 2001.Google Scholar
  66. [ISO03]
    ISO/IEC 15504:2003, Information Technology - Process Assessment, 2003.Google Scholar
  67. [ISO05]
    ISO/IEC 25000:2005, Software engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Guide to SQuaRE, 2005.Google Scholar
  68. [ISO09]
    ISO/IEC PDTR 29110:2009, Software Engineering - Lifecycle Profiles for Very Small Enterprises (VSE), January 2009.Google Scholar
  69. [JBK06]
    Frédéric Jouault, Jean Bézivin, and Ivan Kurtev. Tcs: a dsl for the specification of textual concrete syntaxes in model engineering. In GPCE ’06: Proceedings of the 5th international conference on Generative programming and component engineering, pages 249–254, New York, NY, USA, 2006. ACM.Google Scholar
  70. [JGJ97]
    I. Jacobson, M. Griss, and P. Jonsson. Software Reuse: Architecture, Process and Organization for Business Success. Addison-Wesley Professional, 1997.Google Scholar
  71. [Joh99]
    Ralph E. Johnson. Building Application Frameworks: Object-Oriented Foundations of Framework Design. John Wiley & Sons, 1 edition, September 1999.Google Scholar
  72. [Kan02]
    Stephen H. Kan. Metrics and Models in Software Quality Engineering. Addison-Wesley Longman Publishing, 2002.Google Scholar
  73. [KC04]
    Ralph Kimball and Joe Caserta. The Data Warehouse ETL Toolkit: Practical Techniques for Extracting, Cleaning, Conforming, and Delivering Data. Wiley, September 2004.Google Scholar
  74. [KFN99]
    Cem Kaner, Jack Falk, and Hung Q. Nguyen. Testing Computer Software. Wiley, 2 edition, April 1999.Google Scholar
  75. [Kin01]
    Atte Kinnula. Software Process Engineering Systems: Models and Industry Cases. Oulu University Press, 2001. ISBN 951-42-6508-4.Google Scholar
  76. [KL05]
    A.G. Koru and H. Liu. Building effective defect-prediction models in practice. IEEE Software, 22(6):23–29, 2005.CrossRefGoogle Scholar
  77. [KOS06]
    P. Kruchten, H. Obbink, and J. Stafford. The past, present, and future for software architecture. Software, IEEE, 23(2):22–30, 2006.CrossRefGoogle Scholar
  78. [Kru95]
    Philippe Kruchten. The 4+1 view model of architecture. IEEE Softw., 12(6):42–50, November 1995.CrossRefGoogle Scholar
  79. [Kru03]
    Philippe Kruchten. The Rational Unified Process: An Introduction. Addison-Wesley, 3rd edition, 2003. ISBN 0321197704, 9780321197702.Google Scholar
  80. [KRV07]
    Holger Krahn, Bernhard Rumpe, and Steven Völkel. Integrated definition of abstract and concrete syntax for textual languages. pages 286–300. 2007.Google Scholar
  81. [KT08]
    Steven Kelly and Juha-Pekka Tolvanen. Domain-Specific Modeling: Enabling Full Code Generation. John Wiley & Sons, March 2008.Google Scholar
  82. [KWB03]
    Anneke Kleppe, Jos Warmer, and Wim Bast. MDA Explained: The Model Driven Architecture–Practice and Promise. Addison-Wesley Professional, April 2003.Google Scholar
  83. [KWZ09]
    Thomas Kriechbaum, Rainer Weinreich, and Thomas Ziebermayr. Compatibility rules for the homogeneous evolution of enterprise services. In International Symposium on Service Science (ISSS), pages 189–200. Logos Verlag Berlin, March 2009.Google Scholar
  84. [LBB+05]
    U. Löwen, R. Bertsch, B. Böhm, S. Prummer, and T. Tetzner. Systematisierung des Engineerings von Industrieanlagen. atp - Automatisierungstechnische Praxis, Oldenbourg Industrieverlag, (4):54–61, 2005. in German.Google Scholar
  85. [LH93]
    Wei Li and Sallie Henry. Object-oriented metrics that predict maintainability. J. Syst. Softw., 23(2):111–122, November 1993.CrossRefGoogle Scholar
  86. [LH09]
    Henrik Lochmann and Anders Hessellund. An integrated view on modeling with multiple domain-specific languages. In Proceedings of the IASTED International Conference Software Engineering (SE 2009), pages 1–10. ACTA Press, February 2009.Google Scholar
  87. [LJJ07]
    B. Langlois, C. E. Jitia, and E. Jouenne. Dsl classification. In Proceedings of the 7th OOPSLA Workshop on Domain-Specific Modeling, 2007.Google Scholar
  88. [LKT04]
    Janne Luoma, Steven Kelly, and Juha-Pekka Tolvanen. Defining domainspecific modeling languages: Collected experiences. Proceedings of the 4th OOPSLA Workshop on Domain-Specific Modeling, 2004.Google Scholar
  89. [Lon93]
    J. Lonchamp. A structured conceptual and terminological framework for software process engineering. In Software Process, 1993. Continuous Software Process Improvement, Second International Conference on the, pages 41–53, Feb 1993.Google Scholar
  90. [LR07]
    Stefan Larndorfer and Rudolf Ramler. TestCockpit: business intelligence for test management. In Work in Progress Session in conjunction with 33rd EUROMICRO Conf. on Software Engineering and Advanced Applications, 2007.Google Scholar
  91. [LRB09]
    Stefan Larndorfer, Rudolf Ramler, and Clemens Buchwiser. Experiences and results from establishing a software cockpit. In upcoming, 2009.Google Scholar
  92. [LRFL07]
    Stefan Larndorfer, Rudolf Ramler, Christian Federspiel, and Klaus Lehner. Testing High-Reliability software for continuous casting steel plants - experiences and lessons learned from siemens VAI. In Proceedings of the 33rd EUROMICRO Conference on Software Engineering and Advanced Applications, pages 255–262, Luebeck, Germany, 2007. IEEE Computer Society.Google Scholar
  93. [McF96]
    Bob McFeeley. IDEAL: A user’s guide for software process improvement. Handbook CMU/SEI-96-HB-001, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania 15213, February 1996.Google Scholar
  94. [MD08]
    Tom Mens and Serge Demeyer. Software Evolution. Springer Verlag, March 2008.Google Scholar
  95. [MDT07]
    Nenad Medvidovic, Eric M. Dashofy, and Richard N. Taylor. Moving architectural description from under the technology lamppost. Information and Software Technology, 49(1):12–31, January 2007.CrossRefGoogle Scholar
  96. [MFF+06]
    Pierre-Alain Muller, Franck Fleurey, Frédéric Fondement, Michel Hassenforder, Rémi Schneckenburger, Sébastien Gérard, and Jean-Marc Jézéquel. Model-Driven Analysis and Synthesis of Concrete Syntax. 2006.Google Scholar
  97. [MGF07]
    T. Menzies, J. Greenwald, and A. Frank. Data mining static code attributes to learn defect predictors. IEEE Transactions on Software Engineering, 33(1):2–13, 2007.CrossRefGoogle Scholar
  98. [MH04]
    Jürgen Münch and Jens Heidrich. Software project control centers: concepts and approaches. Journal of Systems and Software, 70(1-2):3–19, February 2004.CrossRefGoogle Scholar
  99. [Mil02]
    Dave Miller. Fundamental Concepts for the Software Quality Engineer, chapter Choice and Application of a Software Quality Model, pages 17–24. ASQ Quality Press, 2002.Google Scholar
  100. [MK08]
    Jennifer Mcginn and Nalini Kotamraju. Data-driven persona development. In CHI ’08: Proceeding of the twenty-sixth annual SIGCHI conference on Human factors in computing systems, pages 1521–1524, New York, NY, USA, 2008. ACM.Google Scholar
  101. [MKB06]
    Brad A. Myers, Andrew J. Ko, and Margaret M. Burnett. Invited research overview: end-user programming. In CHI ’06: CHI ’06 extended abstracts on Human factors in computing systems, pages 75–80, New York, NY, USA, 2006. ACM.Google Scholar
  102. [MKMG97]
    R. T. Monroe, A. Kompanek, R. Melton, and D. Garlan. Architectural styles, design patterns, and objects. Software, IEEE, 14(1):43–52, 1997.CrossRefGoogle Scholar
  103. [MMYA01]
    H. Mili, A. Mili, S. Yacoub, and E. Addy. Reuse-Based Software Engineering: Techniques, Organizations, and Controls. Wiley-Interscience, 2001.Google Scholar
  104. [MT00]
    Nenad Medvidovic and Richard N. Taylor. A classification and comparison framework for software architecture description languages. IEEE Trans. Softw. Eng., 26(1):70–93, January 2000.CrossRefGoogle Scholar
  105. [NBZ06]
    Nachiappan Nagappan, Thomas Ball, and Andreas Zeller. Mining metrics to predict component failures. In Proceedings of the 28th international conference on Software engineering, pages 452–461, Shanghai, China, 2006. ACM.Google Scholar
  106. [Obj07]
    Object Management Group. Uml superstructure specification v2.1.1. OMG Document Number formal/07-02-05, 2007.Google Scholar
  107. [Obj08]
    Object Management Group. Software & systems process engineering metamodel specification, version 2.0., April 2008.Google Scholar
  108. [Ope08]
    OpenUP - Open Unified Process, 2008. Scholar
  109. [OSG07]
    Osgi service platform release 4, 2007.Google Scholar
  110. [PCCW93]
    Mark C. Paulk, Bill Curtis, Mary Beth Chrissis, and Charles V. Weber. Capability maturity model for software, version 1.1. Technical Report CMU/SEI-93-TR-02, Software Engineering Institute, Carnegie Mellon University, February 1993.Google Scholar
  111. [PGP08]
    F. Pino, F. Garcia, and M. Piattini. Software process improvement in small and medium software enterprises: A systematic review. Software Quality Journal, 16(2):1573–1367, June 2008.CrossRefGoogle Scholar
  112. [PHS+08a]
    Herbert Prähofer, Dominik Hurnaus, Roland Schatz, Christian Wirth, and Hanspeter Mössenböck. Monaco: A dsl approach for programming automation systems. In SE 2008 - Software-Engineering-Konferenz 2008, pages 242–256, Munic, Germay, February 2008.Google Scholar
  113. [PHS+08b]
    Herbert Prähofer, Dominik Hurnaus, Roland Schatz, Christian Wirth, and Hanspeter Mössenböck. Software support for building end-user programming environments in the automation domain. In WEUSE ’08: Proceedings of the 4th international workshop on End-user software engineering, pages 76–80, New York, NY, USA, 2008. ACM.Google Scholar
  114. [PP04]
    Gustav Pomberger and Wolfgang Pree. Software Engineering. Hanser Fachbuchverlag, October 2004.Google Scholar
  115. [PP08]
    Michael Pfeiffer and Josef Pichler. A comparison of tool support for textual domain-specific languages. Proceedings of the 8th OOPSLA Workshop on Domain-Specific Modeling, pages 1–7, October 2008.Google Scholar
  116. [PP09]
    Michael Pfeiffer and Josef Pichler. A DSM approach for End-User Programming in the Automation Domain. 2009. accepted for publication at 7th IEEE International Conference on Industrial Informatics (INDIN 2009).Google Scholar
  117. [PPRL07]
    Josef Pichler, Herbert Praehofer, Gernot Reisinger, and Gerhard Leonhartsberger. Aragon: an industrial strength eclipse tool for MMI design for mobile systems. In Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering, pages 156–163, Innsbruck, Austria, 2007. ACTA Press.Google Scholar
  118. [PR08]
    Josef Pichler and Rudolf Ramler. How to test the intangible properties of graphical user interfaces? In Proceedings of the 2008 International Conference on Software Testing, Verification, and Validation, ICST 08, pages 494–497. IEEE Computer Society, 2008.Google Scholar
  119. [PRS00]
    G. Pomberger, M. Rezagholi, and C. Stobbe. Handbuch für Evaluation und Evaluierungsforschung in der Wirtschaftsinformatik, chapter Evaluation und Verbesserung wiederverwendungsorientierter Software-Entwicklung. Oldenbourg Verlag, München/Wien, 2000. in German.Google Scholar
  120. [PRZ09]
    Guenter Pirklbauer, Rudolf Ramler, and Rene Zeilinger. An integrationoriented model for application lifecycle management. 2009. accepted for ICEIS 2009, 11th International Conference on Enterprise Information Systems.Google Scholar
  121. [PSN08]
    R. Plösch, F. Stallinger, and R. Neumann. SISB - systematic improvement of the solution business: Engineering strategies for the industrial solutions business, version 1.0. Technical report, Software Competence Center Hagengerg, August 2008. (non-public project deliverable).Google Scholar
  122. [PW92]
    Dewayne E. Perry and Alexander L. Wolf. Foundations for the study of software architecture. SIGSOFT Softw. Eng. Notes, 17(4):40–52, October 1992.CrossRefGoogle Scholar
  123. [Ram04]
    Rudolf Ramler. Decision support for test management in iterative and evolutionary development. In Proceedings of the 19th IEEE international conference on Automated software engineering, pages 406–409, Linz, Austria, 2004. IEEE Computer Society.Google Scholar
  124. [Ram08]
    Rudolf Ramler. The impact of product development on the lifecycle of defects. In Proceedings of the DEFECTS 2008 Workshop on Defects in Large Software Systems, pages 21–25, Seattle, Washington, 2008. ACM.Google Scholar
  125. [RBG05]
    Rudolf Ramler, Stefan Biffl, and Paul Grünbacher. Value-Based Software Engineering, chapter Value-Based Management of Software Testing, pages 225–244. Springer Verlag, 2005.Google Scholar
  126. [RCS03]
    Rudolf Ramler, Gerald Czech, and Dietmar Schlosser. Unit testing beyond a bar in green and red. In Proceedings of the 4th International Conference on Extreme Programming and Agile Processes in Software Engineering, XP 2003, pages 10–12, Genova, Italy, 2003. LNCS.Google Scholar
  127. [Roy70]
    W. W. Royce. Managing the development of large software systems:: Concepts and techniques. In Proc. IEEE WESCON, pages 1–9. IEEE, August 1970.Google Scholar
  128. [RR99]
    Arthur A. Reyes and Debra J. Richardson. Siddhartha: a method for developing domain-specific test driver generators. In In Proc. 14th Int. Conf. on Automated Software Engineering, pages 12–15, 1999.Google Scholar
  129. [RvW07]
    Ita Richardson and Christiane Gresse von Wangenheim. Why are small software organizations different? IEEE Software, 24(1):18–22, January/February 2007.CrossRefGoogle Scholar
  130. [RW05]
    Nick Rozanski and Eóin Woods. Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Addison-Wesley Professional, April 2005.Google Scholar
  131. [RW06]
    Rudolf Ramler and Klaus Wolfmaier. Economic perspectives in test automation: balancing automated and manual testing with opportunity cost. In Proceedings of the 2006 international workshop on Automation of software test, pages 85–91, Shanghai, China, 2006. ACM.Google Scholar
  132. [RW08]
    Rudolf Ramler and Klaus Wolfmaier. Issues and effort in integrating data from heterogeneous software repositories and corporate databases. In Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement, pages 330–332, Kaiserslautern, Germany, 2008. ACM.Google Scholar
  133. [RWS+09]
    Rudolf Ramler, Klaus Wolfmaier, Erwin Stauder, Felix Kossak, and Thomas Natschläger. Key questions in building defect prediction models in practice. In 10th International Conference on Product Focused Software Development and Process Improvement, PROFES 2009, Oulu, Finnland, 2009.Google Scholar
  134. [RWW+02]
    Rudolf Ramler, Edgar Weippl, Mario Winterer, Wieland Schwinger, and Josef Altmann. A quality-driven approach to web testing. In Ibero-american Conference on Web Engineering, ICWE 2002, pages 81–95, Argentina, 2002.Google Scholar
  135. [Sad08]
    Daniel A. Sadilek. Prototyping domain-specific language semantics. In OOPSLA Companion ’08: Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications, pages 895–896, New York, NY, USA, 2008. ACM.Google Scholar
  136. [Sam01]
    J. Sametinger. Software Engineering with Reusable Components. Springer, 2001.Google Scholar
  137. [SB03]
    Douglas C. Schmidt and Frank Buschmann. Patterns, frameworks, and middleware: their synergistic relationships. In ICSE ’03: Proceedings of the 25th International Conference on Software Engineering, pages 694–704, Washington, DC, USA, 2003. IEEE Computer Society.Google Scholar
  138. [SBPM09]
    David Steinberg, Frank Budinsky, Marcelo Paternostro, and Ed Merks. EMF: Eclipse Modeling Framework (2nd Edition) (Eclipse). Addison-Wesley Longman, Amsterdam, 2nd revised edition (rev). edition, January 2009.Google Scholar
  139. [SCA07]
    Service component architecture specifications, 2007.Google Scholar
  140. [Sch06]
    D. C. Schmidt. Guest editor’s introduction: Model-driven engineering. Computer, 39(2):25–31, 2006.CrossRefGoogle Scholar
  141. [SDR+02]
    F. Stallinger, A. Dorling, T. Rout, B. Henderson-Sellers, and B. Lefever. Software process improvement for component-based software engineering: an introduction to the OOSPICE project. In Proceedings of the 28th Euromicro Conference, pages 318–323. IEEE Computer Society, 2002.Google Scholar
  142. [Sha90]
    M. Shaw. Prospects for an engineering discipline of software. Software, IEEE, 7(6):15–24, Nov 1990.CrossRefGoogle Scholar
  143. [She31]
    Walter A. Shewhart. Economic control of quality of manufactured product. D. Van Nostrand Company, New York, 1931.Google Scholar
  144. [SJSJ05]
    Neeraj Sangal, Ev Jordan, Vineet Sinha, and Daniel Jackson. Using dependency models to manage complex software architecture. SIGPLAN Not., 40(10):167–176, October 2005.CrossRefGoogle Scholar
  145. [Sof07]
    Software Tomography GmbH. Sotoarc., 2007.Google Scholar
  146. [Som04]
    Ian Sommerville. Software Engineering. Addison Wesley, seventh edition, May 2004.Google Scholar
  147. [SPP+06]
    F. Stallinger, R. Plösch, H. Prähofer, S. Prummer, and J. Vollmar. A process reference model for reuse in industrial engineering: Enhancing the ISO/IEC 15504 framework to cope with organizational reuse maturity. In Proc. SPICE 2006, Luxembourg, May 4-5, 2006, pages 49–56, May 2006.Google Scholar
  148. [SPPV09]
    Fritz Stallinger, Reinhold Plösch, Gustav Pomberger, and Jan Vollmar. Bridging the gap between ISO/IEC 15504 conformant process assessment and organizational reuse enhancement. 2009. (accepted for SPICE Conference 2009, Software Process Improvement and Capability Determination, 2-4 June 2009, Turku, Finland).Google Scholar
  149. [Spr08a]
    Spring dynamic modules for osgi(tm) service platforms, 2008.Google Scholar
  150. [Spr08b]
    The spring framework - reference documentation, 2008.Google Scholar
  151. [SPV07]
    F. Stallinger, R. Plösch, and J. Vollmar. A process assessment based approach for improving organizational reuse maturity in multidisciplinary industrial engineering contexts. In Proceedings of ESEPG 2007, Amsterdam, 14th June 2007, June 2007.Google Scholar
  152. [SRA06]
    Christoph Steindl, Rudolf Ramler, and Josef Altmann. Web Engineering: The Discipline of Systematic Development of Web Applications, chapter Testing Web Applications, pages 133–153. Wiley, 2006.Google Scholar
  153. [SSM03]
    A. Sinha, C. S. Smidts, and A. Moran. Enhanced testing of domain specific applications by automatic extraction of axioms from functional specifications. In Software Reliability Engineering, 2003. ISSRE 2003. 14th International Symposium on, pages 181–190, 2003.Google Scholar
  154. [Ste00]
    David B. Stewart. Designing software components for real-time applications. In in Proceedings of Embedded System Conference, page 428, 2000.Google Scholar
  155. [Tas02]
    Gregory Tassy. The economic impacts of inadequate infrastructure for software testing, NIST planning report 02-3, May 2002.Google Scholar
  156. [Tia05]
    Jeff Tian. Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement. Wiley & Sons, 1., auflage edition, February 2005.Google Scholar
  157. [TK05]
    Juha-Pekka Tolvanen and Steven Kelly. Defining domain-specific modeling languages to automate product derivation: Collected experiences. pages 198–209. 2005.Google Scholar
  158. [TMD09]
    R. N. Taylor, Nenad Medvidovi, and Irvine E. Dashofy. Software Architecture: Foundations, Theory, and Practice. John Wiley & Sons, January 2009.Google Scholar
  159. [TvdH07]
    Richard N. Taylor and Andre van der Hoek. Software design and architecture the once and future focus of software engineering. In FOSE ’07: 2007 Future of Software Engineering, pages 226–243, Washington, DC, USA, 2007. IEEE Computer Society.Google Scholar
  160. [V-M06]
    V-Modell XT, part1: Fundamentals of the V-Modell XT, version 1.2.1. Technical report, 2006. Scholar
  161. [vDKV00]
    Arie v. van Deursen, Paul Klint, and Joost Visser. Domain-specific languages: An annotated bibliography. SIGPLAN Notices, 35(6):26–36, 2000.CrossRefGoogle Scholar
  162. [vGB02]
    Jilles van Gurp and Jan Bosch. Design erosion: problems and causes. Journal of Systems and Software, 61(2):105–119, March 2002.CrossRefGoogle Scholar
  163. [Voa08]
    Jeffrey Voas. Software quality unpeeled. STSC CrossTalk, (Jun 2008):27–30, 2008.Google Scholar
  164. [VRM03]
    M. Venzin, C. Rasner, and V. Mahnke. Der Strategieprozess - Praxishandbuch zur Umsetzung im Unternehmen. 2003. in German.Google Scholar
  165. [VS06]
    Markus Völter and Thomas Stahl. Model-Driven Software Development : Technology, Engineering, Management. John Wiley & Sons, June 2006.Google Scholar
  166. [Was96]
    A.I. Wasserman. Toward a discipline of software engineering. Software, IEEE, 13(6):23–31, Nov 1996.CrossRefGoogle Scholar
  167. [Was06]
    Hironori Washizaki. Product-Focused Software Process Improvement, volume 4034 of Lecture Notes in Computer Science, chapter Building Software Process Line Architectures from Bottom Up, pages 415–421. Springer Berlin / Heidelberg, 2006.CrossRefGoogle Scholar
  168. [WH05]
    Eoin Woods and Rich Hilliard. Architecture description languages in practice session report. In WICSA ’05: Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA’05), pages 243–246, Washington, DC, USA, 2005. IEEE Computer Society.Google Scholar
  169. [WV02]
    James A. Whittaker and Jeffrey M. Voas. 50 years of software: Key principles for quality. IT Professional, 4(6):28–35, 2002.CrossRefGoogle Scholar
  170. [WWZ07]
    Rainer Weinreich, Andeas Wiesauer, and Thomas Ziebermayr. A component model for integrating remote applications and services via web portals. Journal of Object Technology (JOT), 6(8), September 2007.Google Scholar
  171. [WZ05]
    Rainer Weinreich and Thomas Ziebermayr. Enhancing presentation level integration of remote applications and services in web portals. In 2005 IEEE International Conference on Services Computing (SCC’05), volume 2, pages 224–236, Los Alamitos, CA, USA, 2005. IEEE Computer Society.Google Scholar
  172. [WZD07]
    Rainer Weinreich, Thomas Ziebermayr, and Dirk Draheim. A versioning model for enterprise services. In 21st International Conference on Advanced Information Networking and Applications Workshops (AINAW’07), volume 2, pages 570–575, Los Alamitos, CA, USA, 2007. IEEE Computer Society.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Gerhard Weiß
    • 1
  • Gustav Pomberger
    • 2
  • Wolfgang Beer
    • 1
  • Georg Buchgeher
    • 1
  • Bernhard Dorninger
    • 1
  • Josef Pichler
    • 1
  • Herbert Prähofer
    • 3
  • Rudolf Ramler
    • 1
  • Fritz Stallinger
    • 1
  • Rainer Weinreich
    • 2
  1. 1.Software Competence Center Hagenberg (SCCH)HagenbergAustria
  2. 2.Institute of Business Informatics – Software EngineeringJohannes Kepler University Linz (JKU)LinzAustria
  3. 3.Institute for System SoftwareJohannes Kepler University Linz (JKU)LinzAustria

Personalised recommendations