Shulou(Shulou.com)06/02 Report--

This article mainly introduces what are the knowledge points in UML modeling tools, which have a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, let the editor take you to understand it.

1. State diagram

Attribute modeling:

Properties have very few values, and there are certain restrictions on the conversion between these values. If an instance property has the two properties listed above, and its value reflects the natural state of its own object, it is called a stateattribute property. A mechanism that represents the state of an object when it is a state property.

It's just that category, which has a strong dynamic behavior in the context of the system.

First find out the category, then list its status, and then draw.

Basic state diagram, nested state, concurrent state and synchronization, instantaneous state of message result parameters, continuous, variable properties

Mealy convention: the UML state diagram described is related to the transition.

Moore convention: the UML state diagram described is state-related.

2. Architecture and interface

The architecture of UML modeling tools includes software architecture, hardware architecture, and the interaction between software architecture and hardware architecture.

A window layout diagram that describes the characteristics of each window. The window navigation diagram, which describes the conversion between windows, which will constitute the navigation path for a particular application.

The purpose of the window navigation diagram is to show how users switch from one window to another according to the mainstream application navigation path. Typically, a window diagram shows the human-computer interaction path of a use case.

The navigation diagram is an easy-to-understand screen transition diagram, which itself is a variant of the state diagram structure.

The UUML modeling tool provides two additional diagrams to describe the software and hardware composition of the system architecture:

Packagediagram: it describes the grouping of pure software elements. Package diagram is very valuable for high-level structure modeling of software.

Configuration diagram: describes the technical unit of the system implementation. Configuration diagrams can also describe how software is distributed over selected technical units, using configuration diagrams representing purely physical technologies (processors) to add software components and their interconnections.

3. Use UML modeling tool to model the structure.

Diagram: class diagram, object diagram

Content: classes (interface, collaboration), objects

Relationships: dependency, generalization, association (modified by name, role, multiplicity, aggregation)

Modify with annotations and extend with stereotypes, tag values, and constraints

Public mechanisms:

Elaborate (specification) specifications

Modify adornments: note note score, partition compartment, etc.

Public partition commondivisions

Extension mechanism extensibilitymechanisms.

L stereotype stereotype (represents a new modeling element)

L tag value taggedvalue (represents the new modeling attribute)

L constraint constraint (represents the new modeling semantics)

Objects: a group of objects and their relationships at a certain point in time, modeling the static designer diagram and static process view of the system-- a snapshot of the system at a certain time, object sets, object states, and relationships between objects.

Content: objects, chains, and all other diagrams can have annotations and constraints

4. The difference between use cases and use case diagrams

Use cases describe requirements, system functional requirements, and use case models are defined in the requirements workflow. It is a functional requirement that indicates what the system is going to do. The main job of the use case is to write the text document, and the diagram is secondary.

Black box use case: use case type: success scenario, other scenarios, refinement, including steps and changes.

Use case driven development: requirements are mainly recorded in use cases. Multiple iterations to export the use case.

Identify other requirements: supplementary rules, vocabularies, prospects (ideas).

5. Domain, dependent set and cohesion

The fields of object classes in UML modeling tools mainly include basic domain, structural domain, commercial domain and application domain.

And which fields they belong to respectively. Basics: Integer, Stack, Set, Date, BinaryTree, Mass

Structure: Transaction, Backup, Port, RemoteMachine, Window and CommandButton

The direct dependent set of a class refers to the size of the direct class reference set of the class. The indirect dependency set of a class refers to the size of the indirect reference set of the class. Direct and indirect class references.

It provides a way to measure the complexity of a class.

Cohesion can measure the degree of perfection that the characteristics of this class belong to a single class as a whole. Including: event type cohesion, mixed domain type cohesion and mixed role type cohesion.

6. State space and behavior

The state space and behavior of the class, the state space and behavior of the subclass, the invariants of the class, and the pre-and post-conditions of the class.

Class state space dimension: the number of attributes. The state space of the subclass is limited by the state space of the parent class. But it can be expanded.

Class behavior: an extension of subclass behavior.

The invariant of a class refers to the state in which every object of the class satisfies the condition at any time (when the object is in equilibrium). The inheritance of invariants of a class (such as a triangle).

Every behavior has: pre-condition and post-condition. (pre-condition: stack is not empty, post-condition: take out the content. )

Together with the preconditions and postconditions of the operation, the invariants of the class form the framework of a design method called "contract design". This design method ensures that the operation of a target object responds correctly to a message provided by its client object, and the message provided by the customer object conforms to the pre-condition of the operation.

Thank you for reading this article carefully. I hope the article "what are the knowledge points in UML modeling tools" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.