Filmed at Irish Museum of Modern Art, Ireland. "Notebook Material" Des Ward Student artwork in notebooks – 1st year groups on the IADT BA Art programme: 2009 – 2014.
"AppSeed lets you take your sketches and make them into functioning prototypes, bridging the gap between pen/paper and digital, through computer vision. It allows you to sketch your designs as you normally would and then manipulate your sketches directly on your phone. Unlike similar products, the use of computer vision speeds up the process and understands your sketches. AppSeed can identify an enclosed space in your sketch, allowing you to make it into a button, input text, map, or another UI element. Making your sketch into a functioning prototype running on your phone."
"A portfolio is a collection of your work, which shows how your skills and ideas have developed over a period of time. It demonstrates your creativity, personality, abilities and commitment, and helps us to evaluate your potential."
(University of the Arts London, 2013)
Videos include: What is a portfolio; Preparing a digital Portfolio; Preparing a portfolio; Why is a portfolio important; What should be in a portfolio; Applying to MA; Applying to BA; Applying to foundation.
"Heidegger's philosophy offers what is arguably the most thorough account of the process of human understanding available. Although his analysis of interpretation is useful if one is to understand activities like innovative design, it never addresses the realm of design directly. Heidegger discusses interpretation at a high level of generality and chooses his examples from interactions between people and physical artifacts, like the use of hammers by carpenters. He is concerned with the nature of understandingly being in the world. While a person's world includes conceptual and imaginative realms like design, Heidegger's examples primarily come from the world of physical artifacts which can be encountered perceptually. ...
Heidegger treats artifacts in the world the same way he would treat design artifacts on the drawing board. That is, he is not really concerned with them as physically present objects of perception. On the contrary, his main effort philosophically is to distinguish artifacts–in–use from traditional conceptions of physically–present–objects. For example, a hammer in use is not understood by the carpenter as an observed object with physical attributes, but is skillfully applied to the activities of the current situation. Furthermore, this skillful use takes place within the context of future–oriented plans and desires, such as the anticipation of the item that is under construction. This is similar to components of a design, which are skillfully arranged in terms of their relationships to other design components and within the context of the anticipated final design. Marks in a design sketch, for instance, are important for their roles within a network of significances, rather than for their physical properties as lines. Interpretation of both physical artifacts and designs is situated. ...
The notion of breakdown in action plays a rather small role in Heidegger's analysis of human understanding. Heidegger uses examples of breakdown in order to make explicit the network of references among artifacts that are only present tacitly under conditions of normal use. Yet, the notion of breakdown has been elevated to central importance in the theories that have tried to adopt Heidegger's analysis to a theory of design and to operationalize this theory for computer support. Thus, breakdown plays an important role in Schön (1985), Winograd & Flores (1986), Suchman (1987), Ehn (1988), Budde & Züllighoven (1990), McCall, Morch, & Fischer (1990), Dreyfus (1991), Coyne & Snodgrass (1991), Fischer & Nakakoji (1992).
The fact that so many writers influenced by Heidegger have focused on breakdown does not provide multiple independent support for this emphasis. ... most of these writers have been influenced by Heidegger only indirectly–either through Dreyfus or through Schön. If one looks closely at the discussions of breakdown in Dreyfus and Schön, one can note an ambiguity in whether they are speaking about a (ontological) breakdown in the network of references or a (practical) breakdown in action. Dreyfus is certainly aware of the ontological role of breakdown, but he is concerned to make his presentation acceptable to an American audience, trained in the rationalist tradition. For the sake of concreteness, he uses examples that stress the breakdown in action. Schön is also aware of the ontological ramifications, but he has couched his discussion in terms of action (e.g., knowing–in–action, reflection–in–action), so it often seems that his examples of breakdown exemplify breakdowns in action rather than breakdowns in situated understanding. Given that it is easier to operationalize breakdowns in action than breakdowns in situated understanding, it is not surprising that people interested in producing practical results from Dreyfus or Schön's theories would tend to emphasize the action–oriented reading of the ambiguous discussions."
(Gerry Stahl, 5 January 2004)
"Suppose that you want to understand the design process of architects, the knowledge that they use, the cognitive actions that they take and the strategies they employ. How would you go about this? One obvious possibility is to ask some architects how they design a building. Interestingly enough, they will not find this an easy question to answer. They are used to do their job, not to explain it. If they do try to tell you how they go about their design work, it is quite possible that their account of it will be incomplete or even incorrect, because they construct this account from memory. They may be inclined to describe the design process neatly in terms of the formal design methods that they acquired during their professional training, whereas the real design process deviates from these methods. Psychologists have demonstrated that such accounts are not very reliable. Another possibility is to look at the architects' designs and at their intermediate sketches. However, now you are looking at the products of the thought processes of these architects, and not at the thought processes themselves. What is needed are more direct data on the ongoing thinking processes during working on a design. If you want to know how they arrive at their designs, what they think, what is difficult for them and what is easy, how they reconcile conflicting demands, a different research method is needed.
A good method in this situation is to ask architects to work on a design and to instruct them to think aloud. What they say is recorded and used as data for analysis of the design process. This is a very direct method to gain insight in the knowledge and methods of human problem–solving. The speech and writings are called spoken and written protocols. In this book we will describe a method for systematically collecting and analysing such think aloud protocols. This method can be used by psychologists and other social scientists who want to know more about cognitive processes. It is also an important method for knowledge engineers whose goal is to build a knowledgebased computer system on the basis of human expertise."
(Maarten W. van Someren, Yvonne F. Barnard, et al., 1994, pp.1–2)
Maarten W. van Someren, Yvonne F. Barnard and Jacobijn A.C. Sandberg. (1994). "The Think Aloud Method: A Practical Guide to Modelling Cognitive Processes".