Thinking in UML Learning notes (i)--building an object model

First, the nature of object-oriented

abstract , when the system reaches beyond its processing power, we can abstract the scope we can deal with to commission abstract level , which allows you to build larger, more complex systems.

1, A way to map the real world to the object world.

2, A method of describing the real world from the object world.

3, A way to verify that the world behavior of an object reflects the real world correctly.

UML is the analytical design method to solve this problem 。

Ii. problems faced by object-oriented

1, the object of analysis and design problems.

2, the meaning of the object structure is ambiguous.

When object-oriented encounters these problems. UML Unified Modeling Language appeared. Learning UML is just a language to learn. And to write a wonderful article, but it is necessary to rely on the writer's understanding of life and sublimation, both indispensable. Therefore, it is more important than learning UML modeling itself to understand the best practices behind the hidden shadows of UML.

Three, UML Unified Modeling Language to solve the problem

1, since UML is a language, as a language to solve the first problem is the communication problem .

2, unification, is to solve the chaotic dialect problem. such as Mandarin is widely recognized by everyone.

3, visualization, easy to be understood and memory (beyond the expression of words).

Iv. the abstract process from reality to model

Modeling is actually a kind of understanding of real things. The real world assumes that we stand at a very high angle to abstract, we will find that no matter how complex this time, its essence is simply composed of people, things, things and rules.

1, UML uses the meta -model which is called the Participant (actor) as the information source provider. Represents the " human " in reality.

2. UML uses a meta-model called use cases to represent the driver's business objectives. That's what the participants want to do and what they get. Represent the " things " in reality.

3, one thing how to do. According to what rules. It is depicted by a uml view called a business scenario (scenario) and a use case scenario (scenario). Represent the rules in reality.

4, the object model of the business in the corresponding reality of the " things ."

v. From the business model to the conceptual model

Analytical Model: UML establishes a model suitable for computer understanding and implementation by means of an analytic process called conceptualization.

The analysis model is a transition model between the original requirements and the computer implementation.

Meta-model of the Analytic model:

1. Boundary Class (boundary): _____

2. Control: ——— rules

3. entity classes (entities):

watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvzgf3yw5nyw5iyw4=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/ Dissolve/70/gravity/southeast "/> ———— material

is the transformation process of the business model to the conceptual model:

Vi. from conceptual model to design model

The design model is a detailed implementation of the conceptual model, which is implemented in more than one way. In the design model. The boundary class in the conceptual model can be converted to an interface of the operator or a system. The control class can be transformed into a computer program or control procedure, such as a workflow, an algorithm, or an entity class that can be transformed into a data table, XML document, or other persisted class. In fact, for different software architectures and frameworks, and for different programming languages. The conceptual models implemented are different.

watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvzgf3yw5nyw5iyw4=/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/ Dissolve/70/gravity/southeast "/>

Object-oriented analysis design complete steps such as the following:

Vii. introduction of RUP

RUP (Rational Unified process) unified processes.

The unified process summarizes and collates a lot of best practices in software project that are summarized in practice. is a use of object-oriented thinking, using UML as a software analysis language, and combined with project management, quality assurance and many other software project knowledge integrated into a very complete and huge software method.

The unified process defines the most important four phases and nine core workflows in the software development process, each with a different side focus on different workflows.

The real soul of a software project is the software process. The need for software processes is why these tools and languages are born.

Thinking in UML Learning notes (i)--building an object model