Careerlab – центр профессионального развития

Автор и соавтор около трех десятков книг, включая бестселлеры «Путь камикадзе» (Death March), «Закат и падение американского программиста» (Decline and Fall of the American Programmer) и «Подъем и возрождение американского программиста» (Rise and Resurrection of the American Programmer) В июне 1997 г. был официально объявлен членом Зала Компьютерной славы (Computer Hall of Fame), объединяющим таких выдающихся людей, как Чарльз Бэббидж, Сеймур Крей, Джемс Мартин, Грейс Хоппер, Джеральд Вайнберг и Билл Гейтс Автор метода структурного системного анализа (метод Йордона) Соавтор методологии объектно-ориентированного анализа Коада-Йордона

Outsourcing: Competing in the Global Productivity Race

(Prentice Hall, 2004).

Outsourcing isn’t only the #1 issue facing IT organizations: it’s provoking profound change throughout American business. Whetheryou’re an executive or a knowledge worker, the decisions you make about outsourcing can make or break your future. This book brings together all the information and insight you need to make those decisions — and make them the right ones.

Death March (2nd edition)

(Prentice Hall, 2003).

Companies continue to create death-march projects; what’s worse is the number of intelligent people who submit to schedules, estimates, budgets, and resources so constrained or skewed, they can hardly survive, much less succeed. Yourdon sheds new light on the reasons why companies spawn death marches, and provides guidance to those caught in lockstep.

Byte Wars: The Impact of September 11 on Information Technology

(Prentice Hall, 2002).

Since 9/11, several IT-related concepts — risk management, “good enough” systems, and death-march projects — face a paradigm shift, while concepts once dismissed as abstract and theoretical are taking on new importance; for example, emergent systems: ad hoc, grass-roots systems that emerge to cope with unanticipated, fast-moving, disruptive changes which traditional top-down approaches cannot handle. To cope with such change, Yourdon argues that governments, companies, communities, and families must embrace emergent-systems approaches — and he illustrates how IT systems will play a vital role in this effort.

Managing High-Intensity Internet Projects

(Prentice Hall, 2001).

Even though the dot-com mania has abated, the manic intensity associated with Internet-related projects has not. Most systems being developed today are Internet-related — either in a direct fashion, such as e-commerce or e-business systems, or in an indirect fashion, because they interface to other systems across the the Internet. That being the case, an obvious question is: what’s so different about developing today’s Internet-related systems?

Time Bomb 2000!, with Jennifer Yourdon (2nd edition)

(Prentice Hall, 1999).

Writings on the year 2000 (Y2K) problem, or the “millennium bug,” were limited to highly technical analyses of specific problems and their solutions; very little attention was paid to how Y2K might have affected the lives of average people and everyday systems, though many prognosticators believed these people, and these systems, would experience the greatest impact. In Time Bomb 2000: What the Year 2000 Computer Crisis Means to You, Edward and Jennifer Yourdon present a collection of scenarios, with each chapter investigating a different area of computing and the possible effects of this potential disaster on each. Although the Yourdons expressed a largely optimistic view — and while Y2K turned out to be a non-event — the tragedy of 9/11 demonstrated the virtues of having backup plans for infrastructure disruptions, the likes of which were once attributed to innocent technology failures.

Case Studies in Object-Oriented Analysis and Design, with Carl Argila

(Prentice Hall, 1996).

The analysis and design of large, complex software systems are not unlike mathematical proofs: they are presented as finished products — but while they may be documented with reams of papers, they rarely show any evidence of how they were developed. Case Studies in Object-Oriented Analysis and Design offers insight to how object-oriented analysis and design are done — for real systems. The treatment goes beyond presenting terminology, notation, and model structure, and offers insight on analysis, design, and project management issues.

Rise and Resurrection of the American Programmer

(Prentice Hall, 1996).

The Decline and Fall of the American Programmer warned of the impending loss of leadership by American software engineers. A great deal changed in the three years that followed, and Yourdon soon recognized a complete reversal of many trends he had previously documented, as well as developments such as the WWW, Java, “good enough” software, and the enormous impact of Microsoft on the world of software and computing — that, together, signified the resurrection of American software engineering.

Object-Oriented Systems Design: An Integrated Approach

(Prentice Hall, 1994).

After Yourdon’s initial OO authoring projects with Peter Coad in 1989-90, he spent the next several years consulting, teaching, and practicing object technology in various projects around the world; An Integrated Approach summarizes those experiences. The text gathers together all that is best and appropriate in OO development — with an emphasis on CASE tools, reuse, project management, metrics, and configuration management.

Decline and Fall of the American Programmer

(Prentice Hall, 1992).

In 1991, Yourdon predicted that software development might soon leave the United States, bound for a dozen countries, unless American software organizations exploited the key software technologies examined in this publication. Yourdon addresses how companies can implement object-oriented methods, CASE tools, software quality assurance, structured methods, software metrics, and re-engineering.

Object-Oriented Design, with Peter Coad

(Prentice Hall, 1991).

Designed as a companion volume to the acclaimed Object-Oriented Analysis, Design focuses on the activity of design. It shows readers how to apply object-oriented design, and how to tailor and expand the method to suit specific organization and project needs. Readers will explore the major issues in OOD; the role of OOD in the systems lifecycle; how to use graphical notation; strategies for creating design; and hints for evaluating the efficiency of a design created with OOD. For software engineers and other users undertaking real-world systems development projects and designing overall software architecture for systems, this reference to improving systems design is indispensable.

Object-Oriented Analysis, with Peter Coad (2nd edition)

(Prentice Hall, 1991).

Yourdon and Coad provide a step-by-step approach to defining and communicating system requirements; understanding the application domain in which the user operates; integrating the data and process models; analyzing and specifying systems using self-contained partitioning; gaining leverage through explicit representation of commonality; applying a consistent underlying representation for analysis; and accommodating families of systems.

Modern Structured Analysis

(Prentice Hall, 1989).

Yourdon provides a fresh perspective on structured systems analysis, integrating traditional methodologies with modern technology. He thoroughly discusses data modeling, real-time systems, prototyping, and 4GLs.N

Classics in Software Engineering

(Yourdon, 1979).

This early text presents a number of vital articles from the early days of software engineering: Dijkstra’s “Go To Statement Considered Harmful” and “Programming Considered as a Human Activity”; Parnas on decomposing systems into modules; Stevens, Myers, and Constantine on structured design; papers by Baker, Mills, Kernighan, and Plauger; and Knuth’s “Structured Programming with go to statements,” among others. ACM recently named Classics in Software Engineering as one of the top 25 “most seminal books that have gone out of print.”

Just Enough Structured Analysis

(This is an update, condensation, and pragmatic revision of the 1989 tome, Modern Structured Analysis, posted on the Web site on a chapter-by-chapter basis. Today, we’re too busy to spend much time thinking about anything, and we’re also far too busy to read more than a couple hundred pages of the bare essentials on any topic. What we want is “just enough” — enough to give us the basic idea, enough to get us started, enough to give us a grounding in the fundamentals. That’s the motivation for Just Enough Structured Analysis. In response to the continued interest in JESA, and given the recent proliferation of Web 2.0 concepts and applications, a revised and updated version of this text is now available in Wiki format.).