SKIP THE SHIPPING
Use code NOSHIP during checkout to save 40% on eligible eBooks, now through January 5. Shop now.
Register your product to gain access to bonus material or receive a coupon.
This landmark book provides a thorough overview of the Unified Process for software development, with a practical focus on modeling using the Unified Modeling Language. The Unified Process goes beyond mere object-oriented analysis and design to spell out a proven family of techniques that supports the complete software development life cycle. The result is a component-based process that is use-case driven, architecture-centric, iterative, and incremental. The Unified Process takes full advantage of the industry-standard Unified Modeling Language. This book demonstrates how the notation and process complement one another, using UML models to illustrate the new process in action. The authors clearly describe the semantics and notation of the different higher-level constructs used in the models. Constructs such as use cases, actors, subsystems, classes, interfaces, active classes, processes, threads, nodes, and most relations are described in the context of a model. Object technology practitioners and software engineers familiar with the authors' past work will appreciate The Unified Software Development Process as a useful means of learning the current best practices in software development.
Preface.
I. THE UNIFIED SOFTWARE DEVELOPMENT PROCESS.
1. The Unified Process: Use-Case Driven, Architecture-Centric, Iterative, and Incremental.The Unified Process in a Nutshell.
The Unified Process Is Use-Case Driven.
The Unified Process Is Architecture-Centric.
The Unified Process Is Iterative and Incremental.
The Life of the Unified Process.
The Product.
Phases within a Cycle.
An Integrated Process. 2. The Four Ps: People, Project, Product, and Process in Software Development.
People Are Crucial.
Development Processes Affect People.
Roles Will Change.
Turning “Resources” into “Workers.”
Projects Make the Product.
Product Is More Than Code.
What Is a Software System?
Artifacts.
A System Has a Collection of Models.
What Is a Model?
Each Model Is a Self-Contained View of the System.
Inside a Model.
Relationships between Models.
Process Directs Projects.
Process: A Template.
Related Activities Make Up Workflows.
Specializing Process.
Merits of Process.
Tools Are Integral to Process.
Tools Impact Process.
Process Drives Tools.
Balance Process and Tools.