Already a member?
Sign in
| Version | User | Scope of changes |
|---|---|---|
| Nov 8 2007, 9:28 AM EST | Refnocs | 1 word added, 1 word deleted, 1 photo added |
| Sep 17 2007, 4:33 PM EDT | joannawiebe |
Changes
Key: Additions Deletions
CORE: Cognitive Organization for Requirements Elicitation)Elicitation
by Joanna Wiebe and Scott Confer
Download our presentation from SlideShare.net
Presentation at theEuroIA 2007 conference in Barcelona, Spain
Poster presentation at the Las Vegas 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, employing two methods of visualizing information:
Take a look at the templates for Rich Pictures, Conceptual Graphs, and Visio ToolsDownload our presentation from SlideShare.net
Presentation at theEuroIA 2007 conference in Barcelona, Spain
Poster presentation at the Las Vegas 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, employing two methods of visualizing information:
- The Rich Picture, which is a fairly unstructured way to focus on structure, function, process, and environment, early in the requirements definition process.
- The Conceptual Graph Structure (CGS), which is a more formal way to analyze documents, dynamic conversations and observations.
We welcome your comments.
This wiki is licensed under a Creative Commons Attribution-Share Alike 3.0 License.
