Rational Rose Rational rose is an object-oriented Unified Modeling Language (UML) software design tool used for visual

modeling. A software designed users Rational Rose to visually create models or frameworks for an application by creating blocks of classes with 1. Actors ( Stick Figures ) 2. Use Case Elements (Ovals ) 3. Objects ( Rectangles ) 4. Relationships ( Arrows ) In a sequence diagram using drag and drop symbols. Rational Rose stores the diagram as it is being constructed and then generates code in one of the following languages :

C++ Visual Basic Java Oracle Cobra Data Definition Language

Two popular features of Rational Rose are ability to provide : 1. Iterative development or Evolutionary development Iterative development is creating applications in stages with the output of that iteration becoming the input to the next iteration. Rational Rose allows designers to take advantage of iterative development This is in contrast to the waterfall development where the whole project is completed from start to finish before the user gets to try it. 2. Round-trip Engineering As the developer begins to understand how the components interact and makes modifications in design, Rational Rose can perform round-trip engineering by back and updating the rest of the model to ensure the code remains consistent.

USE CASE DIAGRAM A use case diagram visually represents what happens when an actor interacts with a system. Therefore a use case diagram captures the functional aspects of the system. Use case diagram describes what a system does from the standpoint of and external observer. The emphasis is on what the system does rather than how the system does. Use case diagrams are usually used for requirement analysis. The components of Use Case Diagram are: 1. System: System is shown as rectangle with the name of the system inside the rectangle. System is the scenario within which all the use cases occur. 2. Actors: Actors are also called stick figures and are represented by:

Actors are uses who initiate the events involved in that task or problem statements. These are external entities of the system are not included in the system. 3. Use Case: These are represented by:

These are the functional part of the system. When we say, what an actor does, that is the use case. Eg.: the customer Browses the internet Books ticket Searches for the books are all use cases. Many actors share a common use case When a use case is not associated with any actor then that use case is considered unnecessary. These are present inside the system box as these represent the system.

4. Types of Relationships: a. Dependency: It is represented as:

A dependency is a type of relationship that signifies that one element, or group of elements, acting as the client depends on another element or group of elements that act as a supplier. It is a weak relationship that denoted that if the supplier is changed, the client may be affected. It is a unidirectional relationship. Dependency is a relationship which specifies that one element cannot exist without another. The dependent element is called the client, and the one on which it depends is called the supplier. For example, shooting a scene is a client of cameraman because it cannot exist without him. b. Include: This relationship is represented by dotted line with an arrow head with a label include

Include is a directed relationship between two use cases, implying that behavior of the included use case is inserted into the behavior of the including case. Eg: In the example we see that Make Payment includes By Cash, B Card and By Net Banking, It means that payment can be made in cash, card or net banking.

Included use cases have the same property as including use case except that including use case outputs describe the including use case. Thus include extracts truly common behaviors between the use cases. c. Extend: This relationship is represented by a dotted line with an arrow head with a label extend

In this interaction a given use case may extend another.The relationship indicates that the behavior of the extension use case may be inserted in extended use case. Eg:

Here login use case remains on one page, while submit moves from the login page to another page. Thus the behavior of login use case has been extended.

d. Association: Associations are shown between actors and use cases by an arrow or a solid line between them.

This only represents the actor using the use case. The arrow head indicated the direction of relationship or indicated primary actor within the use case. e. Generalization: Generalization relationship is indicated by:

When two or more use cases or actors are specialized and some of their common properties be related then a more generalized use case or actor is used to indicated generalization.