Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Jun 15 2010, 5:15 PM EDT (current) | Refnocs | 31 words added, 31 words deleted |
| Jul 27 2009, 3:04 PM EDT | joannawiebe | 3 words added, 1 word deleted |
Changes
Key: Additions Deletions
You can jumpstart Agile IxD processes with concept graphing
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.
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.
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.
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.