| |||||||||||||||
![]() Gutschein erhalten
Tauschen Sie jetzt The Unified Software Development Process (Addison-Wesley Object Technology) gegen einen Amazon-Gutschein in Höhe von EUR 0,25 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
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
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
Tags(Was ist das?)Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte. |
The book as such is very verbose, a lot of the material covered in "The UML User's Guide" and the "The UML Reference Manual" is reiterated. Much of the book is simply an UML tutorial, albeit a good one. If the authors had assumed prior knowledge of this material on the side of the reader, they could have distilled a 150 pages book out of this 450 pages book.
The Unified Process is often criticized as a waterfall model in disguise. After having read this book, you know why.
So, after all, should you buy this book? The only reason that I can imagine is that it is written by THE VERY GURUS (or rather their team of ghostwriters).
By the way: The handcrafting quality of the book itself is very good: few typos, clear writing, etc. My overall impression is "3 out of 5".
The Unified Process is appropriate for using the UML for modeling because it uses a use case driven, architecture centric, iterative/incremental life cycle that complements the main features of the UML.
If you want to learn UML, the best book to buy is "The Unified Modeling Language Users' Guide" by the three amigos. If you want to learn a modern day software development process that makes the best use of the industry standard specifications language, UML, then buy the "Unified Software Development Process", also written by the three amigos.
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.
If you want to create a repeatable development process that is capable of continuous improvement,... Lesen Sie weiter...
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
|
|
|