Mvc -modelo vista controlador

Introduction

The Model-View-Controller (MVC) Its Past and Present Trygve Reenskaug, University of Oslo (trygver@ifi.uio.no)
Abstract.
MVC was conceived in 1978 as the design solution to a particular problem. The top level goal was to support the user's mental model of the relevant information space and to enable the user to inspect and edit this information. The first part of the talkdescribes the original problem and discusses the chosen solution. The second part elaborates the original ideas and extends the scope to include current day challenges to the original goal. We examine some ideas related to MVC that are found in the literature and select those that appear to be particularly relevant to the top level goal. It is all summarized in a condensed MVC pattern language.Notice
This presentation is copyright ©2003 Trygve Reenskaug, Oslo, Norway. All rights reserved. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that the copies are not made for profit or commercial advantage and that copies bear this notice and full citation on the first page.

1. Introduction
This presentation ispart of the InfoBOARD project where I explore IT technologies that help create habitable information systems. The scope of this project is indicated by its main sources of inspiration:

This talk focuses on bridging the gap between man and machine.

2. An MVC Pattern Language
The following is the first draft of a pattern language for a systems architecture based on the MVC ideas. The patternsmay not satisfy the stringent requirements set up by the patterns community. In particular; • Several patterns represent ideas rather than implemented experience • References to interesting, public domain patterns are TBD (To Be Done)

© 2003 Trygve Reenskaug Draft of August 20, 2003 1:26 pm D:\Mine dokumenter\Publications\2003-09-MVC\Handout\50-Patterns.fm

Page 1 of 16

TheModel-View-Controller (MVC) Its Past and Present An MVC Pattern Language Integrated Domain Services

•

The patterns have been written by a single author and have not been discussed in the community

On the other hand, all the patterns are in Alexander’s spirit; every one is motivated by the needs of people and the desire to create habitable information systems. The patterns of this draft version of theMVC pattern language have been developed together with the presentation. The patterns are therefore decorated with the corresponding presentation slides. This first pattern language consists of the following patterns: • P-1: INTEGRATED DOMAIN SERVICES (page 2) • P-2: LINE DEPARTMENT OWNS DOMAIN COMPONENTS (page 3) • P-3: MENTAL OBJECT MODELS (page 4) • P-4: PERSONAL INFORMATION SYSTEMS (page 7) •P-5: DOMAIN/USER MATRIX (page 8) • P-6: MODEL/EDITOR SEPARATION (page 9) • P-7: INPUT/OUTPUT SEPARATION(MVC/1980) (page 10) • P-8: TOOLS FOR TASKS (MVC/1979) (page 11) • P-9: TOOL AS A COMPOSITE (MVC/1979) (page 12) • P-10: SYNCHRONIZE SELECTION (page 13) • P-11: SYNCHRONIZE MODEL AND VIEW (page 14)

P-1: INTEGRATED DOMAIN SERVICES
Context
An enterprise handles a number of different businessfunctions a.k.a. domains. Examples are design, materials management, planning, control, and finance.

Problem
The enterprise needs to support such domains with integrated information systems.

Solution
Create separate domain services for each of the different business domains. Each of these services should be tightly integrated internally, e.g., through a common data base or through tightlycoupled interacting services. Integration between domains will be through mechanisms that are outside the domain services.

© 2003 Trygve Reenskaug Draft of August 20, 2003 1:26 pm D:\Mine dokumenter\Publications\2003-09-MVC\Handout\50-Patterns.fm

Page 2 of 16

The Model-View-Controller (MVC) Its Past and Present An MVC Pattern Language Line Department Owns Domain Components

Notice...