Crisis Management for Software Development and Knowledge Transfer

153 Pages·2016·2.963 MB·English

by  Sergey V. Zykov (auth.)

Smart Innovation, Systems and Technologies 61
Sergey V. Zykov
Crisis Management
for Software
Development and
Knowledge Transfer
123
Smart Innovation, Systems and Technologies
Volume 61
Series editors
Robert James Howlett, KES International, Shoreham-by-sea, UK
e-mail: [email protected]
Lakhmi C. Jain, University of Canberra, Canberra, Australia;
Bournemouth University, UK;
KES International, UK
e-mails: [email protected]; [email protected]
About this Series
The Smart Innovation, Systems and Technologies book series encompasses the
topics of knowledge, intelligence, innovation and sustainability. The aim of the
seriesistomakeavailableaplatformforthepublicationofbooksonallaspectsof
single and multi-disciplinary research on these themes in order to make the latest
results available in a readily-accessible form. Volumes on interdisciplinary
research combining two or more of these areas is particularly sought.
The series covers systems and paradigms that employ knowledge and
intelligence in a broad sense. Its scope is systems having embedded knowledge
and intelligence, which may be applied to the solution of world problems in
industry, the environment and the community. It also focusses on the
knowledge-transfer methodologies and innovation strategies employed to make
this happen effectively. The combination of intelligent systems tools and a broad
range of applications introduces a need for a synergy of disciplines from science,
technology, business and the humanities. The series will include conference
proceedings, edited collections, monographs, handbooks, reference books, and
other relevant types of book in areas of science and technology where smart
systems and technologies can offer innovative solutions.
Highqualitycontentisanessentialfeatureforallbookproposalsacceptedforthe
series. It is expected that editors of all accepted volumes will ensure that
contributionsaresubjectedtoanappropriatelevelofreviewingprocessandadhere
to KES quality principles.
More information about this series at http://www.springer.com/series/8767
Sergey V. Zykov
Crisis Management
for Software Development
and Knowledge Transfer
123
Sergey V.Zykov
Higher Schoolof Economics
National Research University
Moscow
Russia
ISSN 2190-3018 ISSN 2190-3026 (electronic)
Smart Innovation,Systems andTechnologies
ISBN978-3-319-42965-6 ISBN978-3-319-42966-3 (eBook)
DOI 10.1007/978-3-319-42966-3
LibraryofCongressControlNumber:2016946314
©SpringerInternationalPublishingSwitzerland2016
Thisworkissubjecttocopyright.AllrightsarereservedbythePublisher,whetherthewholeorpart
of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations,
recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission
orinformationstorageandretrieval,electronicadaptation,computersoftware,orbysimilarordissimilar
methodologynowknownorhereafterdeveloped.
The use of general descriptive names, registered names, trademarks, service marks, etc. in this
publicationdoesnotimply,evenintheabsenceofaspecificstatement,thatsuchnamesareexemptfrom
therelevantprotectivelawsandregulationsandthereforefreeforgeneraluse.
The publisher, the authors and the editors are safe to assume that the advice and information in this
book are believed to be true and accurate at the date of publication. Neither the publisher nor the
authorsortheeditorsgiveawarranty,expressorimplied,withrespecttothematerialcontainedhereinor
foranyerrorsoromissionsthatmayhavebeenmade.
Printedonacid-freepaper
ThisSpringerimprintispublishedbySpringerNature
TheregisteredcompanyisSpringerInternationalPublishingAGSwitzerland
To God, my teachers, and my family
Foreword
Based upon its title, “Crisis Management for Software Development and
Knowledge Transfer,” the reader might be forgiven for expecting that the subject
of the book is addressing situations where development has gone disastrously
wrong.Nothingcouldbefurtherfrom thetruth.Instead, Sergey Zykovhaswritten
an important book that offers value on many levels. For the student or new
developer, it offers a useful survey of the important software engineering approa-
ches that have emerged over the past six decades. For the more experienced
developer or manager, it presents a thoughtful perspective on how each develop-
ment methodology’s approach to addressing crises can play in choosing the most
appropriate methodology for a particular context. For the academic researcher, it
proposes a number of interesting frameworks and identifies the central role that
knowledgetransferplaysinthesoftwareengineeringprocess.Inotherwords,crises
cannot necessarily be avoided, but they can be more effectively managed.
By beginning the book with an examination of the software crisis of the late
1960s and early 1970s, Zykov performs an important service. A few decades ago,
individuals that had lived through this tumultuous period were well represented in
thetypicalITstaff.Today,mostofthatgroupisretiredordeceased.Unfortunately,
their absence has left a vacuum of experience. The anarchy that characterized
mid-1960s software development has many parallels to much of the dot.com and
Internet development of the past decade. Too often, we see history repeating itself
intheformofsystemsthatdomeetuserneedsthatfailtoachieveacceptablelevels
ofsecurityor thatvastlyunderperform expectations.Through better understanding
thepast,perhapswewillbelesssurprisedbytheseoutcomes.Perhapswemayeven
be able to avoid them.
Almost any reader can benefit from the book’s systematic coverage of different
software engineering methodologies. Emphasizing from the start that there is no
“silver bullet” approach, Zykov clarifies often subtle differences between approa-
ches—e.g. how does an evolutionary development approach differ from a spiral
vii
viii Foreword
model—with concise explanations and helpful diagrams. He also introduces a
number of specialized approaches, such as Microsoft Solution Framework, which
arewidelyusedinindustrybutareoftenignoredingeneralwritingsbecauseoftheir
vendor specificity. In doing so, he builds a helpful bridge from academic concep-
tions of software engineering to the world of software engineering practice.
One of the book’s greatest strengths is its crisis-driven perspective. Rather than
viewing a “crisis” as a unique event that cannot be anticipated in advance, Zykov
treatscrisesasmore-or-lessinevitable.And,asaresultofthisinevitability,helooks
at different software engineering approaches in terms of their suitability for han-
dlingdifferenttypesofcrises.Weallrecognizethatthelarge-scalemission-critical
system may need to be engineered differently from other types of systems. The
booklooksatthesesystemsandconsiderswhatapproachesmaybemosteffective.
It also looks at how pure software engineering approaches may be rendered more
effective by incorporating techniques drawn from other approaches, such as
incorporating incremental prototyping into projects whose overall structure is dri-
ven by a waterfall model.
Avery important element ofthe book isthe rich systems engineering examples
thatareintroducedthroughoutthebook,andparticularlyinthelaterchapters.While
thereisnoshortageofexamplesinthesoftwareengineeringliterature,fartoomany
of them derive from USA and Western European sources. Many readers, like
myself,willbeintriguedbytheRussianexamplesandperspectivespresentedinthe
book.Thesimilaritiesanddifferencesbetweentheseandtheexamplesfamiliartous
can help broaden our thinking. As such, the book is well suited to the global
audience.
My personal favorite part of the book was the chapter that preceded the final
conclusions. It deals software engineering from a knowledge transfer perspective.
Becausemyownareaofresearchisthetransdisciplinaryfieldofinformingscience,
I tend to see the informing (i.e. knowledge transfer) aspects of every situation as
being central to understanding that context. Unfortunately, much that has been
written about software engineering imagines such transfer as being something that
willoccurautomatically(providedtherightprocessisinplace).Indirectcontrastto
this,Zykovlooksatknowledgetransferprocessesveryexplicitly.Heevengoesso
far astoprovide acase study involving Innopolis,a Russiancity,being builtfrom
the ground up to serve as a community that integrates education, research, and
practice. Specifically, he considers the challenges that emerged as researchers and
educators from Carnegie Mellon University attempted to work with Russian
researchers, including Zykov himself, to develop a software engineering curricu-
lum. The entire project makes for fascinating reading.
Zykov concludes his book with the statement:
Inourview,therootcauseofthesoftwaredevelopmentcrisisisthehumanminditself,and
wecanmanagethecrisisifweapproachhuman-relatedandtechnology-relatedissuesand
challengesinasystematicanddisciplinedway.
Foreword ix
Upon reading the book, I felt far more knowledgeable about the challenges
facing the managers of software development processes. I also felt more confident
inmyownabilitytodiscussthetopic(inaninformedway)withmystudents,andin
my own writing. It is an important book, one that is well worth reading.
T. Grandon Gill, DBA
Professor and DBA Academic Director
Information Systems and Decision Sciences Department
Muma College of Business
University of South Florida
Tampa, FL, USA
Contents
1 Software Engineering: The End of the Crisis?. . . . . . . . . . . . . . . . . 1
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Software Development and Material Production:
The Same or Different? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3 Software Engineering: Start and Evolution . . . . . . . . . . . . . . . . . . 4
4 Software Engineering and Product Lifecycle. . . . . . . . . . . . . . . . . 7
5 Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2 Software Product Lifecycles: What Can Be Optimized
and How?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2 Simple Lifecycles: Brief and Straightforward . . . . . . . . . . . . . . . . 28
3 Simple Iterative Lifecycles: Incremental and Prototyping . . . . . . . . 31
4 Complex Iterative Lifecycles: Spiral, Synch-and-Stabilize
and Object-Oriented. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5 Managing Lifecycles: Flexible Methodologies. . . . . . . . . . . . . . . . 42
6 Optimizing the Lifecycle: Enhanced Spiral Methodology . . . . . . . . 44
7 Organizing the Lifecycle: Sequential Elaboration. . . . . . . . . . . . . . 46
8 Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3 Software Methodologies: Are Our Processes Crisis-Agile?. . . . . . . . 51
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2 Methodologies: Flexible Process Frameworks. . . . . . . . . . . . . . . . 52
3 Rational Process: Managing Mission-Critical Development. . . . . . . 55
4 The Microsoft Way: From Formal to Agile . . . . . . . . . . . . . . . . . 60
5 Flexible Methodologies: Adding Crisis Agility . . . . . . . . . . . . . . . 65
6 Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
xi