# data[].attributes.body
The view this part with which the user interacts, is like the logic of the business

# data[].attributes.body
-the person running the process
-the part of the architecture that processes the data

# data[].attributes.body
Model have the bussines logic, stores data. Controller give information from DataBases or  other source and the model return data and solve the operation.

# data[].attributes.body
it's a software architecture pattern, that separates the data into separate internal representations that is used in developing user interfaces

# data[].attributes.body
In a MVC framework a model component stores and render the data request from the view frame, and retrieve data to fullfil the user's needs. The model frame responds to the instructions of the controller and the demands of the user.

# data[].attributes.headline
EDWIN GONZALEZ                  its the interface that the user interacts with.  

# data[].attributes.subject
EDWIN GONZALEZ                  its the interface that the user interacts with.  

# data[].attributes.body
it is difficult to read, modify, and unit test. Developers must have a good understanding of multiple technologies.

# data[].attributes.body
-Complex to reuse the model
-Developers need know-how of different technologies
-Collaborative work of the programmers

# data[].attributes.body
1. Easy code maintenance
2. MVC Model component can be
tested separately from the user
3. best support for test-driven
development
4. all classes and objects are independent
5. avoid complexity
6. works well for Web apps

# data[].attributes.body
Controller : the model de component stores data and  its related logic

# data[].attributes.body
The advantages can be said that the code maintenance is easy, the sed model components can be tested separately

# data[].attributes.body
It's a way to see a system in three parts (Model, View, Controller), each part is responsible for specifics process in the system.

# data[].attributes.body
By separating the data from the view, it is clear where each logic should go, and this facilitates the maintenance and growth of the application.

# data[].attributes.body
The Controller interprets the mouse and keyboard inputs from the user

# data[].attributes.body
The Controller manages the user interaction and the application , interprets the mouse and keyboards inputs also the communication between view and model

# data[].attributes.body
*there is a need for multiple programmers to conduct parallel programming.
*the programmers need to maintain many codes in Controller

# data[].attributes.body
The controller receives input from view

# data[].attributes.body
Dificults: it is not easy to read, change, to unit test,.
For developers is necesary to know multiple technologies

# data[].attributes.body
Controller: Brains of the application

# data[].attributes.body
is a component of MVC, its funtion is to present data to the user or manage their interaction.

# data[].attributes.body
The MVC is a Model component that can be tested separately from the user.

# data[].attributes.body
It´s a style to write and structurate software focused in separate all code source into 3 components to process data. these 3 components interact with each other to meet the established objetives; this model has 3 components:

View: it serves to get human interaction and show data application, and get data from model layer.

Controller: it`s middle between view and model, to view:

*set updates and get user actions.

*To model set updates and get notify.

Model: Establish how to work with data and interact with any source like database or flat file.