The Unified Software Development Process

Jacobson, Ivar; Booch, Grady; Rumbaugh, James

ISBN 10: 0201571692 / ISBN 13: 9780201571691

Published by Addison-Wesley Professional, 1998

About this Item

Gently used with minor shelf wear. There is a personal inscription from prior owner and there might be writing in the margins, possibly underlining and highlighting of text, but no missing pages or anything that would compromise the legibility or understanding of the text. Get fast and secure shipping knowing your purchase helps empower our community to transform their lives through work. Seller Inventory # 4RZUQ8000K6P

Bibliographic Details

Title: The Unified Software Development Process

Publisher: Addison-Wesley Professional

Publication Date: 1998

Binding: Hardcover

Condition: Acceptable

About this title

Synopsis:

Presents a complete guide to the Unified Process from the original designers. Demonstrates how the notation and process compliment one another, using UML models to illustrate the new process in action. Clearly describes the semantics and notation of the different higher-level constructs used in the models. DLC: Computer software--Development.

Review:

A software process defines the steps required to create software successfully. Written by the same authors who brought you the Unified Modeling Language (UML), The Unified Software Development Process introduces a new standard for creating today's software that will certainly be useful for any software developer or manager who is acquainted with UML.

Early sections introduce four basic principles of the unified process: that software should stress use cases (which show how it interacts with users), that the process is architecture-centric, and that it is iterative and incremental. The authors then apply these principles to their software process, which involves everything from gathering system requirements to analysis, design, implementation, and testing. The use-case examples are excellent and include concrete examples drawn from such areas as banking and inventory control.

The authors point out the connection between UML document types (like use cases, class diagrams, and state transition diagrams) with various models used throughout the software process. They provide very short, real-world examples that illustrate how their ideas have been successfully applied. The straightforward tour of the new unified software process gets extra elaboration--along with some advice--in later chapters that further describe the author's ideas on design. With the weight of these three expert authors behind it, readers can expect The Unified Software Development Process to be an important book and one that will be valuable to any working designer or manager. --Richard Dragan