Already a member?
Sign in
| Version | User | Scope of changes |
|---|---|---|
| Apr 3 2007, 5:03 PM EDT (current) | Refnocs | |
| Mar 31 2007, 11:38 PM EDT | joannawiebe |
Changes
Key: Additions Deletions
How to get out of a mess:
use the CORE methodology (Cognitive Organization for Requirements Elicitation)
Poster presentation by Joanna Wiebe and Scott Confer at the IA Summit 2007
Using a case study drawn from the Orbitz.com information architecture environment, our 2007 IA Summit poster uses visuals and text to describe a rules-based soft systems methodology for collaborative decision-making, Cognitive Organization for Requirements Elicitation (CORE).
In this case study, the Orbitz information architect was faced with a need to rapidly develop specifications for new web application features. Produced in the absence of use cases, functional requirements, or business requirements, these new specifications had to be both culturally and technically acceptable, and meet changing business and user needs.
Our poster describes the seven-step structure-definition process which was followed by the Orbitz information architect:
In this case study, the Orbitz information architect was faced with a need to rapidly develop specifications for new web application features. Produced in the absence of use cases, functional requirements, or business requirements, these new specifications had to be both culturally and technically acceptable, and meet changing business and user needs.
Our poster describes the seven-step structure-definition process which was followed by the Orbitz information architect:
1. An unstructured situation is identified, along with the team of people who play the roles of investigator, subject matter expert, client, problem-owner and problem-solver. Research follows a taxonomy of question probes.
2. The investigator develops an ‘as-is’ “Rich Picture” to focus on structure, function, process, and environment. Ideally, existing applications and business processes have been captured in functional requirements documents and use cases. Or more realistically, the investigator may be working from raw interview notes, whiteboard sketches and assumptions.
3. Root definitions of “relevant systems” are written to describe Rich Picture elements of structure, function, process and environment.
4. The descriptions are analyzed and graphed as Conceptual Graph Structures (CGSs). Dynamic conversations and debate lead to consensus about concepts and goals, captured iteratively in CGSs.
5. IA comparison of the CGSs with the Rich Picture leads to iterations of the CGSs. Two types of knowledge emerge to inform the user interface:
· inconsistencies or problems with the existing situations/systems and
· new solutions/innovations for the user tasks.
From this phase, a list of preliminary requirements is made.
6. Systemically desirable and culturally feasible requirements are agreed upon. A key benefit of the CORE methodology is that team members are invested collaboratively in the requirements.
7. Requirements are translated into information architecture. These include changes to structure, function, process and environment of the situation as collaboratively defined. Changes in attitude and policy also may result.
Read the full case study
Take a look at the templates for Rich Pictures, Conceptual Graphs, and Visio Tools
Download our CORE Powerpoint loaded with information!
This wiki is licensed under a Creative Commons Attribution-Share Alike 3.0 License.
