Writing good requirements is difficult. Authors of requirements specifications need to acquire specific habits and professional writing styles to avoid ambigu-ities. However, gaining and sharing related experience and abilities is challenging. Heuristic Critiques offer help in this situation. Experience on writing good re-quirements can be codified as heuristic critiques. When integrated in a requirements tool, a heuristic critique can automatically check requirements specifications and provide constructive feedback (critique), whenever a piece of experience is applicable. Observing this feedback helps requirements authors to transfer expe-rience in writing, and internalize it. In this paper we describe the concept of learning to write better re-quirements through heuristic critiques - both, on an individual level and on an organizational level. The proposed concept has been applied in several dedicat-ed requirements support tools; it can also be used to improve existing tools and methods.
[1]
D. Schoen,et al.
The Reflective Practitioner: How Professionals Think in Action
,
1985
.
[2]
Kurt Schneider,et al.
Experience and Knowledge Management in Software Engineering
,
2009
.
[3]
Eric Knauss,et al.
Feedback-driven requirements engineering: The Heuristic Requirements Assistant
,
2009,
2009 IEEE 31st International Conference on Software Engineering.
[4]
Donald A. Sch.
The reflective practitioner: how professionals think in action
,
1983
.
[5]
Eric Knauss,et al.
Lightweight Process Documentation: Just Enough Structure in Automotive Pre-development
,
2008,
EuroSPI.
[6]
Gerhard Fischer.
Domain-oriented design environments
,
2004,
Automated Software Engineering.