Abstract
The design of interactive systems to be used in mobile and pervasive scenarios, such as emergency management, requires novel methodologies which combine user-centred design approaches and software engineering approaches tailored for distributed architectures. In this paper, the methodology adopted in a successful research project is presented together with a case study.
Similar content being viewed by others
References
D. Battista, M. de Leoni, A. De Gaetanis, M. Mecella, A. Pezzullo, A. Russo, and C. Saponaro: ROME4EU—A Web Service-Based Process—Aware System for Smart Devices. Service-Oriented Computing, Springer Berlin/Heidelberg, ICSOC 2008.
J.M. Caroll, and M.B. Rosson: Getting Around the Task-artefact Cycle—How to Make Claims and Design by Scenario. ACM Transactions on Information Systems, 1992.
S. Denning: The Springboard - How Storytelling Ignites Action in Knowledge-Era Organizations. Butterworth-Heinemann, Boston, 2001.
A. Dix, J. Finlay, G. Abowd, and R. Beale: Human Computer Interaction (3rd edition). Prentice Hall, Upper Saddle River, 2003.
European Council: Establishing a Community Mechanism to Facilitate Reinforced Cooperation in Civil Protection Assistance Interventions (2001/792/EC, Euratom). Official Journal of the European Union, p. 7–11, Council Decision of October 23, 2001.
GIS for Emergency Management. http://www.esri.com/library/whitepapers/pdfs/emermgmt.pdf, prompted on May 15, 2007.
International Civil Defense Directory (2007): Activities International Cooperation. Available online: http://www.icdo.org/act-coopdirectory.html, (last accessed: 11.4.2007).
International Standardisation Organisation: Human-Centred Design Processes For Interactive Systems. International Standards Organization, Geneva, 1999, ISO Standard 13407.
I. Jacobson, G. Booch, and J. Rumbaugh: The Unified Software Development Process. Addison Wesley, Upper Saddle River, 1999.
D.A. Norman: Simplicity Is Not the Answer. ACM Interactions, XV5, 45–46, 2008.
H. Sharp, Y. Rogers, and J. Preece: Interaction Design—Beyond Human-Computer Interaction (2nd edition). Wiley, New York, 2007.
J. Sodhi, and P. Sodhi: Managing IT System Requirements. Management Concepts, Vienna, 2003.
R.J. Sternberg: Cognitive Psychology (3rd edition). Wadsworth, Belmont, 2002.
G. Sutcliffe: Scenario-Based Requirements Engineering. Proceedings of the 11th IEEE International Conference on Requirements Engineering, IEEE Computer Society, Washington DC, USA, pp. 320–329, 2003.
K. Wiegers: More About Software Requirements. Thorny Issues and Practical Advice. Microsoft Press, Redmond, 2006.
K. Wiegers: K. Wiegers Describes 10 Requirements Traps to Avoid. Software Testing and Quality Engineering Journal, 2(1), 2000.
Acknowledgments
The authors would like to thank all the other technical partners in the project, namely IBM ITALIA, MOVIQUITY, SOFTWARE 602, the Distributed Systems Group of the Technical University of Wien, the Università di Roma TOR VERGATA, for their valuable inputs and fruitful discussions, and the Dipartimento della Protezione Civile, Regione Calabria, namely Salvatore Alcaro, Giuseppe Iiritano, Francesco Manti and Antonino Scopelliti, for invaluable support throughout the project and when interacting continuously with users.
Author information
Authors and Affiliations
Corresponding author
Additional information
This work has been partly supported by the EU research project WORKPAD—http://www.workpad-project.eu/.
Appendix 1
Appendix 1
Interview Template
The moderator asks potential users the following questions:
Basic Data
Date: | |
Name of the interviewed person: | |
Organisation: | |
Position in the organisation | |
Moderator: | |
Present Persons: |
Question 1: What are your main responsibilities within this organisation?
Question 2: In what kind of emergencies is your organisation involved?
Question 3: What is your role during an emergency? In which phase of an emergency are you involved?
Question 4: Do you know the statistical frequency according to which an emergency happens in your territory?
At this point (it depends on the user), the interview is divided in two trunks: the first concerns front-end users and the second concerns back-end users. The main idea is to immerse the user in the context of an emergency. It means that we have to investigate the steps that the user performs when preparing himself to face the emergency (when he/she gets a call related to an emergency), until the moment in which he/she has to act really. In this way, we create an “implicit scenario” for the user (he/she believes to be in an emergency situation), and he can answer in the way he wants to.
Front End User
Shortly after the emergency has happened
Question 5a: Which steps do you perform shortly after the emergency has happened?
Question 6a: What kind of information (related to the emergency) do you get from the control centre?
Question 7a: How long is the front-end team actively involved in this phase of the emergency (average)?
Question 8a: What kind of information do you exchange with other members of the team during the transport to the place where the emergency has happened?
During the emergency
Question 9a: Describe the composition of the team and the various roles of the team members allocated to them during the emergency.
Question 10a: What kind of technical devices do you currently use in emergencies?
Question 11a: How do you communicate with the other team members and the back-end centre?
Does your team use a separate communication channel?
Question 12a: What kind of technology do you currently use in/after emergency situations?
Question 13a: What kind of information (and in which form) do you exchange with the team leader?
Question 14a: What kind of information (and in which form) do you exchange with the back-end centre?
Question 15a: Do you co-operate with members of other organisations? (For example police, etc.)?
Do you exchange information and/or data?
Do you share a common technology?
Back End User
Shortly after the emergency has happened
Question 5b: Which steps do you perform shortly after the emergency has happened?
Question 6b: How much time are the back-end team actively involved in this phase of the emergency (average)?
Question 7b: What kind of information do you send to front-end operators, who have to prepare them to face the emergency?
Question 8b: In what way do you obtain such information and in which format?
Question 9b: Please, describe the structure of your organisation and the various roles assigned to the team members in this phase of the emergency?
During the emergency
Question 10b: What kind of technical devices do you use for the communication with the front-end operators?
Question 11b: What kind of communication technology do you use?
Does your organisation use a separate communication channel?
Question 12b: Does the communication take place with a particular team member(s) or can you communicate arbitrarily with everybody (how strict are the hierarchical and the communication structures defined within your organisation)?
Question 13b: What kind of information do you send to the front-end users?
Question 14b: What kind of information do you receive from the front-end users?
Question 15b: Do you share technology and data with other organisations?
Which kind of data/technology?
In which way does this exchange of information take place?
The last questions are the same for every user.
Question 16: Do you currently use Geographic Information Systems (GIS)?
If yes, which software and data do you use?
Question 17: Do you think that the devices and technologies used to face the emergency are conform to the purpose for which they are used?
Question 18: What do you think would be a big improvement concerning the technology part?
What kind of improvement would you propose?
Rights and permissions
About this article
Cite this article
Humayoun, S.R., Catarci, T., de Leoni, M. et al. Designing Mobile Systems in Highly Dynamic Scenarios: The WORKPAD Methodology. Know Techn Pol 22, 25–43 (2009). https://doi.org/10.1007/s12130-009-9070-3
Received:
Accepted:
Published:
Issue Date:
DOI: https://doi.org/10.1007/s12130-009-9070-3