Free Ebook The Unified Process ExplainedBy Kendall Scott
Never mind if you do not have adequate time to go to the e-book establishment as well as look for the favourite publication to review. Nowadays, the on the internet e-book The Unified Process ExplainedBy Kendall Scott is concerning provide ease of checking out habit. You may not have to go outdoors to search guide The Unified Process ExplainedBy Kendall Scott Searching and also downloading guide qualify The Unified Process ExplainedBy Kendall Scott in this post will certainly give you much better option. Yeah, on the internet e-book The Unified Process ExplainedBy Kendall Scott is a type of digital e-book that you can enter the link download offered.
The Unified Process ExplainedBy Kendall Scott
Free Ebook The Unified Process ExplainedBy Kendall Scott
Having several leisures and also have no concepts to do something when holiday is extremely boring. In such time, you will possibly really feel that you are tired of your activities. Going outside or socializing with your pals might require more money. So, this is right to try attaching to the web and also look for guide collection. If you intend to be created also in your vacations, you can use the priceless collections of publications to check out.
The Unified Process ExplainedBy Kendall Scott has the tendency to be referred publication, not just by this site. Lots of people have actually verified that it actually functions to them. Just how's concerning you? As long as the topic and problem that you ace is related to just what this book has, it will actually assist you. Fixing the troubles can be thought about with several resources. Listening to the other advice is essential. But, getting the truths and ideas from the written resources and also the specialist will certainly be truly finished.
Reserve, will certainly not always belongs to what you have to get. Bok could likewise remain in some numerous styles. Religious beliefs, Sciences, socials, sports, politics, legislation, and also numerous book designs come to be the resources that sometimes you need to read all. Nonetheless, when you have had the analysis routine as well as find out more books as The Unified Process ExplainedBy Kendall Scott, you could really feel much better. Why? Because, your chance to check out is not just for the need because time but additionally for constant tasks to constantly improve and also improve your brighter future as well as life high quality.
It's no any mistakes when others with their phone on their hand, and also you're also. The distinction might last on the product to open The Unified Process ExplainedBy Kendall Scott When others open up the phone for talking and speaking all points, you could occasionally open up and also check out the soft data of the The Unified Process ExplainedBy Kendall Scott Of course, it's unless your phone is available. You could also make or save it in your laptop or computer that relieves you to read The Unified Process ExplainedBy Kendall Scott.
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 Book
The 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
The Unified Process ExplainedBy Kendall Scott PDF
The Unified Process ExplainedBy Kendall Scott EPub
The Unified Process ExplainedBy Kendall Scott Doc
The Unified Process ExplainedBy Kendall Scott iBooks
The Unified Process ExplainedBy Kendall Scott rtf
The Unified Process ExplainedBy Kendall Scott Mobipocket
The Unified Process ExplainedBy Kendall Scott Kindle
The Unified Process ExplainedBy Kendall Scott PDF
The Unified Process ExplainedBy Kendall Scott PDF
The Unified Process ExplainedBy Kendall Scott PDF
The Unified Process ExplainedBy Kendall Scott PDF
