2010
DOI: 10.1007/978-1-84996-347-3_7
|View full text |Cite
|
Sign up to set email alerts
|

Participatory Design in Information Systems Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0
1

Year Published

2010
2010
2019
2019

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 16 publications
(13 citation statements)
references
References 22 publications
0
9
0
1
Order By: Relevance
“…The layout of the first interface for the Phone Oximeter was created through a participatory design process that included discussions with the engineering team, usability experts and anaesthetists [10].…”
Section: Methodsmentioning
confidence: 99%
“…The layout of the first interface for the Phone Oximeter was created through a participatory design process that included discussions with the engineering team, usability experts and anaesthetists [10].…”
Section: Methodsmentioning
confidence: 99%
“…It is recommended that each user type is involved in decisions concerning design of the facilities they will use in the future, i.e. the ones that are relevant to them (Bødker et al, 2011;Damodaran, 1996). Bødker et al (2004) recommend that users considered for participation should have: knowledge of the relevant work domains; professional respect among their coworkers; and enough time to participate in the project.…”
Section: Stakeholder Types and Roles In Pdmentioning
confidence: 99%
“…In PD and IS in general, this has often meant users of various kinds (Avison & Fitzgerald, 2006;Bødker et al, 2011). However, Avison & Fitzgerald (2006) categorize stakeholders as: those on the organizational/business unit side, generically known as the users; those on the development side (e.g.…”
Section: Stakeholder Types and Roles In Pdmentioning
confidence: 99%
“…Como trabalhos futuros, estudos mais aprofundados, mais metódicos do ponto de vista da seleção dos participantes e das técnicas de análise dos dados, serão realizados para aprofundar o nível em que os requisitos são elicitados. Além disso, será realizada uma comparação entre o SPIDe e outros processos de elicitação de requisitos, como: Design Thinking [23], JAD [9] e MUST [7]. Posteriormente, a contribuição do SPIDe para a Engenharia de RequisitosÁgeis será investigada, considerando a relação custo-benefício de cada técnica, o tempo gasto e o esforço em suas aplicações, tópicos que ainda são desafios em abertos para o SPIDe e estão sendo avaliados.…”
Section: Considerações Finaisunclassified