Download Ebook The Unified Process Explained, by Kendall Scott
However, what's your issue not too liked reading The Unified Process Explained, By Kendall Scott It is a wonderful activity that will always provide great advantages. Why you come to be so bizarre of it? Numerous things can be sensible why people do not like to check out The Unified Process Explained, By Kendall Scott It can be the uninteresting tasks, the book The Unified Process Explained, By Kendall Scott compilations to read, also careless to bring spaces everywhere. Now, for this The Unified Process Explained, By Kendall Scott, you will certainly begin to like reading. Why? Do you know why? Read this web page by completed.
The Unified Process Explained, by Kendall Scott
Download Ebook The Unified Process Explained, by Kendall Scott
Book The Unified Process Explained, By Kendall Scott is among the priceless well worth that will certainly make you always abundant. It will certainly not mean as abundant as the cash offer you. When some people have lack to deal with the life, people with many publications sometimes will be better in doing the life. Why need to be book The Unified Process Explained, By Kendall Scott It is really not implied that e-book The Unified Process Explained, By Kendall Scott will offer you power to get to every little thing. Guide is to check out as well as what we suggested is the e-book that is reviewed. You could also see how the e-book entitles The Unified Process Explained, By Kendall Scott as well as varieties of publication collections are providing right here.
When getting this book The Unified Process Explained, By Kendall Scott as recommendation to read, you could obtain not only motivation however additionally brand-new knowledge and driving lessons. It has greater than typical advantages to take. What sort of book that you read it will work for you? So, why need to obtain this e-book qualified The Unified Process Explained, By Kendall Scott in this short article? As in web link download, you can get guide The Unified Process Explained, By Kendall Scott by online.
When getting the publication The Unified Process Explained, By Kendall Scott by online, you can read them any place you are. Yeah, even you are in the train, bus, waiting checklist, or various other places, on the internet e-book The Unified Process Explained, By Kendall Scott can be your excellent buddy. Whenever is a great time to review. It will certainly boost your expertise, fun, amusing, session, as well as encounter without investing even more cash. This is why on the internet e-book The Unified Process Explained, By Kendall Scott becomes most wanted.
Be the first that are reviewing this The Unified Process Explained, By Kendall Scott Based upon some factors, reading this e-book will supply more perks. Even you have to review it step by step, page by page, you can finish it whenever as well as wherever you have time. Again, this on the internet publication The Unified Process Explained, By Kendall Scott will certainly provide you very easy of reviewing time and also activity. It likewise provides the experience that is economical to get to as well as get substantially for far better life.
A presentation of the Rational Unified Process (RUP) in simple terms, designed to help developers and managers get up-to-speed with this potentially complex methodology. Kendall Scott seeks to present technical material in a straightforward fashion. He debunks the argument that the RUP has just too much detail for the common developer to comprehend.
- Sales Rank: #3699729 in Books
- Color: White
- Published on: 2001-12-06
- Released on: 2001-11-26
- Original language: English
- Number of items: 1
- Dimensions: 9.10" h x .60" w x 7.30" l, .92 pounds
- Binding: Paperback
- 208 pages
From the Back Cover
The Rational Unified Process (RUP) has been widely adopted across the software industry. However, many software developers and managers--especially those working in medium-to-small development organizations--are hesitant to delve into this seemingly complex and time-consuming topic.
The Unified Process Explained is a concise, accessible, and practical guide that's meant to help significantly shorten the learning curve for practitioners unfamiliar with this methodology. It explains the essentials of the Unified Process (the RUP's core elements), guides you through the process step-by-step, and shows how you can put the methodology to work on your next project.
The book starts with a useful overview of the history, motivation, key concepts, and terminology of the Unified Process. The author then details the five pillars of development: requirements, analysis, design, implementation, and test workflows. In addition, the book enumerates the four phases of Unified Process development: inception, elaboration, construction, and transition; and it shows how the workflows are integrated into these phases. In laying out the details of this integration, the book illustrates the Unified Process's most useful feature--its iterative nature.
With this book as your guide, you will gain an understanding of important concepts and activities such as:
- Iterations and increments
- Business and domain modeling
- Identifying actors and use cases
- Prototyping the user interface
- Robustness analysis
- Design and deployment models
- Statechart and activity diagrams
- Implementation models
A large-scale example of an Internet bookstore runs throughout the book to illustrate concepts and techniques. The industry-standard Unified Modeling Language is used to express structure and function. The Unified Process Explained demystifies this valuable methodology and will lead you on your way to successfully applying the Rational Unified Process.
0201742047B11142001
About the Author
Kendall Scott is a UML trainer and consultant. With more than sixteen years of experience as a technical writer, he is skilled in converting complex, technical material into understandable and easy-to-use manuals.
Excerpt. © Reprinted by permission. All rights reserved.
Why This Book?
From the moment the Unified Process made its appearance, I heard many people describing it as really big and complicated, at conferences like UML World and in various public forums, such as Rational's Object Technology User Group (OTUG) mailing list. I agreed that in comparison to other well-known processes, it was rather large, but I didn't think that it was all that complicated, all things considered.
In Chapter 2 of UML Explained, I managed to describe the fundamental concepts that underlie the Unified Process in about ten pages. While I was still writing that book, it occurred to me that I could probably describe the most important details of the Unified Process in a book not much bigger than that one (that is, 200 pages rather than my usual 150 or so). So, I set about writing this book partially to debunk the notion that the process contained just too much for the average person to get his or her arms around, and also to establish that the process doesn't specify tasks that people on a project don't do anyway, in one way or another.
The result is a book that I've specifically conceived as a companion piece to UML Explained. Rather than try to teach you about the UML, which the Unified Process makes fairly heavy use of, I've included references to chapters and sections in that book that offer details about the various UML diagrams and techniques that come into play within the process. I've also brought a number of the diagrams over from that book into this one, to help the continuity and flow across both books. As Picasso said, "Good artists borrow; great artists steal."
Here are some other key features of this book:
- I've made domain modeling and business modeling, which tend to get short shrift in other books about this process, full players, with the associated artifacts and activities part of the Requirements workflow where they belong.
- I've minimized the amount of project management material. Walker Royce's Software Project Management: A Unified Framework (Addison-Wesley, 1998) is the definitive work on how to do project management in conjunction with the Unified Process, and I see no need to try to add value to what he's written.
- Chapters 7 through 9 include the story of how The Internet Bookstore, a sample project, was designed and built. Whereas Chapters 2 through 6 include diagrams from UML Explained relevant to that example, the later chapters explain how the project team broke the system down into chunks in the course of doing iterative and incremental development. Applying Use Case Driven Object Modeling with UML (Rosenberg and Scott, Addison-Wesley, 2001) contains other views of the same bookstore project. (My attitude is, stick with what you know!)
My goal was to write a book that would demystify what people like to call A Real Big Process or some variation of that. I hope you think I've succeeded.
Organization of This BookThe body of this book can usefully be divided into four parts.
The first part comprises Chapter 1. This chapter provides an overview of the Unified Process, in the form of a "nutshell" description, some history, exploration of the major themes (use case driven, architecture-centric, and iterative and incremental), and definitions of the major terminology: workflows, phases, iterations and increments, and artifacts, workers, and activities.
The second part comprises Chapters 2 through 6. These chapters provide the details about the five workflows (Requirements, Analysis, Design, Implementation, and Test) that the process defines. Each chapter includes the following:
- An introduction that offers a brief overview of what's included in the workflow and its primary goals
- Descriptions of the various artifacts that get produced during the workflow
- Descriptions of the various roles that people play during the workflow, expressed in terms of "workers"
- Descriptions of the various activities that workers perform during the workflow in order to produce the artifacts
Each of the Activities sections has a diagram that shows the nonlinear nature of the given workflow. Solid lines on this diagram show logical sequences in which to perform the activities; in some cases, one activity is basically a prerequisite to another activity, whereas in other cases, the work that the team performs for one activity will cause a cycling back to one or more activities that it previously performed. Dashed lines are for data flow: The contents of the artifact that results when one activity is finished feed into the next activity or a previous activity.
The third part comprises Chapters 7 through 9. These chapters provide the details about three of the four phases (Inception, Elaboration, and Construction) that the process defines. Each chapter includes the following:
- An introduction that offers a brief overview of what the project team does during the phase, including its primary goals and a high-level look at how each of the five workflows "cuts across" the phase. (You might think of the workflows and the phases as forming a matrix, with the workflows running down the left-hand side and the phases across the top.)
- A description of the tasks that the project manager should perform before the development team begins the activities defined by the phase.
- Descriptions of the activities, defined by one or more of the workflows, that the project team performs during the phase. These descriptions are expressed in terms of what specifically needs to happen during the phase (the team performs an activity to a greater or lesser extent depending on the context) and also in terms of The Internet Bookstore. The bookstore team did one iteration of Inception, three of Elaboration, and two of Construction; each chapter provides part of their story with text that describes what they did for each activity during each iteration and excerpts from the various models that they produced along the way.
Each of these chapters also calls out the deliverables of the given phase at appropriate places.
The fourth part comprises Chapter 10. This chapter describes the Transition phase, which is the phase during which the project team rolls out the system to its customers. The format for this chapter is the same as that for Chapters 7 through 9. This chapter is in a separate part because workflow activities don't cut across Transition the way they do the other three phases, and because the chapter doesn't discuss the bookstore project.
The book also includes the following end matter:
- Appendix A, which describes what the Rational Unified Process (RUP) adds to the core Unified Process
- Appendix B, which compares and contrasts the RUP with the fundamental aspects of eXtreme Programming (XP)
- Appendix C, which describes the ICONIX process, whose roots are the same as those for the Unified Process
- A bibliography, which lists all the books I mention and a few more for the sake of reference
- A glossary, which contains definitions for all the terms I introduce
- A complete index
0201742047P11142001
Most helpful customer reviews
4 of 4 people found the following review helpful.
Should be widely read by software developers
By A Customer
This book solves a very basic problem with the Rational Unified Process: its apparent mystery and complexity.
You see, Rational's own documentation tends to be overly academic and self-referential, meaning it uses its own lingo heavily to explain the lingo. This serves well as a reference to a practitioner, but no good as an introduction. And you can't get your whole team, much less your customer, to read thick documentation. You can do an overview presentation for the customer, but I believe team members need much greater understanding of the methodology, and they need it *now*, beforehand, not discovering it as they go.
Scott cuts through and succinctly but thoroughly present RUP in about 160 pages. He does this in a consistent, deliberate format. This can be scanned page-by-page in less than 30 minutes by every development team member, and the benefits can be enormous.
In my experience, RUP practitioners tend to be one of two types: overly zealous or overly loose. The former regards the process as a set of decree laws around which everyone, including the customers must suffer. The latter, well. This is unfortunate and is usually the result of the team's insufficient buy-in and understanding of the role of a development methodology like RUP. If Scott's explanations are more widely read and understood, more teams would apply the principles more appropriately and produce better results. This book makes this understanding much easier to achieve. I know I'm getting my whole team to read this.
The bief end sections comparing RUP with Extreme Programming and ICONIX are very helpful in putting all 3 in perspective, again in a clear, demystifying approach.
A minor improvement would have been to present the four phases and five workflows TOGETHER on a few typical visual graphics. He describes them in words as "cuts-through" in a "matrix" but this isn't very helpful, unless of course you already know what he means.
The Unified Process Explained, by Kendall Scott PDF
The Unified Process Explained, by Kendall Scott EPub
The Unified Process Explained, by Kendall Scott Doc
The Unified Process Explained, by Kendall Scott iBooks
The Unified Process Explained, by Kendall Scott rtf
The Unified Process Explained, by Kendall Scott Mobipocket
The Unified Process Explained, by Kendall Scott Kindle
Tidak ada komentar:
Posting Komentar