Eureka! Why Analysts Should Invent Requirements

@article{Robertson2002EurekaWA,
  title={Eureka! Why Analysts Should Invent Requirements},
  author={James Robertson},
  journal={IEEE Software},
  year={2002},
  volume={19},
  pages={20-22}
}
0 7 4 0 7 4 5 9 / 0 2 / $ 1 7 . 0 0 © 2 0 0 2 I E E E T he traditional job of the requirements analyst is to talk to users, find out how they work, ask them what they want, specify what is required, and have a system built. But something’s missing: this activity doesn’t improve anything. We need a step in the requirements activity called “invent something better.” This column is about how to go about doing that. 
Highly Cited
This paper has 125 citations. REVIEW CITATIONS

Topic

Statistics

01020'03'05'07'09'11'13'15'17
Citations per Year

126 Citations

Semantic Scholar estimates that this publication has 126 citations based on the available data.

See our FAQ for additional information.