In-Use, In-Situ: Extending field research methods .

1. In-Use, In-Situ: Extending field research methods. BCS London.28th October, 2005

2. Activity Theory, Air Traffic Control and tool development in research. Simone Rozzi, Peter Woodward, Bob Fields, Paola Amaldi, William Wong. Interaction Design Centre, Middlesex University. London. UK

3. Purpose of this work • The focus is on the design of analytical artefacts developed during research into a process control environment • The development of the analytical tool is described in the framework of Activity Theory (AT)

4. The context • The AD4 project is a EU founded project aimed at the development of a new 3-4D HMI for air traffic control • We were responsible for the development of the of the Operational Concept Report for airport Tower and Approach control • Its objective was to develop the user and visual requirements for the new HMI system

5. Artefact Object Subject Rules Community Division of Labour AT Framework IDC Research Activity 1-Field study in Tower Control 2-Data analysis 3-Requirement elicitation We use the Engenstrom model in order to look at our system of activities 3-OCR writing

6. The AT framework applied to AD4 • Artefact • ATC hardware/software • Video/Audio recordings • ATC knowledge of Controllers • Tower environment (flight strip etc) IDC research group Subject Object Operational Concepts (Report) • Rules • Deadlines • Departmental and project protocols • Inter-departmental practice • Security and operational Restrictions (e.g. camera use) • Division Of Labour • Focus on work practices, work flow • Focus on existing technology Community Controllers, AD4 project partners, Managers

7. What was needed: A representation An encapsulation A categorization What was present: The complexity of the ATC scenarios The (partially) reflected experience of the research team (Draft requirements list) Breakdown in practice

8. What was needed: A representation An encapsulation A categorization What was present: The complexity of the ATC scenarios The (partially) reflected experience of the research team (Draft requirements list) Breakdown in practice

9. The complexity of the ATC scenarios 1.ATC domain is a highly complex environment to study • Presence of multiple actors • Complex aerodrome ground/air space • Communication intense environment • Presence of multiple goals, not entirely compatible (safety vs. efficiency) • Decision making affected by external and internal factors

10. Draft requirements list 2.Results from data collection showed that we needed a systematic way to understand and structure requirements • User requirement List (Draft) • Need to know taxiway availability according to aircraft characteristics • Detect incorrect taxiing • Identify the aircraft, especially when far from the tower • ……. • Identification and • Categorization of • Requirements • --------------------- • ----------------- • ----------------------- • ----------------------- • ---------------------- • ------------------- • --- 2-Data analysis 1-Field study 3-REQ elicitation 3-OCR writing

11. Draft requirements list 2.Results from data collection showed that we needed a systematic way to understand and structure requirements What’s the problem? -How to consider visibility issues? -How to extend these requirements across a multiple situations? e.g. separation of aircraft appeared to be relevant in some portion of the airport but not in other… • User requirement List (Draft) • Need to know taxiway availability according to aircraft characteristics • Detect incorrect taxiing • Identify the aircraft, especially when far from the tower • ……. 2-Data analysis 1-Field study 3-REQ elicitation 3-OCR writing

12. Subject Object Community Break down in practice: resolution Tool aimed at the gathering and structuring of the Requirements Tool aimed at the gathering and structuring of the Scenario • Commencement of a new activity to resolve the contradiction; • Once new tool had been developed then we could return to complete the initial process.

13. What was present: The complexity of the ATC scenarios Presence of multiple actors Complex aerodrome ground/air space Communication intense environment Presence of multiple goals, not entirely compatible (safety vs. efficiency) Decision making affected by external and internal factors Draft requirements list Break down in practice: resolution • …….

14. Gathering and structuring User requirements Goals Actors Portion of the airport Visual requirements

15. Scenario/Problem space External factors • Complex aerodrome space

16. Scenario/Problem space Are there any other scenarios that have similar factors as these ? What are the procedures during low visibility ? What if - this situation occurred during take-off ?

17. Conclusions With regard to the project (AD4): • AD4 is entering the state of design, based on the requirements provided by MDX . • The requirements tools when further developed are expect to improve documentation and analysis Activity Theory (AT) was useful to give an account for of what happened: • Reflection upon our activities led to new perspectives within the investigation process and aided overall Communicative activity between researcher, developers and controllers • AT highlighted contradictions due to both the lack of available tool and research goal • Identification of origins of breakdown, which in case was embedded in the tools available, can lead to progress through resolution of contradiction