The Enterprise Unified Process: Extending the Rational Unified Process [Paperback]

Scott W. Ambler (Author), John Nalbone (Author), Michael J. Vizdos (Author)

Book Description

ISBN-10: 0131914510 | ISBN-13: 978-0131914513 | Publication Date: February 21, 2005 | Edition: 1

This book describes the fundamentals of the Enterprise Unified Process(EUP), an extension of the IBM/Rational Unified Process (RUP) that helpsmake it a full IT lifecycle. The book is, above all, practical. It gives a short, tothe point description of what the EUP is and how it addresses the shortfalls ofthe RUP that most organizations will encounter. While there are several RUPbooks, no single book address organizationsal issues that the EUP addresses(namely, where the RUP falls short). With this in mind, the authors provide abrief overview of the RUP but focuses mainly on the issues that the RUP mostignores (e.g. cross-project and enterprise issues). This is a "how to" guide usingreal-world experiences and examples for the practitioner. This book is notproduct specific and it is tool agnostic. Enterprise Unified Process is built onbeing an add-on to the RUP, instead of a detractor.

Editorial Reviews

From the Back Cover

Extend RUP to Drive Improvements Across the Entire IT Lifecycle

The Rational Unified Process is a powerful tool for improving software development -- but it doesn't go nearly far enough. Today's development organizations need to extend RUP to cover the entire IT lifecycle, including the cross-project and enterprise issues it largely ignores. The Enterprise Unified Process (EUP) does precisely that, enabling you to deliver systems that meet all the needs of today's businesses. Now, EUP's creator and architects present the definitive introduction to EUP, and demonstrate how to use it in your environment.

The Enterprise Unified Process systematically identifies the business and technical problems that RUP fails to address, and shows how EUP fills those gaps. Using actual examples and case studies, the authors introduce processes and disciplines for producing new software, implementing strategic reuse, "sunsetting" obsolete code and systems, managing software portfolios, and much more. Their independent, "tool agnostic" coverage will be indispensable no matter which RUP products or platforms you've invested in. Coverage includes

• Practical, step-by-step guidance for adopting EUP in midsized-to-large organizations

• Proven processes for optimizing ongoing IT operations and support

• Enterprise business modeling and architecture with EUP

• EUP disciplines for enterprise administration, people management, and software process improvement

• Using the new EUP plug-in for IBM's RUP platform

• Workflow diagrams fully consistent with RUP for easy understanding

• Detailed appendices covering EUP roles, artifacts, and terminology

EUP is the missing link that can help IT professionals achieve the full benefits of RUP in the enterprise. This book will help you discover it, master it, implement it, and succeed with it.

© Copyright Pearson Education. All rights reserved.

About the Author

The Enterpise Unified Process: Extending the Rational Unified ProcessAbout the Authors

Scott Ambler is a senior consultant with Ronin International, Inc. specializing in software process improvement, adoption, and mentoring. He has contributed to the RUP and has been working with organizations since 1999 to adopt and extend the RUP. He is the thought leader behind the Enterprise Unified Process (EUP), Agile Model Driven Development (AMDD), the Agile Data (AD) method, and the process patterns of the Object-Oriented Software Process (OOSP). He has worked in the information technology (IT) industry since the late 1980s in a wide range of roles within a variety of industries, including financial, retail, military, and health. He has either authored or co-authored numerous books, including The Object Primer, The Practical Guide to Enterprise Architecture, Agile Database Techniques, and the four-book Unified Process series. He is a senior editor with Software Development (http://www.sdmagazine.com) and an international speaker in the IT field.

John Nalbone is a senior consultant with Ronin International, Inc. He has worked in the information technology (IT) industry since the late 1980s in a variety of roles. Although he started his career as a coder, his experience covers a wide range, including being an analyst, designer, architect, developer, project manager, and process engineer. He has worked on a variety of projects over the years, including debugging operating systems, developing expert systems, and enterprise architecture efforts, with a number of different clients, including startups, government agencies, and Fortune 500 companies. His current focus is on helping companies with their process improvement efforts; in particular helping them to adopt both the RUP and/or the EUP.

Michael Vizdos is President of Ronin International, Inc. Michael has more than 15 years of experience in the IT industry and has worked in all aspects of the system lifecycle. He came to Ronin with a variety of experience, including six years at Electronic Data Systems and two start-up companies. His specialty is building successful Professional Services teams, and he is also a Certified Scrum Master (http://www.michaelvizdos.com). Michael speaks and writes about various process IT-related topics.

Ronin International, Inc. is based in Evergreen Colorado, just outside of Denver. The team at Ronin is known and respected as a market leader for planning, improving, and implementing various software practices throughout the world. Ronin consultants are in the "knowledge transfer" business. Their goal is to transfer knowledge from their experts to your team members. They work with clients to develop working software, create or improve new software process improvement efforts, and facilitate long-term strategic planning sessions for your IT organization.

© Copyright Pearson Education. All rights reserved.

See all Editorial Reviews

Product Details

• Paperback: 408 pages
• Publisher: Prentice Hall; 1 edition (February 21, 2005)
• Language: English
• ISBN-10: 0131914510
• ISBN-13: 978-0131914513
• Product Dimensions: 9.4 x 6.9 x 1 inches
• Shipping Weight: 1.7 pounds (View shipping rates and policies)
• Average Customer Review: 4.8 out of 5 stars  See all reviews (9 customer reviews)
• Amazon Best Sellers Rank: #1,017,010 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

5 of 5 people found the following review helpful:

5.0 out of 5 stars Beyond the limits of RUP, June 22, 2005

By 

Gary K. Evans "OO Guru" (Columbia, SC United States) - See all my reviews
(REAL NAME)   

This review is from: The Enterprise Unified Process: Extending the Rational Unified Process (Paperback)

In the interests of disclosure, I must share that I was one of the technical reviewers for this fascinating book. But my recommendations of it are based upon its sensible content. Here is my take on how the Enterprise Unified Process can improve your organization.

Enterprise thinking is not about thinking "bigger", it's about thinking differently. The Enterprise Unified Process is a qualitative leap forward that will change the scope of your project from simply a development lifecycle to a SYSTEM lifecycle. The authors aptly recommend that if you are not yet using an iterative process, then you should first adopt the Rational UP, Scrum, FDD or other project-focused development process. But if your needs go beyond merely managing or executing development projects, you will need to move to the EUP.

Structurally, the EUP builds on the RUP, and augments RUP to address the needs of an enterprise rather than just software development. Structurally, the EUP adds two new phases to RUP: the Production phase and the Retirement Phase. The Production phase begins after RUP's Transition phase, and this is where each release of software spends its entire life after it is developed. The activities of the Production phase focus on keeping your software and systems running, backed-up, and that defect reports are being addressed. The Retirement phase defines the activities involved in removing software, or a system, from production. Retirement is a complex process that can be accomplished all-at-once, or incrementally over time, but retirement always requires coordination with other processes in your organization.

EUP adds a new support Discipline to RUP: the Operations and Support Discipline. This discipline includes disaster planning and recovery, service-level agreements between operations and support teams, and addressing end-user questions and problem reports for systems in production.

But EUP goes far beyond vanilla RUP with the addition of "Enterprise Management Disciplines" that are specific and unique to the enterprise context. Here, EUP introduces the disciplines and associated roles and activities for:
* Enterprise Business Modeling
* Portfolio Managment
* Enterprise Architecture
* Strategic Reuse
* People Management
* Enterprise Administration
* Software Process Improvement

Each discipline is explained clearly with discussion of the workflows that are executed, sample case studies, tools that can assist you in the discipline, and--my favorite--"anti-patterns" for each discipline. For me the anti-patterns helped me to better understand each discipline's goals.

If you are familiar with RUP, you should have a feeling now for how much RUP does not address for the enterprise, and how much the EUP has to offer. But how can an organization move to EUP? Luckily, the authors conclude the book with sound recommendations on adopting the EUP. If you are involved with, or responsible for, software development to support your company's business goals, this book will help you understand the many dimensions that RUP does not begin to address.

4 of 4 people found the following review helpful:

4.0 out of 5 stars RUP Expanded, June 10, 2005

By 

Jacques B. Surveyer "photofinisher" (Toronto ON) - See all my reviews
(REAL NAME)   

This review is from: The Enterprise Unified Process: Extending the Rational Unified Process (Paperback)

Scott Ambler and the crew at Ronin have helped define the nature of Agile development (see www.agilemodeling.com) and that is the task set here : make RUP, a very structured IT development process more agile and flexible. But also along the way, Scott and crew also help to make it more complete - they bring the single process up into a larger framework of an organizational viewpoint. This is aided by extending the Zachman framework slightly plus adding three key components to the RUP development cycle.

First, the the RUP Transition is expanded into Transition, Production and Retirement. By explicitly bringing a complete cycle view of development key IT asset issues are addressed which otherwise might be omitted. Ditto for adding Strategic Reuse and Software Process Improvement - these are tough issues to handle. For example, many eXtreme Programming adherents are dead set against any amounts of time spent on Reuse and Strategic Improvements; but Scott and company set some disciplined guidelines for both processes.

But the most important contribution of the book is to set reasonable goals for modeling and planning- in effect, EUP strives to make these activities deliver clear benefits measured better team communications, consensus building and measurable targets and process goals. Agile uses models as tests of design.

So what is missing, since we rated this 4 on 5. First, although the book does treat risk management it does not use it as a guide to process effectiveness - those models and plans and every step of the EUP process better help reduce the risks of a project or one of its phases going awry or they have failed to deliver. See Boehm and Turner's Balancing Agility and Discipline for the risk based approach to project management. Second, SOA-Service Oriented Architectures and Web Services are changing the nature of development profoundly because they up the value of workflow and integration between systems (long neglected in IT projects). As noted EUP catches some of this but unfortunately does not look at the specific ramifications.

But overall this book is conundrum challenging - its a disciplined and fruitful look at making a structured planning process more agile.

2 of 2 people found the following review helpful:

5.0 out of 5 stars Uniting diverse disciplines...under an easy to follow framework, September 12, 2005

By 

William Ulrich - See all my reviews
(REAL NAME)   

This review is from: The Enterprise Unified Process: Extending the Rational Unified Process (Paperback)

The Enterprise Unified Process (EUP) unites diverse disciplines, including development, enterprise architecture, operations, production and portfolio management, reuse and business process modeling, under an easy to follow framework. It was refreshing to find a book that recognizes the need to accommodate the installed base of existing software as part of the planning, development and deployment process. This is an excellent guide for any manager who wants to ensure that essential IT disciplines are addressed.

The focus of EUP is to enhance the commonly accepted Rational Unified Process (RUP). The authors have added new disciplines to RUP that include business modeling, portfolio management, enterprise administration, reuse, enterprise architecture and process improvement. The introduction of business modeling into the overall process is essential to weave IT processes and disciplines into the most essential driver of any systems initiative - the business. The enterprise architecture discussion was also refreshing given that many organizations have forgone this discipline and have created redundant, stovepipe applications and data structures that significantly stifle business agility.

The "Reuse" chapter raises the rarely deployed reuse strategy. It is critically important to not replicate business processes, models, systems, data structures, source code and interfaces. The costs and risks of trying to keep parallel assets synchronized have been written about extensively. This book promotes the idea that reuse is just another aspect of the enterprise unified process. It is also one of the few discussions about reuse that recognizes the value of harvesting existing assets.

Also of note is the portfolio management discussion that focuses attention on the need to incorporate project management with application management. It should be noted, however, that portfolio management has much less focus on applications than the traditional industry definition as promoted by Gartner, Inc.

Finally, this book makes great use of tips, tool references and citations to books or papers that readers can use to expand on their understanding of a given topic. The last chapter of the book takes a realistic and honest look at deploying the enterprise unified process, including its possible retirement.