Home > Store

Visual Modeling with Rational Rose 2002 and UML, 3rd Edition

Register your product to gain access to bonus material or receive a coupon.

Visual Modeling with Rational Rose 2002 and UML, 3rd Edition

Book

  • Sorry, this book is no longer in print.
Not for Sale

Description

  • Copyright 2003
  • Dimensions: 7" x 9"
  • Edition: 3rd
  • Book
  • ISBN-10: 0-201-72932-6
  • ISBN-13: 978-0-201-72932-0

The third edition of this popular book retains the practical approach to teaching visual modeling techniques and the industry standard Unified Modeling Language. Author Terry Quatrani, the Rose Evangelist from Rational Software Corporation, still uses the simplified case study (a course registration system for a fictional university) that has taught thousands of readers how to analyze and design an application using UML, and how to implement the application using Rational Rose. The screen shots and Rational Rose instructions have been updated to reflect the release of Rational Rose 2002. After a short history of the evolution of UML and a guide to the basic terms of software engineering, the book introduces the concept of requirements, use cases, and class diagrams. Further chapters move toward defining an architecture and even refining the design within the incremental methodology of Rational Rose.

Sample Content

Online Sample Chapter

Introduction to Visual Modeling with Rational Rose 2002 and UML

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 1

Table of Contents

(NOTE: Each chapter concludes with a Summary.)

Foreword.


Preface.


1. Introduction.

What Is Visual Modeling?

The Triangle for Success.

The Role of Notation.

History of the UML.

The Role of Process.

What Is Iterative and Incremental Development?

The Rational Unified Process.

The Rational Rose Tool.



2. Beginning a Project.

Defining the Right Project.

Eastern State University (ESU) Background.

Risks for the Course Registration Problem.

ESU Course Registration Problem Statement.



3. Creating Use Cases.

System Behavior.

Actors.

Use Cases.

Use Case Relationships.

Use Case Diagrams.

Activity Diagrams.



4. Finding Classes.

What Is an Object?

State, Behavior, and Identity.

What Is a Class?

Stereotypes and Classes.

Discovering Classes.

Documenting Classes.

Packages.

Objects and Classes in the ESU Course Registration Problem.

Class Diagrams.



5. Discovering Object Interaction.

Use Case Realization.

Documenting Scenarios.

Sequence Diagrams.

Sequence Diagrams and Boundary Classes.

Complexity and Sequence Diagrams.

Collaboration Diagrams.

Why Are There Two Different Diagrams?

Sequence Diagram for the ESU Course Registration System.



6. Specifying Relationships.

The Need for Relationships.

Association Relationships.

Aggregation Relationships.

Association or Aggregation?

Naming Relationships.

Role Names.

Multiplicity Indicators.

Reflexive Relationships.

Finding Relationships.

Package Relationships.



7. Adding Behavior and Structure.

Representing Behavior and Structure.

Creating Operations.

Documenting Operations.

Relationships and Operation Signatures.

Creating Attributes.

Documenting Attributes.

Displaying Attributes and Operations.

Association Classes.



8. Discovering Inheritance.

Inheritance.

Generalization.

Specialization.

Inheritance Trees.

Single Inheritance versus Multiple Inheritance.

Inheritance versus Aggregation.



9. Analyzing Object Behavior.

Modeling Dynamic Behavior.

States.

State Transitions.

Special States.

State Transition Details.

State Details.



10. Checking the Model.

Why Homogenize?

Combining Classes.

Splitting Classes.

Eliminating Classes.

Consistency Checking.

Scenario Walk-Through.

Event Tracing.

Documentation Review.



11. Designing the System Architecture.

The Need for Architecture.

The Architecture Team.

The 4+1 View of Architecture.

The Logical View.

The Implementation View.

The Process View.

The Deployment View.

The Use Case View.



12. Building the Iterations.

The Iteration Planning Process.

Designing the User Interface.

Adding Design Classes.

The Emergence of Patterns.

Designing Relationships.

Designing Attributes and Operations.

Designing for Inheritance.

Coding, Testing, and Documenting the Iteration.

Using Reverse Engineering to Set the Stage for the Next Iteration.



Appendix A: Code Generation and Reverse Engineering with C++.


Appendix B: Code Generation and Reverse Engineering with Visual C++ and Visual Basic.


Appendix C: A Visual Basic Example.


Glossary.


Index. 0201729326T09262002

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. 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.



0201729326P09262002

Index

Click below to download the Index file related to this title:
Index

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020