The Unified Software Development Process (Addison-Wesley Object Technology)

Jacobson, Ivar, Booch, Grady

ISBN 10: 0201571692 / ISBN 13: 9780201571691

Published by Addison-Wesley Professional, 1998

About this Item

Ausreichend/Acceptable: Exemplar mit vollständigem Text und sämtlichen Abbildungen oder Karten. Schmutztitel oder Vorsatz können fehlen. Einband bzw. Schutzumschlag weisen unter Umständen starke Gebrauchsspuren auf. / Describes a book or dust jacket that has the complete text pages (including those with maps or plates) but may lack endpapers, half-title, etc. (which must be noted). Binding, dust jacket (if any), etc may also be worn. Seller Inventory # M00201571692-B

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