THING-MODEL-VIEW-EDITOR.PDFVIP

THING-MODEL-VIEW-EDITOR an Example from a planningsystem To LRG From Trygve Reenskaug Filed on [IVY]ReenskaugSMALL TERMIN0LOGY2.DOC Date 12 MAY 1979 The purpose of this note is to explore the thing-model-view-editor metaphors through a coherent set of examples. The examples are all drawn from my planningsystem, and illustrate the above four notions. All examples have been implemented, albeit not within the clean class structure described here. The metaphors correspond to real world-Model-view-Tool as proposed in A note on DynaBook requirements ([Ivy]ReenskaugDynaBook.doc). THING DESCRIPTION OF TERM Something that is of interest to the user. It could be concrete, like a house or an integrated circuit. It could be abstract, like a new idea or opinions about a paper. It could be a whole, like a computer, or a part, like a circuit element. EXAMPLE: A LARGE PROJECT The Thing is here a large project. It could be the design and construction of a major bridge, a power station or an off-shore oil production platform. Such projects represent complex tasks with a very large number of interdependent details. Those responsible for a project have to keep track of all these details and their dependencies in order to understand the consequences of various real or proposed situations that may arise. A great variety of different abstractions are used as aids in controlling large projects. Each abstraction highlights particular aspects of the total project, and are used alone or together with other abstractions for the control of those aspects. Examples of abstractions are ways of thinking about the requirements for materials; cost estimating; and various budgeting and accounting theories. One particularly useful abstraction is the notion of activity networks or Pert diagrams. This abstraction links together what should be done with who should do it and when it is to be done. In the net