Process-based software risk assessment

  • Alfred Bröckers
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 913)


Analyzing software process models to predict the behavior of software processes helps in planning and enacting software projects. Since software process models can capture the key information that is necessary to assess process-related risks, this paper discusses how approaches for software process analysis may be applied to software risk assessment. A characterization scheme for process analysis approaches is stated based on a set of necessary risk assessment requirements. Existing analysis approaches are evaluated with respect to the characterization scheme. Proceeding from this evaluation, an approach to software process analysis is proposed that is specifically tailored to software risk assessment. This analysis approach takes advantage of a wide range of information by integrating empirically validated models. It is also shown how this approach fits into the context of the MVP (multi-view processes) project at the University of Kaiserslautern.


Software process analysis survey of software process analysis approaches processbased risk assessment risk analysis MVP project 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Tarek K. Abdel-Hamid. A multiproject perspective of single-project dynamics. Journal of Systems and Software, 22(3):151–165, September 1993.Google Scholar
  2. 2.
    Tarek K. Abdel-Hamid and Stuart E. Madnick. Lessons learned from modeling the dynamics of software development. Communications of the-ACM, 32(12): 1426–1438, December 1989.Google Scholar
  3. 3.
    Barry Boehm. Software Risk Management. IEEE Computer Society Press, 1989.Google Scholar
  4. 4.
    Barry W. Boehm. Software Engineering Economics. Advances in Computing Science and Technology. Prentice Hall, 1981.Google Scholar
  5. 5.
    Barry W. Boehm. Software risk management: Principles and practices. IEEE Software, 8:32–41, January 1991.Google Scholar
  6. 6.
    Alfred Bröckers, Christopher M. Lott, H. Dieter Rombach, and Martin Verlage. MVP Language Report. Technical Report 229/92, Fachbereich Informatik, Universität Kaiserslautern, December 1992.Google Scholar
  7. 7.
    Robert N. Charette. Software Engineering Risk Analysis and Management. McGraw-Hill, NY, 1989.Google Scholar
  8. 8.
    Alan M. Christie. Process-centered development environments: an exploration of issues. Technical Report CMU/SEI-93-TR-4, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213, June 1993.Google Scholar
  9. 9.
    Wolfgang Deiters and Volker Gruhn. The FUNSOFT net approach to software process management. Technical Report ISST 2 (ISSN 0943-1624), Institut für Software und Systemtechnik, Fraunhofer-Gesellschafte.V., 44227 Dortmund, February 1993.Google Scholar
  10. 10.
    Peter H. Feiler and Watts S. Humphrey. Software process development and enactment: concepts and definitions. Technical Report CMU/SEI-92-TR-04, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, September 1992.Google Scholar
  11. 11.
    Norman Fenton. Software measurement: A necessary scientific basis. IEEE Transactions on Software Engineering, 20(3): 199–206, March 1994.Google Scholar
  12. 12.
    Michael R. Goodman. Study Notes in System Dynamics. Wright-Allen Press, Cambridge Massachusetts 02142, 1974.Google Scholar
  13. 13.
    David Harel, Hagi Lachover, Ammon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4), April 1990.Google Scholar
  14. 14.
    Mark I. Kellner. Software process modeling: value and experience. In SEI Technical Review, pages 23–54. Software Engineering Institute, Pittsburgh, Pennsylvania 15213, 1989.Google Scholar
  15. 15.
    Chi Y. Lin and Reuven R. Levary. Computer-aided software development process design. IEEE Transactions on Software Engineering, 15(9):1025–1037, September 1989.Google Scholar
  16. 16.
    Lung-Chun Liu and Ellis Horowitz. A formal model for software project management. IEEE Transactions on Software Engineering, 15(10):1280–1293, October 1989.Google Scholar
  17. 17.
    Jaques Lonchamp. A structured conceptual and terminological framework for software process engineering. In Proceedings of the 2 nd International Conference on the Software Process, pages 41–53. IEEE Computer Society Press, February 1993.Google Scholar
  18. 18.
    Christopher M. Lott. Process and measurement support in SEEs. ACM SIGSOFT Software Engineering Notes, 18(4):83–93, October 1993.Google Scholar
  19. 19.
    Peiwei Mi and Walt Scacchi. A knowledge-based environment for modeling and simulating software engineering processes. IEEE Transactions on Knowledge and Data Engineering, 2(3):283–294, September 1990.Google Scholar
  20. 20.
    H. Dieter Rombach, Alfred Bröckers, Christopher M. Lott, and Martin Verlage. Development environments for support of quality-oriented project plans (in German). Softwaretechnik-Trends: Mitteilungen der GI-Fachgruppen 'software-Engineering’ und ‘Requirements-Engineering', 13(3):1–8, August 1993.Google Scholar
  21. 21.
    T.M. Williams. Risk analysis using an embedded CPA package. International Journal of Project Management, 8(2):84–88, 1990.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • Alfred Bröckers
    • 1
  1. 1.AG Software Engineering Department of Computer ScienceUniversity of KaiserslauternKaiserslauternGermany

Personalised recommendations