31,026
edits
Language and development rules: Difference between revisions
Jump to navigation
Jump to search
m
→Patterns of code organization
| Line 190: | Line 190: | ||
[[wikipedia:Martin Fowler|Martin Fowler]] has identified 3 way to organize: | [[wikipedia:Martin Fowler|Martin Fowler]] has identified 3 way to organize: | ||
* The '''Transaction Script''' (The source code is linear for each user action). | * The '''Transaction Script''' (The source code is linear for each user action). | ||
This is the old | This is the old school used by all procedural languages. | ||
Inconvenient: Redundancy of code. Need to know the physical model of data to develop. | Inconvenient: Redundancy of code. Need to know the physical model of data to develop. | ||
* The '''Domain Model''' | * The '''Domain Model''' | ||
This notion is available with object languages. It is business process (to identify before) that are used for objects classes. | |||
Inconvenient: Model very complex to maintain. | |||
* The '''Table Module''' | * The '''Table Module''' | ||
This is a mix between 2 previous where we have only one unique class for each table of database. | This is a mix between 2 previous where we have only one unique class for each table of database. | ||