2015/03/21-15:12
"Declaration" Welcome reprint, but please keep the article original source: http://blog.csdn.net/yelangjueqi/article/details/44710217
1. One of the basic reasons why modeling is:modeling is to better understand the systems under development
2. By modeling, there are four objectives:(1) Modeling helps visualize the system according to the actual situation or according to the desired style
(2) modeling has the ability to regulate the structure and behavior of the system
(3), modeling gives a template for guiding the construction system
(4), modeling to document the decisions made
The larger the system, the more complex, the greater the importance of modeling, a simple reason:
because a complex system cannot be fully understood, it is modeled
People are limited in their ability to understand responsible issues. By modeling, narrowing the scope of the research problem, focusing only on one aspect of it at a time, which is the basic method of "divide and conquer" that Edsger Dijkstra a few years ago, that is, to divide a difficult problem into a series of small problems that can be solved, and solve these small problems. In addition, modeling can enhance human intelligence, and an appropriately selected model can enable modelers to work at a higher level of abstraction.
3. Modeling principles;
(1), choose what model to create, have a profound impact on how to solve the problem and how to form a solution
(2), each model can be represented at different levels of accuracy
In any case, the best model should be this: it allows you to choose the level of detail based on who is observing and why. Analysts or end users are primarily concerned with what to do, and the developer focuses on the "how to" issue, which is to visualize the system at different levels of detail at various times
(3) The best model is associated with reality
(4), a single model or view is inadequate, and for each important system it is best to use a small group of almost independent models to approach from multiple perspectives
In order to understand the architecture of the system, several complementary or interlocking views are needed: The usage view (revealing the requirements of the system), the Design view (the vocabulary that captures the problem space and the space), the interactive view (showing the connection between the various parts of the system and the system to the environment), the implementation view (describing the physical implementation of the system and deployment views (focusing on system engineering issues), each view may have structural and behavioral aspects. Together, these views depict the software blueprint as a whole.
UML Modeling QuickStart 01 background
