The methodological approach for the elaboration of the non-technical requirements (NTR) was a stepwise approach

(1) Items and constructs from the technology acceptance models UTAUT and TAM3 were examined and a preliminary list of non-technology require-ments for ESRIUM services was derived. The final list will serve as a basis for future measurements of user acceptance of ESRIUM services and shall help to optimize human-system interaction and thus increase user and technol-ogy acceptance.

(2) In addition, the non-technical requirements were associated with

a. The use cases defined

b. Relevant Stakeholders (e.g. road operator, truck driver, logistics op-erator, OEM in the roles as customer or supplier of the respective services)

(3) The preliminary NTR list was then revised in an internal validation process during a workshop with numerous project partners (e.g. road operators, tech-nical experts) to ensure a multidisciplinary view from different perspectives.

(4) Finally, an external validation of the NTR list will be performed by ASECAP members and the feedback received will be incorporated into a final version.