Tuesday, September 13, 2005
I'm Sick of Readings!
I realise that this has no relation whatsoever to our FYP except in perhaps the remotest of ways. I just thought my South Park avatar was cute (I know, self praise is no praise at all) and decided to share share...
Get your own!
Interesting, no?
Ok... stress relief over. Back to work. Bahz.
Get your own!
Interesting, no?
Ok... stress relief over. Back to work. Bahz.
Monday, September 12, 2005
Web Usability
Reading this interesting book on WU 吴 web usability... about how to construct a pattern language from different patterns... gonna take some time... has some sample patterns inside also
Sunday, September 04, 2005
what i read!
hey guys i read: managing the paradoxes of mobile technology (This is quite relevant)
i will be reading: Incorporating user satisfaction into the look and feel of mobile phone design
i will be reading: Incorporating user satisfaction into the look and feel of mobile phone design
A Pattern Approach to Interaction Design
Find it at http://media.informatik.rwth-aachen.de/materials/publications/borchers2000a.pdf
I think this part would be the most relevant...
Each pattern of a language captures a recurring design problem, and suggests a proven solution to it. The language consists of a set of such patterns for a specific design
domain, such as urban architecture.
Each pattern has a context represented by edges pointing to it from higher-level patterns. They sketch the design situations in which it can be used.
Similarly, its references show what lower-level patterns can be applied after it has been used. This relationship creates a hierarchy within the pattern language. It leads the designer from patterns addressing large-scale design issues, to patterns about small design details, and helps him locate related patterns quickly.
The name of a pattern helps to refer to its central idea quickly, and build a vocabulary for communication within a team or design community.
The ranking shows how universally valid the pattern author believes this pattern is. It
helps readers to distinuish early pattern ideas from truly timeless patterns that have been confirmed on countless occasions.
The opening illustration gives readers a quick idea of a typical example situation for the pattern, even if they are not professionals. Media choice depends on the domain of the language: Architecture can be represented by photos of buildings and locations; HCI may prefer screen shots, video sequences of an interaction, audio recordings for a voicecontrolled menu, etc.
The problem states what the major issue is that the pattern addresses.
The forces further elaborate the problem statement. They are aspects of the design that need to be optimised. They usually come in pairs contradicting each
other.
The examples section is the largest of each pattern. It shows existing situations in which the problem at hand can be (or has been) encountered, and how it has been solved in those situations.
The solution generalizes from the examples a proven way to balance the forces at hand optimally for the given design context. It is not simply prescriptive, but generic so that
it can generate a solution when it is applied to concrete problem situations of the form specified by the context.
The diagram supports the solution by summarizing its main idea in a graphical way, omitting any unnecessary details. For experts, the diagram is quicker to grasp than the
opening illustration. Media choice again depends on the domain: a graphical sketch for architecture, pseudo-code or UML diagram for software engineering, a storyboard sketch for HCI, a score fragment for music, etc.
The rest are how to use the patterns etc... then its mostly for music (Worldbeat). Some of its references look interesting though. This article mostly provides a framework to build on.
I think this part would be the most relevant...
Each pattern of a language captures a recurring design problem, and suggests a proven solution to it. The language consists of a set of such patterns for a specific design
domain, such as urban architecture.
Each pattern has a context represented by edges pointing to it from higher-level patterns. They sketch the design situations in which it can be used.
Similarly, its references show what lower-level patterns can be applied after it has been used. This relationship creates a hierarchy within the pattern language. It leads the designer from patterns addressing large-scale design issues, to patterns about small design details, and helps him locate related patterns quickly.
The name of a pattern helps to refer to its central idea quickly, and build a vocabulary for communication within a team or design community.
The ranking shows how universally valid the pattern author believes this pattern is. It
helps readers to distinuish early pattern ideas from truly timeless patterns that have been confirmed on countless occasions.
The opening illustration gives readers a quick idea of a typical example situation for the pattern, even if they are not professionals. Media choice depends on the domain of the language: Architecture can be represented by photos of buildings and locations; HCI may prefer screen shots, video sequences of an interaction, audio recordings for a voicecontrolled menu, etc.
The problem states what the major issue is that the pattern addresses.
The forces further elaborate the problem statement. They are aspects of the design that need to be optimised. They usually come in pairs contradicting each
other.
The examples section is the largest of each pattern. It shows existing situations in which the problem at hand can be (or has been) encountered, and how it has been solved in those situations.
The solution generalizes from the examples a proven way to balance the forces at hand optimally for the given design context. It is not simply prescriptive, but generic so that
it can generate a solution when it is applied to concrete problem situations of the form specified by the context.
The diagram supports the solution by summarizing its main idea in a graphical way, omitting any unnecessary details. For experts, the diagram is quicker to grasp than the
opening illustration. Media choice again depends on the domain: a graphical sketch for architecture, pseudo-code or UML diagram for software engineering, a storyboard sketch for HCI, a score fragment for music, etc.
The rest are how to use the patterns etc... then its mostly for music (Worldbeat). Some of its references look interesting though. This article mostly provides a framework to build on.
Thursday, September 01, 2005
Proxy Post: On behalf of Margaret
1)http://www.intel.com/research/network/j_landay.htm
Edited: Adjusted link so that second one works.
Also, please post any articles you've read/currently reading. IF anyone forgets their password, you can get blogger to send you your password.
- Relevant points made in article: Digital Simplicity
- This article tells us due to the complex technology, people are not using or fully utilizing digtial devices.
- Solution: Digital Simplicty
- Trying to create a common underlying interaction language among the various devices so that once you learned it for one device, you could use them all. Eg. pattern language for hp, PDA, mp3player, camera similar or same
- Bcos of pattern language, can use applications without or minimal learning. --> more to intuition
- Pattern language should help users to embrace new devices faster, instead of hinder their embracement of pdt, or take an extremly long time to learn. eg, ppl take extremly long time to use computer when it was first out.
- If you want ur digital pdt to take off well, should use digital simplicity eg. use friendly Interfaces should be built to make our digital devices easier to use and our lives simplier
- When designing user interfaces, have to understand user's needs and devices' capabilities
- Acknowledges a problem that identical data stored on computers and different devices are weakly connected. Users needs: Hope can be connected. Eg. central database
- I dont know how relevant is that. But may be useful ?
- Rest of the article talks about the context and forces driving this need. The solution. The consequences
Edited: Adjusted link so that second one works.
Also, please post any articles you've read/currently reading. IF anyone forgets their password, you can get blogger to send you your password.
