University of Limerick Institutional Repository

Software crisis 2.0

DSpace Repository

Show simple item record

dc.contributor.author Fitzgerald, Brian
dc.date.accessioned 2012-10-04T14:37:28Z
dc.date.available 2012-10-04T14:37:28Z
dc.date.issued 2012
dc.identifier.uri http://hdl.handle.net/10344/2575
dc.description peer-reviewed en_US
dc.description.abstract Although only about 50 years old, the software domain has already endured one well documented crisis, which was identified early in its evolution in the 1960s. Simply summarised, the initial software crisis – Software Crisis 1.0 as it is termed here – referred to the fact that software took longer to develop than estimated, cost more to develop than estimated, and did not work very well when eventually delivered. Over the years many studies have confirmed the Software Crisis 1.0. Nevertheless, software has been one of the key success stories of the past 50 years and has truly revolutionised modern life. However, over the past 50 years, there have also been enormous advances in hardware capability – dramatic reductions in hardware costs allied to dramatic increases in processing power and proliferation of devices; almost infinite amounts of data are now available through ubiquitous sensors and through applications such as Google. Complementing these ‘push’ factors, there is a significant ‘pull’ factor arising through the emergence of ‘digital native’ technology consumers who have never known life without technology. The opportunities for individuals, business and society afforded by the advances in hardware technology and the vast amounts of data potentially available, when allied to the insatiable appetite of digital natives, are truly enormous. Unfortunately there have not been similar advances in relation to our software development capability, and thus the critical limiting factor in realising the potential of the advances mentioned above is again software – the Software Crisis 2.0 as I label it here. Individual efforts are seeking to address this crisis – data analytics, parallel processing, new development methods, cloud services – but these are disjointed, and not likely to deliver the software development capacity needed. en_US
dc.language.iso eng en_US
dc.publisher IEEE Computer Society en_US
dc.relation.ispartofseries IEEE Computer;45(4), pp. 89-97
dc.relation.uri http://dx.doi.org/ 10.1109/MC.2012.147
dc.rights “© 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.” en_US
dc.subject software crisis en_US
dc.subject software engineering en_US
dc.subject software technologies en_US
dc.title Software crisis 2.0 en_US
dc.type info:eu-repo/semantics/article en_US
dc.type.supercollection all_ul_research en_US
dc.type.supercollection ul_published_reviewed en_US
dc.contributor.sponsor SFI en_US
dc.rights.accessrights info:eu-repo/semantics/openAccess en_US
dc.internal.rssid 1392528
dc.internal.rssid 1404639


Files in this item

This item appears in the following Collection(s)

Show simple item record

Search ULIR


Browse

My Account

Statistics