Eliciting required characteristics for usable requirements engineering approaches

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Eliciting required characteristics for usable requirements engineering approaches

Full text

Pdf (546 KB)

Source

Symposium on Applied Computing archive
Proceedings of the 2009 ACM symposium on Applied Computing table of contents

Honolulu, Hawaii

SESSION: Requirement engineering track table of contents

Pages 360-364

Year of Publication: 2009

ISBN:978-1-60558-166-8

Authors

Kristina Winbladh	University of California, Irvine
Hadar Ziv	University of California, Irvine
Debra J. Richardson	University of California, Irvine

Sponsor

SIGAPP: ACM Special Interest Group on Applied Computing

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 16, Downloads (12 Months): 65, Citation Count: 0

Additional Information:

abstract references index terms collaborative colleagues

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1529282.1529361 What is a DOI?

ABSTRACT

It has been reported that many software companies do not use existing requirements engineering approaches. This indicates that there is room and opportunity for improving the usability of existing requirements engineering approaches. This paper describes a market study intended to elicit a set of characteristics that could improve the usability of requirements engineering approaches. The survey is aimed toward software stakeholders such as developers, designers, customers, and managers at various software companies. The survey results are used to define a set of desirable characteristics for usable requirements engineering approaches and to suggest a set of guidelines that could help achieve the desirable characteristics.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	J. Aranda, S. M. Easterbrook, and G. Wilson. Requirements in the wild: How small companies do it. In RE'07, 2007.
	2	V. R. Basili. Software development: a paradigm for the future. In COMPSAC'89, Sep 1989.
	3	Ravishankar Boddu , Lan Guo , Supratik Mukhopadhyay , Bojan Cukic, RETNA: From Requirements to Testing in a Natural Way, Proceedings of the Requirements Engineering Conference, 12th IEEE International, p.262-271, September 06-10, 2004 [doi>10.1109/RE.2004.46]
	4	A. Borgida , S. Greenspan , J. Mylopoulos, Knowledge Representation as the Basis for Requirements Specifications, Computer, v.18 n.4, p.82-91, April 1985 [doi>10.1109/MC.1985.1662870]
	5	Jaelson Castro , Manuel Kolp , John Mylopoulos, Towards requirements-driven information systems engineering: the Tropos project, Information Systems, v.27 n.6, p.365-389, September 2002 [doi>10.1016/S0306-4379(02)00012-1]
	6	Alistair Cockburn, Writing Effective Use Cases, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
	7	Anne Dardenne , Axel van Lamsweerde , Stephen Fickas, Goal-directed requirements acquisition, Science of Computer Programming, v.20 n.1-2, p.3-50, April 1993
	8	A. Eberlein and J. do Prado Leite. Agile requirements definition: A view from requirements engineering. In TCRE'02, Sep 2002.
	9	D. Firesmith. Specifying good requirements. Journal of Object Technology, 2(4): 77--87, 2003. http://www/jot.fm/issues/issue_2003_07/column7.
	10	Martin Glinz, An Integrated Formal Model of Scenarios Based on Statecharts, Proceedings of the 5th European Software Engineering Conference, p.254-271, September 25-28, 1995
	11	Michael Jackson, Problem frames: analyzing and structuring software development problems, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
	12	Colin Potts , Kenji Takahashi , Annie I. Antón, Inquiry-Based Requirements Analysis, IEEE Software, v.11 n.2, p.21-32, March 1994 [doi>10.1109/52.268952]
	13	The Institute of Electrical and Electronics Engineers. IEEE recommended practice for software requirements specifications. IEEE std 830--1998.
	14	K. Winbladh, H. Ziv, and D. J. Richardson. Surveying the usability of requirements approaches using a 3-dimensional framework. Technical Report UCI-ISR-08-3, UC, Irvine, August 2008.