Rqmts_core at Ia Summit Barcelona

8/6/2019 Rqmts_core at Ia Summit Barcelona

1/38

Creative Commons license. Wiebe & Confer, 2007

A seven-step methodology using cognitive graphing in a soft systems framework

Scott M. Confer

User Experience Manager

Sears Holdings Corporation

Joanna Wiebe

Information Architect

Orbitz Worldwide


http://onemind.wetpaint.com

Download this presentation at:

Fractal image by Digon3


2/38

2


3/38


(Cognitive Organization for

Requirements Elicitation)

integrates twoanalytical

methodologies

3 Amigurumi photo by Ashley Ringrose (MrTruffle)


4/38Creative Commons license. Wiebe & Confer, 2007

CORE characteristics

4



CORE hasseven steps

5 Amigurumi photo by Ashley Ringrose (MrTruffle)



Example Mess: late night, guests, need stimulantFirst there is is...

6



Example Mess: late night, guests, need stimulant

7



Example Mess: late night, guests, need stimulant

8



Good requirements are:

9



How do we get out of a mess?

10 Coffee cup photo by Zesmerelda, at Leonardos in Chicago, IllinoisFractal image by Digon3


11/38


structure the mess: form your team

problem-solver

investigator subjectmatterexpert

customer/client

problem-owner

11 Amigurumi by anapaulaoli and others


12/38


13/38

Example: Rich Picture for making coffee


14/38


2

draw a Rich Picture

14


15/38

Creative Commons license. Wiebe & Confer, 2007P.J. Lewis, 'Rich Picture building in the SSM,' European Journal of Information Systems

Rich Picture example

15


16/38


Rich Picture example

16


17/38


define the system . . .

17 Coffee cup photo by Zesmerelda, at Leonardos in Chicago, Illinois


18/38


conceptualize the problem space . . .

18

Event: Needstimulant Initiates

Goal: stay awake Concept: CoffeeRefers-to

Goal - Action:Decide to make your

own

Means

Reason

Goal: Brewcoffee


19/38


1 2

3

theyrule.net Network Diagrams of Conspiracy

Mark Lombardi

Internet Search

Dubberly Design Office

4

The Budget Graph

Jesse Bachman

example network diagrams of concepts


20/38


closeup network diagram: no grammar


21/38


conceptual graphs dont have to be fancy

21


22/38


23/38


a diagram of nodes connected by arcs

23


24/38


FamilyOrbitz requirements

sources

BudgetCalculatorBR13ShoppingCartBR12Recommendation EngineBR11TripBuilderBR10RoadTripToolBR9CommunityBuildingBR8CareBR7

EnhancedFilteringBR6EnhancedMappingBR5ExclusiveFamilyContentBR4FamilyTravelDealsBR3PurchaseTravelBR2GeneralBR1

Area of FocusID

BudgetCalculatorBR13ShoppingCartBR12Recommendation EngineBR11TripBuilderBR10RoadTripToolBR9CommunityBuildingBR8CareBR7

EnhancedFilteringBR6EnhancedMappingBR5ExclusiveFamilyContentBR4FamilyTravelDealsBR3PurchaseTravelBR2GeneralBR1

Area of FocusID

Family Orbitz requirements sources

23

24


25/38


Family Orbitz conceptual graph structure

25


26/38


Family Orbitz visual layout concept


27/38


Concept: registereduser role

Concept:unregistered user

role

State: temp profilecreated for

unregistered role

Hascons

equence

Goal: Manageevent travel

Concept: customer

service agent role

Goal: Confirmtraveler itinerary

Goal - Action: Applytravel policy

Means

Mea

ns

Concept: Thirdparty event site

Concept: TravelArranger role

Ha

sco

nse

que

nce

Event: User dataenters system

State: registeredrole profile

prepopulated

Hasconsequence

Goal - Action:Create participant

types

Goal - Action:Create policy

Before

After

Conceptual Graph Structure

Meeting Site IntegrationCustomer perspective: A system to enable customers to book and

manage travel online at the same time that they register for meetings,without having to make a second login.

Relevant system

Taxonomy Goal hierarchyCausal network

Hasproperty

Haspart

Haspart

Haspa

rt

Haspart

Concept: Emailaddress

Refers-to

Concept: Thirdparty database

Goal: Displaytraveler itinerary

Before

State: datavalidated

Has

consequen

ce

Haspart

Concept:Archived policy

Goal - Action:Single sign on

Concept: Roles

Has part

V. 1.0

V. 2.0

Version

Style: behind thescenes

Manner

Event:user passed to

system Initiates

Refers-

to

Hasconsequence

Another Orbitz Worldwide project

27

Spatial relations

Concept: Paymentmodule

Concept: Servicefees

Has

part

Concept:Reservation page

Has part

b k t th ff l l hi h


28/38


back to the coffee example: goal hierarchy

Event: needstimulant

Initiates

Goal - Action:Decide to make

your own

Means

Goal: Brew hotcoffee

Before

State: SleepyOr

Initiates

Goal - Action: Getstimulant

Goal: stay awake

Event: want to bestimulated

Initiates

Reason Means

Reason

Goal - Action: Drinkcoffee

Means

Reason

During Before

Goal hierarchy

b k t th ff l t i t k


29/38



Initiates


your own

Means


Before

State: SleepyOr

Initiates


Goal: stay awake


Initiates

Reason Means

Reason


Means

Reason

During Before

Goal hierarchy Taxonomic networkConcept: Coffee

Refers-to

Concept:stimulating drink

Is-a

Concept: brewedcoffee

Has-instance-of

Concept: espresso

Has-instance-of

Concept: Food

Is-a

Concept: water

Concept: Coffeegrounds

Has-part

Has-part

back to the coffee example: taxonomic network


30/38



Initiates


your own

Means


Before

State: SleepyOr

Initiates


Goal: stay awake


Initiates

Reason Means

Reason


Means

Reason

During Before

Goal hierarchy Taxonomic networkConcept: Coffee

Refers-to

Concept:stimulating drink

Is-a

Concept: brewedcoffee

Has-instance-of

Concept: espresso

Has-instance-of

Concept: Food

Is-a

Concept: water

Concept: Coffeegrounds

Has-part

Has-part

back to the coffee example: more detailed goals

Goal hierarchy: moredetailed level goal

Event: decide tomake own coffee

Initiates

Event: coffee usedup

State: coffeegrounds left in

makerOr

Goal - Action:

empty out oldcoffee and grounds

Initiates

Initiates

Means

Goal - Action: make

fresh pot with newwater and groundsBefore

Means

Goal - Action: start

brew

Means

Before

30

nodes


31/38


Event:

Goal - Act ion:

State:

Concept:

Style:

Goal:

NODE TYPE DEFINITION

Agoal node indicates a circumstance, situation, state of affairs or event desired by a person or an agent

(such as a software application). It does not indicate how the goal is accomplished.

Agoal-action nod e indicates either:

- action(s) performed by the person or agent to attain a goal, or

- a mix of both goal and activity/activities of a person or agent toward a goal.

Anevent node indicates a condition of transition between one stable state and another stable state.

Aconcept node indicates a single entity, idea or construct, with a single name, which can be a word or

phrase.

Astate node indicates a relatively stable situation, circumstance, manner or condition of being.

Astyle node indicates:

- a quality of a goal-action, such as duration or speed, or

- an instrumentality of a goal-action (what agent or person does it?)

Event:

Coffee brews

Goal - Action:Make coffee

State:Hot coffee ready

Concept:Stimulating

drink

Style:Home-brewed

Goal:Stay awake

EXAMPLES

nodes

From: (Gordon et al.)31

arcs


32/38


ARC TYPE DEFINITION

Reason

Means

Before

During

After

Initiates

Has-consequence

Refers-to

And

Or

Manner

Is-a

Equivalent-to

Has-instance-of

Has-property

Has-part

Implies

Spatial relations

Why or how something is done.

How something is done, or the action by which a goal or goal-action is performed.

Something happens or exists before something else.

Two things happen or exist simultaneously; neither happens or exists before the other.

Something happens or exists after something else.

Something starts, cues, or causes an agent to acquire a goal or perform an action.

Indicates an action has had some result.

Indicate that a node is composed of at least one other concept.

Two things co-occur, order not important, and a temporal relationship between the nodes does NOT exist.

Indicates that only one of a group of things, usually two, occurs, but NOT both.

A specific way in which something is done.

A concept is one in a group of similar concepts that are types or kinds of another broader based concept.

A concept is functionally the same as another concept, and differs only name.

Indicates that there is a specific, concrete example or illustration of a concept.

The presence of particular characteristics or dynamic features of a concept.

A concept is one in a group of physical or conceptual pieces, or components, of another concept.

When the presence of a particular state, event, or style infers another is present, but is not caused by the first.

on, contains, above, below, left-of, right-of, etc. for common locations

arcs

From: (Gordon et al.)

32

legal combinations


33/38


Goal hierarchy substructure

SOURCE NODE ARC TYPE

Means

Initiates

Reason

During

Before

AfterGoal -

Action:

Goal:

TERMINAL NODE

Goal -Action:

Goal:

Goal -Action:

Goal:

Goal -Action:

Event:

State:

Style:

Goal -Action:

Goal:

Manner

Has-consequence

And

Or

Goal -Action:

Goal -Action:

Style:

Event:

State:

Style:

Goal -Action:

TERMINAL NODE

Is-a

Equivalent-to

Has-instance-of

Has-property

Taxonomy substructure

Concept: Concept:

Concept: Concept:

Event: Event:

State: State:

Concept:

Event:

State:

Goal -Action:

Goal:

SOURCE NODE ARC TYPE

Has-part

Causal network substructure

Event:

State:

Style:

Implies

Has-consequence

And

Or

Event:

Manner

Event:

Style:

Style:Style:

Manner

Event:

State:

Before

During

After

Event:

State:

Event:

State:

Style:

Refers-to

Concept:

SOURCE NODE ARC TYPE TERMINAL NODE

Event:

State:

Style:

Spatial relations substructure

Concept: Concept:

< any spatial relation >

SOURCE NODE ARC TYPE TERMINAL NODEGoal -

Action:

Concept:

Goal:

legal combinations

Download Visio smartstencils and viewexamples of Cognitive Graph Structuresat http://onemind.wetpaint.com

TM

From: (Gordon et al.)33

how to make


34/38


context

how to make

34Amigurumi book by Weenah3

how to make


35/38


write requirements


36/38


write requirements

agree on requirements

implement into information architecture

2036

CORE works in all design contexts


37/38


CORE works in all design contexts

37 Photo bypapixulooo37

FREEdownloads


38/38


y Amy Clampitt

Scott M. ConferUser Experience ManagerSears Holdings Corporation

[email protected]

Key references

Checkland, P.B. (1981). Systems Thinking, Systems Practice. John Wiley & Sons.

Gordon, S. E. & Gill, R. T. (1997). Cognitive Task Analysis. In C. Zsambok & G. Klein,(Eds.), Naturalistic Decision Making (pp. 131-140). Hillsdale, NJ: Lawrence Erlbaum.

Gordon, S.E., Schmierer, K.A., & Gill, R. T. (1993). Conceptual graph analysis: Knowledgeacquisition for instructional system design. Human Factors, 35, 459-481.

Joanna WiebeInformation ArchitectOrbitz [email protected]

http://onemind.wetpaint.com

20


TM

Documents

Rqmts_core at Ia Summit Barcelona