Empowering Agile Method Feature-Driven Development by Extending It in RUP Shell

  • Rinky DwivediEmail author
  • Vinita Rohilla
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 553)


The System Engineering Methods (SEM) can consider as standardization for the development of information systems often demands a methodical approach to knowing which steps have to be taken in which order and at which time in the development process. These methods usually designed for delimited parts of software development life cycle, leaving other phases of SDLC in an ad hoc environment. This results in a need to extend SEMethods and empowered them with the potential to support other phases of software development as well. The paper addresses this issue and shows how popular agile method Feature-Driven Development (FDD) can be extended to satisfy case organizational requirements.


Software engineering Agile methods Feature-driven development 


  1. 1.
    Karlsson F. “Meta Method for method configuration- A Rational Unified Process Case”, ISBN 91-7373-474-8, Faculty of art and science, Sweden, 2002.Google Scholar
  2. 2.
    Dwivedi, R. and Gupta, D. ‘A framework to support project-in-hand and selection of software development method’, Journal of Theoretical and Applied Information Technology, Vol. 73, No. 1, pp. 137–148, 2015.Google Scholar
  3. 3.
    Harmsen A.F., Situational Method Engineering. Moret Ernst & Young, 1997.Google Scholar
  4. 4.
    Bajec M., “Practice driven approach for creating project-specific software development methods”, Information and Software technology, Vol. 49, 345–365, 2007.Google Scholar
  5. 5.
    Karlsson, F. and Ågerfalk, P.J. ‘Exploring agile values in method configuration’, European Journal of Information Systems, Vol. 18, No. 4, pp. 300–316, 2009.Google Scholar
  6. 6.
    Dwivedi, R. and Gupta, D. ‘Applying machine learning for configuring agile methods’, International Journal of Software Engineering and its applications, Vol. 9(3), pp. 29–40, (2015).Google Scholar
  7. 7.
    Dwivedi, R. and Gupta, D. ‘the agile method engineering: Applying fuzzy logic for evaluating and configuring agile methods in practice’, Int. J. Computer Aided Engineering and Technology, (In Production).Google Scholar
  8. 8.
    Beck, K. ‘Embracing change with extreme programming’, IEEE Computer Society Press, Vol. 32, No. 10, pp. 70–77, (1999).Google Scholar
  9. 9.
    Dwivedi, R. ‘Configuring issues and effort for configuring agile approaches-situational based method engineering’, International Journal of Computer Application, January, Vol. 16, No. 17, pp 23–27, 2013.Google Scholar
  10. 10.
    Schwaber, K. and Beedle, M. Agile Software Development with Scrum, Nouvelle editions, (2002).Google Scholar
  11. 11.
    Abrahamsson, P. et al. ‘Agile Software Development Methods Review and Analysis’, VIT Publications, Juhani Warsta, University of Oulu, (2002).Google Scholar
  12. 12.
    Agile Manifesto Manifesto for Agile Software Development, [online] (2001).
  13. 13.
    Jim Highsmith, “Agile software development ecosystems”, publisher Addisson-wesley, Pub-date May 26, 2002, ISBN 0-201-76043-6.Google Scholar
  14. 14.
    Karlstrom, D., Runeson, P.,. Combining agile methods with StarGate project management. IEEE Software 22 (3), 43–49, 2005.Google Scholar
  15. 15.
    Salo, O., Abrahamsson, P., 2008. Agile methods in European embedded development organizations: a survey study of extreme programming and scrum. IET Software Vol. 2 (1), 58–64.Google Scholar
  16. 16.
    Misra S. C. et al. “Identifying some important success factors in adopting agile software development practices”, Journal of system and software, Vol. 82, pp 1869–1890, 2009.Google Scholar
  17. 17.
    Jokela, T. & Abrahamsson, P. (2004) “Usability assessment of an Extreme Programming Project: Close Co-Operation with the Customer Does Not Equal to Good Usability”. In PROFES 2004, Keihanna-Plaza, Kansai Science City, Japan.Google Scholar
  18. 18.
    Jordan et. al. “Overview and guidance on agile development in large organisation”, Communications of the association for information systems, Vol. 29, Article 2, 2011.Google Scholar
  19. 19.
    Qureshi M. R. J. “Agile Software development methodology for medium and large projects”, IET software, Vol 6 (4), pp. 358–363.Google Scholar
  20. 20.
    Hanssen G. K., Faegi T.E., “Process fusion: An industrial case study on agile software product line engineering”, Journal of systems and software, Vol. 81, pp. 843–854, 2008.Google Scholar
  21. 21.
    Dwivedi, R. and Gupta, D. ‘Customizing agile methods using genetic algorithm’, Proceedings of International Conference on Advances in Communication, Network and Computing, Elsevier, 2014.Google Scholar
  22. 22.
    Fitzgerald, B., Hartnett, G. and Conboy, K. ‘Customizing agile methods to software practices at Intel Shannon’, European Journal of Information Systems, Vol. 15, No. 2, pp. 197–210, 2006.Google Scholar
  23. 23.
    Hunt, J. ‘Feature driven development’, Agile Software Construction, pp. 161–182, Springer, ISBN: 978-1-85233-944-9 (Print) 978-1-84628-262-1 (Online), 2006.Google Scholar
  24. 24.
    Palmer, S.R. and Felsing, J.M. (2002) ‘A Practical Guide to Feature-Driven-Development’, Prentice-Hall, Upper Saddle River, NJ, (2008).Google Scholar
  25. 25.
    Highsmith, J. A. “Adaptive software development: A collaborative approach to managing complex systems New York, NY, Dorset house publishing.Google Scholar
  26. 26.
    Prakash N. and Goyal S.B., ‘Towards a Life Cycle for Method Engineering’, Proceedings Eleventh International Workshop on Exploring Modelling Methods in Systems Analysis and Design (EMMSAD’07), 27–36, (2007).Google Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2017

Authors and Affiliations

  1. 1.Computer Science Engineering DepartmentMaharaja Surajmal Institute of TechnologyNew DelhiIndia

Personalised recommendations