"By 2020, the Fourth Industrial Revolution will have brought us advanced robotics and autonomous transport, artificial intelligence and machine learning, advanced materials, biotechnology and genomics.
These developments will transform the way we live, and the way we work. Some jobs will disappear, others will grow and jobs that don't even exist today will become commonplace. What is certain is that the future workforce will need to align its skillset to keep pace.
A new Forum report, The Future of Jobs, looks at the employment, skills and workforce strategy for the future."
(Alex Gray, 19 January 2016, World Economic Forum)
"Metaphors facilitate the understanding of an unfamiliar situation in terms of a known situation (Ortony, 1991). By means of metaphors, it is possible to make reference to what is clearly understood in order to elucidate the unknown. Basically, metaphors constitute an uncommon juxtaposition of the familiar and the unusual. They induce the discovery of innovative associations that broaden the human capacity for interpretation (Lakoff, 1987, 1993). For that reason, metaphors are seen as valuable aids in problem–solving tasks.
The relevance of metaphors to problem–solving is pertinent to three fundamental steps (Gentner, Bowdle, Wolff, & Boronat, 2001). The first step consists of extracting a variety of unfamiliar concepts from remote domains, where possible relationships with the problem at hand are not always evident. The second step involves establishing a mapping of deep or high–level relationships between the metaphorical concept and the problem. Correspondences are identified by means of abstractions and generalizations. Relationships of secondary importance are discarded, and only structural correspondences between the metaphorical source and the problem are set up. The last step deals with transferring and applying structural correspondences associated with the metaphorical source to the problem at hand, which at the end generally leads to a novel solution."
(Hernan Pablo Casakin, 2007)
Hernan Pablo Casakin (2007). "Metaphors in Design Problem Solving: Implications for Creativity." International Journal of Design 1(2).
"In this studio paper students will be introduced to creative and analytical thinking skills, idea generation and visualisation common to art and design practice. They will begin to acquire specific techniques, skills and processes in art–making across different media. They will learn to discuss and evaluate their work and the work of their peers."
[First year students undertaking coursework as part of the Studio I (Art Lab) paper at Massey University College of Creative Arts in Wellington, Aotearoa New Zealand]
"2.1 Abstraction Levels: An abstraction for a software artifact is a succinct description that suppresses the details that are unimportant to software developer and emphasizes the information that is important. For example, the abstraction provided by high level programming language allows a programmer to construct the algorithms without having to worry about the details of hardware register allocation. Software typically consists of several layers of abstraction built on top of raw hardware; the lowest–level software abstraction is object code, or machine code. Implementation is a common terminology for the lowest level of detail in an abstraction. When abstraction is applied to computer programming, program behavior is emphasized and implementation details are suppressed. The knowledge of a software product at various levels of abstraction undoubtedly underlies operations regarding the maintenance and reuses the existing software components. It is, therefore natural that there is a steadying growing interest in reverse engineering, as a capable of extracting information and documents from a software product to present in higher levels of abstraction than that of code. The abstraction as the process of ignoring certain details in order to simplify the problem and so facilitates the specification, design and implementation of a system to proceed in step–wise fashion. In the context of software maintenance , four levels of reverse engineering abstraction are defined: implementation abstraction, structural abstraction, functional abstraction and domain abstraction.
Implementation abstraction is a lowest level of abstraction and at this level the abstraction of the knowledge of the language in which the system is written, the syntax and semantics of language and the hierarchy of system components (program or module tree) rather then data structures and algorithms is abstracted. Structural abstraction level is a further abstraction of system components (program or modules) to extract the program structures, how the components are related and control to each other. Functional abstraction level is a higher abstraction level, it usually achieve by further abstraction of components or sub–components (programs or modules or class) to reveal the relations and logic, which perform certain tasks. Domain Abstraction further abstracts the functions by replacing its algorithmic nature with concepts and specific to the application domain."
(Nadim Asif, 2003)
Nadim Asif (2003). "Reverse Engineering Methodology to Recover the Design Artifacts: A Case Study". International Conference on Software Engineering Research and Practice, SERP '03 Las Vegas, Nevada, USA. Volume 2.