Objects and MVC... stuff!
Software Engineers break down complex problems into manageable chunks of deliciousness. The problems are broken into components by pulling nouns and verbs from it's written form. The nouns are tasty things, which can be represented by objects. Verbs are made into actions by writing functions/methods that perform the desired logistics with/from savory objects. Often these nouns and verbs are aggregations/relationships of smaller nouns and verbs, thus are further broken down before being represented in code. It's like Jenga with cookies... or maybe I'm just hungry.
The relationships of objects are observed and implemented using similarities in an MVC pattern. There they are separated into the Model, View, and Controller. The Model represents data, the View is the interface which displays the Model, and other pertinent information, and the Controller handles coordinating between user input, and Model-View interactions.
MVC is a strong pattern as it segregates tasks to promote clarity and cohesion (grouping of 'similar' ideas.) I'll keep this short and sweet, like a caramel flan... and go eat lunch.
This comment has been removed by the author.
ReplyDeleteAhoy!
DeleteThis is really awesome. I like your words “Jenga with cookies”. That is what the problems are to us. I do have the same belief that the MVC is a very strong pattern. By separating the objects into categories Model, View, and Controller, the confusions between the role of those objects are reduced. Plus, the separation of responsibilities allows flexibility, so we can develop further one category without affecting the others.
ReplyDelete