TABLE OF CONTENT
INTRODUCTION 1
PROBLEM SPACE 2
Characteristics of Problem Space 2
A
framework for explicating assumptions 2
CONCEPTUAL MODELS 5
•Conceptual models based on
activities 5
Instructing
Conversing
Manipulating
and navigating
Exploring
and browsing
• Conceptual models based on objects 7
A CASE OF MIX AND
MATCH? 8
INTERFACE
METAPHORS 9
§
Benefits of interface metaphors
§
Oppositions/Demerits
-Breaking the rules
-Too constraining
-Conflicts with design principles
-Not being able to understand the system functionality
beyond the metaphor
-Overly literal translation of existing bad designs etc
INTERACTION
PARADIGM 12
ubiquitous computing (technology embedded in
the environment)
pervasive computing (seamless integration of
technologies)
wearable computing(wearable)
tangible bits, augmented reality, and
physical/virtual integration
attentive environments (computers attend to
user’s needs)
the Workaday World (social aspects of
technology use)
CONCLUSION 17
REFERENCE 18
INTRODUCTION
In a situation where you are asked to
design an application to let people organize, store and retrieve information in
a fast efficient and enjoyable way, you begin with thinking about why what and
how you are going to design the application. The first idea that probably comes
to your mind is how you can solve this problem on your own, the coding or
probably go ahead with the task of asking people on what they think the
interface might or should look like, there expectation, their recent experience
with other current applications that performs similar actions and existing
email tools.
Basically, it is important to realize
that having a clear understanding of what, why and how you are going to design
something, before writing any code can save time and efforts later on the
design process if the application architecture is first worked out before
design. Once ideas are committed to coding, they become more inevitable. Such
pre-thinking through ideas about users need and what kind of design might be
appropriate is a skill that needs to be learned. This skill is not something
that can be acquired overnight, because it requires practice in learning to
identify, understand and examine the issues just like learning to write a
program, most especially, by focusing on what it takes to understand and
conceptualize interaction.
