Aim
To study the concept
and terminologies used in rational rose.
Visual Modeling
In the world today,we have to business
process and computer systems. Asthere is a rapid changes in software
development processes, software professionals have challenges in handling those
changes. That is why modeling comes in,modeling involves capturing the
important real world things and mapping these things to computer system’s
method that is used to show this mapping is called visual mapping.
Modelingcreates a blue print for the system we want to built using a standard
languages that is understood by all. This languages is the UML(Unified Modeling
Language).
Unified Modeling Language
The UML is the standard language for
visualizing,specifying,constructing and documenting the artifacts of the
software system.UML can be used for support your entire life cycle.
- See the interaction with the outside world in the use case diagram
- Visualize object interaction in sequence and collaboration diagram
- Look at the structure of your system by examining class diagram
- View the system architecture by looking at the defined package
- Explore the physical nature of the system using component diagram
UML diagram
UML has set of notations,
conventions and diagrams to describe and model an application. There are 8 UML
diagrams,
Ø
Use case diagram
Ø
Activity diagram
Ø
Sequence diagram
Ø
Collaboration
diagram
Ø
Class diagram
Ø
Component diagram
Ø
Deployment diagram
Ø
State chart diagram
Use case diagram
A use case diagram
is created to visualize the interaction of your system with outside world.It is
a visual representation,what the customer wants to do.It represents a major
piece of functionality that is computer from beginning to end.
Elements
Ø
Use case
Ø
Actor
Ø
Relationship
Use case
A
use case is a sequence of action performed by asystem to yield a measurable
value for an actor. An actor is someone or something outside the system that
interacts with thesystem. A relationship diagram shows the flow of events within
our system. The workflow often consists of a basic flow and one or more
alternate flows.
Activity Diagram
An activity
diagram is a variation of state machine diagram in which the states are
activities representing the performance of operations and the transitions are
triggered by the completion of the operation.
Elements
- Activity – It represents the performance of a task during the work flow.
- Start state – It shows the beginning of the activity diagram.
- End state- It represents a final or terminal state on a activity diagram.
- Static transition - A state transition shows what activity flows after another.
- Decision - A decision is a point in an activity diagram where guard conditions are used to indicate different possible transactions.
- Synchronization bars – It allows you to show concurrent thread in a work flow of a use case.
Sequence diagram
A sequence diagram shows step by step
what must happen to accomplish a piece of functionality provided by the system.
Elements
Ø
Actor
Ø
Objects
Ø
Messages
Ø
Life line
Ø
Focus of
control
Actor: An actor is someone or something outside
the system that interacts with the system either by giving or receiving
information or both.
Objects: An object is an instance of a class.
Messages: A message is a communication between two
objects that trigger an event
Life Lines: A life line represents aexistence of the
object at the particular time.
Focus of control: It shows a period of time during which an
object is performing an action either directly or through a subordinate
procedure.
Collaboration diagram
A collaboration
diagram displays objects and their links to one another.
Elements
Ø
Actor
Ø
Objects
Ø
Links
Ø Messages
Actors:
An actor is someone
or something outside the system that interacts with the system either by giving
or receiving information or both.
Objects:
An object is an
instance of a class.
Links:
A link is the
pathway for communication between the collaboration diagram.
Messages: A message is a communication between two
objects that trigger an event.
Class diagram
Class is aset of
objects that shares the same attributes,operations,relationship and semantics.
Association
An association is
the most general relationship and indicates the relationship between classes.
Generalization
A generalization is
a parent child relationship where one class shares the structure and of more
classes.
Multiplicity
It is the number of
instance of another class
Eg:
0......n,1.......n, 0........1
Association name
An association name
is the labeled that classifies the meaning of the association.
Role name
A role name is the
label that is specifiedat the end of the association.
Rational Rose interface
The Rational rose
interface includes the following
- Browser
- Diagram window
- Diagram toolbar
- Documentation window
- log window
The Browser
The browser allows you to textually view and
navigate the views and diagrams in Rational Rose.
Diagram window
The diagram window
allows you to create and update graphical views of the current model .
Diagram Toolbar
The diagram toolbar
is includes the element to build a diagram .Each diagram Toolbar is unique to
that diagram. It will be active only when the diagram is displayed.
Documentation window
It is used to create
view or modify text that explains a selected item within a diagram.
Log window
Log window reports
progresses, result and errors.
Result
Thus the concept and
terminologies of Rational Rose were studied.
No comments:
Post a Comment