JOURNAL BROWSE
Search
Advanced SearchSearch Tips
Communication-Centered Project Management for Requirements Definition Phase
facebook(new window)  Pirnt(new window) E-mail(new window) Excel Download
 Title & Authors
Communication-Centered Project Management for Requirements Definition Phase
Ishii, Nobuaki; Muraki, Masaaki;
  PDF(new window)
 Abstract
Requirements definition, which determines a project baseline, has a strong impact on the success of a project. However, since in-depth requirements are gradually revealed through the requirements definition process, the requirements definition is not a straight forward process and often falls into disorder. Thus project management standpoints are critical for the success of the requirements definition. In this paper, we present a framework and mechanisms of communication-centered project management, which controls the requirements definition process based on the situation of communication-oriented activities among stakeholders. In addition, we present a communication-centered project plan with a planning method. The project plan, which represents a time schedule of requirements definition activities, is made by a simulation-optimization algorithm using a stakeholder matrix showing the relations of requirements domains and relevant stakeholders. The effectiveness and the significance of communication-centered project management at the requirements definition phase are demonstrated by numerical examples.
 Keywords
Project Management;Stakeholder;Simulation-Optimization;Requirements Definition;
 Language
English
 Cited by
1.
A Study of Global Manufacturing Education and Training for Chinese Company Manager,;;;;

Industrial Engineering and Management Systems, 2014. vol.13. 3, pp.252-257 crossref(new window)
1.
A Study of Global Manufacturing Education and Training for Chinese Company Manager, Industrial Engineering and Management Systems, 2014, 13, 3, 252  crossref(new windwow)
 References
1.
Berenbach, B., Paulishi, D. J., Kazmeier J., and Rudorfer A. (2009), Software and Systems Requirements Engineering: in Practice, McGraw-Hill, NY.

2.
Blanchard, B. S. (2004), Logistics Engineering and Management, Sixth Edition, Pearson Prentice Hall, Upper Saddle River, NJ.

3.
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.

4.
Boesel, J., Nelson, B. L., and Ishii, N. (2003), A framework for simulation-optimization software, IIE Transactions, 35(3), 221-229. crossref(new window)

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. crossref(new window)

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. crossref(new window)

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. crossref(new window)

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. crossref(new window)

12.
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.

13.
Project Management Institute (2008), A Guide to the Project Management Body of Knowledge, Fourth Edition, Project Management Institute, Newton Square, PA.

14.
Robertson, S. and Robertson J. (2005), Requirements-Led Project Management, Addison-Wesley, MA.

15.
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.

16.
Sommerville, I. and Sawyer, P. (2006), Requirements Engineering, John Wiley and Sons, UK.

17.
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.

18.
Wiegers, K. E. (2006), More about Software Requirements: Thorny Issues and Practical Advice, Microsoft Press, Redmond, WA.

19.
Woolridge, R. W., McManus, D. J., and Hale, J. E. (2007), Stakeholder risk assessment: an outcome-based approach, IEEE Software, 24(2), 36-45. crossref(new window)