Learning modeling tool rose (2)

Overview

In this ever-changing era of object-oriented application development, it is increasingly difficult to develop and manage high-quality applications within a reasonable period of time. In order to face this challenge, a general object model Language (UML) that every company can use is developed ). UML is a blueprint for the information technology industry and a method to describe the system structure in detail. Using this blueprint, we are increasingly easy to establish and maintain systems to ensure that the system can adapt to changes in requirements. After a system model is built, it lays a good foundation for meeting user needs, ensuring system stability and quality, and improving system scalability. Rose is one of the tools for Rapid Application Development Using UML. It is an object-oriented modeling tool.

Unified UML modeling language

UML, unified modeling language, and unified modeling language are object-oriented modeling languages that help us describe and model software systems in an object-oriented manner, it can describe the entire process from requirement analysis to implementation and testing. UML builds an entire model and depicts the objective world by establishing associations between various types and classes, and how classes/objects work together to implement dynamic behavior of the system (these are called model elements. UML provides various graphs, such as the use case diagram, class diagram, sequence diagram, collaboration diagram, and state diagram, to visualize these model elements and their relationships, let people understand the model clearly and easily. We can examine the model from multiple perspectives to better understand the model. In this way, the same model element may appear in Multiple Graphs and correspond to multiple graphic elements.

It consists of view, digoal, model element, general mechanism, and other components. A view is a subset of UML modeling elements that express one aspect of a system's features. It consists of Multiple Graphs and is an abstract representation of the system at a certain abstraction layer. A graph is a graphical representation of a model element set. It is usually composed of an arc (Link) and a vertex (other model elements. MODEL elements represent the classes, objects, messages, and relationships of object-oriented objects, and are the most basic and common concepts used to form graphs. common mechanisms are used to represent other information, such as annotations and semantics of model elements. In addition, it provides an extension mechanism that enables the UML language to adapt to a special method (or process), or expand to an organization or user.

UML is used to describe a model. A model is used to describe the system's structure or static features, as well as behavior or dynamic features. Model the system architecture from different perspectives to form different views of the system ).

The Use Case view emphasizes the system functions that you can see or need from the user's perspective. It is a model diagram of the system functions observed by external users called participants;

The logical view is used to display the static or structural components and features of the system, also known as the structural model view or static view );

The concurrent view reflects the system's dynamic or behavioral characteristics, also known as the Behavioral Model View and dynamic view );

The component view reflects the structure and behavior characteristics of the system implementation, also known as the implementation model view );

The deployment view reflects the structure and behavior characteristics of the system's implementation environment, also known as the environment model view or the physical view ).

Modeling tool rose

Rose is an object-oriented modeling tool of rational in the United States. With this tool, we can build a model for a software system described using UML, in addition, it can automatically generate and maintain code in C ++, Java, VB, Oracle, and other languages and systems.

Rose is a menu-driven application. It uses the toolbar to help you use common features. Its interface is divided into three parts: browser window, digoal window, and document window. The browser window is used to browse, create, delete, and modify model elements in the model. The divisor window is used to display and create various models; the document window is used to display and write document comments for each model element.

Rose Interface

The four views of the Rose model are the use case, logical, component, and deployment views. Each view has different purposes for different objects. The Use Case view includes all roles, cases, and use case diagrams in the system, as well as sequence diagrams and collaboration diagrams.

Use Case View

The logical view focuses on how the system implements the features mentioned in the use case. It provides detailed system graphics and describes how components are associated. In addition to other content, the logical view also includes the required Class, Class diagram, and state transition diagram. With these details, developers can construct detailed system designs.

Logical view

The component view includes information about the model code library, execution library, and other components. A component is the actual module of the Code. The main user of the component view is the person responsible for controlling code and compiling and deploying applications. Some components are code libraries, and some components are running components, such as execution files or dynamic link library (DLL) files.

The collaboration diagram focuses on system deployment, which may be different from the logical structure of the system. The entire team uses the collaboration diagram to understand system deployment, but the user is the person who publishes the application.

Nine charts of Rose

Use Case digoal to describe system functions
Class diagram Class digoal, which describes the static structure of the system
Object digoal, which describes the static structure of the system at a specific time point.
Sequence diagram sequence divisor, which describes the interaction between system elements in chronological order
Collaboration digoal: Describes the interaction between system elements and their relationships in chronological and spatial order.
Status chart state divisor describes the state conditions and responses of system elements.
Activity diagram activity digoal, which describes the activity of system elements.
Component diagram component digoal, which describes the organization of elements that implement the system.
Configuration map deployment divisor describes the configuration of Environment Elements and maps the elements of the implementation system to the configuration.

Based on their applications in different architecture views, nine types of graphs can be divided:

User Model View: use case diagram
Structure Model View: class diagram and object Diagram
Behavior Model View: sequence diagram, collaboration diagram, state diagram, activity diagram (dynamic diagram)
Model View: component Diagram
Environment Model View: configuration Diagram