Yumnam Subadani Devi; Laishram Prabhakar

Management of Possible Roles for Distributed Software Projects Using Layer Architecture

Full Text (PDF, 374KB), PP.57-65

Views: 0 Downloads: 0

Author(s)

Yumnam Subadani Devi ^1,* Laishram Prabhakar ¹

1. Manipur Institute of Management Studies, Manipur University, Canchipur, Imphal 795003, Manipur, India

* Corresponding author.

DOI: https://doi.org/10.5815/ijitcs.2015.07.07

Received: 10 Nov. 2014 / Revised: 4 Feb. 2015 / Accepted: 26 Mar. 2015 / Published: 8 Jun. 2015

Index Terms

Layer Architecture, Responsibility Index, Team Management, Customer Service, Distributed Projects

Abstract

Several members are involved in development and management of the Distributed Software Projects. Each member needs to know the responsibilities of each other for proper management of the activities of such distributed projects to produce coherent outcomes. Distribution middleware software has higher-level distributed programming models whose reusable APIs (application programming interface) and components automate and extend native operating system capabilities. Software management tools like Work break-down structure (WBS), Gantt chart, Critical Path Method, and Critical Chain Method etc. does not fully help the managers to manage the member's responsibilities during the development of distributed applications. The layered architecture can help to do so. This style not only gives the layer level description of the activity involved, it also defines and directs the group of workforce. By listing the groups of workforce, the development team as well as the customer can know the activity and the member involved to work on those specific activities. This layered architecture is much benefited to development team and also to numbers of stakeholder of the large distributed project. The extended new approach of layer pattern with 'Responsibility Index' adds extra value to manage all the members' responsibilities. Managers, stakeholders and others can have an easy management system. The request or complaint from the customer can be passed to appropriate team without much delay. Most importantly this will give facility to collect timely feedback from all levels of customers.

Cite This Paper

Yumnam Subadani Devi, Laishram Prabhakar, "Management of Possible Roles for Distributed Software Projects Using Layer Architecture", International Journal of Information Technology and Computer Science(IJITCS), vol.7, no.7, pp.57-65, 2015. DOI:10.5815/ijitcs.2015.07.07

Reference

[1]JD Herbsleb, D Moitra, D, “Global Software Development,” IEEE Software, 2001, 18(2): 16–20.

[2]RC Martin."Design Principles and Design Patterns." Retrieved 2000.

[3]RS Pressman, WS Jawadeka. "Software engineering." New York 1992.

[4]M Shaw, D Garlan, "Software architecture: perspectives on an emerging discipline" PH, 1996.

[5]P Morris, JK Pinto (Eds.) "The Wiley Guide to Project Program and Portfolio Management", 336 pp. The Wiley Guides to the Management of Projects.Wiley, Hoboken NJ , 2008.

[6]G.Kapogiannis, "a conceptual framework for project managers to improve projects performance", Ph.D. Thesis, University of Salford, Salford, UK,2013

[7]B. Meyer, "The unspoken revolution in software engineering," IEEE Computer,2006, 39(1): 121-123.

[8]AY Lewin, S Massini, C Peeters "Why are companies offshoring innovation?The emerging global race for talent," J. of Int. Business Studies, 2008.

[9]J.Espinosa,DeLone, W., and Lee, G. "Global boundaries, task processes and IS project success: a field study," Information Technology and People, 2006: 345-370

[10]Y.Subadani Devi, Y. Jayanta Singh, Laishram Prabhakar. "Grooming a New Team with Potential Roles using the Scrum Practices."Proc. Int. Multi Conf. of Engineers & Computer Scientists. Hong Kong, 2012.

[11]ANH Zaied. "An integrated knowledge management capabilities framework for assessing organizational performance."Int. Journal of Information Technology and Computer Science(IJITCS)4.2(2012): 1.

[12]Standish. The Chaos Report. www.standishgroup.com /sample research/PDFpages/-chaos1994.pdf,1994.

[13]W.C.Peterson "SEI’s software process program-presentation to the board of visitors", Software Engineering Institute, Carnegie Mellon University.1997

[14]Y. Subadani Devi and L. Prabhakar. "A Preventive Risk Analysis for Managing Distributed Software Projects based on Deliverable." International Journal of Computer Applications 68.1 (2013): 27-31.

[15]DG Malcolm, JH Roseboom, CE Clark, "Application of a Technique for Research and Development Program Evaluation OPERATIONS RESEARCH",7(5): 646–669

[16]M. Shaw and D. Garlan. "Software Architecture: Perspectives on an Emerging Discipline", Upper Saddle River, N.J., Prentice Hall, 1996.

[17]Z Mushtaq, MRJ Qureshi. "Novel Hybrid Model: Integrating Scrum and XP." International Journal of Information Technology and Computer Science (IJITCS) 4.6 (2012): 39.

[18]E Praynlin, P Latha. "Performance analysis of software effort estimation models using neural networks." Int. Journal of Information Technology and Computer Science (IJITCS) 5.9 (2013): 101.

[19]M. Shaw, P. Clements. "A Field Boxology: Preliminary Classification of Architectural Styles for Software Systems", 1996.

[20]J.Goodbody, "Critical success factors for global virtual teams" Strategic Communication Management, 2005,9(2):18-21.

International Journal of Information Technology and Computer Science (IJITCS)