Visual Modeling with Rational Rose 2000 and UML (2nd Edition) (Addison Wesley Object Technology Series) [Paperback]

Terry Quatrani (Author)

Book Description

ISBN-10: 0201699613 | ISBN-13: 978-0201699616 | Publication Date: October 27, 1999 | Edition: 2

The Unified Modeling Language (UML) offers standard semantics and notation for describing object structure and behavior and has emerged as the design medium of choice for developing large-scale distributed object applications. Augmented by the Rational Unified Process, an extensive set of software development guidelines, and the Rational Rose visual modeling tool, the UML greatly facilitates the development of quality object-oriented applications that meet both deadlines and requirements. Visual Modeling with Rational Rose 2000 and UML is a comprehensive introduction and tutorial providing guidance on how to use a tool (Rational Rose 2000), a process (the Rational Unified Process), and a language (the UML) to successfully visualize, specify, document, and construct a software system. Written by the Rose Evangelist at Rational Software Corporation, a leader in UML and object technology, this book breaks the technology down to its essentials and provides clear explanations of each element. It follows a simplified version of the Rational Unified Process from project inception through system analysis and design. A sample case study running throughout the book illustrates this iterative development process, the UML in practice, and the application of Rational Rose. New appendices demonstrate code generation and reverse engineering using Rational Rose 2000 with the Visual C++, C++, and Visual Basic languages. Topics covered include: *Creating use cases *Finding objects and classes *UML stereotypes and packages *Scenarios, sequence diagrams, and collaboration diagrams *Discovering object interaction *Specifying relationships, association, and aggregation *Adding behavior and structure *Superclass/subclass relationships and inheritance *Object behavior and Harel state transition diagrams *Checking for model consistency *Specifying, visualizing, and documenting system architecture *The iteration planning process 0201699613B04062001

Editorial Reviews

From the Inside Flap

Goals

Two years ago, when I set out to write the first version of this book, I thought, "This should be pretty easy . . . I do this for a living." Boy, was I wrong! Putting into words what I do on a daily basis was one of the hardest things I have ever done (all right, childbirth was more painful, but not by much). But I persevered, spent many, many nights and weekends in front of my computer, and gave birth to Visual Modeling with Rational Rose and UML. I must admit that the first time I saw my book on the bookshelf at a local bookstore, I was thrilled. I also found out that you need to have very thick skin to read book reviews. My book is unique since people seem to love it (5 stars) or they are less than impressed with it (1 star). For some reason, I rarely get a rating in between.

As I write the second version of my book, I would like to address the two camps of reviewers. First of all, to the people who love it, I thank you. It is really nice to have someone say "Good job, I really learned from your book." When I was giving a seminar in New York a gentleman came up to me, holding my book, and said, "Thank you, this book has been a lifesaver." That made my day; in fact, I think it made my week. These people have truly understood the goal of my book: to be a simple introduction to the world of visual modeling.

Now for the people who have been less than impressed: You will probably not like this version either. I say this since the goal of the book has not changed. It is not a complete guide to the UML (these books have been written by Grady and Jim and I am not even going to attempt to compete with the definitive experts). It is not a complete guide to the Rational Unified Process (these books have been written, quite nicely, by Philippe and Ivar). It is not even a good book on C++ (in fact, I usually tell people that I no longer write code for a living, and there is a very good reason that I don't). As I stated, this book is meant to take a simple, first look at how a process, a language, and a tool may be used to create a blueprint of your system. Approach

This book takes a practical approach to teaching visual modeling techniques and the UML. It uses a case study to show the analysis and design of an application. The application is a course registration system for a university. This problem domain was chosen because it is understood easily and is not specific to any field of computer science. You can concentrate on the specifics of modeling the domain rather than investing time in understanding an unfamiliar problem domain.

The problem is treated seriously enough to give you practical exercise with visual modeling techniques and the feeling for solving a real problem, without being so realistic that you are bogged down in details. Thus many interesting and perhaps necessary requirements, considerations, and constraints were put aside to produce a simplified, yet useful case study fitting the scope of this book.

For additional details on visual modeling and the UML or on applying the techniques to your application, you should consider the training and mentoring services offered by Rational Software Corporation. Rational Software Corporation may be contacted at 2800 San Tomas Expressway, Santa Clara, CA 95051, 1-800-767-3237. You may send e-mail to Rational at product_info@rational. You can also visit the Rational website at rational. Chapter Summaries

The ordering and number of chapters in this version of the book have not been changed, but the content of most of the chapters has been updated. The screen shots and Rational Rose instructions have been changed so they reflect what you will see with Rational Rose 2000. The biggest wording changes may be found in Chapters 5 and 11. In Chapter 5, "Discovering Object Interaction," sequence diagrams and collaboration diagrams are now stored in the Logical View of the tool. I have done this so my scaled-down process is more in line with the Rational Unified Process. Chapter 11, "Architecture," has been updated to show the current icon for a component along with the use of lollypop notation for interface classes. I also have included additional appendixes that show how to use Rational Rose with both Visual Basic and Visual C++. Chapter 1: Introduction

Introduces the techniques, language, and process that are used throughout the book. This chapter discusses the benefits of visual modeling, the history of the UML, and the software development process used. Chapter 2: Beginning a Project

Contains information that is related to the Course Registration System case study that is used throughout the book. Chapter 3: Creating Use Cases

Discusses the techniques used to examine system behavior from a use-case approach. Chapter 4: Finding Classes

Discusses the concepts and notations used for finding objects and classes. This chapter also discusses the UML concepts of stereotypes and packages. Chapter 5: Discovering Object Interaction

Discusses the addition of scenarios to the system to describe how use cases are realized as interactions among societies of objects. This chapter also examines how sequence diagrams and collaboration diagrams may be used to capture scenarios. Chapter 6: Specifying Relationships

Illustrates the definition of relationships between classes in the system. Specifically, the concepts of association and aggregation are explored. Chapter 7: Adding Behavior and Structure

Shows how the needed structure and behavior of classes are added to the model under development. Chapter 8: Discovering Inheritance

Illustrates the application of generalization and specialization principles to discover superclass/subclass relationships. Chapter 9: Analyzing Object Behavior

Uses Harel state transition diagrams to provide additional analysis techniques for classes with significant dynamic behavior. Chapter 10: Checking the Model

Discusses techniques used to blend and check models for consistency. These techniques are needed when different teams are working on a single project in parallel. Chapter 11: Designing the System Architecture

Contains an introduction to the concepts and notation needed to specify and document the system architecture. This chapter is not meant to be a tell-all process guide to the development of the architecture--it is meant to be a guide to the notation and process used to specify, visualize, and document the system architecture. It is placed at this point in the structure of the book since the architectural decisions specified in this chapter must be made prior to the information contained in later chapters. Chapter 12: Building the Iterations

Discusses the iteration planning process. It also looks at the UML notation used to specify and document the design decisions that occur during the implementation of an iteration. The chapter does not focus on good (or bad) design decisions--it looks at the process and notations used to capture the design of an iteration. Appendix A: Code Generation and Reverse Engineering with C++

Provides step-by-step guides to code generation and reverse engineering using the Rational Rose 2000 and the C++ language. Appendix B: Code Generation and Reverse Engineering with Visual C++ and Visual Basic

Provides step-by-step guides to code generation and reverse engineering using Rational Rose 2000 and the Visual C++ and Visual Basic languages. Appendix C: A Visual Basic Example

Provides a step-by-step demonstration showing how to create and reuse a Visual Basic DLL. Glossary

Provides definitions of terms used throughout the book. Acknowledgments

I would like to thank a number of individuals for their contributions to the content, style, presentation, and writing of this book.

Special thanks to the following people:

Steve Bailey (Tier Technologies), Naveena Bereny, Kurt Bittner, Grady Booch, Jim Conallen, Ed Delio, Lisa Dornell, Matt Drahzal, Maria Ericsson, Jim Ford, Adam Frankl, Scott Frohman, Jim Gillespie, Dorothy Green, Jon Hopkins, Ivar Jacobson, Jason James, Philippe Kruchten, Eric Lipanovich, Peter Luckey, Greg Meyers, Sue Mickel, Laura Mullins, Larry O'Brien, Sylvia Pacheco, Jim Pietrocarlo, Hugo Sanchez, Charlie Snyder, Lynne Steele, Walker Royce, Jim Rumbaugh, Tom Schultz, John Smith, and Dave Tropeano. I would also like to thank my editor Carter Shanklin and his assistant Kristin Erickson, for without their help this book would never have gone to print.

0201699613P04062001

From the Back Cover

The Unified Modeling Language (UML) offers standard semantics and notation for describing object structure and behavior and has emerged as the design medium of choice for developing large-scale distributed object applications. Augmented by the Rational Unified Process, an extensive set of software development guidelines, and the Rational Rose visual modeling tool, the UML greatly facilitates the development of quality object-oriented applications that meet both deadlines and requirements.

Visual Modeling with Rational Rose 2000 and UML is a comprehensive introduction and tutorial providing guidance on how to use a tool (Rational Rose 2000), a process (the Rational Unified Process), and a language (the UML) to successfully visualize, specify, document, and construct a software system. Written by the Rose Evangelist at Rational Software Corporation, a leader in UML and object technology, this book breaks the technology down to its essentials and provides clear explanations of each element. It follows a simplified version of the Rational Unified Process from project inception through system analysis and design. A sample case study running throughout the book illustrates this iterative development process, the UML in practice, and the application of Rational Rose. New appendices demonstrate code generation and reverse engineering using Rational Rose 2000 with the Visual C++, C++, and Visual Basic languages.

Topics covered include:

• Creating use cases
• Finding objects and classes
• UML stereotypes and packages
• Scenarios, sequence diagrams, and collaboration diagrams
• Discovering object interaction
• Specifying relationships, association, and aggregation
• Adding behavior and structure
• Superclass/subclass relationships and inheritance
• Object behavior and Harel state transition diagrams
• Checking for model consistency
• Specifying, visualizing, and documenting system architecture
• The iteration planning process

0201699613B04062001

See all Editorial Reviews

Product Details

• Paperback: 288 pages
• Publisher: Addison-Wesley Professional; 2 edition (October 27, 1999)
• Language: English
• ISBN-10: 0201699613
• ISBN-13: 978-0201699616
• Product Dimensions: 9 x 7 x 0.7 inches
• Shipping Weight: 1.1 pounds
• Average Customer Review: 3.3 out of 5 stars  See all reviews (21 customer reviews)
• Amazon Best Sellers Rank: #2,494,088 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

19 of 19 people found the following review helpful:

4.0 out of 5 stars good for where the rubber meets the road, June 6, 2000

By A Customer

This review is from: Visual Modeling with Rational Rose 2000 and UML (2nd Edition) (Addison Wesley Object Technology Series) (Paperback)

I've been working on word templates for my project based on the Rational Unified Process (RUP) web pages for my project. We will use these templates to create concept models, design models, code reviews, and inspections.

While the RUP web page provides a great overview of a development process in the large, it lacks much of the details needed when the rubber meets the road. Exact templates for design documents and detailed step-by-step instructions are not provided. Such detail is not the purpose of the RUP pages. This is the primary reason that I am melding RUP and other standards to produce the templates listed above.

I have found that "Visual Modeling with Rational Rose 2000 and UML" by Terry Quatrani is an excellent guide for moving from the inception phase through the elaboration phase and into the implementation phase. The book is a step by step description of the details involved in using Rose 2000 (or 98i) to create use-cases, tie them into design, and move to implementation.

I highly recommend using the Quantrani book as the guide to fill in the details not present in the RUP pages. This edition, while somewhat focused on a single example, is significantly better than the previous edition.

6 of 6 people found the following review helpful:

5.0 out of 5 stars A Must to First Time Rose Users, August 18, 2000

By 

elaine (San Francisco, CA USA) - See all my reviews

This review is from: Visual Modeling with Rational Rose 2000 and UML (2nd Edition) (Addison Wesley Object Technology Series) (Paperback)

I am glad that I had this book when I first started to use Rose. It is well structured and organized. It tells you what you need to do exactly, how to do it step by step. More important, it tells you nothing more. I think this is very important because I often find books that fill with too much information that are not necessary useful to first time users. I also find it is a better manual than the tutorial comes with Rose for a beginner to Rose. Once you know more about Rose, the Rose tutorial/manual will be a better choice.

3 of 3 people found the following review helpful:

4.0 out of 5 stars it is about Visual Modelling and not about UML in details, December 16, 2001

By 

yoppi effendie (berlin, berlin Deutschland) - See all my reviews

This review is from: Visual Modeling with Rational Rose 2000 and UML (2nd Edition) (Addison Wesley Object Technology Series) (Paperback)

This book, just like the title says, is just about visual modelling with rational rose and doesn't explain the details whether about UML or OODA. Just about Visual Modelling.
I recommend this book for peoples who are looking for tutorial in Rational Rose, this will be the right one. But I don't recommend this book anybody, who is looking for UML or OODA books, because it is not the right book for that.
For a tutorial is this book probably too expensive ...