1 Boehm, B.W.: ‘Software risk management: principles and practices’, IEEE Software, 1991, 8, (1), pp. 32–41 2 Pinheiro, F.A.C.: ‘Requirements honesty’. Int. Workshop on Time-Constrained Requirements Engineering (TCRE002)’Germany, September 2002 3 van Lamsweerde, A., Dardenne, A., Delcourt, B., and Dubisy, F.: ‘The KAOS Project: knowledge acquisition in automated specification of software’. Proc. AAAI Spring Symp. Series, March 1991, (Stanford University, AAAI), pp. 59–62 4 Keil, M., Cule, P.E., Lyytinen, K., and Schmidt, R.C.: ‘A framework for identifying software project risks’, Commun. ACM, 1998, 41, (11), pp. 76–83 5 Wallace, L., and Keil, M.: ‘Software project risks and their effect on outcomes’, Commun. ACM, 2004, 47, (4), pp. 68–73 6 Wallace, L., Keil, M., and Rai, A.: ‘How software project risk affects project performance: an investigation of the dimensions of risk and an exploratory model’, Decision Sci., 2004, 35, (2), pp. 289–321 7 Bernader, P., and Andrews, A.: ‘Requirements prioritization’ in Aurum, A., and Wohlin, C. (Eds.): ‘Engineering and managing software requirements’ (Springer, 2006), pp. 69–94 8 IEEE Std. 1233-1996, IEEE guide for developing system requirements specifications’, IEEE, June 1996 9 Karlsson, J., and Ryan, K.: ‘A cost-value approach for prioritizing requirements’, IEEE Software, 1997, 14, (5), pp. 67–74 10 Karlsson, J., Wohlin, C., and Regnell, B.: ‘An evaluation of methods for prioritizing software requirements’, J. Information Software Technol., 1998, 39, (14–15), pp. 939–947 11 Dardenne, A., Fickas, S., and van Lamsweerde, A.: ‘Goal-directed concept acquisition in requirements elicitation’. Proc. 6th EEE Workshop System Specification and Design, Como, Italy, 1991, pp. 14–21 12 Darimont, R.: ‘Requirements engineering with objectiver: from goal analysis to automatically derived requirements documents. RE’03 Exhibitors’ Track Int. Conf. Requirements Engineering (RE03), IEEE Computer Society Press, Los Alamitos, CA, 2003 56 IET Softw., Vol. 2, No. 1, February 2008 Authorized licensed use limited to: University of Reading Library. Downloaded on July 20,2010 at 21:36:10 UTC from IEEE Xplore. Restrictions apply. 13 Rising, L., and Janoff, N.: ‘The scrum software development process for small teams’, IEEE Software, 2000, 17, (4), pp. 26–32 14 Boehm, B.W.: ‘A spiral model of software development and enhancement’, Computer, 1988, 21, (5), pp. 61–72 15 Baniassad, E., Clements, P.C., Arau´jo, J., Moreira, A., Rashid, A., and Tekinerdogan, B.: ‘Discovering early aspects’, IEEE Software, 2006, 23, (1), pp. 61–70 16 Mylopoulos, J., Chung, L., and Nixon, B.: ‘Representing and using nonfunctional requirements: a process oriented approach’, IEEE Trans. Software Eng., 1992, 18, (6), pp. 483–497 17 Rashid, A., Sawyer, P., Moreira, A., and Araujo, J.: ‘Early aspects: a model for aspect-oriented requirements engineering’. Requirements Engineering 2002 (RE002), Germany, 2002, pp. 199–202 18 Hall, J.G., Jackson, M., Laney, R.C., Nuseibeh, B., and Rapanotti, L.: ‘Relating software requirements and architectures using problem frames’. Tenth Int. IEEE Conf. Requirements Engineering, Los Alamitos, CA, 2002, (IEEE Computer Society Press), pp. 137–144 19 Jackson, M.: ‘Problem frames: analysing and structuring software development problems’ (Addison Wesley, 2000) 20 Cornford, S.L., Feather, M.S., and Hicks, K.A.: ‘DDP – a tool for life-cycle risk management’. Proc. IEEE Aerospace Conf., Big Sky, Montana, 2001, pp. 441–451 21 Freimut, B., Briand, L.C., and Vollei, F.: ‘Determining inspection cost-effectiveness by combining project data and expert opinion’, IEEE Trans. Software Eng., 2005, 31, (12), pp 1074–1092 22 Ruhe, G., Eberlein, A., and Pfahl, D.: ‘Quantitative WinWin: a new method for decision support in requirements negotiation’. Proc. 14th Int. Conf. Software Engineering and Knowledge Engineering (SEKE002), Ischia, Italy, July 2002, pp. 159–166