A4TeamCacti
Last modified by Thomas Cavalier on 2010/09/20 15:56
A4TeamCacti
To-Do
- selection process: choose one of the design methodologies (not yet taken by another group) from the list (and mark it as chosen by editing the wiki page with the list of options — “first come / first served”)
- do research (read papers, interview software designers, analyze existing systems—hint: the abovementioned wiki site contains references to resources) and answer the following specific questions for your chosen design methodology:
- Define your chosen design methodology.
- FROM LUKE
- Characterize your chosen design methodology.
- FROM LUKE
- What are the strengths of your selected methodology?
- Meta-design allows tools to grow and evolve with how their user's interact with them, instead of requiring the interference of a developer to make changes. This allows systems to change organically to be more efficient. As a user gets more skilled in working (both in their job and a particular tool) their habits and patterns of use will change. If the tool was created with meta-design in mind, it will be able to grow with the person and continue to be the right tool for the job. While developers are brought in to create tools, the users are the ones who will actually be using the system. A meta-designed system will allow those users (who know their own work best) to modify the tool to best fit their working style. Meta-designed tools present the user with "opportunities, tools, and social reward structures to extend the system to fit their needs" (1). By integrating this user feedback the tool's lifetime and applicability are increased.
- What are the weaknesses of your selected methodology?
- For what domains or problems is your selected design methodology appropriate?
- For what domains or problems is your selected design methodology inappropriate?
- Why is design methodology important (suited) or not important (suited) for human-centered computing?