User Tools

Site Tools


principles:model_principle

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
principles:model_principle [2019-12-13 11:39]
82.165.232.20 [Example 4: Brake and Air Conditioning]
principles:model_principle [2019-12-31 20:31] (current)
68.72.140.10 [Description]
Line 21: Line 21:
 ===== Description ===== ===== Description =====
  
-The software should model and mirror the "real world"​. This first of all means, that the structure of the software---to some extend---models the structure of the problem. When the "real world action"​ that the software should support comprises certain entities like e.g. customers, products, and orders, then there should be one object for each customer, product and order. Furthermore there should be one class for each concept. And if there is a certain relationship between customers, orders, and products, there should also be an association between the corresponding classes and references between the objects. So the object structure models the structure of the real world concepts.+The software should model and mirror the "real world"​. This first of all means, that the structure of the software---to some extent---models the structure of the problem. When the "real world action"​ that the software should support comprises certain entities like e.g. customers, products, and orders, then there should be one object for each customer, product and order. Furthermore there should be one class for each concept. And if there is a certain relationship between customers, orders, and products, there should also be an association between the corresponding classes and references between the objects. So the object structure models the structure of the real world concepts.
  
 Real world actions are then //​mirrored//​ in the software system. This means that each action in the real world triggers a corresponding action in the model world which ensures that the model stays consistent with the real world. So the software is a kind of a simulation of what actually happens. If customer orders some product, the software reacts by creating an order object, which is connected to the customer and the product objects corresponding to the customer and the product involved in the real world action. Real world actions are then //​mirrored//​ in the software system. This means that each action in the real world triggers a corresponding action in the model world which ensures that the model stays consistent with the real world. So the software is a kind of a simulation of what actually happens. If customer orders some product, the software reacts by creating an order object, which is connected to the customer and the product objects corresponding to the customer and the product involved in the real world action.
principles/model_principle.txt · Last modified: 2019-12-31 20:31 by 68.72.140.10