A Usability-Pattern-Based Requirements-Analysis Method to Bridge the Gap between User Tasks and Application Features

Lee, Sang‐Hyun; Ko, In-Young; Kang, Sungwon; Lee, Danhyung

doi:10.1109/compsac.2010.39

Cited by 11 publications

(16 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several studies deal with methodologies that are used to extend agile methodologies like scrum and XP, with the aim to better [41], [42], [43], [44], [45], [46], [47], [35], [36], [48], [49], [37], [50], [51], [52], [38], [53], [54], [39], [40], [55] N…”

Section: Methodologies In Agile Rementioning

confidence: 99%

See 1 more Smart Citation

Agile Requirements Engineering: A systematic literature review

Schön

Thomaschewski

Cuaresma

2017

Computer Standards & Interfaces

268

148

View full text Add to dashboard Cite

Section: Methodologies In Agile Rementioning

confidence: 99%

“…Artifacts are used for communication, elaboration, validation and documentation of requirements in agile environment. In sum, [41], [42], [43], [57], [44], [58], [46], [47], [60], [48], [36], [49], [62], [59], [50], [52], [38], [53], [40], [55] N…”

Section: Artifacts In Agile Rementioning

confidence: 99%

Agile Requirements Engineering: A systematic literature review

Schön

Thomaschewski

Cuaresma

2017

Computer Standards & Interfaces

268

148

View full text Add to dashboard Cite

“…The identification of user tasks in various software systems is critical. For instance, it has been reported that in agile user-centered design process, the specialists encounter difficulty in building links between user tasks and application features ( Lee et al, 2010 ). Measuring human performance and the success and failure scenarios for a specific task can also be considered a critical concern for serious-game design process.…”

Section: Introductionmentioning

confidence: 99%

“…This is not possible with UML-AD. However, in the literature there are few studies such as ( Lee et al, 2010 ; Memmel, Gundelsweiler & Reiterer, 2007 ) that consider the identification of user tasks. In addition, the current software design tools’ ability to identify and represent the user tasks in the software design is limited.…”

Section: Introductionmentioning

confidence: 99%

A user task design notation for improved software design

Özcan¹,

Topalli

Tokdemir

et al. 2021

PeerJ Computer Science

View full text Add to dashboard Cite

System design is recognized as one of the most critical components of a software system that bridges system requirements and coding. System design also has a significant impact on testing and maintenance activities, and on further improvements during the lifespan of the software system. Software design should reflect all necessary components of the requirements in a clear and understandable manner by all stakeholders of the software system. To distinguish system elements, separation of concerns in software design is suggested. In this respect, identification of the user tasks, i.e., the tasks that need to be performed by the user, is not currently reflected explicitly in system design documents. Our main assumption in this study is that software quality can be improved significantly by clearly identifying the user tasks from those that need to be performed by the computer system itself. Additionally, what we propose has the potential to better reflect the user requirements and main objectives of the system on the software design and thereby to improve software quality. The main aim of this study is to introduce a novel notation for software developers in the frame of UML Activity Diagram (UML-AD) that enables designers to identify the user tasks and define them separately from the system tasks. For this purpose, an extension of UML-AD, named UML-ADE (UML-Activity Diagram Extended) was proposed. Afterwards, it was implemented in a serious game case for which the specification of user tasks is extremely important. Finally, its effectiveness was analyzed and compared to UML-AD experimentally with 72 participants. The defect detection performance of the participants on both diagrams with two real-life serious game scenarios was evaluated. Results show a higher level of understandability for those using UML-ADE, which in turn may indicate a better design and higher software quality. The results encourage researchers to develop specific design representations dedicated to task design to improve system quality and to conduct further evaluations of the impact of these design on each of the above mentioned potential benefits for the software systems.

show abstract

“…That role becomes a connector between UX designers and application developers. However, other researchers ( (Lee et al 2010) point out that Agile-UCD specialist also encounters problems. First problem is no common understandable representation of user tasks and application features.…”

Section: Introducing Ucd In Agile Projectsmentioning

confidence: 99%