Impact of Collaborative ALM on Software Project Management

Full Text (PDF, 296KB), PP.61-67

Views: 0 Downloads: 0

Author(s)

Tahmoor Shoukat 1,* Muhammad Nadeem Majeed 1

1. University of Engineering and Technology, Taxila, Pakistan

* Corresponding author.

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

Received: 20 Sep. 2013 / Revised: 2 Feb. 2014 / Accepted: 15 Mar. 2014 / Published: 8 May 2014

Index Terms

Application Lifecycle Management (ALM), Service-oriented architectures (SOAs), Software Development Life Cycle (SDLC), Configuration Management (CM)

Abstract

To produce a release of software, ALM is a key for streaming the team’s ability. ALM consists of the core disciplines of requirements definition and its management, asset management, development, build creation, testing, and release that are all planned by project management and orchestrated by using some form of process [1]. The assets and their relationships are stored by the development team repository. Detailed reports and charts provide visibility into team’s progress. In this paper we will describe how the ALM involves software development activities and assets coordination for the production and management of software applications throughout their entire life cycle.

Cite This Paper

Tahmoor Shoukat, Muhammad Nadeem Majeed, "Impact of Collaborative ALM on Software Project Management", International Journal of Information Technology and Computer Science(IJITCS), vol.6, no.6, pp.61-67, 2014. DOI:10.5815/ijitcs.2014.06.09

Reference

[1]Göthe, M., Pampino, C., Monson, P., Nizami, K., Patel, K., Smith, B. and Yuce, N. (2008) Collaborative Application Lifecycle Management with IBM Rational Products, An IBM Redbooks publication, December 2008. 

[2]Schwaber, C. (2006) The Changing Face of Application Life-Cycle Management, Forrester Research Inc., White Paper, 18 August.

[3]Jalali, S. and Wohlin, C. (2010) Agile practices in global software engineering – a systematic map, International Conference on Global Software Engineering, ICGSE 2010, Princeton, NJ, USA, August 23–26, 2010, pp. 45–54.

[4]Goth, G. (2009) Agile Tool Market Growing with the Philosophy, IEEE Software, Vol. 26, No. 2, pp. 88–91. 

[5]Battin, R.D., Crocker, R., Kreidler, J. and Subramanian, K. (2001) Leveraging resources in global software development, IEEE Software, Vol. 18, Issue 2, March-April 2001, pp. 70–77

[6]Driving Your Business Forward with Application Life-cycle Management (ALM), Microsoft, White Paper, August 2007.

[7]“Eleven steps to kickoff application lifecycle management” by John Scarpino, D. Sc.

[8]Doyle, C. and Lloyd, R. (2007) Application lifecycle management in embedded systems engineering, Embedded System Engineering (ESE magazine), Vol. 15, No. 2, March, pp. 24–25.

[9]Carolyn Pampino (2011) Five imperatives for effective Application Lifecycle Management, IBM December 2011.

[10]Ebert, C. and De Neve, P. (2001) Surviving global software development. IEEE Software, Vol. 18, Iss. 2, March–April 2001, pp. 62–69. 

[11]Booch, G. and Brown, A. (2003) Collaborative development environments, Advances in Computers, Vol. 59, Academic Press. 

[12]Nari Kannan (2012) Designing and implementing ALM quality dashboards. ALM and Agile Strategies - July 2012, Vol. 1 Iss. 3

[13]Dearle, A. (2007) Software deployment, past, present and future, Future of Software Engineering (FOSE ‘07), 23–25 May, Minneapolis, MN, USA, pp. 269–284. 

[14]Murta, L., Werner, C. and Estublier, J. (2010) The Configuration Management Role in Collaborative Software Engineering, In: Mistrík et al., Collaborative Software Engineering, Springer-Verlag, Berlin, Heidelberg, pp. 179–194.