or
Sign in to turn on 1-Click ordering.
More Buying Choices
Have one to sell? Sell yours here
Sorry, this item is not available in
Image not available for
Colour:
Image not available

 
Tell the Publisher!
Id like to read this book on Kindle

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

The Unified Software Development Process (Object Technology Series) [Hardcover]

Ivar Jacobson , Grady Booch , James Rumbaugh
4.0 out of 5 stars  See all reviews (20 customer reviews)
Price: 50.99 & FREE Delivery in the UK. Details
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Temporarily out of stock.
Order now and we'll deliver when available. We'll e-mail you with an estimated delivery date as soon as we have more information. Your account will only be charged when we dispatch the item.
Dispatched from and sold by Amazon. Gift-wrap available.

Formats

Amazon Price New from Used from
Hardcover 50.99  
Paperback 47.99  

Book Description

4 Feb 1999 0201571692 978-0201571691 1

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.


Frequently Bought Together

The Unified Software Development Process (Object Technology Series) + The Unified Modeling Language User Guide (Object Technology Series)
Price For Both: 83.13

One of these items is dispatched sooner than the other.

Buy the selected items together


Product details

  • Hardcover: 512 pages
  • Publisher: Addison Wesley; 1 edition (4 Feb 1999)
  • Language: English
  • ISBN-10: 0201571692
  • ISBN-13: 978-0201571691
  • Product Dimensions: 24.2 x 19.3 x 3.1 cm
  • Average Customer Review: 4.0 out of 5 stars  See all reviews (20 customer reviews)
  • Amazon Bestsellers Rank: 769,679 in Books (See Top 100 in Books)
  • See Complete Table of Contents

More About the Authors

Discover books, learn about writers, and more.

Product Description

Amazon Review

A software process defines the steps required to create software successfully. Written by the same authors who brought you the Unified Modelling 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

From the Back Cover

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 (UML). 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.

0201571692B04062001


Sell a Digital Version of This Book in the Kindle Store

If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store. Learn more

Customer Reviews

Most Helpful Customer Reviews
3 of 3 people found the following review helpful
By A Customer
Format:Hardcover
This book defines a process for object oriented software development. Essentially, it could do for the software engineering community, what UML has already done, that is draw together from the best methods and create a well thought out and vivid process. As a book, it clearly explains each essential aspect of the process (Use Case Driven, Architecture Centric, Iterative and Incremental), the steps needed to carry out the process and the 'artifacts' that are the result of each iteration of work. There are plenty of diagrams that back up each explanation, allowing the reader to get the whole picture. The book does require reading from cover to cover if you are not familiar with object oriented development. The book does not cover the software project management aspects in very much detail, leaving the reader to find details of the management aspects (eg Change control and Risk Management) to find in another book that covers these topics (Software Project Management by Royce, which is another book in the Addison Wesley Object Technology Series).
Comment | 
Was this review helpful to you?
2 of 2 people found the following review helpful
3.0 out of 5 stars good book but lacks practical advice 19 Jan 2004
Format:Hardcover
The book gives a complete overview of the Unified Process describing first the basic workflows (requirements, analysis, design, implementation, test), and then the 4 phases (inception, elaboration, construction and transition). In the second half of the book the basic workflows are described thoroughly in the context of each phase.
Although the main principles are discussed with a suitable level of detail, the book does not contain the necessary information that is needed for a successful implementation of the process: there is neither a satisfactory discussion of how to manage iterative-processes from a Project Manager standpoint (what is the best way to proceed with the work breakdown structure?), nor there is a thorough description of how to implement configuration management. The book is generally well written, but it is probably oversized: the gist could have been condensed in some 200 pages.
In conlusion, the book is a must read for it introduces the foundations of the most mature architecture-first, use case driven, iterative-incremental approach to software development.
Comment | 
Was this review helpful to you?
2 of 2 people found the following review helpful
3.0 out of 5 stars Good content -- presented like a dry lecture. 30 Aug 1999
By A Customer
Format:Hardcover
Remember in college how you had some professors who would lecture and some who would teach? This book, unfortunately, isn't about teaching.
The authors have written "The Unified Software Development Process" to the academic OO community, not to students eager to learn OO techniques from the masters. Every reference in this book is footnoted, every historical precedent mentioned, every alternative way of doing something is brought up so it can properly be dismissed. It reads like a Ph.D. thesis.
In other words, the authors seem more interested in pleasing OO academicians than in transferring their experience to OO disciples eager to learn from their years of experience.
Still, I can't fault the actual content of the book. It's a good book, with good content. I just spent way too much time struggling to pull the content out of this book that reads like academic lecture notes.
Comment | 
Was this review helpful to you?
2 of 2 people found the following review helpful
5.0 out of 5 stars THE Software Development Process book. 2 Aug 1999
By A Customer
Format:Hardcover
Most of us use a process to software development. Most of us do not use a formal process to do it. This book describes a formal process to software development. It is not the first book in its class nor is the last one. But it is one of the best I have ever read.
Ivar's describes the Unified Software Development Process from top to bottom (the workflows) and from minute 0 to project delivery (the phases) in great detail.
Be aware that this is not a object oriented analysis and design book. It is a software development process book.
He explains what is the role that every developer should have in every workflow (requirements, analysis, design, implementation) and also the list of deliverables in every phase.
The author explains in great detail what to look for (the goals) in every step on the software development. This is something that I have found really valuable.
Comment | 
Was this review helpful to you?
2 of 2 people found the following review helpful
Format:Hardcover
Having already reviewed this book a while ago, I wanted to update my review - so here are some additional comments. I still think the book is good, and suggests a process for OO development in conjunction with UML, but it seems to suggest guidelines with very small detail - which I don't believe is a good thing. Everyone should follow a development process, but everyone is an individual and they are going to want to do things in their own way, even if they have a set of guidelines and documents to produce during a development process. In short, it is a good book for the experienced developer to gain insight into how other experienced developers points of views of the development process are, especially in large scale projects. (My opinion at this moment of time!)
Comment | 
Was this review helpful to you?
1 of 1 people found the following review helpful
By A Customer
Format:Hardcover
For three people as highly respected as Messrs. Jacobson, Booch, and Rumbaugh to have produced a book is so completely NOT about a software development process is a travesty. These gentlemen know about designing systems in an object-oriented environment. They seem to know nothing about obtaining and defining requirements for such a system.
They begin with the "use case". This is not an attempt to determine what kinds of automation are appropriate for a given business function. It does not ask the question, "Should this process continue to be done in a newly automated world?" It presumes the process and presumes a systems whose basic shape and technology were already determined by the analyst before he began. It then simply addresses the question of what the user interface would look like.
The appropriate place to start requirements analysis is with determination of the basic functions of the business, followed by determination of the extent to which current activities contribute to those functions. Many of the current activities only exist because of shortcomings in current systems. These should not be automated at all. They should be eliminated.
After extensively discussing use cases, the three gentlemen then proceed to wave their hands over analysis, briefly describing "analysis artifacts" as being "more abstract" than design artifacts, but never really coming to grips with what such artifacts are supposed to do.
Requirements analysis is the process of coming to grips with the fundamental processes, data structures and business rules of the organization. What is the nature of the company? How does it work? What is the true, fundamental, structure of its data?
Read more ›
Comment | 
Was this review helpful to you?
Would you like to see more reviews about this item?
Were these reviews helpful?   Let us know
Most Recent Customer Reviews
5.0 out of 5 stars Blue print for software development
The Unified Software Development Process by Ivar Jacobson is a must have for those going into object-oriented software design and development. Read more
Published 13 months ago by Joviman
5.0 out of 5 stars Great book.
I needed this book for Uni. It is a great book and explains the process very clearly. Recommend this to anyone who wants to learn this particular process.
Published 14 months ago by Mr. Michael J. Barber
1.0 out of 5 stars Vaguely, talks about methodologies in general.
I read the first six chapters and then gave up with a brief browse through the rest! I can't find anything of substance in this book. Read more
Published on 15 Oct 1999
4.0 out of 5 stars excellent if you understand some caveats
An excellent book, it will without doubt make any given reader a better software engineer.
However, the writing drones a bit. Read more
Published on 26 Aug 1999
5.0 out of 5 stars Must-have addition to your bookshelf...
This book is a well-written concise overview of the software development process. It does not go into great depth in each area, but provides a well-chosen view into the different... Read more
Published on 26 July 1999
5.0 out of 5 stars Best, most complete overview of the unified process.,
For those looking for a comprehensive model for a disciplined software development process, this book is it. Read more
Published on 22 July 1999
5.0 out of 5 stars Solid framework for standardized software development
Many organizations continue to look for silver bullets to answer the aliments of their software delivery capabilities. Read more
Published on 5 Jun 1999
5.0 out of 5 stars Must-read - going to be the default OO process
The hard thing to understand is how this is any different than the Rational Unified Process documented in another book. My conclusion is that it isn't. Read more
Published on 1 Jun 1999
Search Customer Reviews
Only search this product's reviews

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 

Search Customer Discussions
Search all Amazon discussions
   


Look for similar items by category


Feedback