Abstract
Empirical evaluation is one of the widely accepted validation method in the domain of software engineering which investigates the proposed technique via practical experience and reflects its benefits and limitations. Due to various advantages, agile models have been taking over the conventional software development methodologies since last two decades. However besides the benefits, various limitations have been noticed as well by the researchers and software industry in agile family. To achieve the maximum benefits it is vital to fix the limitations by customizing the development structure of agile models. This paper deals with the empirical analysis of modified agile models called Simplified Extreme Programing (SXP) and Simplified Feature Driven Development (SFDD), which are the modified forms of Extreme Programing (XP) and Feature Driven Development (FDD). SXP was presented to eliminate the issues of conventional XP such as, lack of documentation, poor architectural structure and less focus on design. SFDD was proposed to take care of reported issues in FDD such as explicit dependency on experienced staff, little or no guidance for requirement gathering, rigid nature to accommodate requirement changes and heavy development structure. This study evaluates SXP and SFDD through implementing client oriented projects and discusses the results with empirical analysis.
Highlights
Conventional software process models are replaced by lightweight agile development methodologies
Even though the working environment as well as the size and nature of both the applications were same, but Simplified Feature Driven Development (SFDD) performed much better than Simplified Extreme Programing (SXP)
SFDD has taken care of the issues reported in Feature Driven Development (FDD), such as explicit dependency on experienced staff, no guidance for requirement gathering, rigid nature to accommodate requirement changes and heavy development structure
Summary
Conventional software process models are replaced by lightweight agile development methodologies. Benefits provided by FDD model includes the iterative and incremental approach along with ETVX pattern which ensures the development of high quality software according to client valued features. Some limitations of FDD were reported such as: little or no guidance for requirement gathering, explicit dependency on experience staff, rigid nature to handle changing requirements and heavy development structure including various activities and team roles. All these issues make it only suitable for medium or large scale projects. This study empirically valuates the proposed models through empirical case studies conducted in software industry
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
