Intangible trust requirements - how to fill the requirements trust "gap"?
dc.contributor.author | French, Tim | en_GB |
dc.contributor.author | Huang, Wei | en_GB |
dc.date.accessioned | 2013-04-07T18:34:46Z | |
dc.date.available | 2013-04-07T18:34:46Z | |
dc.date.issued | 2010 | |
dc.identifier.citation | French, T., and Huang, W. (2010) 'Intangible Trust Requirements - How to Fill the Requirements Trust "Gap"? '. In Proceedings of the First International Workshop on the Interplay between User Experience and Software Development. Rekjavick, Iceland, October 17th, 2010, Vol. 656: 13-17. | en_GB |
dc.identifier.issn | 1613-0073 | |
dc.identifier.uri | http://hdl.handle.net/10547/279168 | |
dc.description.abstract | Previous research efforts have been expended in terms of the capture and subsequent instantiation of "soft" trust requirements that relate to HCI usability concerns or in relation to "hard" tangible security requirements that primarily relate to security a ssurance and security protocols. Little direct focus has been paid to managing intangible trust related requirements per se. This 'gap' is perhaps most evident in the public B2C (Business to Consumer) E- Systems we all use on a daily basis. Some speculative suggestions are made as to how to fill the 'gap'. Visual card sorting is suggested as a suitable evaluative tool; whilst deontic logic trust norms and UML extended notation are the suggested (methodologically invariant) means by which software development teams can perhaps more fully capture hence visualize intangible trust requirements. | |
dc.language.iso | en | en |
dc.publisher | Audio Visual Services (A VS), University of Leicester, UK | en_GB |
dc.relation.url | http://www.informatik.uni-trier.de/~ley/db/conf/iused/iuxsed2010.html | en_GB |
dc.relation.url | http://ceur-ws.org/Vol-656/I-UxSED2010-Proceedings-Complete.pdf | en_GB |
dc.subject | intangible trust requirements | en_GB |
dc.subject | visual card-sorts | en_GB |
dc.subject | deontic norms | en_GB |
dc.title | Intangible trust requirements - how to fill the requirements trust "gap"? | en |
dc.type | Conference papers, meetings and proceedings | en |
dc.contributor.department | University of Bedfordshire | en_GB |
html.description.abstract | Previous research efforts have been expended in terms of the capture and subsequent instantiation of "soft" trust requirements that relate to HCI usability concerns or in relation to "hard" tangible security requirements that primarily relate to security a ssurance and security protocols. Little direct focus has been paid to managing intangible trust related requirements per se. This 'gap' is perhaps most evident in the public B2C (Business to Consumer) E- Systems we all use on a daily basis. Some speculative suggestions are made as to how to fill the 'gap'. Visual card sorting is suggested as a suitable evaluative tool; whilst deontic logic trust norms and UML extended notation are the suggested (methodologically invariant) means by which software development teams can perhaps more fully capture hence visualize intangible trust requirements. |