Visual Modeling With Rational Rose and Uml (Addison-Wesley Object Technology Series) - Softcover

Terry Quatrani

Softcover

ISBN 10: 0201310163 ISBN 13: 9780201310160

Publisher: Addison-Wesley Pub (Sd), 1997

Synopsis

As software application development becomes more complex, the benefits of developing a comprehensive "blueprint" enabling developers to visualize the complete scope of a project increase substantially. Three elements are needed to successfully diagram and visualize a software system-a process, a notation, and a modeling tool. This timely new book introduces the reader to three of the most popular and influential such elements; the Rational Objectory process, the Unified Modeling Language (UML), and Rational Rose. With the practical direction offered in this book, you will be able to specify, visualize, document, and create software solutions. Throughout the book, a simplified case study (a course registration system for a university) is employed to illustrate the analysis and design of an application. The presentation is structured to allow concentration on the specifics of modeling the domain without getting bogged down in unnecessary detail. This efficient approach to teaching visual modeling and the application of UML enables you to focus on learning to apply an iterative and incremental process to analysis and design.

Other highlights include: an examination of system behavior from a use case approach a discussion of the concepts and notations used for finding objects and classes an introduction to the concepts and notation needed to create and document a system's architecture a review of the iteration planning process

About this title

About the Author

Terry Quatrani is the Rose Evangelist for Rational Software Corporation, where she is responsible for preaching the visual modeling gospel according to Grady, Jim, and Ivar. During her 17 years of experience in the development and deployment of large software systems, she also worked for General Electric, where she was one of the founding consultants of the Lockheed Martin Advanced Concepts Center.

From the Back Cover

As software application development becomes more complex, the benefits of developing a comprehensive "blueprint" enabling developers to visualize the complete scope of a project increase substantially. Three elements are needed to successfully diagram and visualize a software system--a process, a notation, and a modeling tool. This timely new book introduces the reader to three of the most popular and influential such elements; the Rational Objectory process, the Unified Modeling Language (UML), and Rational Rose. With the practical direction offered in this book, you will be able to specify, visualize, document, and create software solutions.

Throughout the book, a simplified case study (a course registration system for a university) is employed to illustrate the analysis and design of an application. The presentation is structured to allow concentration on the specifics of modeling the domain without getting bogged down in unnecessary detail. This efficient approach to teaching visual modeling and the application of UML enables you to focus on learning to apply an iterative and incremental process to analysis and design.

Other highlights include:

* an examination of system behavior from a use case approach
* a discussion of the concepts and notations used for finding objects and classes
* an introduction to the concepts and notation needed to create and document a system's architecture
* a review of the iteration planning process

Excerpt. © Reprinted by permission. All rights reserved.

Goals

Following martin fowler's style in his book UML Distilled, let me tell you what this book is not.

* It is not a tutorial on all the ins and outs of analysis and design using UML. This is the purpose of the Unified Modeling Language User Guide being developed by Grady Booch (with help from the other amigos).
* It is not a tutorial on all the details in the Rational Objectory Process. This is the purpose of the Objectory Software Development Process being developed by Ivar Jacobson (with help from the other amigos).
* It is not an explanation of all the notation and semantics of the UML. This is the purpose of the Unified Modeling Language Reference Manual being developed by Jim Rumbaugh (with help from the other amigos).
* It is not an abridged explanation of the UML Notation, which is very nicely done in Martin Fowler's book.
* It is not a book on software architecture or C++ design; many books and papers are available on these subjects.

Well then, what is it? This book is an introduction to the concepts needed to visualize a software system--a process, a notation, and a tool. It provides practical guidance on visual modeling, using a limited version of the Rational Objectory Process, the Unified Modeling Language (UML), and the Rational Rose tool. It demonstrates how all three elements (process, notation, and tool) can be used in tandem to specify, visualize, document, and create a software solution to a problem in an iterative and incremental manner. 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 easily understood and is not specific to any field of computer science. The reader 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 the reader practical exercise with visual modeling techniques and the feeling for solving a real problem, without being so realistic that the reader is 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 Software Corporation at product_info@rational.com. You can also visit the Rational website at rational. Chapter Summaries Chapter 1: Introduction

Introduces the techniques, language, and process 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 given after this chapter. Chapter 12: Building the Iterations

Discusses the iteration planning process. This chapter also looks at the UML notation used to specify and document the design decisions that occur during the implementation of an iteration. It does not focus on good (or bad) design decisions, but at the process and notations used to capture the design of an iteration. Appendix A

Provides step-by-step guides to code generation and reverse engineering using the Rational Rose / C++ tool. Future appendixes will be available at the Addison-Wesley website for step-by step guides to the other variants of Rational Rose. Appendix B

Provides sample code generated by Rational Rose/C++. Glossary

Provides definitions of terms used throughout the book.

Edition details

• Publisher: Addison-Wesley Pub (Sd)
• Publication date: 1997
• Language: English
• ISBN 10: 0201310163
• ISBN 13: 9780201310160
• Binding: Paperback
• Edition number: 1
• Number of pages: 240