| spelling |
oapen-20.500.12657-492322021-11-23T13:58:55Z Chapter User-Centered Design Doroftei, Daniela Gancet, Jeremi Serrano, Daniel Cubber, Geert De Wagemans, Rene Matos, Anibal Silva, Eduardo Lobo, Victor Cardoso, Guerreiro Chintamani, Keshav Govindaraj, Shashank user requirements engineering, system requirements, system validation, design formalisms bic Book Industry Communication::J Society & social sciences::JK Social services & welfare, criminology::JKS Social welfare & social services::JKSW Emergency services::JKSW3 Ambulance & rescue services The successful introduction and acceptance of novel technological tools are only possible if end users are completely integrated in the design process. However, obtaining such integration of end users is not obvious, as end‐user organizations often do not consider research toward new technological aids as their core business and are therefore reluctant to engage in these kinds of activities. This chapter explains how this problem was tackled in the ICARUS project, by carefully identifying and approaching the targeted user communities and by compiling user requirements. Resulting from these user requirements, system requirements and a system architecture for the ICARUS system were deduced. An important aspect of the user‐centered design approach is that it is an iterative methodology, based on multiple intermediate operational validations by end users of the developed tools, leading to a final validation according to user‐scripted validation scenarios. 2021-06-02T10:10:06Z 2021-06-02T10:10:06Z 2017 chapter ONIX_20210602_10.5772/intechopen.69483_346 https://library.oapen.org/handle/20.500.12657/49232 eng application/pdf n/a 56037.pdf InTechOpen 10.5772/intechopen.69483 10.5772/intechopen.69483 09f6769d-48ed-467d-b150-4cf2680656a1 FP7-SEC-2011-1 285417 open access
|
| description |
The successful introduction and acceptance of novel technological tools are only possible if end users are completely integrated in the design process. However, obtaining such integration of end users is not obvious, as end‐user organizations often do not consider research toward new technological aids as their core business and are therefore reluctant to engage in these kinds of activities. This chapter explains how this problem was tackled in the ICARUS project, by carefully identifying and approaching the targeted user communities and by compiling user requirements. Resulting from these user requirements, system requirements and a system architecture for the ICARUS system were deduced. An important aspect of the user‐centered design approach is that it is an iterative methodology, based on multiple intermediate operational validations by end users of the developed tools, leading to a final validation according to user‐scripted validation scenarios.
|
