2004
DOI: 10.1007/s00766-004-0196-2
|View full text |Cite
|
Sign up to set email alerts
|

An operational model for structuring the requirements generation process

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2007
2007
2022
2022

Publication Types

Select...
4
3
1

Relationship

2
6

Authors

Journals

citations
Cited by 22 publications
(11 citation statements)
references
References 13 publications
0
11
0
Order By: Relevance
“…As designers are usually not users of the environment that they design , there is a lack of empathy for and interpretation of the requirements of diverse users and, subsequently, restricted practical solutions. Because successful universal design is typically built on the basis of gaining a better understanding of real-user needs (Clarkson et al, 2007;Darses and Wolff, 2006), the ability to capture user needs early and correctly is essential to reduce late discovery and to increase user satisfaction (Arthur and Grö ner, 2005;Harding et al, 2001). Thus, eliciting, capturing, and describing diverse user needs are as important as focusing on the representation, solution, and optimization of universal design requirements.…”
Section: Introductionmentioning
confidence: 99%
“…As designers are usually not users of the environment that they design , there is a lack of empathy for and interpretation of the requirements of diverse users and, subsequently, restricted practical solutions. Because successful universal design is typically built on the basis of gaining a better understanding of real-user needs (Clarkson et al, 2007;Darses and Wolff, 2006), the ability to capture user needs early and correctly is essential to reduce late discovery and to increase user satisfaction (Arthur and Grö ner, 2005;Harding et al, 2001). Thus, eliciting, capturing, and describing diverse user needs are as important as focusing on the representation, solution, and optimization of universal design requirements.…”
Section: Introductionmentioning
confidence: 99%
“…We contend that these issues can be resolved by structuring the Agile RE process by identifying a conventional RE approach and modifying it somewhat to reflect an agile environment. In this work, we tailor the Requirements Generation Model (RGM) [3], a conventional requirements gathering approach to reflect the agile philosophy. The result is the Agile Requirements Generation Model (Agile RGM) [4] that (1) is an iterative and incremental approach to gathering requirements and (2) reflects the values of agility.…”
Section: Introductionmentioning
confidence: 99%
“…• Some plain language statements can mean two different things, e.g., words can be synonyms or homonyms (Tsumaki & Tamai, 2006). The way people express problems can be misleading (Arthur & Groner, 2005). …”
Section: There Are Human Aspects Of Re That Preclude Simple Communicamentioning
confidence: 99%
“…• Some clients only know about a single section of the business that needs to be fixed (Arthur & Groner, 2005).…”
Section: The Client Cannot Say What the Business Needsmentioning
confidence: 99%
See 1 more Smart Citation