Comparison between Adaptive Software Development and Feature Driven Development

Chowdhury, Ashraf Ferdouse; Huda, Mohammad Nazmul

doi:10.1109/iccsnt.2011.6181977

Cited by 13 publications

(7 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Each iteration usually lasts one to three weeks. Customers are given work packages to test after they are completed [17]. The FDD lifecycle is shown in Fig.…”

Section: Feature Driven Development (Fdd)mentioning

confidence: 99%

Section: F Adaptive Software Development (Asd)mentioning

confidence: 99%

“…ASD was introduced by James A. Highsmith in 2000 [17]. Instead of the static software development life cycle of plan design build, he proposed a dynamic Speculate collaborate learn software development life cycle [17]. The process begins with the initiation phase of the project, which establishes the development cycle's goals and timelines.…”

Section: F Adaptive Software Development (Asd)mentioning

confidence: 99%

See 2 more Smart Citations

A Review of Agile Methods for Requirement Change Management in Web Engineering

Alsharari

Zainon

Letchmunan

et al. 2023

2023 International Conference on Smart Computing and Application (ICSCA)

View full text Add to dashboard Cite

Web-based systems are essential in many different applications, which makes web-based development different from traditional software development. The agile methodology has gained lots of popularity in the last 15 years and become very traditional and acceptable widely among software engineers; nevertheless, the use of agile methods has extended to cover other areas of software engineering field including Requirement Engineering (RE) that fit the need of web engineering. The pace of the current web's software development is fast and dynamic such that the changes of the requirements during software development and after turning to production phase are possible and recurrent. Therefore, agile software engineering conceptuality has evolved as an adequate approach to overcome changes in the web's software's requirements; due to frequent changes in requirements, web engineers call for help of agile software engineering methods, which strive to truly manage changes in requirements rather than preventing these changes. This paper provides a review on the available agile methodologies that used to assess requirement change management in web engineering.

show abstract

“…Each iteration usually lasts one to three weeks. Customers are given work packages to test after they are completed [17]. The FDD lifecycle is shown in Fig.…”

Section: Feature Driven Development (Fdd)mentioning

confidence: 99%

Section: F Adaptive Software Development (Asd)mentioning

confidence: 99%

Section: F Adaptive Software Development (Asd)mentioning

confidence: 99%

See 1 more Smart Citation

A Review of Agile Methods for Requirement Change Management in Web Engineering

Alsharari

Zainon

Letchmunan

et al. 2023

2023 International Conference on Smart Computing and Application (ICSCA)

View full text Add to dashboard Cite

show abstract

“…This approach significantly speeds up the process of designing software in an unfamiliar domain.  FDD (Features Driven Development) [8] attempts to combine the most recognized software development methodologies in the industry, based on important functionality (properties) of the developed software for the customer. The main goal of this methodology is to systematically develop real, working software within the set deadlines.…”

Section: Fig 2 Approach To End-to-end Testing Of the Considered Appli...mentioning

confidence: 99%

Approach to end-to-end testing of the application for managing the configuration of enterprise virtual infrastructure

Geraskin,

Voinov

2023

Proceedings of ISP RAS

View full text Add to dashboard Cite

The article is devoted to end-to-end testing of the application for managing the configuration of enterprise virtual infrastructure. The main idea is to develop a software framework to create and perform end-to-end tests written in Python. The approach involves a comprehensive evaluation of the system from the user interface to the database. The testing process is performed in a continuous integration environment, which enables the team to test the system continually as new code is added. The testing process also includes the use of automated tests written in Python. The automated tests allow for faster and more reliable testing and enable the team to test the system across multiple platforms and configurations. The approach also includes the use of virtual environments to simulate the production environment. This enables the team to identify potential issues that may arise in the production environment and to test the system's performance under various conditions.

show abstract

“…However, a problem remains in that there are no security elements inside FDD. Additionally, there is no specific security role inside FDD [66][67][68]. Of course there are many security methods that been applied in the real world [69][70][71][72][73][74][75][76][77][78][79][80], especially in Malaysia [80] and India [81].There is also discussion and much awareness among IT organizations regarding software security practices [82] and the human factors that could attribute to software security [83].However, there is no specific research regarding the integration of security and FDD.…”

Section: Q3: How Is the Integration Between Security And Fddmentioning

confidence: 99%

A Systematic Literature Review on Secure Software Development using Feature Driven Development (FDD) Agile Model

Arbain¹,

Ghani²,

Jeong

2014

Journal of Korean Society for Internet Information

View full text Add to dashboard Cite

Agile methodologies have gained recognition as efficient development processes through their quick delivery of software, even under time constraints. However, like other agile methods such as Scrum, Extreme Programming (XP) and The Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD) has been criticized due to the unavailability of security elements in its twelve practices. In order to examine this matter more closely, we conducted a systematic literature review (SLR) and studied literature for the years 2001-2012. Our findings highlight that, in its current form, the FDD model partially supports the development of secure software. However, there is little research on this topic, as detailed information about the usage of secure software is rarely published. Thus, we have been able to conclude that the existing five phases of FDD have not been enough to develop secure software until recently. For this reason, security-based phase and practices in FDD need to be proposed.

show abstract

Comparison between Adaptive Software Development and Feature Driven Development

Cited by 13 publications

References 4 publications

A Review of Agile Methods for Requirement Change Management in Web Engineering

A Review of Agile Methods for Requirement Change Management in Web Engineering

Approach to end-to-end testing of the application for managing the configuration of enterprise virtual infrastructure

A Systematic Literature Review on Secure Software Development using Feature Driven Development (FDD) Agile Model

Contact Info

Product

Resources

About