Advertisement

On Verification of the Software Development Process

  • Deniss KumlanderEmail author
Conference paper
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 313)

Abstract

The implementation of the best software engineering process do not guarantee the best result. The ratio of failures is still very high although the formal review of the processes shows no defects. The most common problem is the amount of additional work discovered at the very end of the projects leading either to delays and extra cost or to sufficient decrease in the product quality. All this is unacceptable in the modern rapidly evolving world with a high level of competition and demand to produce software in time with acceptable level of quality. The paper describes how the software process can be examined and verified to ensure that it is not only established, but also followed and all potential risks and uncertainties are resolved right when they occur instead of suppressing.

Keywords

Software engineering Process Verification 

References

  1. 1.
    O. Forsgren, Churchmanian co-design – basic ideas and application examples, Advances in Information systems development: bridging the gap between academia and industry, Springer, 2006, pp.35-46.Google Scholar
  2. 2.
    A. Cockburn, Agile Software Development; Addison Wesley, 2002Google Scholar
  3. 3.
    M. Beedle, K. Schwaber, Agile Software Development with SCRUM, Prentice Hall, Englewood Cliffs, NJ, 2001Google Scholar
  4. 4.
    K. Braithwaite, T. Joyce, XP Expanded: Distributed Extreme Programming, 6th International Conference on eXtreme Programming and Agile Processes in Software Engineering, Springer, 2005, pp. 180-188.Google Scholar
  5. 5.
    M. Rauterberg, O. Strohm, Work organisation and software development, Annual Review of Automatic Programming, Vol.16, 1992, 121-128Google Scholar
  6. 6.
    I. Somerville, R. Jane, An empirical study of industrial requirements engineering process assessment and improvement, ACM Transactions on Software Engineering andMethodology, Vol.14, No.1, 2005, pp. 85-117Google Scholar
  7. 7.
    E. N. Bennatan, K.E. Emam, Software project success and failure, Cutter Consortium, http://www.cutter.com/press/050824.html, 2005
  8. 8.
    A. A. Khan, Tale of two methodologies for web development: heavyweight vs agile, Postgraduate Minor Research Project, 2004, pp. 619-690.Google Scholar
  9. 9.
    R. Kumar, Managing risks in IT projects: an options perspective, Information and Management, Vol. 40, 2002, 63–74.Google Scholar
  10. 10.
    D. Kumlander, Uncertainties Management Framework - Foundational Principles, Proceedings of the 11th International Conference on Enterprise Information Systems, INSTICC Press, 2009, pp. 103 - 108.Google Scholar
  11. 11.
    D. Kumlander, Software design by uncertain requirements, Proceedings of the IASTED International Conference on Software Engineering, 2006, pp. 224-2296Google Scholar
  12. 12.
    D. Kumlander, Bridging gaps between requirements, expectations and delivered software in information systems development, WSEAS Transactions on Computers, Vol.5, No.12, 2006, 2933-2939Google Scholar
  13. 13.
    D. Kumlander, Uncertainty Management Framework Elements – Test Based Verification of the Process, Proceedings of the 6th WSEAS European Computing Conference, 2012, pp. 517 - 521.Google Scholar

Copyright information

© Springer International Publishing Switzerland 2015

Authors and Affiliations

  1. 1.Department of InformaticsTTUTallinnEstonia

Personalised recommendations