Meta-requirements that Model Change

One of the common problems encountered in software engineering is addressing and responding to the changing nature of requirements. While several approaches have been devised to address this issue, ranging from instilling resistance to changing requirements in order to mitigate impact to project schedules, to developing an agile mindset towards requirements, the approach discussed in this paper is one of conceptualizing the delta in requirement and modeling it, in order to plan a response to it. To provide some context here, change is first formally identified and categorized as either formal change or informal change. While agile methodology facilitates informal change, the approach discussed in this paper seeks to develop the idea of facilitating formal change. To collect, document meta-requirements that represent the phenomena of change would be a pro-active measure towards building a realistic cognition of the requirements entity that can further be harnessed in the software engineering process.

Authors:

• Gouri Prakash

Keywords:

• Change Management
• Agile methodology
• Metarequirements

References:

[1] Kotonya, G., and Sommerville, I., Requirements Engineering Processes
and Techniques. John Wiley and Sons., 1998, NY
[2] Sidky, A. and Smith, G., Becoming Agile in an imperfect World ,
Manning Publications Co., Greenwich CT 2009
[3] Software Product Line v5 documentation,
http://www.sei.cmu.edu/productlines/ , Software Engineering Institute,
Carnegie Mellon, July 2009
[4] Barbara Paech, "What Is a Requirements Engineer?," IEEE Software,
vol. 25, no. 4, pp. 16-17, July/Aug. 2008, doi:10.1109/MS.2008.106
[5] H. Elizabeth, J. Ken and D. Jeremy, "Requirements Engineering",
Springer Publications, 2005
[6] K. Schwaber and M. Beedle, "Agile Software Development with
Scrum", Prentice Hall, 2001
[7] S.W. Ambler, "Agile Architecture: Strategies for scaling Agile
Development", 2001-2008, http://www.agilemodeling.com