Presentation is loading. Please wait.

Presentation is loading. Please wait.

Concepts in design Functionality and beyond. work organization/ practice Client users’ knowledge/ behavior/needs Technology Task Model 1 Task Model 2.

Similar presentations


Presentation on theme: "Concepts in design Functionality and beyond. work organization/ practice Client users’ knowledge/ behavior/needs Technology Task Model 1 Task Model 2."— Presentation transcript:

1 Concepts in design Functionality and beyond

2 work organization/ practice Client users’ knowledge/ behavior/needs Technology Task Model 1 Task Model 2 Scenario Simulation Prototype Functionality Dialog Representation Implementation usability measuring ethnography psychological knowledge acquisition/ hermeneutics problem analysis/ specification specification/ negotiation constraints/ opportunities feedback specification early evaluation early evaluation UVM maintaining consistency Documents/ artifacts validity analysis As soon as the system is implemented

3 Task World Ontology (Martijn van Welie) Task Agent Role Event Object name(string) goal(string) start_condition(string) stop_condition(string) initial_state(string) final_state(string) duration(integer) frequency(string) type(enum) user_actions(string) system_operations(string) name(string) skills(string) attitude(string) miscellaneous(string) name(string) goal(string) name(string) attribute(Name,Value)* action(Name)* name(string) description(string) Contains Responsible Performed_by PlaysTriggers Subtask Uses Triggers Used_by Subrole Is Performed_by

4 EUTERPE GTA representations

5 Task models Pretend to describe the whole domain of design: All … Tasks Roles actors Objects Events

6 The UVM One for each role, But include relations to other roles (as a note to relate)

7 functionality From task model 2: For each relevant role (i.e. when new technology is envisioned) As far as relevant for the design (i.e., what is new in our envisioning) Unit (or basic) tasks Related objects Object attributes Object – role relations Events

8 Unit tasks From task model 2: For each relevant role (i.e. when new technology is envisioned) Tasks that are different from task model 1 and not trivial

9 Objects “things” that feature in any new unit task: As conditions As triggers Being created, changed, transferred That help to manage new technology Competences of all involved roles to the object: Allowance to create, change, transfer, inspect

10 Events Trigger start or end of tasks Conditions for start or end As far as not effect of modeled tasks


Download ppt "Concepts in design Functionality and beyond. work organization/ practice Client users’ knowledge/ behavior/needs Technology Task Model 1 Task Model 2."

Similar presentations


Ads by Google