Towards a framework for understanding the relationships between classical software engineering and agile methodologies

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2008, Pages 9-14

  Jiang, Li ^a   Eberlein, Armin ^b  

^a UNIVERSITY OF ADELAIDE   (Australia)

^b AMERICAN UNIVERSITY OF SHARJAH   (United Arab Emirates)

Author keywords

Agile methodology; Philosophy; Software engineering; Software engineering methodology; Software process; Waterfall model

Indexed keywords

AGILE METHODOLOGIES; PHILOSOPHY; SOFTWARE ENGINEERING METHODOLOGY; SOFTWARE PROCESS; WATERFALL MODEL;

ENGINEERING; FENCES; KNOWLEDGE BASED SYSTEMS; ONTOLOGY; PHILOSOPHICAL ASPECTS; SOFTWARE ENGINEERING;

TECHNICAL PRESENTATIONS;

EID: 78650474642     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1370143.1370146     Document Type: Conference Paper

References (31)

1. Rakitin S. 2001. "Manifesto Elicits Cynicism, " Computer, Dec. 2001, p. 4.
2. Harrison, W. 2003. Is Software Engineering As We Know It Over the Hill?, IEEE Software, Vol. 20, Issue: 3. pp: 5- 7, .
3. Nerur S. and Balijepally V.G. 2007. "Theoretical Reflections on Agile Development Methodologies, " Communications of the ACM, Vol. 50, 2007, pp: 79-83.
4. Beck K., et. al. 2001. Manifesto for Agile Software Development, http://agilemanifesto.org/principles.html, 2001 (As shown in the webpage).
5. Glass, R.L. 2001. Agile Versus Traditional: Make Love Not War. Cutter IT Journal, Vol. 14, No. 12, 2001, pp: 12-18.
6. Austin, R.; Devin, L. 2003. Beyond Requirements: Software Making As Art, IEEE Software, Vol. 20, Issue 1, pp:93 - 95.
7. Turner R. & Jain A. 2002. Agile Meets CMMI: Culture Clash or Common Cause? In Wells D. and Williams L. (Eds.): LNCS, XP/Agile Universe 2002, pp. 153-165.
8. Fritzsche M., Keil P. 2007. Agile Methods and CMMI: Compatibility or Conflict? e-Informatica Software Engineering Journal, Vol. 1, Issue 1, 2007.
9. Paetsch F., Eberlein A. and Maurer F. 2003. Requirements Engineering and Agile Software Development, Proceedings of the IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WETICE-2003), Linz, Austria, 2003, pp. 308 -313.
10. Eberlein A. 2003. Requirements Engineering and Agile Methods: Can they benefit from each other? Position Statement in the Proceedings of the Canadian Invited Workshop on Scaling XP/Agile Methods, Banff, Canada.
11. Boehm, B.W. 2002. Get Ready for Agile Methods, with Care. IEEE Computer, 2002.
12. Boehm B. W., Turner R, 2003. Balancing Agility and Discipline. Addison-Wesley.
13. Bound D. et al. 2007. Delivering IT Solutions in the Real World! Fujitsu Inc. Australia. http://www.cs.adelaide.edu.au/~ljiang/Courses-Information.html (click SE In Industry and then click Resources, then select Fujitsu).
14. Owen C. et. al. 2007. IT Solution Delivery, Adelaide Bank, http://www.cs.adelaide.edu.au/~ljiang/Courses-Information.html(click SE In Industry and then click Resources, then select Adelaide Bank ), .
15. Cumpston B. et. al. 2007. Ebor Computing, Ebor Computing Inc.http://www.cs.adelaide.edu.au/~ljiang/Courses-Information.html, 2007 (click SE In Industry and then click Resources, then select Ebor Computing).
16. Paulk M. C. et al. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, Mass., 1995.
17. Floyd C. 1986. A Comparative Evaluation of System Development Methods, In Olle, T.W., Sol, H.S., and Verrijn- Stuart, A.A., (ed) (North-Holland, Amsterdam), 1986, pp:19- 54.
18. Jiang L, 2005. A framework for requirements engineering process development. University of Calgary, PhD Thesis, Sept. 2005.
19. Cockburn A. 2002, Agile Software Development, Addison-Wesley, 2002.
20. Jiang, L. 2006. Exploring Philosophical Origin and Foundation of the Fundamental Practices In Classical Software Engineering Methods and Agile Method with Qualitative Evidence (POSEA), http://www.cs.adelaide.edu.au/~ljiang/ ResearchHomePage.html.
21. Reifer, D.J., 2003. XP and the CMM, IEEE Software, Vol. 20, Issue 3, May-June 2003, pp: 14 - 15.
22. Paulk, M. C. 2001. Extreme Programming from a CMM Perspective. IEEE Software, 2001.
23. McConnell, S. 2002. IEEE Software, Vol: 19, Issue: 1, pp: 3- 5 Jan/Feb. 2002.
24. Software Program Managers Network (SPMN). 1999. 16 Critical Software Practices™ for Performance-based Management. http://www.spmn.com/critical- software-practices.html, 1999.
25. Dahlbom B. Mathiassen L. 1992. Systems Development Philosophy, ACM SIGCAS, Computers and Society, Vol. 22, Issue 1-4, Oct. 1992, pp: 12 - 23.
26. Carl M. 1998. The Importance of Philosophy to Engineering, Teorema XVII (3), 1998, pp. 27-47.
27. Royce W. W. 1970. Managing the Development of large Software Systems: Concepts and Techniques, Proceeding of the IEEE WESTCON, Los Angeles, California, 1970.
28. Boehm B. W. 1988. A Spiral Model of Software Development and Enhancement. IEEE Computer 21(5): 1988, pp: 61-72.
29. Beck K. and Andres C. 2005. Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston, 2005.
30. Schwaber K., Beedle M. 2001. Agile Software Development with SCRUM, Prentice Hall; 1st edition, 2001.
31. Basili V. R. 1996. The Role of Experimentation In Software Engineering: Past, Current, and Future, Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996, pp: 442 - 449.