Differences and meanings of frameworks, models, and models

So-called frameworks, models, and models

After reading the paper for so long, I finally understood the differences and specific meanings of these three concepts. During discussions with lab students, I found that many students were not very clear about this issue, so I wrote a small article to record it.

The first thing to note is that the framework, model, and model mentioned in this article are often mentioned when you look at research papers. They may be different from the corresponding concepts in the software engineering field. And because of the limited level, my understanding may be incorrect.

First, let's talk about the framework. The so-called framework should be a processing process. The typical framework may be as follows:

This picture may not be clear, but it is not important. The framework is a process for solving a specific problem. We are familiar with ASP. NET frameworks and rails frameworks.
They solve the problem of how to build Web applications. ASP. NET and rails both define a series of processing procedures, from getting user requests to directing requests to appropriate classes, how to call user Definitions
And then send the processing result to the user.

The so-called model is a tool to describe the problem. Here, we need to note that the model I mentioned is not the model obtained by "mathematical modeling" or "software modeling", but another model, such as the object model.
Type, relational model, and so on. These models are rules that describe how to describe a concept and define a series of operations that describe how to interact between concepts. Typical
It is a relational model. It describes a concept (Database Table) using many attributes (database fields) and the relationships between these concepts, such as Union (corresponding to Union operations ).
Project (corresponding to select columnname from
Tablename. A model is a tool used to help people record and analyze problems. Other common models include object models and UML models.

The last is the mode. We can think that what we get from model modeling is a model, such as a database design and a software design. It should be noted that although MySQL manages its database as a model
But a running database is not a mode, but a specific instance of a mode. Because the same mode can have many implementations, such as the northwind database on many machines
But all of them use the northwind database mode.

The pattern here is the so-called schema, not the pattern of the design pattern. Schema is used to describe the relationship between concepts and concepts, while pattern is more used to describe the relationship between conceptual instances. For example, some data has a specific pattern ), for example, the telephone number is always in the "area code-number" mode.