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 December 2024
Reseach Article

Ground Axioms to Achieve Movables: Methodology

by Sahil Aggarwal, Saru Dhir
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 69 - Number 14
Year of Publication: 2013
Authors: Sahil Aggarwal, Saru Dhir
10.5120/11908-8006

Sahil Aggarwal, Saru Dhir . Ground Axioms to Achieve Movables: Methodology. International Journal of Computer Applications. 69, 14 ( May 2013), 8-11. DOI=10.5120/11908-8006

@article{ 10.5120/11908-8006,
author = { Sahil Aggarwal, Saru Dhir },
title = { Ground Axioms to Achieve Movables: Methodology },
journal = { International Journal of Computer Applications },
issue_date = { May 2013 },
volume = { 69 },
number = { 14 },
month = { May },
year = { 2013 },
issn = { 0975-8887 },
pages = { 8-11 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume69/number14/11908-8006/ },
doi = { 10.5120/11908-8006 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T21:30:13.875237+05:30
%A Sahil Aggarwal
%A Saru Dhir
%T Ground Axioms to Achieve Movables: Methodology
%J International Journal of Computer Applications
%@ 0975-8887
%V 69
%N 14
%P 8-11
%D 2013
%I Foundation of Computer Science (FCS), NY, USA
Abstract

To develop any software there is a need to go through particular phases which software should follow during its lifetime that is known as software development life cycle (SDLC). In SDLC both organizational standards and customer needs are fulfilled. Organization standards help in making quality of software and to meet market deadlines. The demand of current time is that the development system should be efficient enough to deliver, when the customers need and it should welcome changing in requirements at any phase of development. This paper reviews the classical methodology and agile methodology of developing software and also explains that how the working of agile methodology is different from the classical methodology and it is the need of the day. This paper also suggests the conditions that are needed in both the methodologies and improvements of agile methodology so that this methodology of development can be implemented in the organization effectively.

References
  1. Jack Milunsky, How Agile methods resolve chaos and unpredictability, January 2009.
  2. B. Boehm, Get Ready for Agile Methods, with Care, IEEE Computer, vol. 35, no. 1, pp. 64-69, 2002.
  3. IBM, Rational Unified Process: Best practice for software development teams, http://www. ibm. com/developerworks/rational/library/253. html, 2003 .
  4. Agile Manifesto, Manifesto for Agile Software Development, http://agilemanifesto. org, December 2007
  5. M. Vouk and A. T. Rivers, Construction of Reliable Software in Resource-Constrained Environments, W. R. Blischke and D. N. P Murthy, Eds. Hoboken, NJ; Wiley-Intersience, JohnWiley and sons, pp 205-231, 2003.
  6. Dyba, Tore, Empirical studies of agile software development: A systematic review, 24 January 2008.
  7. Vijayasarathy, Leo R, Agile Software Development: A survey of early adopters, Journal of Information Technology.
  8. Mark C. Paulk, Agile Methodologies and Process Discipline, Carnegie Mellon University.
  9. Rico, David F, What is The ROI of Agile vs. Traditional Methods, 2008.
  10. Scott W. Ambler, The Agile Data Method, http://agiledata. org.
  11. Weam M. Farid, Frank J. Mitropoulos, NORMATIC: A Visual Tool for Modeling Non-Functional Requirements in Agile Process, 2012.
  12. Carayannis, Agile Project Management for IT project, Greenwood Press, Quorum Books,2002.
Index Terms

Computer Science
Information Sciences

Keywords

Agile Methodologies Classical Methodologies Return On Investment (ROI) Software Development Life Cycle (SDLC) Validation Verification