Conquering Complexity
Mike Hinchey Β· Lorcan Coyle
ααααΆ 2012 Β· Springer Science & Business Media
ααααα
βα’αα‘α·α
ααααΌαα·α
468
ααααα
reportααΆαααΆαααααα αα·αααα·ααΆαααααααα·αααααΌαααΆααααααααααΆαααα αααααααααααααα
α’αααΈααααα βα’αα‘α·α ααααΌαα·αααα
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.
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.
ααΆααααααααααα βα’αα‘α·α ααααΌαα·αααα
ααααΆααααΎαα’αααΈααΆααααααΎαααααα’αααα
α’αΆαβααααααΆα
ααΌαααααααααΆααα αα·αβααααααα
ααα‘αΎααααααα·ααΈ Google Play Books αααααΆαα Android αα·α iPad/iPhone α ααΆβααααΎααααΆαααααβαααααααααααααααα·ααΆαα½αβααααΈβααααα’αααβ αα·αβα’αα»ααααΆαα±ααβα’αααα’αΆααααβααΆαα’ααΈαααΊαα·α α¬ααααΆαβα’ααΈαααΊαα·αβαα
αααααααΈααααααα
αα»αααααΌαααβαα½ααα αα·ααα»αααααΌααα
α’αααα’αΆα
ααααΆααααααα
ααΆααα‘αααααααΆααα·ααα
αααα»α Google Play αααααααΎαααααα·ααΈαα»αααααΆαα’ααΈαααΊαα·ααααα»ααα»αααααΌαααααααα’αααα
eReaders αα·αβα§αααααβαααααβααα
ααΎααααΈα’αΆααα
ααΎβα§ααααα e-ink ααΌα
ααΆβα§αααααα’αΆαβααααα
α’αα‘α·α
ααααΌαα·α Kobo α’αααααΉαααααΌαβααΆαααβα―αααΆα α αΎαβαααααααΆαα
βα§αααααβααααα’αααα ααΌαα’αα»ααααααΆαβααΆαααααΆααααα’α·αααααααααααααααααα½α ααΎααααΈαααααα―αααΆαβαα
α§αααααα’αΆαααααα
βα’αα‘α·α
ααααΌαα·ααααααααΆααα
