1. 마스터 제목 스타일 편집 마스터 텍스트 스타일을 편집합니다 둘째 수준 셋째 수준 넷째 수준 다섯째 수준 Ecological Interface Design Ch.2 : Work Domain Analysis 1 조 : 이석원, 남택수

2. Division of Information Management Engineering UI Lab. 2 Introduction In order to incorporate domain information into our design, we need a systematic way of searching for this information Abstraction Hierarchy (AH) Part-Whole Hierarchy

3. Division of Information Management Engineering UI Lab. 3 Defining the System of Interest WDA begins by examining the environment. This environment is the system that will be controlled by the user. 1)Defining system boundary 2)Determine the scale of the problem to solve

4. Division of Information Management Engineering UI Lab. 4 What is an Abstraction Hierarchy? Components of AH -Levels -Tree-like structure -Levels are different and ordered along a dimension Five levels of the AH

5. Division of Information Management Engineering UI Lab. 5

6. Division of Information Management Engineering UI Lab. 6 Level by level, Working Through an AH 1)Functional Purpose -What the work domain was designed to do? -Designed for purpose of the WD -Include some evaluate criteria -Defining at least two purpose Task vs. Purpose

7. Division of Information Management Engineering UI Lab. 7 Level by level, Working Through an AH (cont.) 2) Abstraction Function -Casual relationships underlying the WD -The laws of physics -Flows of things that are conversed (p.21)

8. Division of Information Management Engineering UI Lab. 8 Level by level, Working Through an AH (cont.) 3) Generalized Function -How the casual laws of the AF level are achieved -Process of the system (p.23) -More concrete description Task and Process

9. Division of Information Management Engineering UI Lab. 9 Level by level, Working Through an AH (cont.) 4) Physical Function -What is in a WD? -Components of the WD -Capabilities

10. Division of Information Management Engineering UI Lab. 10 Level by level, Working Through an AH (cont.) 5) Physical Form -Physical appearance of the WD -Size, Shape, Color, Location, Condition, Material et al.

11. Division of Information Management Engineering UI Lab. 11 Level by level, Working Through an AH (cont.) 6) Functional and Casual Description -Functional AH : shows means-ends links -Casual AH : shows flows within each level

12. Division of Information Management Engineering UI Lab. 12 Part-Whole Hierarchies Part-Whole Hierarchy -An analysis that breaks apart the system into subsystems and components. -“contains” going down and “is part of” going up

13. Division of Information Management Engineering UI Lab. 13 Part-Whole Hierarchies (cont.) Work Domain Analysis - A complete analysis, Abstraction Hierarchy + Part-Whole Hierarchy

14. Division of Information Management Engineering UI Lab. 14 Model with Social Constraints

15. Division of Information Management Engineering UI Lab. 15 Techniques for Managing Large Models In modeling a large system, work domain models quickly become unwieldy Systematic Decomposition Link Tables

16. Division of Information Management Engineering UI Lab. 16 Models of Multiple Domains Sometimes the users do not have full control over all regions of their work domain -> make a separate work domain model for each region

17. Division of Information Management Engineering UI Lab. 17 Testing Your Model for Completeness The value of a work domain model is for the most part justified by how useful it is in later activities. -A good model will generate new kinds of information and relationships. Objectives of a validation of a work domain -Confirm that the relationships in the model exist and connect -Confirm that the model is not missing information and relationships Scenario Mapping Questionnaires

18. Division of Information Management Engineering UI Lab. 18 Testing Your Model for Completeness (cont.) Scenario Mapping -Useful technique that can confirm work domain model, obtain new information, and provide a working demonstration of the model. -A scenario is “walked through” while checking that the work domain model contains the requirements to complete the scenario -Key consideration (p.37) -General procedure (p.38) Questionnaires - to translate work domain model into a set of questions that can be evaluate (p.40)

19. Division of Information Management Engineering UI Lab. 19 Summary : Double-Checking your Work Domain Model Rules To Use As You Actually Build It 1)Define the System of Interest 2)Start Building Your Abstraction Hierarchy from the Top 3)Next Work from the Bottom 4)Complete the Middle 5)Make Sure Every Box is Connected Up and Down 6)Check Your Language 7)Develop Detail as Time Allows 8)Translate Your Hierarchy in Variables, Constraints, and Relationships 9)Show the Value of Your Analysis