Learning modeling tool rose (1)

With the wide application of object-oriented programming, visual programming has blossomed everywhere. Today, the status of programming staff has been shaken, and it is no longer the mainstream in development, the application of software engineering has been paid more and more attention as an important witness to the quality and efficiency of software development. For the obvious shortcomings of the early structured modeling tools, rose draws on the advantages of many modeling tools, excluding its shortcomings, the use of sophisticated object-oriented technology and two-way engineering skills, to improve the efficiency of software development, to ensure the quality and maintainability of software development has made a huge contribution.
Software Engineering Overview
Software development is a set of engineering disciplines based on the definition, tasks, and functions of each stage of software development. To solve the software crisis, it guides people to use scientific and effective methods to develop software, improving and ensuring the efficiency and quality of software development. Software Development Process: Requirement Analysis (initial stage) -- Outline Design (static structure) -- Detailed Design (dynamic structure) -- Coding-test-Maintenance
Structured Model Design Method
A.E-R diagram (entity diagram)
Entity: an object that exists objectively and can be differentiated.
Attribute: a property of an object. An object can have multiple attributes.
Relationship: the relationship between entities, which can be divided into, 1: N, and M: N.

B. Data Flow Diagram

C. functional module diagram

Insufficient Structured Model
The model created by the design of the traditional structured model cannot reflect the source code and is out of touch with the program design. The model has almost nothing to do with the code. Such a model cannot generate code, and the code cannot generate a model. Most of the models are shown or hidden by the leaders. Therefore, the quality of software cannot be guaranteed, and it is not easy to maintain software. There is no binding force and no testing standard. Its disadvantages are obvious.
Object-oriented Model Design Method
Definition: divides an application into many small pieces (objects) using the object-oriented method. These objects are independent and then combine these objects to create programs.
Features: packaging, inheritance, and polymorphism.
Commonly used modeling tools: playcase, Rational Rose, Computer Association bpwin, Computer Association Erwin, oracle designer/2000, Sybase powerdesigner
UML language Overview
Definition: a unified object-oriented modeling language.
Purpose: Help us to perform object-oriented and modeling for software systems.
Core: the relationship between classes.
Modeling: By ing users' business earthquake requirements into code, the code can meet these requirements, and the code can easily backtrack the requirements. This process is called modeling.
Rose modeling tool
Definition: an object-oriented modeling tool for analysis and design.
Purpose: using the Rose tool, we can build a model of a software system using UML, automatically generates and maintains code for C ++, Java, VB, Pb, Oracle, and other languages and systems.
Core: Seven block charts
1. Use-Case Diagrams (use case diagram)
2. Sequence divisor (sequence diagram)
3. Collaboration didiagram)
4. Class digoal (class diagram)
5. State Transition divisor (status diagram)
6. Component divisor (Component diagram)
7. Deployment divisor (Extended block diagram)
The following is a combination of software engineering knowledge and Rose modeling tools. I have used the rose model in the development of the power department's "110kv Standard Design graphic Management System" and analyzed the development practices of Rose.
I. Demand analysis stage
Task: create user requirements and function modules to determine roles and use cases in the system. Use rose to generate roles, use cases, and generate Use Case Diagrams
Block Diagram used:
1. Use-Case Diagrams: displays the interaction between a use case (indicating a system function) and a role (person or system. For example:

Use Case: define and describe the coherent functional units of a system or system without displaying a system or internal structure.
Role: the person who uses the software or the external system itself.
2. Sequence digoal
Analyze the use cases from top to bottom in chronological order to determine the handling process of the case. For example:

3 collaboration digoal:
The analysis process for determining the relationship between objects. For example:

Ii. Outline Design Stage
Task: Analyze use-case diagrams to obtain the classes used and analyze the attributes, operations, and relationships of these classes.
Block Diagram used:
1. class diagrams.
Displays the interaction between classes in the system.

2. Package: a diagram that combines some common classes.

 
Iii. Detailed Design Stage
Task: refined and personalized use-case descriptions, such as class operations and message correspondence between objects, filling parameters and complex class design.
Block Diagram used:
1. Class Diagrams
2. State Diagrams: displays the lifecycle of an object from generation to deletion.
Iv. coding and testing phase
Task: develop and test the software and generate a component diagram.
Component: indicates the physical module of the Code.
Component diagram: the components in the system and their dependencies.
Delpoyment diagrams: displays the physical layout and positions of various components in the network.

Bidirectional Engineering
1. generate code: generate the code of the corresponding program based on the language of the selected application.
Step: Check model-generate component-map Class components-set code generation attributes-select class, component, and package-generate code
2. Reverse Transfer Project: generate the code of the corresponding program based on the language of the selected application.
Step: Check model-generate component-map Class components-set code generation attributes-select class, component, and package-generate code