- Hardcover: 512 pages
- Publisher: Addison-Wesley Professional; 1 edition (February 14, 1999)
- Language: English
- ISBN-10: 0201571692
- ISBN-13: 978-0201571691
- Product Dimensions: 7.7 x 1.2 x 9.6 inches
- Shipping Weight: 2 pounds
- Average Customer Review: 35 customer reviews
- Amazon Best Sellers Rank: #623,991 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
The Unified Software Development Process 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Customers who viewed this item also viewed
Customers who bought this item also bought
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
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.
Read reviews that mention
Showing 1-5 of 35 reviews
There was a problem filtering reviews right now. Please try again later.
Getting through this book will be challenging, though. You'll be thirsty not for more material, but a glass of water by the time you're done. It is bone-dry.
The Unified process has five workflows (requirements, analysis, design, build, test) that repeat within four phases (inception, elaboration, construction, transition). There are unfortunately huge chapters devoted to each of the workflows and each of the phases separately, with only a smaller amount of material focusing on how the process is actually done, which is each workflow occuring in the context of each phase. As a result, the book seems a lot bigger than it needs to be. (I'm not panning the process, though, which does indeed work, just the presentation.)
There's a running example through the text of building an automated teller application. While running examples help unify ideas, they show a narrow view of how the process can work in practice. In applying the process to my projects, it's difficult to translate such a financial application to my work (which is scientific and library-based in nature). I'd like to see a lot more examples that give alternative viewpoints in addition to the running example that demonstrates the process as a whole.
Unlike the other two books of the Big-Three, the diagrams in this one are the best. They're clean, consistent, and easy to read, and there are a lot of them. It's professionally typeset and each page is pretty.
What we need is a book similar to Fowler's "UML Distilled" called "Unified Process Distilled." The process is great---it just shouldn't take 500 pages to describe it.
The primary difficultly with the work lies in some of the assumptions of the unified process. First, analysis and the upper lifecycle of systems development are treated very cavalierly. The attitude is that analysis is okay and may yield some valuable information, but you should be able to go right into design without wasting all that time in analysis. My 11 years of professional experience indicates otherwise.
The next difficultly is communication between various audiences. UML is touted as the most effective diagramming technique for communicating both business and software concepts. Yet the modeling techniques are severely lacking in techniques for capturing fundemental business information. In addition, many of the concepts presented are very esoteric and peculiar to object modeling and are not easily applied to the business world or even to transaction-based software applications.
There is also a concerted effort to ignore many valuable techniques developed in such disciplines as Information Engineering, Structured Analysis and Design, etc. The UML will be a mature enough modeling language only after these missing pieces have been incorporated.
If you want to familiarize yourself with the buzz words of the object community, buy the book. Otherwise, I wouldn't recommend wasting your money.
After reading the Unified Modeling Language User Guide by the same authors, I was concerned that the Unified Process book would have the same vagueness in its definitions. Not at all. It is very clear, concise and detailed. The subject matter is divided into a very logical and progressive sequence.
The Unified Process is the cornerstone to understanding other processes, including Waterfall, Rational UP, Open UP, Agile UP, and many others. It also helps to understand Agile Frameworks and best practices, such as Scrum and XP. Agile fits into the "iterative and incremental" part of UP, and XP fits into the inferred Continuous Integration and Test Driven Development (or BDD, etc...). With this global view of the Unified Process as a template that incorporates other frameworks and best practices, it is easy to understand just about any process that is already defined, and to tailor a process to specific needs.
This is a must read for Project Managers, Product Owners, and Architects, and for everyone who wants to understand why processes are defined the way they are and how they can be improved.
This is on my top 10 book list.
Need I say more?
Most diagrams are about the USDP rather than diagrams about the artifacts that the USDP requires. Never is there a really good illustration of the blood and guts of the process, a "Use Case".
I had 72 students ready to lynch me. It was the worst mistake I ever made in the textbook selection process.