Fundamentals of Rational Rose (Reading Notes)

Fundamentals of Rational Rose

Module 1: Visual Modeling and the
UML

Summary:
Visual modeling Captures business process, Is a
communication tool, Manages complexity, Promotes resuse.
The UML is the
standard language for visualizing, specifying, constructing, and documenting the
artifacts of a software-intensive system.

Module 2: Rose Modeling
Basics

Summary:
Rational Rose uses views and diagrams to depict
varying perspectives and a system's parts.
There are five views
in
Rational Rose: Use-Case View, Logic View, Process View, Component View
(Implementation View), Deployment View.
Diagrams are a graphical means to
view a system's parts.

The browser in the Rose tool shows all of your
model elements.
The diagram tool-bar is unique to each diagram.
The
Options window is used to set all of your defaults for modeling.
Elements
deleted from the browser are deleted from the model.
Elements delete from the
diagram are not necessarily deleted from the model.
You can add elements to a
diagram from either the browser or diagram toolbar.

Module 3: Using Rose in
a Team

Summary:
......

Module 4: The Use-Case
Model

The use-case diagram
is a visual representation of
WHAT the customer wants the system to do.  Shows a sequence of actions a system
performs that yield an observable result and is of value to a particular
actor.

A use case is a sequence of actions performed by the system that
yields a measurable value for an actor.

The navigation direction
represents who is initiating the communication. The end with the arrow indicates
who or what is receiving the communication. An association without an arrowhead
denotes communication in both directions.

Flow of Events Does NOT
describe user interface details.

Summary:
The use-case model is
the visual contract between customer and developer and is a representation of
the system's intend functions and its environment. It is created in the Use-Case
View and include: Use-case diagrams, Use-case flow of events, Project artifacts,
Activity diagrams.

A use-case diagram is an illustration that shows the
relationships among use cases and actors and among related use cases. A use case
represents a major piece of functionality that is complete from begining to end.
An actor is someone or something outside the system that interacts with the
system.

An associaton repationship is the most general relationship and
indicates communication only. A flow of events is a text description of the use
case. An activity diagram in the use-case model is the visual representation of
the flow of events.

Module 5: Use-Case Realization
Structure

Summary:
The use-case realization structure

helps organize model elements necessary to "realize" the use cases in the design
model. The structure includes: Use-case realization packages, Traceabilities
diagrams, Interaction diagrams, Class diagrams.

Module 6: Interaction
Diagrams

An interaction diagram
models the dynamic aspects
of the system by showing relationships among objects and the messages they may
dispatch.

Sequence
Collaboration

Interaction diagrams visually
capture a single instance of a use case's flow of
events.

Summary:
Interaction diagrams show relationships among objects
and model the dynamic aspects of the system. They are created in the Logical
View under the appropriate use-case realization. There are 2 types of
interaction diagrams: Sequence and Collaboration.

Both interaction
diagrams are semantically equivalent. They simply show different perspectives.
At least one interaction diagram is created for each flow through a use case.
Interaction diagrams are made up of Actors, Objects and Messages.

Module 7: Class
Diagrams

Analysis classes represent the FUNCTIONAL

requirements of the problem domain. Design classes represent the NON-FUNCTIONAL

requirements of the solution domain.

Summary:
Class diagrams

show a set of classes, interfaces, and collaborations and their relationships.
They are modeled in the Logical View and show the static view of the system.
They are made up of the following elements: Class and Relationships
(Association, Aggregations, Generalizations)

An aggregate
association
is a type of association in which a whole is related to its
part(s). Association in a class diagram can be further defined with :
Association Names, Role Names, Multiplicity. A generalization is a parent/child
relationship where one class shares the structure and behavior of one or more
classes.

Module 8: Introduction to Round-Trip
engineering

Summary:
....