首页> 外文会议>International conference on computers helping people with special needs >Group-Based Expert Walkthroughs to Compensate for Limited Access to Target User Groups as in Case of Chronically Ill Patients
【24h】

Group-Based Expert Walkthroughs to Compensate for Limited Access to Target User Groups as in Case of Chronically Ill Patients

机译:基于组的专家演练,以补偿针对慢性病患者的对目标用户组的有限访问

获取原文

摘要

Involvement of real end users right from the beginning of an IT project is understood nowadays as good practice particularly in research projects where new and innovative concepts are to be investigated. In some situations, this is not feasible though, because this would cause unreasonable burden on target users, e.g., in case of chronically ill older patients or it is simply not possible, because administrative hurdles like permission by ethical committees need to be overcome, therefore it is necessary to install substituting methods. In the PICASO project (Personalised Integrated Care Approach for Service Organisations and Care Models for Patients with Multi-Morbidity and Chronic Conditions) this was achieved by implementing group-based expert walkthroughs where experts with different work-domain expert knowledge, in this case from usability, accessibility, clinical practice and software development, walked through an application by following typical usage scenarios target users are supposed to achieve. In contrast to the original method outcomes of walkthroughs were documented in form of software requirements, i.e. essential functionalities and features of the envisioned application instead of usability and accessibility issues. This way a reference document for developers evolved that closed the gap in bringing user requirements to application development.
机译:如今,从IT项目一开始就让真正的最终用户参与进来已被视为一种良好实践,特别是在研究项目中要研究新的和创新概念的情况下。在某些情况下,这是不可行的,因为这将给目标用户造成不合理的负担,例如,在慢性病的老年患者中,或者根本不可能,因为需要克服诸如伦理委员会许可的行政障碍,因此必须安装替代方法。在PICASO项目(服务机构的个性化综合护理方法和患有多种疾病和慢性病的患者的护理模型)中,这是通过实施基于小组的专家演练来实现的,其中具有不同工作领域专家知识的专家(在这种情况下是出于可用性的考虑) ,可访问性,临床实践和软件开发,通过遵循目标用户应实现的典型使用场景来逐步完成一个应用程序。与原始方法相反,演练的结果以软件要求的形式记录下来,即所设想的应用程序的基本功能和特性,而不是可用性和可访问性问题。这样,针对开发人员的参考文档就不断完善,从而消除了将用户需求带入应用程序开发中的空白。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号