The Unified Process Elaboration Phase: Best Practices in Implementing the UP

Scott W. Ambler, Larry Constantine

  • 出版商: CRC Press
  • 出版日期: 2000-01-06
  • 售價: $399
  • 語言: 英文
  • 頁數: 304
  • 裝訂: Paperback
  • ISBN: 1929629052
  • ISBN-13: 9781929629053

限量商品 (庫存=4)





Is the Unified Process the be all and end all standard for developing object-oriented component-based software? Scott Ambler doesn't think so. This book is one in a four-volume series that presents a critical review of the Unified Process -- designed to present a more robust software process that addresses your development and production needs. The series has been organized to address each of the four phases of the UP -- Inception, Elaboration, Construction, and Transition. It will:

- Provide you a balanced perspective of the alternative design methodologies available.

- Propose a synthesized software process that addresses the scope of your real world.

- Present materials from the Software Development magazine that will flesh out each of the UP phases.

You get the collective wisdom of industry luminaries. Articles by Peter Coad, Larry Constantine, Martin Fowler, David Linthicum, Mary Loomis, Steve Maguire, Steve McConnell, Clemens Szyperski, and Karl Wiegers, and others, provide perspective on the macro issues like:

- How large-scale, mission critical software is developed and maintained.

- How each workflow fits into the overall development lifecycle.

- Tips and techniques to enhance your role (and career).

And they address the details of implementing a software process with best practices on such issues as code inspections, configuration management, change control, and architectural modeling of your software organization.

Fill the gaps between theory and practice with a plan that includes the nuts and bolts. The Elaboration Phase -- the second of four chronological phases in the UP -- focuses on defining, validating, and establishing the baseline architecture for a system. A carefully selected array of articles address the vital elements of this phase. Subjects include developing frameworks, component architectures, designing with interfaces, building large systems, using the Unified Modeling Language (UML) effectively, working with legacy systems, modeling business rules, selecting tools, building your development team, user interface prototyping, testing your requirements, and effectively managing metrics.

Scott W. Ambler started developing software in the early 80s, and has worked in object-oriented development for the past ten years in an array of roles. He is presently engaged as a software process mentor with AmbySoft Inc., a contributing editor with Software Development magazine, and as a columnist for Computing Canada. His previous books include The Object Primer (1995), Building Object Applications That Work (1997), Process Patterns (1998), and More Process Patterns (1999).

Larry L. Constantine has been a pioneer in software development methods for nearly four decades. His interest in figuring out how to do things better quickly led him into management and process issues, with the aim of bridging the divide between the people side and the technology side of software development. Larry has published 14 books and over 150 articles, many of which appear in The Peopleware Papers (Prentice Hall, 2000) and in Managing Chaos: The Expert Edge in Software Development (Addison-Wesley, 2000), which incorporates the best from his popular Software Development "Management Forum". He is also a co-author of Jolt-award-winning Software for Use (Addison-Wesley, 1999). He is a trainer and consultant with clients around the world, as well as a professor of computing science at the University of Technology, Sydney, Australia.


Table of Contents:



Chapter 1 Introduction

  • The Unified Process
  • Moving Beyond the Unified Process
  • The Enhanced Lifecycle for the Unified Process
  • The Goals of the Elaboration Phase
  • How Work Generally Proceeds During the Elaboration Phase
  • The Organization of this Book

Chapter 2 Best Practices for the Project Management Workflow

  • Managing Multi-Team Development
  • Managing People
  • Managing the Recruitment and Team-Definition Process
  • Managing Your Training and Education Efforts
  • The Articles

Chapter 3 Best Practices for the Business Modeling Workflow

  • From Modeling Your Business to Business Process Re-engineering
  • A Common Modeling Notation
  • The Articles

Chapter 4 Best Practices for the Requirements Workflow

  • Use Cases and Beyond
  • User Interface Prototyping
  • Why are Requirements Important?
  • The Articles

Chapter 5 Best Practices for the Infrastructure Management Workflow

  • Enterprise Requirements and Architectural Modeling
  • Integrating with Legacy Applications: EAI
  • The Articles

Chapter 6 Best Practices for the Analysis and Design Workflow

  • Architecture-Centric Modeling Practices
  • Separation of Concerns
  • Distributed Architectures
  • Component and Framework-Based Architectures
  • Architecting the Reuse of Legacy Software
  • Interface Design and Design Patterns
  • The Articles

Chapter 7 Best Practices for the Test Workflow

  • Test Articles

Chapter 8 Parting Words

  • Looking Toward Construction

Appendix A References and Recommended Reading

  • Printed Resources
  • Web-Based Resources

Appendix B The Article Authors