The first part about this tutorial
Welcome to Rational Rose Tutorial Rational Rose is a visual modeling tool for developing robust, effective solutions in C / S, distributed corporate environments to meet real business needs. This tutorial teaches you how to use Rose by guiding the real implementation of a complex business problem.
Estimation Completion Time: It takes about 10 hours to complete the entire tutorial. Of course, you can start and end from any part, and the remaining part will be seen later. Each portion also has time required to complete this part, such as about 5 minutes.
Example Model: In this tutorial, you will develop a POS system for a fiction called Classics. Classics is a rapidly growing chain, operating classic music, movies, books. The company's POS system is outdated, and now you must make a new set of order processing and implementation systems (OPFS). As this tutorial continues to deepen, you will develop an OPFS system to help Classics better manage their stores and inventories.
Is the tutorial suitable for me? If you have a little or there is no Rational Rose knowledge, you can use this tutorial. Of course, you have to have some basic understanding of Windows (NT / 95/98) Operating System, Object-Oriented Analysis & Design (OOAD).
How is this tutorial organization? This tutorial is conducted in accordance with the behavior steps in business and application modeling, each part is based on the knowledge presented in the previous part. But every part is a separate unit. This means you can start from any part and skip the rest. For example, if you understand business modeling, you can skip the Part 3 directly on Part 4.
Can I follow the order of each part? In accordance with the order of each part, you can simulate a real-world development environment. After reading the introduction materials of the first and Part 2, naturally enter the work of the OPFS of Part 3. In Part 3, you will start the business modeling of Classic. Next, modeling applications and implementation are made. Code and positive reverse model and code will be generated in the final part
What is there in each part? Each section contains:
l (a introduction to what you want to do and why dry)
l (a time required to complete this section) estimation
l (a sample model developed by a completed section)
l (a detailed guidance of the characteristics introduced in this section) 'Try a try'
l A completed model
l (a characteristic of Rose learned in this section)
Use a sample model This tutorial uses a handleman's way to teach you how to learn Rational Rose. At each part, you want to load a semi-finished model for this part. As the directive, the model is refined and enters the next development phase. If you choose to skip some part, you can still use the back model, as long as the appropriate sample model is loaded
Additional Information You can get other information about Rational Rose, including terminology and visual text
What is the next step? Part 2 relates to the advantages of modeling, and introduces some main principles of Rational ROSE
Part II for Rose
About this section This section introduces you to model the RATIONAL ROSE. In this section, you will learn how to help you produce better software. You can also learn some basic knowledge using ROSE.
Estimation Completion Time: About 15 minutes
What is visual modeling? Visual modeling is the process of describing the system developed in a graphic manner. Visual modeling allows you to make a necessary detail of a complex problem, filtering unnecessary details. It also provides a mechanism for observing the development system from different perspectives.
Why model it? Designing a software model is like a building that requires a blueprint. Good models can: l Different demand and communication information
l How to interact with the components of the system, rather than trapped in specific details
l Make you understand the relationship between design components.
l Improve cross-team communication by using a common graphic language
Why use Rational Rose? There is a lot of reasons to explain your development work using Rational Rose. Just say a few:
l
Development of model-driven development can improve developers' productivity
l Use case and focus on business development energy improvement software quality
l Common standard language - (UML) can improve team communication
l Reverse engineering capabilities allow you to integrate traditional OO systems
l Model and code Keep synchronization by development cycle
Rose version
Rose
There are three available versions now:
l Rose Modeler - No language support
l Rose Professional - only supporting a language
l Rose Enterprise - Support multiple languages include (VC , VB, Java, And Corba)
All versions of ROSE can use this tutorial. But decided to version of the ROSE you use, you may not have the functions of all parts in this tutorial.
Rose GUI
You may have been familiar with the GUI convention used in ROSE.
l Standard toolbar
l Chart Toolbox
l Chart window
l text window
l Specification (description)
These items will continue to introduce. As for how these entries are used, where used, and why use, will gradually be clear during your study.
Toolbar and Toolbox
The ROSE standard toolbar is located near the top of the window and is always displayed - independent of today's graphical type. In Rose, when placing the mouse pointer on the toolbar, the tooltip of the corresponding icon will be displayed.. Depending on the illustrated diagram, Rose's chart toolbox will make a corresponding change (show in a window with blue title bar.) Is the same as the standard toolbar, when you put the mouse pointer to the corresponding When the icon is on, the tooltip of the corresponding icon will be displayed. .
Chart window
You can create, present, or modify the ROSE block diagram in the chart window. If you let multiple boxes open at the same time, they or laminated or tiles. A stacked window is divided into a field that is partially arranged in size, and all of the diagrams are visible.
The Browser
Rose browser is to allow you to watch the name of the representative diagram and model elements and a hierarchical navigation tool for the image. The positive ( ) flag is close to the icon indicates that the project is folded, and the information is located under the column. Click Sign, the tree is deployed. Instead, the negative (-) logo indicates that those who enter the fully expanded column. If the browser is not displayed, select the browser from the View menu.
Documentation window
The documentation window allows you to create a document your own model and generate a document yourself through the model.
You can create, view, or modify information in the documentation boxes you can, or those who are described in those vectors.
If the documentation window is invisible, select the documentation from the view menu. If there is a check of the symbol next to the document, and you still can't see the window, then move your cursor to the bottom of the browser. When the pointer cursor becomes a decoller cursor, drag the browser window to display the documentation window.
This window makes the corresponding update when you choose a different map.
Model view
It is like a lot of works in the construction of the house. Rational Rose organizes the following views in the software engineering together: 1 case
l logic
l component
l Deployment
These views, each of which reflects the different aspects of the model, which will explain in the subsequent process.
Modal view
Use an example to help you understand and use the system. This view observes how the executor and the use case are interacting.
The block diagram in this view is:
l
Use case
l sequence diagram
l collaboration map
l
This view contains a master block diagram in the default. In addition, the block diagram will increase during the analysis and design of the entire process.
Logical view
Logical views are used for system feature requirements. This view focuses on the relationship between classes and classes.
The block diagram in this view is:
l map
l status map
This view contains a master block diagram in the default. In addition, the block diagram will increase during the analysis and design of the entire process.
Component view
Component view for software organization structure of the system. This view contains information about the software, system of executable and class library components. This view only contains a component diagram.
This view contains a master block diagram in the default. In addition, the block diagram will increase during the analysis and design of the entire process.
Configuration view
Configure the view display software in the hardware environment. This picture is very useful in applications and servers in a different location of a distributed architecture.
This view only has a block diagram - configuration diagram.
block diagram
In short, a block diagram is a graphical representation of your system elements. Different block diagram types allow you to observe your system from multiple perspectives. You can create different types of block diagrams in Rational Rose. Box diagram include:
l use example
l map
l
l status map
l component diagram
l configuration diagram
Each block diagram will be introduced later. to be continued……
Welcome to Rose, Together and UML QQ group 3487395
Welcome to Rose, Together and UML QQ group 3487395
Welcome to Rose, Together and UML QQ group 3487395
