We apologize for a recent technical issue with our email system, which temporarily affected account activations. Accounts have now been activated. Authors may proceed with paper submissions. PhDFocusTM
CFP last date
20 November 2024
Call for Paper
December Edition
IJCA solicits high quality original research papers for the upcoming December edition of the journal. The last date of research paper submission is 20 November 2024

Submit your paper
Know more
Reseach Article

Existing Software Stakeholder Practices an Overview

by Smiju Sudevan, M. Bhasi, K. V. Pramod
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 102 - Number 3
Year of Publication: 2014
Authors: Smiju Sudevan, M. Bhasi, K. V. Pramod
10.5120/17793-8593

Smiju Sudevan, M. Bhasi, K. V. Pramod . Existing Software Stakeholder Practices an Overview. International Journal of Computer Applications. 102, 3 ( September 2014), 7-12. DOI=10.5120/17793-8593

@article{ 10.5120/17793-8593,
author = { Smiju Sudevan, M. Bhasi, K. V. Pramod },
title = { Existing Software Stakeholder Practices an Overview },
journal = { International Journal of Computer Applications },
issue_date = { September 2014 },
volume = { 102 },
number = { 3 },
month = { September },
year = { 2014 },
issn = { 0975-8887 },
pages = { 7-12 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume102/number3/17793-8593/ },
doi = { 10.5120/17793-8593 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T22:32:08.135915+05:30
%A Smiju Sudevan
%A M. Bhasi
%A K. V. Pramod
%T Existing Software Stakeholder Practices an Overview
%J International Journal of Computer Applications
%@ 0975-8887
%V 102
%N 3
%P 7-12
%D 2014
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Software technology is an everchanging and dynamic science. As in other spheres, here too, despite the vast extent of interactive and participatory software practice and theory, there is still little shared understanding amongst those involved. The success of a software project is directly affected by the lack of understanding and estimating stakeholder's needs and expectations along with lack of effective communication amongst the software stakeholders. The following paper aims to understand the existing software stakeholder management techniques in IT industry. This will further help in dealing with unforeseen circumstances and potential risks.

References
  1. Hitt, M. , Freeman, R. & Harrison, J. (2001). The Blackwell Handbook of Strategic Management. Hoboken, NJ: Wiley- Blackwell Publishers Ltd.
  2. Freeman, R. E. (1984). Strategic Management: A Stakeholder Approach. Boston: Pitman
  3. Cooper, SC (2004). Corporate Social Performance: A Stakeholder Approach. England: Ashgate Publishing Limited.
  4. Dowling, GR. (1994). Corporate Reputations- Strategies for Developing the Corporate Brand. Melbourne: Longman Professional.
  5. King, A. (1998). The social performance uncertainty principle. Corporate Reputation Review, v 1, no 3, pp 43-46. Henry Stewart Publications.
  6. Waddock, S. & McIntosh, M. (2009). Beyond corporate responsibility: implications for management development. Business and Society Review, Fall, v 114, no 3, 295.
  7. Post, J. , Preston, L. , & Saschs, S. (2002). Redefining the Corporation. Stakeholder Management and Organizational Wealth. Stanford Business Books. California: Stanford University Press.
  8. Ronald K. Mitchell, Bradley R. Agile, Donna J. Wood, (1997). Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts, The Academy of Management Review,pp. 853-886
  9. Ken Power, (2010). Stakeholder Identification in Agile Software Product Development Organizations - A model for understanding who and what really counts, IEEE Publication, pp 87-94, AGILE Conference
  10. Bendik Bygstad,(2004) Controlling Iterative Software Development Projects: The Challenge of Stakeholder and Technical Integration – System Sciences,Proceedings of the 37th Annual Hawaii International Conference,2004
  11. Svendsen, A. (1998) The Stakeholder Strategy. Profiting from Collaborative Business Relationships. San Francisco: Berrett-Koehlert Publishers Inc
  12. Simmons, J. (2003). Balancing performance, accountability and equity in stakeholder relationships: towards more socially responsible HR practice. Corporate Social Responsibility and Environmental Management 10, 129-140
  13. Grunig, J. (1992). Excellence in Public Relations and Communication Management. New Jersey: Lawrence Erlbaum Associates
  14. R. L. Glass, (2002) "Failure Is Looking More Like Success These Days," IEEE Software, vol. 19, no. 1, 2002, pp. 103–104. [15 ]Naemura, Kenji (1995) User Involvement in the life cycles of Information Technology (IT) and telecommunication standards. The Politics and Economics of Standards in natural and technical environments. Edward Elgar, Adershot, UK/Brookfield, US, pp. 93-102.
  15. Lim. S. L,Bentley. P. J,2011. Evolving relationships between social networks and stakeholder involvement in software projects. In: Proceedings of the 13th Annual conference on Genetic and Evolutionary computation, Doublin, Ireland, pp. 1899-1906.
  16. Lewis, CW. 1991, Understanding who and what matters: Stakeholder analysis, Jossey-Bass, CA, USA
  17. Lim. S. L,Quercia,Finkelstein. A,2010 StakeNet:using social networks to analyze the stakeholders of large-scale software projects, In:proceedings of ACM/IEEE 32nd International Conference on Software Engineering, Cape Town, South Africa,vol. 1. pp,295-304
  18. R. K. Mitchell, B. R. Agile and D. J. Wood, "Toward a Theory of Stakeholder Identification and Salience: Defining the principle of who and what really counts," Academy of management review, vol. 22, no. 4, pp. 853-886, October 1997.
  19. K. Power," Software Development: A Stakeholder Approach (PhD Thesis),"J. E. Cairnes School of Business & Economics, National University of Ireland, Galway, In Progress.
  20. K. Power,"DynamicStakeholder relationships in Software development Organizations," In progress, 2010.
  21. Coughlan J, Lycett M, Macredie RD (2003) Communication issues in requirements elicitation: a content analysis of stakeholder experiences,Inf Softw Technol 45(8):525-537
  22. Coughlin J, Lycett M, Macredie RD (2002) Effective Communication in requirements elicitation:comparison methodologies. requirEng J 7(2):47-60, doi: 10. 1007/s00766020004
  23. Khalifa G,Irani Z,Baldwin LP,Jones S(2000) Evaluating Information technology with you in mind . Electron J Inf Syst Eval 4(1):Paper 5
  24. Pacheco C, Tovar E(2007) Stakeholder Identification as an issue in the improvement of Software Requirements Quality. krogstie J,Opdahl AL,Sindre G(eds) CAiSE 2007,LNCS 4495,pp 370-380
  25. Pan GSC (2005) Information Systems project abandonment: a stakeholder analysis. Int J Inf Manag 25(2):173-184, doi:10. 1016/j. ijinfomgt. 2004. 12. 003
  26. Sharp H. Finkelstein A, Galal G(1999) Stakeholder Identification in the requirements engineering process . DEXA workshop 1999:3876-391
Index Terms

Computer Science
Information Sciences

Keywords

Stakeholder Software management Stakeholder management Stakeholder Identification Stakeholder analysis