Software needs engineering - a position paper

Abstract

When the general press refers to `software' in its headlines, then this is often not to relate a success story, but to expand on yet another `software-risk-turned-problem-story'. For many people, the term `software' evokes the image of an application package running either on a PC or some similar stand-alone usage. Over 70% of all software, however, are not developed in the traditional software houses as part of the creation of such packages. Much of this software comes in the form of products and services that end-users would not readily associate with software. These can be complex systems with crucial connections made through software, such as telecommunication or banking systems, or the logistics systems of airports; or they can be end-user products with software embedded, ranging from battery management systems in electric shavers, to mobile phones, to engine management and safety systems in cars. E-commerce systems fall into this category too. Yes, there is software that works reliably and as expected, and there are professional approaches to create such products - one can engineer software, in the right environment, with the right people