The document describes the CORE methodology for requirements elicitation. CORE integrates conceptual graphing and soft systems inquiry frameworks. It is a 7-step process that includes: 1) defining an unstructured situation, 2) creating a rich picture, 3) writing root definitions of relevant systems, 4) creating conceptual graphs, 5) iterating graphs to develop preliminary requirements, 6) reaching team agreement on requirements, and 7) translating requirements to information architecture. The methodology provides structure for clarifying vague requirements through a collaborative process focused on user goals.

2. How to get out of a mess: Use the CORE methodology Cognitive Organization for Requirements Elicitation Scott M. Confer Information Architect Author contact: joanna.wiebe@orbitz.com 312.260.8274 Joanna Wiebe Information Architect

10. Step 1: The Unstructured Situation Also known as the “Mess TM ” in soft systems In an unstructured situation, “…human perceptions, behavior or actions seemed to be the dominating factors…goals, objectives and even interpretation of events are all problematic.” (Naughton, 2005)

15. Step 2: Create a “Rich Picture”

19. Key Actors 1

20. Structure of actor interactions 2

21. New Features 3

22. Process flow 4

23. Environmental factors 5

24. “ Hard” or “soft” information 6 6

25. Types of requirements 7

26. Tasks to understand the requirements 8

29. Step 4: Create conceptual graphs CGS method is broadly applicable to human endeavors The grammar is based on the cognitive psychology and story comprehension research by Arthur Graesser.

33. Examples of concept mapping found online… 1 2 3 theyrule.net Network Diagrams of Conspiracy Mark Lombardi Internet Search Dubberly Design Office 4 The Budget Graph Jesse Bachman … enable discovery but don’t necessarily show user goals or use formal grammar

35. Goal hierarchy example

36. Substructure 1. Goal hierarchy example Goal Hierarchies are our ‘bread and butter’ for system design.

39. Key question probes for primary research Start with goals, add in supporting concepts. For innovation, focus on manual and machine-aided tasks that are difficult, time intensive, repetitive, and pet peeves.

40. Step 5 Iterate graphs/develop preliminary requirements The process of analysis that is encouraged to find and develop new solutions serves as a scaffolding for the “a-ha” moment.

44. Case study example: Preliminary requirements Thirty-five pages of a “requirements doc” were transformed into succinct, prioritized requirements

46. Step 7 Translate to Information Architecture