Tobey Hiller; Phillip Ziegler:Recreating Partnership: A Solution-Oriented, Collaborative Approach to Couples Therapy
- Livro de bolso 2010, ISBN: 9780393703498
Edição encadernada
Longman Pub Group. Very Good. Paperback. 1998. 188 pages. <br>Use Cases allow a system architect to identify the required features of a software system based upon how each end-u se… mais…
Longman Pub Group. Very Good. Paperback. 1998. 188 pages. <br>Use Cases allow a system architect to identify the required features of a software system based upon how each end-u ser will use the system. This guide gives readers more control ov er the development of their projects, enabling them to deliver a software project on time and under budget. Editorial Reviews Am azon.com Review With the emergence of the Unified Modeling Langua ge (UML) over the last few years, developers new to the advantage s of thorough software-engineering practices now have a better no tational system for designing more effective software. To use UML effectively, you will want to create use cases, which help descr ibe the requirements of a system. In their concise and very reada ble book, the authors of Applying Use Cases show how use cases ca n benefit all aspects of the software-design process and let you create better software in less time. This guide provides a case study for a mail-order business (with some e-commerce as well) as its central example. Use cases define how actors (i.e., users) a re defined for all the various components of a mail-order busines s, including inventory, accounting, and order fulfillment. The au thors suggest that while use cases are particularly useful at the beginning of a project cycle--for assessing risks and setting pr oject timetables, for instance--they are also useful for testing and deployment of systems (specifically, for creating documentati on and help manuals). The sample use cases--and supporting design documents--are what's best in this text. --Richard Dragan From the Inside Flap You're about to start a new project. Sometimes it seems like colonizing the moon would be easier. But you assemb le a stalwart team and prepare to set sail on the good ship Requi rements hoping to reach the fabled land of Success. They say ther e are no failed projects in Success and the profit margin is so h igh, the streets are paved with gold. There are many dangers be tween here and Success. Many a ship is sunk on the way some say a s many as 80 percent never reach that fabled land. You query thos e who have tried before. Use a ship from the OO line, they say. B ooch, OMT, OOSE, UML are all good models to choose from. You'll a lso need a chart showing risks along the way and an architecture of the major land masses. And finally you'll need to plot a cours e of use cases to reach your destination. Use Cases are included in the Unified Modeling Language and are used throughout the Rati onal Unified Process. They are gaining wide acceptance in many di fferent businesses and industries. Most often, use cases are appl ied to software projects and enterprise-wide applications. This book is for anyone interested in applying use cases to project d evelopment. While we can't guarantee you will always have success ful projects when using use cases, we can give you another way of looking at the projects you are developing and some tools that w ill make success more likely. You will get more benefit out of th e book if you have some basic knowledge of object-oriented concep ts. We will use the Unified Modeling Language for the notation, e xplaining the notation as we use it. A good book to use for refer ence on the notation is UML Distilled by Fowler. This is an excel lent book on the topic and easy to read. This book is organized using the Rational Unified Process as a framework. Within the ph ases of the process, we talk about the activities in the phase, f ocusing on activities based on use cases. We touch lightly on act ivities that interact with use cases, such as software architectu re, project management, and object-oriented analysis and design. These are very important activities, with whole books devoted to each topic. Therefore, in the resource list in Appendix A, you wi ll find our favorite books on these topics. We have used one ex ample, an order-processing system for a mail order company, throu ghout the book. This allows us to maintain consistency and build up a reasonably complex example. Parts of the solution are given in the various chapters to illustrate the concepts. This book i s presented as a sequence of steps, though life is never that sim ple. Each part will contribute to the rest until the system is co mplete. So if a section says to create an architecture, do what y ou can at that time, using what you currently know. You will add to it and refine it based on knowledge gained while working throu gh the process. You don't have to read the whole book before st arting with use cases. Chapters 1 through 5 give the basics of wo rking with use cases. We recommend that everyone reads those chap ters. Chapter 6 covers architecture and mapping use cases into th e architecture. Chapter 7 covers documenting use cases. Chapter 8 covers project planning with use cases, and Chapter 9 covers rev iewing the use case documents. Chapter 10 goes into moving from u se cases to OOAD. Ultimately, use cases are about documenting you r system. Plan on doing a lot of writing. Appendix A provides a l ist of books we reference throughout the text, as well as other b ooks we have found useful when developing projects. Appendix B sh ows the document templates used. These provide an example and a s tarting point for your own project. Modify them as needed to work with your project. In October of 1995, Rational Software Corpor ation merged with Objective Systems. Among other things, this mer ger brought with it Ivar Jacobson and his use cases. In February 1996, I wrote and delivered the first use case course for Rationa l, which combined use cases with the object-oriented methodologie s of Grady Booch and Jim Rumbaugh. Since that time, I have taught and run workshops on use cases with many of Rational's customers , as well as customers of my consulting company, Wyyzzk Training and Consulting. As I have taught them, so they have taught me. Th is book came out of what I've learned through the workshops. Ac knowledgments Thanks to: My parents, Phil and Joan Schneider. T heir love and faith give me the confidence to reach for the stars and the persistence to succeed. My professors at Southern Illi nois University, Edwardsville, in particular Dr. Nadine Verderber , Dr. Greg Stephen, and Dr. Eric Sturley. The education I receive d has proved to be a firm foundation on which I could build knowl edge and skills. Dr. Ivar Jacobson for the original work on use cases. I've built on the foundations he defined. Thanks also for his comments on the book in its early stages. His comments got m e past a stuck point at a critical time. My colleagues at Ratio nal Software Corporation for their encouragement and support, par ticularly the men and women in the North American Field Organizat ion, the International Field Organization, and Technical Support. Each one is an outstanding engineer, always willing to share wit h the rest what he or she has learned. This free exchange of idea s has been invaluable for maturing the processes we all teach use cases, OOAD, and OOPM. In particular I want to thank my former t eam, Deborah Bell, Sue Mickel, and Jean-Pierre Schoch, for their support and encouragement. Neal Reizer, Bill Fairfield, and Gar th Andrews for their support and encouragement and my customers a nd students, who taught me much while I was mentoring them. Kar in Palmkvist who helped us tremendously by doing a final review o f the manuscript. Bob and Norma Hughes for mowing our lawn when we got too busy with the book to do it. And we didn't even ask! Special thanks to Dr. James Rumbaugh. He has helped me through the publishing process, giving advice and encouragement along the way. His intercession led to Addison-Wesley reviewing and publis hing this book. Many thanks to our distinguished reviewers. They worked as hard as we did to make this book happen. Kurt Bittner - - Rational Software Corporation Lois Delcambre -- Professor, Comp uter Science and Engineering Department, Oregon Graduate Institut e Kelli A. Houston -- Rational Software Corporation John Sunda Hs ia Dean Larsen Phil Price -- Qualcomm Arthur J. Riel Somboon Supa kkul Speaking of hard workers, we were most fortunate to be work ing with J. Carter Shanklin, Angela Buenning, Rachel Beavers, and Krysia Bebick at Addison Wesley Longman. Our most heartfelt than ks for all your support and encouragement. You guys did all the t ough work to make this book a reality. Special thanks to Marilyn Rash, and her team of editing and typesetting experts, who made s ure this book got through production. Last, but not least, than k you to Jason Winters for his love, support, and encouragement. He is the storyteller who brought the book to life. His unique in sights brought clarity to a sometimes difficult subject. Geri Sch neider Winters Santa Clara, California 0201309815P04062001 From the Back Cover Many projects struggle to define the specific fun ctions of software, and end users often find that the final produ ct does not perform as expected. Use cases allow analysts to iden tify the required features of a software system based on how each end user will use the system. This efficient and straightforward analysis process gives end users direct input into the design of the system that will serve them. Applying Use Cases provides a practical and clear introduction to developing use cases, demons trating their use via a continuing case study. Using the Unified Software Development Process as a framework and the Unified Model ing Language (UML) as a notation, the authors step the reader thr ough applying use cases in the different phases of the process, f ocusing on where and how use cases are best applied. Other high lights include: A collection of realistic examples showing how to apply use cases, drawn from the authors' extensive experience in this area A case study that offers insight into the common m istakes and pitfalls that can plague an object-oriented project An illustration of the latest version of the UML notation for di agramming use cases A practical how-to discussion on applying u se cases to identify system requirements 0201309815B04062001 About the Author Geri Schneider is the founder of Wyyzzk, Inc. a company focused on improving the practice of software product dev elopment. She specifically helps companies improve in the areas o f business agility, solution anthropology, iterative development, business architecture, and software architecture. She has taught software engineering courses at Northern Arizona University, Uni versity of California, Carnegie Mellon University, and HiLCoE Col lege. In her spare time she mentors a FIRST Robotics team.  Jaso n P. Winters is a staff research engineer at the Robotics Institu te of Carnegie Mellon University. He has previously been a staff engineer for Cadence Design Systems and Octel Communications. In his spare time he mentors a FIRST Robotics team and indulges his passion for photography. 0201309815AB04062001 From the Inside Fl ap You're about to start a new project. Sometimes it seems like colonizing the moon would be easier. But you assemble a stalwart team and prepare to set sail on the good ship Requirements hoping to reach the fabled land of Success. They say there are no faile d projects in Success and the profit margin is so high, the stree ts are paved with gold. There are many dangers between here and Success. Many a ship is sunk on the way some say as many as 80 p ercent never reach that fabled land. You query those who have tri ed before. Use a ship from the OO line, they say. Booch, OMT, OOS E, UML are all good models to choose from. You'll also need a cha rt showing risks along the way and an architecture of the major l and masses. And finally you'll need to plot a course of use cases to reach your destination. Use Cases are included in the Unified Modeling Language and are used throughout the Rational Unified P rocess. They are gaining wide acceptance in many different busine sses and industries. Most often, use cases are applied to softwar e projects and enterprise-wide applications. This book is for a nyone interested in applying use cases to project development. Wh ile we can't guarantee you will always have successful projects w hen using use cases, we can give you another way of looking at th e projects you are developing and some tools that will make succe ss more likely. You will get more benefit out of the book if you have some basic knowledge of object-oriented concepts. We will us e the Unified Modeling Language for the notation, explaining the notation as we use it. A good book to use for reference on the no tation is UML Distilled by Fowler. This is an excellent book on t he topic and easy to read. This book is organized using the Rat ional Unified Process as a framework. Within the phases of the pr ocess, we talk about the activities in the phase, focusing on act ivities based on use cases. We touch lightly on activities that i nteract with use cases, such as software architecture, project ma nagement, and object-oriented analysis and design. These are very important activities, with whole books devoted to each topic. Th erefore, in the resource list in Appendix A, you will find our fa vorite books on these topics. We have used one example, an orde r-processing system for a mail order company, throughout the book . This allows us to maintain consistency and build up a reasonabl y complex example. Parts of the solution are given in the various chapters to illustrate the concepts. This book is presented as a sequence of steps, though life is never that simple. Each part will contribute to the rest until the system is complete. So if a section says to create an architecture, do what you can at that time, using what you currently know. You will add to it and refi ne it based on knowledge gained while working through the process . You don't have to read the whole book before starting with us e cases. Chapters 1 through 5 give the basics of working with use cases. We recommend that everyone reads those chapters. Chapter 6 covers architecture and mapping use cases into the architecture . Chapter 7 covers documenting use cases. Chapter 8 covers projec t planning with use cases, and Chapter 9 covers reviewing the use case documents. Chapter 10 goes into moving from use cases to OO AD. Ultimately, use cases are about documenting your system. Plan on doing a lot of writing. Appendix A provides a list of books w e reference throughout the text, as well as other books we have f ound useful when developing projects. Appendix B shows the docume nt templates used. These provide an example and a starting point for your own project. Modify them as needed to work with your pr, Longman Pub Group, 1998, 3, Esri Press. Very Good. 7.56 x 1.2 x 9.12 inches. Paperback. 2010. 592 pages. <br>Getting to Know ArcGIS Desktop introduces principl es of GIS as it teaches the mechanics of using ESRI's leading tec hnology. Key concepts are combined with detailed illustrations an d step-by-step exercises to acquaint readers with the building bl ocks of ArcGIS© Desktop including ArcMap™, for displaying and que rying maps, ArcCatalog™, for organizing geographic data, and Mode lBuilder™, for diagramming and processing solutions to complex sp atial analysis problems. Its broad scope, simple style, and pract ical orientation make this book an ideal classroom text and an ex cellent resource for those learning GIS on their own. A data CD f or working through the exercises and a fully functioning 180-day trial ArcGIS© Desktop 10 software is included. Editorial Reviews About the Author Tim Ormsby, Eileen Napoleon, Robert Burke, Car olyn Groessl, and Laura Feaster are all technical writers at ESRI Press and authors of Getting to Know ArcView GIS and Extending A rcView GIS, They live in Redlands, California. After receiving h er master's degree in geography, Eileen J. Napoleon went to work as a geographer, first for the U.S. Forest Service, and later for ESRI, where she has worked in GIS education for the last 15 year s. Burke is an ESRI instructors. Carolyn Groessl was a technica l writer for ESRI Press. ., Esri Press, 2010, 3, O'Reilly Media, Incorporated. Used - Very Good. Ships from the UK. Used book that is in excellent condition. May show signs of wear or have minor defects., O'Reilly Media, Incorporated, 3, W. W. Norton & Company, 2001-07-15. Hardcover. Used: Good., W. W. Norton & Company, 2001-07-15, 2.5<
