Abstract
[Context and motivation] Experiences in working with customers in the software development community have shown that the language used to talk about requirements is inconsistent. Because of this inconsistency, projects are struggling to develop products that meet the organizations’ goals. [Question/problem] An inconsistent terminology leads to barriers to communication, which increases both the cost and length of time of development. In addition, the artifacts of requirements planning efforts are often ill-defined, and the team creates products that are not aligned with the organization’s goals. [Principal ideas/results] As an attempt at resolving this inconsistent terminology and its fallout, this paper outlines the need for a common language. We propose a solution in the form of a Requirements Object Model (ROM) and study the use of the ROM in the requirements efforts on three software development projects. [Contribution] Evidence from these three projects demonstrates that the adoption of a common terminology leads to improved communication among project teams, and as a result, alignment about the business objectives for software development projects was achieved.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
IAG Consulting: Business Analysis Benchmark Report (2008), http://www.iag.biz
The Standish Group: The Chaos Report (1994), http://www.standishgroup.com
Boehm, B.: Software Engineering Economics. Prentice-Hall, Englewood Cliffs (1981)
Alexander, I., Beus-Dukic, L.: Discovering Requirements: How to Specify Products and Services. Wiley, Chichester (2009)
Wiegers, K.: More About Software Requirements. Microsoft Press, Redmond (2006)
Alexander, I., Stevens, R.: Writing Better Requirements. Addison-Wesley Professional, Redmond (2002)
Young, R.: Effective Requirements Practices. Addison-Wesley, Boston (2001)
Gottesdiener, E.: Requirements by Collaboration. Addison-Wesley, Boston (2002)
International Institute of Business Analysis: Business Analysis Body of Knowledge (2008), http://www.theiiba.org/AM/Template.cfm?Section=Body_of_Knowledge
Hooks, I., Farry, K.: Customer-Centered Products. AMACOM, New York (2000)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Beatty, J., Hulgan, J. (2009). Experiences with a Requirements Object Model. In: Glinz, M., Heymans, P. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2009. Lecture Notes in Computer Science, vol 5512. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-02050-6_9
Download citation
DOI: https://doi.org/10.1007/978-3-642-02050-6_9
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-02049-0
Online ISBN: 978-3-642-02050-6
eBook Packages: Computer ScienceComputer Science (R0)