Cargando…

Conquering Complexity

Software has long been perceived as complex, at least within Software Engineering circles. We have been living in a recognised state of crisis since the first NATO Software Engineering conference in 1968. Time and again we have been proven unable to engineer reliable software as easily/cheaply as we...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor Corporativo: SpringerLink (Online service)
Otros Autores: Hinchey, Mike (Editor ), Coyle, Lorcan (Editor )
Formato: Electrónico eBook
Idioma:Inglés
Publicado: London : Springer London : Imprint: Springer, 2012.
Edición:1st ed. 2012.
Temas:
Acceso en línea:Texto Completo

MARC

LEADER 00000nam a22000005i 4500
001 978-1-4471-2297-5
003 DE-He213
005 20220112220752.0
007 cr nn 008mamaa
008 120101s2012 xxk| s |||| 0|eng d
020 |a 9781447122975  |9 978-1-4471-2297-5 
024 7 |a 10.1007/978-1-4471-2297-5  |2 doi 
050 4 |a QA75.5-76.95 
072 7 |a UY  |2 bicssc 
072 7 |a COM014000  |2 bisacsh 
072 7 |a UY  |2 thema 
082 0 4 |a 004  |2 23 
245 1 0 |a Conquering Complexity  |h [electronic resource] /  |c edited by Mike Hinchey, Lorcan Coyle. 
250 |a 1st ed. 2012. 
264 1 |a London :  |b Springer London :  |b Imprint: Springer,  |c 2012. 
300 |a XXIV, 468 p.  |b online resource. 
336 |a text  |b txt  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
347 |a text file  |b PDF  |2 rda 
520 |a Software has long been perceived as complex, at least within Software Engineering circles. We have been living in a recognised state of crisis since the first NATO Software Engineering conference in 1968. Time and again we have been proven unable to engineer reliable software as easily/cheaply as we imagined. Cost overruns and expensive failures are the norm. The problem is fundamentally one of complexity: software is fundamentally complex because it must be precise. Problems that appear to be specified quite easily in plain language become far more complex when written in a more formal notation, such as computer code. Comparisons with other engineering disciplines are deceptive.  One cannot easily increase the factor of safety of software in the same way that one could in building a steel structure, for example. Software is typically built assuming perfection, often without adequate safety nets in case the unthinkable happens. In such circumstances it should not be surprising to find out that (seemingly) minor errors have the potential to cause entire software systems to collapse. The goal of this book is to uncover techniques that will aid in overcoming complexity and enable us to produce reliable, dependable computer systems that will operate as intended, and yet are produced on-time, in budget, and are evolvable, both over time and at run time. We hope that the contributions in this book will aid in understanding the nature of software complexity and provide guidance for the control or avoidance of complexity in the engineering of complex software systems. 
650 0 |a Computer science. 
650 1 4 |a Computer Science. 
700 1 |a Hinchey, Mike.  |e editor.  |0 (orcid)0000-0001-5110-561X  |1 https://orcid.org/0000-0001-5110-561X  |4 edt  |4 http://id.loc.gov/vocabulary/relators/edt 
700 1 |a Coyle, Lorcan.  |e editor.  |4 edt  |4 http://id.loc.gov/vocabulary/relators/edt 
710 2 |a SpringerLink (Online service) 
773 0 |t Springer Nature eBook 
776 0 8 |i Printed edition:  |z 9781447158264 
776 0 8 |i Printed edition:  |z 9781447122968 
776 0 8 |i Printed edition:  |z 9781447122982 
856 4 0 |u https://doi.uam.elogim.com/10.1007/978-1-4471-2297-5  |z Texto Completo 
912 |a ZDB-2-SCS 
912 |a ZDB-2-SXCS 
950 |a Computer Science (SpringerNature-11645) 
950 |a Computer Science (R0) (SpringerNature-43710)