Capturing visions and goals to inform communication design
Proceedings of the 23rd annual international conference on Design of communication: documenting & designing for pervasive information
On formalisation of the goal concept in law
Engineering Applications of Artificial Intelligence
A Reorganization Strategy to Build Fault-Tolerant Multi-Agent Systems
CAI '07 Proceedings of the 20th conference of the Canadian Society for Computational Studies of Intelligence on Advances in Artificial Intelligence
Evaluating the communication design of branded websites: a value-based framework
Proceedings of the 27th ACM international conference on Design of communication
A process for goal oriented requirement engineering
SE '08 Proceedings of the IASTED International Conference on Software Engineering
Impact analysis of goal-oriented requirements in web engineering
ICCSA'11 Proceedings of the 2011 international conference on Computational science and Its applications - Volume Part V
Software process improvement success factors for small and medium Web companies: A qualitative study
Information and Software Technology
ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
| Hi-index | 0.00 |
Task analysis has been used traditionally in HCI and CSCW to define requirements for user interfaces, web-based or otherwise. This paper argues that a shift of paradigm is needed in web engineering from task-oriented to goal-oriented approaches for designing applications delivering a quality user experience and achieving the objectives of the stakeholders. Task models focus on fine-grained and precisely defined user needs, thereby risking a commitment to premature design decisions. Moreover, since task analysis focuses on users doing things with the system, tasks do not capture the goals of other stakeholders who are not users. Goal-oriented methods, on the other hand, provide specific support for coping with high-level users' and stakeholders' goals, facilitates the exploration of design alternatives and the definition of requirements at a suitable level of abstraction. As such, goal-based techniques are more suitable for early stages of requirements analysis; task models can be used for laterstages, such as detailed interaction design and usability evaluation. The paper conducts a detailed comparison of task- and goal-analysis design techniques, using an ongoing project for a museum website to illustrate the two techniques and their relative strengths.