2010 15th IEEE International Conference on Engineering of Complex Computer Systems 2010
DOI: 10.1109/iceccs.2010.50
|View full text |Cite
|
Sign up to set email alerts
|

Requirements Elicitation with Adapted CUTA Cards: First Experiences with Business Process Analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
2
2
2

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 20 publications
0
3
0
Order By: Relevance
“…Another similar work explores an adapted version of CUTA (Collaborative User's Task Analysis) as an alternative approach to identify business processes [35]. This has evolved into the CUTA4BPM [36] where different semi-structured cards are used to capture details about business process activities and control flow.…”
Section: Related Workmentioning
confidence: 99%
“…Another similar work explores an adapted version of CUTA (Collaborative User's Task Analysis) as an alternative approach to identify business processes [35]. This has evolved into the CUTA4BPM [36] where different semi-structured cards are used to capture details about business process activities and control flow.…”
Section: Related Workmentioning
confidence: 99%
“…These challenges increase manifold when a project is globally distributed across geographical, temporal, and socio‐cultural units [9]. Understanding stakeholders’ problems, persuading them to express their ideas, priorities, and reservations openly and representing the requirements easily are challenges which – once overcome – help to design and develop what customer/client needs [20]. The success of requirements elicitation phase depends upon the communication skills and experience of requirements engineers since this phase is interdisciplinary and the challenges for novices are profound [17].…”
Section: Related Workmentioning
confidence: 99%
“…Two papers use psychological approach to obtain requirements from users. The two approaches have been identified as Activity Theory and small group theory respectively [11]- [16] whereby 2 papers have mentioned prototype as the way to get the requirements from their domain [9], [11], [15]- [16]. Regardless of various elicitation techniques, a traditional technique such as interview [5]- [7] is still being implemented in order to gain requirements from user and there is also a participatory approach from expert as well as users [13]- [14] in CSCW development.…”
Section: B Requirements Elicitation Techniquementioning
confidence: 99%