Abstract
Empirical analysis evaluates the proposed system via practical experience and reveals its pros and cons. Such type of evaluation is one of the widely used validation approach in software engineering. Conventional software process models were performed well till mid 1990s but then gradually were replaced by agile methodologies. This happened due to the various features, the agile family offered, which the conventional models failed to provide. However besides the advantages, agile models lacked at some areas as well. To get the extreme benefits from any agile model, it is necessary to eliminate the weaknesses of that model by customizing its development structure. Feature Driven Development (FDD) is one of the widely used agile models in software industry particularly for large scale projects. This model has been criticized by many researchers due to its weaknesses such as explicit dependency on experienced staff, little or no guidance for requirement gathering, rigid nature to accommodate requirement changes and heavy development structure. All these weaknesses make the FDD model suitable only for large scale projects where the requirements are less likely to change. This paper deals with the empirical evaluation of FDD during the development of a small scale web project so that the areas and practices of this model can be identified with empirical proof, which make this model suitable only for large projects. For effective evaluation, the results of FDD case study are compared with a published case study of Extreme Programing (XP), which is widely used for small scale projects.
Highlights
Today the agile methodologies have taken over the conventional models in software industry [13,14,15]
Feature Driven Development (FDD) is one of the widely used agile models in software industry for large scale projects. This model is criticized by many researchers due to its weakness such as: dependency on experienced staff due to its complex structure, rigid nature to accept requirement changes at later stages, little or no guidance for requirement extraction, and heavy development structure
This paper evaluated the FDD process model on a small scale project through an empirical case study
Summary
Today the agile methodologies have taken over the conventional models in software industry [13,14,15]. All the models work under one umbrella and follows the practices, values, and principles suggested by “Agile Manifesto” [24,25,26] This manifesto is considered as a parent document of all the agile process models and consists of twelve basic rules of software development [14,15]. It is claimed that its explicit dependency on experienced staff and rigid nature to handle changing requirements make it only suitable for medium to large scale projects [13], [15], [19] Due to these limitations, many researchers have proposed its customizations and integrations with other software models. The empirical results presented in this research can be used as a baseline for further empirical comparisons
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
