The purpose of a scenario is to expose individuals’ interactions with a potential software product. This generates questions of feasibility, viability and desirability, and affords an architect to refine his or her understanding of the situation. A scenario will typically contain several distinct interactions which can be identified and extracted. Connect existing Create new Has Narrower Narrow Match Has Related Close Match Exact Match Has Broader Broad Match Has Narrower Narrow Match Has Related Close Match Exact Match Has Broader Broad Match activity (statement) affordance architect (Cooper) client (process model) cognitive science composition (process model) computation computer conceptual integrity constraint customer (process model) design digital media engineer (Cooper) extension feed fitness variable form information ecology intension interaction design linguistics live document mathematics name collision opacity (information resource) persona post-industrial post-industrial process model problem-solving process producer programmer (Cooper) project scaffold protocol dysphoria reference catalogue scenario science semiotics social science software technology user