PATHS User Requirements Methodology. Our approach to gathering and applying user requirements for the PATHS system supports the principles of user-centred design outlined above, and the following diagram summarises the overall methodology, and illustrates its relationship with other areas of the project.
PATHS User Requirements Methodology. Key Knowledge base All project deliverables Context D1.1 User Requirements and D1.2 State of the Art System development D1.1 User Requirements and WP2, WP3, WP4 System evaluation WP5 and later stages of D1.1 User Requirements As with the PATHS project overall, the user requirements activity is underpinned by sound theoretical principles and knowledge assimilated through extensive and ongoing reviews of the research literature. This knowledge informs the selection of methods for user requirements gathering, and the design and use of these methods to understand the needs of potential users of the PATHS system. Primary methods for the PATHS user requirements gathering comprise surveys, both quantitative and qualitative approaches, and user experiments, incorporating task-analysis and user observation. This primary data is supplemented by desk research focused on contextual information, and understanding of the outcomes and learning from relevant previous projects in areas related to digital cultural heritage. Data collected via these methods are then used in the practical context of system development and refinement, and are documented and evidenced through output of project deliverables in the form of reports and artefacts. Elements of the methodology directly relevant to this D1.1 User Requirements deliverable are explained in more detail below.
