Fee Download The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten
When getting the book The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten by on-line, you could review them anywhere you are. Yeah, also you remain in the train, bus, waiting list, or other areas, on the internet publication The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten could be your excellent friend. Each time is a great time to check out. It will certainly boost your expertise, enjoyable, amusing, session, and experience without spending even more money. This is why online publication The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten ends up being most really wanted.
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten
Fee Download The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten
Discover the trick to boost the lifestyle by reading this The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten This is a sort of publication that you require now. Besides, it can be your favorite publication to review after having this publication The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten Do you ask why? Well, The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten is a publication that has different particular with others. You might not should recognize which the author is, exactly how popular the job is. As sensible word, never evaluate the words from which talks, but make the words as your inexpensive to your life.
Obtaining guides The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten now is not kind of difficult means. You can not just going for book shop or collection or borrowing from your pals to read them. This is an extremely simple means to specifically get guide by on-line. This online book The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten could be among the options to accompany you when having extra time. It will certainly not squander your time. Think me, guide will certainly reveal you new point to check out. Just invest little time to open this on-line e-book The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten and also review them any place you are now.
Sooner you obtain guide The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten, sooner you could take pleasure in checking out the e-book. It will certainly be your turn to maintain downloading the book The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten in given link. By doing this, you can actually choose that is served to obtain your personal publication on the internet. Right here, be the initial to obtain guide entitled The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten and be the very first to understand exactly how the writer suggests the message and understanding for you.
It will certainly have no question when you are visiting select this book. This inspiring The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten e-book could be read completely in certain time depending upon exactly how commonly you open and also review them. One to keep in mind is that every e-book has their very own manufacturing to get by each visitor. So, be the excellent reader and be a far better person after reviewing this publication The Rational Unified Process, By Philippe Kruchten, Philippe Kruchten
This book is a brief introduction to the Rational Unified Process. This new software development process is derived primarily from the three market-leading object-oriented analysis and design methods: Booch, OOSE (Use-Case), and OMT. It represents a collaboration and extension of the three leading object-oriented methodologists, Ivar Jacobson, Grady Booch and James Rumbaugh. In an attempt to standardize the process of analysis and design, these three leading methodologists have merged and refined their popular methods while incorporating successful ideas drawn from many other time-tested methods. The end result is the truly groundbreaking Rational Unified Process: a software development process, delivered through a web-enabled, searchable knowledge base that enhances team productivity and delivers software best practices via guidelines, templates, and tool mentors for all critical software lifecycle activities.
- Sales Rank: #3971799 in Books
- Published on: 1998-12-01
- Original language: English
- Number of items: 1
- Dimensions: 9.00" h x 7.25" w x .50" l, .96 pounds
- Binding: Textbook Binding
- 272 pages
Review
The Rational Unified Process: An Introduction is a good overview of Rational's prescription for whole-project health. The process is unified as in "Unified Field Theory." Thesis, Antithesis, and Synthesis, (or Booch, Jacobson, and Rumbaugh, as they are known today) twine in a celestial dance to the Spheres, Rectangles, Clouds, and stray pointers that make up UML and its increasingly ambitious extensions, additions, and heroic leaps of faith.
Rational visualizes the elements and modalities of code and projects in a fashion found compelling by increasing numbers of corporate customers. It's a vision embodied in several software suites, including the eponymous Rational Unified Process, for which this book is designed to serve as the introduction. Face it, you are going to run into Rational on the job. This volume is a good place to get know about it.
The book is not an independent assessment of Rational. Editor Philippe Kruchten is lead architect of the Rational Unified Process product. The thrust is the process of processes, specifically process in software projects, as viewed by Rational and supported by its project-management toolsets. Read more--Jack Woehr, Dr. Dobb's Journal -- Dr. Dobb's Journal
From the Back Cover
Second Edition now available!
The Rational Unified Process embodies the best practices of proven software development methods, and is an optimal match to the features of the UML. --Grady Booch, Ivar Jacobson, and James Rumbaugh
This concise book offers a quick introduction to the concepts, structure, content,and motivation of the Rational Unified Process. This revolutionary software development process provides a disciplined approach to assigning, managing, and completing tasks within a software development organization and is the first development process to exploit the full capabilities of the industry-standard Unified Modeling Language. The Rational Unified Process is unique in that it captures many of the proven best practices in modern software development and presents them in a form that can be tailored to a wide range of projects and organizations.
The Rational Unified Process will help software development teams produce, within a predictable schedule and a reasonable budget, the highest-quality software possible to meet the needs of end users. Throughout the book, the author shares his inside knowledge of the process, focusing his coverage on key aspects that are critical to mastering this proven approach to software development.
In this book you will discover:
What the Rational Unified Process is--and what it is not
The concepts used in the Rational Unified Process, as well as its structure
The best practices that have been synthesized in this process
How this process can provide the guidance you need for your specific project responsibilities
About the Author
Philippe Kruchten is the lead architect of the Rational Unified Process. He has more than thirty years of experience in the development of large software-intensive systems for the telecommunications, defense, aerospace, and transportation industries. His book The Rational Unified Process: An Introduction (Addison-Wesley) has been translated into eight languages and has sold more than 160,000 copies in its two previous editions.
0201604590AB11072003
Most helpful customer reviews
31 of 31 people found the following review helpful.
A fine, readable introduction
By Cem Kaner, J.D, Ph.D.
This book is an introduction to the Rational Unified Process (RUP). It is suitable for readers who have never heard of RUP before and for readers who have little experience with thoughtful analysis of software lifecycles. (I think it's also very useful as a quick, easy-to-read overview of RUP for more advanced readers, but you can read about that use of the book in other reviews.)
I teach Computer Science at Florida Tech, including undergraduate and graduate courses in software testing. Krutchen provides a thoughtful but very readable, persuasive discussion of risks associated with different software lifecycles. In my experience as a teacher, my students' ability to appreciate differences among lifecycles and analyze them critically is significantly boosted by study and discussion of Krutchen. Accordingly, I require my students to read the relevant section of his book, they have detailed small-group discussions of it, and it often appears on their exam.
This book is an introduction. It doesn't address all of the problems with RUP. It doesn't cover all of the areas of RUP equally well. It won't make any reader an expert in the process or its favored practices. It won't persuade someone who doesn't like RUP that they should like. What it does do is expose the reader to the thinking and practices that make up this particular approach to software engineering.
This book is much deeper than marketing fluff, but not so deep as to lose a junior reader. As a teacher, I am delighted to have materials like this available.
(Disclosure: a little bit of my work has been included in RUP, and I have developed a course for Rational on software testing within the Rational process. However, I identify more with the agile development / XP community than with the RUP community. In any case, the question that I'm interested in answering in this review is not whether RUP is any good -- it has its good points and its weaknesses -- but rather whether Krutchen's introduction to RUP is a fair and useful introduction to that subject matter. My conclusion is that it is.)
31 of 31 people found the following review helpful.
A fine book despite some reservations
By Vince Kenyon
An excellent book well organized and generally well written. Recommended either to learn about Rational Corporation's Rational Unified Process (RUP) or even just to get a general acquaintance with current ideas about software development methodology.
Mr. Kruchten advocates describing a software product with various summary, abstract views. In this book, he practices what he preaches by giving just the "architectural" view of RUP, whose in-depth treatment would not fit in just 300 pages. There are seventeen chapters divided into two sections. A reader interested only in RUP's distinctive features may skip chapters 1 and 14-17.
Section I comprising chapters 1-6 provides the motivation (software development best practices) and the dominant themes (architecture and use cases) of RUP, describing it also along two main dimensions: the dynamic dimension of phase and iteration and the static dimension of workflow.
Section II dedicates a chapter to each of RUP's nine workflows. There are two final chapters, one with sample plans for iterations in different project phases and one discussing how to implement RUP in a development organization. There are two useful appendices, a dictionary of acronyms, a glossary, and a quite helpful annotated bibliography.
In RUP a workflow is an interrelated set of activities producing a cohesive subset of the artifacts of a software development project. The chapters describing workflows vary somewhat in length and quality, but they all follow the same pattern: (1) start with guiding principles; (2) describe the activities, workers, and artifacts of the workflow; (3) conclude with some comments on tool support (a little marketing for Rational Corporation's tool suite). The best workflow chapters: Project Management, Business Modeling, Test, Configuration and Change Management.
The high recommendation comes not without some reservations.
Architectures are important in RUP, but Chapter 5, "An Architecture-centric Process," garbles this message by describing architectures as mere derivatives of "complete" system descriptions (called "models"): "Architecture is what remains when you cannot take away any more things and still understand the system and explain how it works (p. 82)." Again, " . . . models are complete representations of the system, whereas an architectural view focuses only on what is architecturally significant (p. 89)." Finally, "Architectural views are like slices cut through the various models, illuminating only the important, significant elements . . . (p. 90)."
These explanations fail to recognize that architectures come first. Architectures are constraints that determine subsequent design and construction of the system. They are primary, not derivative, not mere views of models. Fortunately, RUP recognizes the primacy of architecture even if these explanations do not.
These explanations also fail to recognize that an architecture is a complete and distinct model in its own right. They are out of harmony with the book's own (wordy) definition of architecture, which includes "The selection of structural elements and their interfaces by which the system is composed . . . (p. 84)." So when the elements and interfaces have been defined, the architecture is complete, right? It escapes this reader how architectures can be inherently less complete than models (whatever they are), when there is not even any one model that completely describes a system (see p. 81).
The relationship that Chapter 5 describes between architectures and models is very similar to that described in Chapter 10 between the analysis model and the design model. Mr. Kruchten limits the value of retaining the analysis model as a distinct artifact: "Generally, there is one design model . . .. The upper layers of this model describe the application-specific, or more analysis-oriented, aspects . . . In some companies-those in which systems live for decades or there are many variants of the system-a separate analysis model has proved useful (p. 175)."
Generally, companies that plan to stay in business DO expect their systems to live for decades-as do companies that spend millions of dollars using RUP to build them. As for "the extra work required to ensure that the analysis and design models remain consistent (p. 175)," the right tool can make all the difference. Anyone familiar with tools for database design (Erwin, for example) knows that they provide extensive facilities for maintaining separate, consistent analysis (logical) and design (physical) models. The tools offered by Rational Corporation, however, do NOT provide such a facility. Could Mr. Kruchten be tailoring the methodology to fit the limitations of the tool that his sponsor sells?
Compare his attitude toward the analysis model with that of another author in the Addison-Wesley Object Technology Series. Martin Fowler in his UML Distilled says, " . . . it is very important to separate the specification perspective and the implementation perspective (p. 52)." Mr. Fowler uses different terminology, but he is saying essentially that the analysis model ("specification perspective") is valuable as an artifact distinct from the design model ("implementation perspective").
Despite these issues-which might profitably have been discussed at greater length-this fine book admirably fulfills its purpose.
37 of 38 people found the following review helpful.
Much better read than Unified Software Development Process
By Linus W Freeman
This book is a much better read than the generic process described by the book named The Unified Software Development Process (UP). The Rational Unified Process (RUP) is a specific instance of the more generic UP. The RUP can be tailored to an organization or project and is considered a product offering by Rational Corp. Many big technology firms are using RUP to include major companies from Telecommunications, Transportation, Aerospace, Defense, Manufacturing, Financial Institutions, and System Integratrors. Some of the major well known companies include: Xerox, Intel, Oracle, Lockheed-Martin, Merrill Lynch, MCI and Charles Schwab.
This book is easy to follow and very informative about a modern user-case driven, architecture centric, iterative/incremental development process. After an introduction to the whole process structure consisting of a Conception Phase, Elaboration Phase, Construction Phase and Transition Phase, each succeeding chapter covers a single workflow such as Business Modeling, Requirements Management, Analysis & Design, Implementation, Testing, Deployment, Configuration & Change Management, Project Management and Environment.
This book is actually an enjoyable read and makes the reader aware of what it takes to develop software using an object-oriented software development process using a proven methodology.
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten PDF
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten EPub
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten Doc
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten iBooks
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten rtf
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten Mobipocket
The Rational Unified Process, by Philippe Kruchten, Philippe Kruchten Kindle
Tidak ada komentar:
Posting Komentar