Abstract
[Context and motivation] Our company’s software development process describes seven roles, one of which is the requirements engineer. We want the work of the requirements engineer to give more benefit in our development projects than is currently the case.
[Question/problem] The requirements engineer works in an interdisciplinary setting closely together with the other roles, in particular with the user experience specialist, the software architect, and the project manager. We have found that these three roles are performing most of the actual RE work in our projects. As a consequence, the requirements engineer often only plays a minor role, which is also explained by the fact that the requirements engineer role is not given high organisational attention. With a few exceptions, the requirements engineer is appointed ad hoc, at project level. This poses a potential risk of neglecting important RE activities. The problem that we address is how to best distribute responsibilities between the requirements engineer role and the other roles in our organization.
[Principal ideas/results] We have surveyed a number of recent projects and have analysed to which extent RE has been carried out, by which roles, and with which techniques and tools.
[Contribution] Our contribution is to discuss our survey results and on this basis propose a redefinition of the requirements engineer role that respects that user experience, software architecture, and project management have a higher organisational priority.
This is a preview of subscription content, log in via an institution to check access.
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
Jørgensen, J.B., Kjær, M.Y.: Mjølner’s software process improvement: A discussion and strengthening using the SPI manifesto. In: Riel, A., O’Connor, R., Tichkiewitch, S., Messnarz, R. (eds.) EuroSPI 2010. CCIS, vol. 99, pp. 222–232. Springer, Heidelberg (2010)
Lauesen, S.: Software Requirements - Styles and Techniques. Addison-Wesley (2004)
Robertson, J., Robertson, S.: Mastering the Requirements Process. Addison-Wesley (2006)
Wieringa, R.J.: Design Methods for Reactive Systems. Morgan-Kaufmann (2003)
Sutcliffe, A.: Requirements Engineering From an HCI Perspective. In: Dam, R., Soegaard, M. (eds.) The Encyclopedia of Human-Computer Interaction (2011), http://www.interaction-design.org/encyclopedia/requirements_engineering.html
Sabaliauskaite, G., Loconsole, A., Engström, E., Unterkalmsteiner, M., Regnell, B., Runeson, P., Gorschek, T., Feldt, R.: Challenges in aligning requirements engineering and verification in a large-scale industrial context. In: Wieringa, R., Persson, A. (eds.) REFSQ 2010. LNCS, vol. 6182, pp. 128–142. Springer, Heidelberg (2010)
Hochmüller, E.: The Requirements Engineer as a Liaison Officer in Agile Software Development. In: AREW 201, 1st Workshop on Agile Requirements Engineering, Article No. 2, New York (2011)
Cao, L., Ramesh, B.: Agile Requirements: Engineering Practices: An Empirical Study. IEEE Software 25(1), 60–67 (2008)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Bennett-Therkildsen, A., Jørgensen, J.B., Nørskov, K., Rubin, N.M. (2013). Redefinition of the Requirements Engineer Role in Mjølner’s Software Development Process. In: Doerr, J., Opdahl, A.L. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2013. Lecture Notes in Computer Science, vol 7830. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-37422-7_20
Download citation
DOI: https://doi.org/10.1007/978-3-642-37422-7_20
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-37421-0
Online ISBN: 978-3-642-37422-7
eBook Packages: Computer ScienceComputer Science (R0)