1 |
Sommerville, I. and Sawyer, P. (2006), Requirements Engineering, John Wiley and Sons, UK.
|
2 |
van Lamsweerde, A. (2001), Goal-oriented requirements engineering: a guide tour, Proceedings RE'01, 5th IEEE International Symposium on Requirements Engineering, Toronto, Canada, 249-263.
|
3 |
Wiegers, K. E. (2006), More about Software Requirements: Thorny Issues and Practical Advice, Microsoft Press, Redmond, WA.
|
4 |
Woolridge, R. W., McManus, D. J., and Hale, J. E. (2007), Stakeholder risk assessment: an outcome-based approach, IEEE Software, 24(2), 36-45.
DOI
|
5 |
Browne, G. J. and Rogich, M. B. (2001), An empirical investigation of user requirements elicitation: comparing the effectiveness of prompting techniques, Journal of Management Information Systems, 17(4), 223-249.
DOI
|
6 |
Grunbacher, P. and Seyff, N. (2005), Requirements negotiation, In Aurum, A. and Wohlin, C. (ed), Engineering and Managing Software Requirements (Berlin, Springer), 7, 143-162.
|
7 |
Hickey, A. M. and Davis A. M. (2004), A unified model of requirements elicitation, Journal of Management Information Systems, 20(4), 65-84.
DOI
|
8 |
Ishii, N. (2006), A project management framework at the system requirements definition phase, Proceedings of 3rd International Conference on Project Management, Sydney, Australia.
|
9 |
Morton, T. E. and Pentico, D. W. (1993), Heuristic Scheduling Systems, John Wiley & Sons, NY.
|
10 |
Nguyen, L. and Swatman, P. A. (2003), Managing the requirements engineering process, Requirements Engineering, 8, 55-68.
DOI
ScienceOn
|
11 |
Ocker, R., Fjermestad, J., Hiltz, S. R., and Johnson, K. (1998), Effects of four modes of group communication on the outcomes of software requirements determination, Journal of Management Information Systems, 15(1), 99-118.
DOI
|
12 |
Sharp, H., Finkelstein, A., and Galal, G. (1999), Stakeholder identification in the requirements engineering process, Proceedings of Tenth International Workshop on Database and Expert Systems Applications, Florence, Italy, 387-391.
|
13 |
Pacheco, C. and Tovar, E. (2007), Stakeholder identification as an issue in the improvement of software requirements quality, Proceedings of 19th International Conference, CAiSE, Trondheim, Norway.
|
14 |
Project Management Institute (2008), A Guide to the Project Management Body of Knowledge, Fourth Edition, Project Management Institute, Newton Square, PA.
|
15 |
Robertson, S. and Robertson J. (2005), Requirements-Led Project Management, Addison-Wesley, MA.
|
16 |
Boesel, J., Nelson, B. L., and Ishii, N. (2003), A framework for simulation-optimization software, IIE Transactions, 35(3), 221-229.
DOI
ScienceOn
|
17 |
Berenbach, B., Paulishi, D. J., Kazmeier J., and Rudorfer A. (2009), Software and Systems Requirements Engineering: in Practice, McGraw-Hill, NY.
|
18 |
Blanchard, B. S. (2004), Logistics Engineering and Management, Sixth Edition, Pearson Prentice Hall, Upper Saddle River, NJ.
|
19 |
Boehm, B., Bose, P., Horowitz, E., and Lee, M.-J. (1994), Software requirements as negotiated win conditions, Requirements Engineering, Proceedings of the First International Conference, Colorado Springs, CO, 74-83.
|