Workshop 1-part 2

2.Learn about the Model View Controller (MVC) approach to Web application design

Some referance link for learning about Model view contoller are listed as follows:

1. Michael P. Peterson (2008). "International Perspectives on Maps and the Internet". Iillustrated Edition. Received 2nd April, 2009 fr0m the url - http://books.google.com.hk/books?id=Uv0CZft3nEEC&pg=PA171&dq=Model+View+Controller+approach

In this book, it tells me that the work flow of MVC, that is,

• 1. User, manipulated one or more contollers to affect change.
• 2. Controller, one or more controllers alter the model.
• 3. Model, one or more views reflect the current state of the model.
• 4. View, views are perceived by the user.
• 5. Please see the flow figure.

• In this book, it tells me that a model is used for storing data about a given domain, a view which renders model information in a form which a user can sense and possibly interact with; and a controller which processes and reponds to events, such as user actions or the results of a process.

2. Serge Fdida (1997). "Multimedia applications, services, and techniques: ECMAST '97". Received 2nd April, 2009 fr0m the url - http://books.google.com.hk/books?id=dJNbmJkj_jcC&pg=PA702&dq=Model+View+Controller+approach&lr=

This book tells me that MVC is an object based approach having two basic objectives, the first one that MVC can make the development of user interface componets (views) independent from the services and data (model), and form the applications (controllers), allowing different skilled groups to develop different software levels; the second one that MVC can reuse software components, both user interface software and application software. As a result of that, immediate software integration, easy unitary tests and validation, and the possibility of having multiple different user interfaces for the same application are obtained.