Visual Modeling with Rational Rose 2002 and UML / Edition 3

Paperback (Print)
Rent
Rent from BN.com
$15.97
(Save 71%)
Est. Return Date: 06/22/2014
Buy Used
Buy Used from BN.com
$32.35
(Save 41%)
Item is in good condition but packaging may have signs of shelf wear/aging or torn packaging.
Condition: Used – Good details
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 96%)
Other sellers (Paperback)
  • All (35) from $1.99   
  • New (5) from $9.85   
  • Used (30) from $1.99   

Overview

Within the space of just a few years, the Unified Modeling Language (UML) has emerged as the design medium of choice for developing large-scale distributed object applications. The UML's standard semantics and notation for describing object structure and behavior make it particularly well suited to this function. 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 process of developing quality object-oriented applications that meet both deadlines and requirements.

Fully updated and revised, Visual Modeling with Rational Rose 2002 and UML is a comprehensive introduction and tutorial that shows how to use a tool (Rational Rose 2002), a process (the Rational Unified Process), and a language (the UML) to successfully visualize, specify, document, and construct a software system. This timely new edition, written by the UML Evangelist at Rational Software Corporation, breaks the technology down to its essentials and provides clear explanations of each element. The book follows a simplified version of the Rational Unified Process from project inception through system analysis and design. The popular sample case study from the previous editions (a registration system for a fictional university) has been retained and updated, now better illustrating the iterative development process in practice, the UML in action, and the proper application of Rational Rose 2002. Newly updated appendixes demonstrate code generation and reverse engineering using Rational Rose 2002 with the C++, Visual C++, and Visual Basic programming languages. In addition, a handy glossary defines keyobject technology and software modeling terms.

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
Read More Show Less

Product Details

  • ISBN-13: 9780201729320
  • Publisher: Addison-Wesley
  • Publication date: 10/9/2002
  • Series: Addison-Wesley Object Technology Series
  • Edition description: New Edition
  • Edition number: 3
  • Pages: 288
  • Product dimensions: 7.00 (w) x 9.06 (h) x 0.59 (d)

Meet the Author

Terry Quatrani, IBM Rational’s UML Evangelist, is responsible for training and transitioning Fortune 500 companies to object technology and for preaching the visual modeling gospel of Grady Booch, Jim Rumbaugh, and Ivar Jacobson. She has spent twenty-one years developing and deploying large software systems. Formerly at GE, she was founding consultant for the Lockheed Martin Advanced Concepts Center.

Read More Show Less

Read an Excerpt

Goals

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.

I have also figured out that writing a book that is tied to a tool is like rearing a child—it needs constant care. So, once again, I have spent hours in front of my computer updating my book to adhere to the features found in Rational Rose 2002. And no, writing it has not gotten much easier. As far as the two camps of reviewers, nothing will change there. If you liked the first two versions, you will like this one since the goal of the book has not changed: to be a simple introduction to the world of visual modeling.

If you were less than impressed with the first two versions, you will probably not like this version either. 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. Details may be found at the Rational website: www.rational.com.Chapter Summaries

The ordering and number of chapters in this version of the book have not been changed, but the content 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 2002.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 2002 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 2002 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.

Read More Show Less

Table of Contents

Foreword
Preface
Ch. 1 Introduction 1
Ch. 2 Beginning a Project 13
Ch. 3 Creating Use Cases 19
Ch. 4 Finding Classes 51
Ch. 5 Discovering Object Interaction 71
Ch. 6 Specifying Relationships 87
Ch. 7 Adding Behavior and Structure 103
Ch. 8 Discovering Inheritance 117
Ch. 9 Analyzing Object Behavior 129
Ch. 10 Checking the Model 143
Ch. 11 Designing the System Architecture 151
Ch. 12 Building the Iterations 169
App. A Code Generation and Reverse Engineering with C++ 187
App. B Code Generation and Reverse Engineering with Visual C++ and Visual Basic 209
App. C: A Visual Basic Example 221
Glossary 239
Index 249
Read More Show Less

Preface

Goals

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.

I have also figured out that writing a book that is tied to a tool is like rearing a child—it needs constant care. So, once again, I have spent hours in front of my computer updating my book to adhere to the features found in Rational Rose 2002. And no, writing it has not gotten much easier. As far as the two camps of reviewers, nothing will change there. If you liked the first two versions, you will like this one since the goal of the book has not changed: to be a simple introduction to the world of visual modeling.

If you were less than impressed with the first two versions, 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 UnifiedProcess (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. Details may be found at the Rational website.

Chapter Summaries

The ordering and number of chapters in this version of the book have not been changed, but the content 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 2002.

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 2002 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 engi-neering using Rational Rose 2002 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.



Read More Show Less

Customer Reviews

Average Rating 5
( 1 )
Rating Distribution

5 Star

(1)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Anonymous

    Posted October 4, 2004

    Awesome

    The book is very useful to beginers, who would like to do modeling using Rational Rose. I will defenitely recommend this book to all novice people out there.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)