Have a Wetpaint account? Sign in
Welcome! This is a website that everyone can build together. It's easy!
Home
Jumpstart Agile IxD processes with concept graphing
Agile interaction designers need to quickly represent problems.
Our lightweight concept graphing toolkit enables rapid modeling. It gives Agile teams a metacognitive scaffolding for user-centric solution design.
Semantic relationships and built-in grammar make it unique. Nodes and arcs can only be connected in “legal” ways, an approach derived from cognitive task analysis and research in story telling.
Six types of agency can be linked via eighteen interaction types to indicate relationships (e.g. “event” and “goal” connect via an “initiates” arc). Workflows, taxonomies, domains, goal hierarchies, causal relationships, and more are built by simply snapping arcs to nodes.
Understand what you're going to build at Cycle 0 and throughout the lifecycle of the project
Do you need a formal method by which your team can develop useful requirements for a greenfield or complex application? Cognitive organization for requirements definition, or CORE, is such a method.
It is an Agile method, because it continually revisits requirements throughout the lifecycle of a project.
It's not a quick and easy, down and dirty approach. There is rigor to it, a formal process. It requires research with end-users, and analysis using cognitive tools that have to be learned. It's collaborative. And it works. To learn more:
This wiki is licensed under a Creative Commons Attribution-Share Alike 3.0 License.
Agile interaction designers need to quickly represent problems.
Our lightweight concept graphing toolkit enables rapid modeling. It gives Agile teams a metacognitive scaffolding for user-centric solution design.
Semantic relationships and built-in grammar make it unique. Nodes and arcs can only be connected in “legal” ways, an approach derived from cognitive task analysis and research in story telling.
Six types of agency can be linked via eighteen interaction types to indicate relationships (e.g. “event” and “goal” connect via an “initiates” arc). Workflows, taxonomies, domains, goal hierarchies, causal relationships, and more are built by simply snapping arcs to nodes.
Understand what you're going to build at Cycle 0 and throughout the lifecycle of the project
Do you need a formal method by which your team can develop useful requirements for a greenfield or complex application? Cognitive organization for requirements definition, or CORE, is such a method.
It is an Agile method, because it continually revisits requirements throughout the lifecycle of a project.
It's not a quick and easy, down and dirty approach. There is rigor to it, a formal process. It requires research with end-users, and analysis using cognitive tools that have to be learned. It's collaborative. And it works. To learn more:
|
joannawiebe |
Latest page update: made by joannawiebe
, Jan 28 2009, 1:32 PM EST
(about this update
About This Update
4 words added 2 words deleted view changes - complete history) |
|
Keyword tags:
Agile
causal relationship
cognitive task analysis
concept graph
concept graphing
domains
Euro IA
goal heirarchies
goal heirarchy
IA Summit
information architect
information architecture
interaction design
interaction designer
IxDA
rapid modeling
taxonomies
taxonomy
user-centric
workflow
workflows
More Info: links to this page
|
There are no threads for this page.
Be the first to start a new thread.

