Feature-Driven Development Research Articles

Development of Information System for Asset Management

An information system for asset management in a university is very important, especially in a faculty with many majors. There are a lot of assets, including laboratories and items inside. In this research, the authors present the development of an information system using feature-driven development (FDD) methodology, which is one of the agile methods, giving flexible and collaborative methods prioritizing main users. To communicate between stakeholders, the development of initial models using UML diagrams, such as use case diagrams, sequence diagrams, and deployment diagrams. The modules on this asset management website are administration for building and room data, asset categorization, asset search, and asset maintenance and problem reporting. The website was developed using PHP with a Laravel framework and MySQL database. This website is beneficial for increasing the efficiency of assets, with future development involving more advanced technology.

Development of E-Modules Using Smart Apps Creator to Improve Learning Outcomes of Islamic Cultural History Grade V

This study aims to develop digital teaching materials in the form of E-modules using Smart Apps Creator in learning Islamic Cultural History that are valid and effective, and can improve student learning outcomes on the material of the exemplary story of Abu Bakar Ash-Shiddiq as a friend and caliph. The development of android-based E-modules follows the Rowntree model which is integrated with the FDD (Feature Driven Development) model which has five stages of the process (Build an Overall Model, Build a Feature List Plan by Feature, Design by Feature and Build by Feature). The research subjects were material experts, instructional design experts, and learning media experts as well as MIT Salsabila students. The sample in this study was class V A. The effectiveness test was carried out by comparing the pretest and posttest scores. The results showed that the quality of the E-module developed was classified as very valid (9302%), very good in the one to one trial (93.96%) very good for small groups (94.29%) and very good for large groups (94.86%). While the t_count value is 6.4915 and the t_table value at a significant level of 5% is 2.0859 then t_count>t_table or 6.4915>2.0859, so h_a is accepted and h_0 is rejected, thus there is a significant difference in the ability between students after being given treatment in the form of using E-Modules. This shows that this E-module is feasible and effective and can facilitate students in analyzing the exemplary story of Abu Bakar Ash-Shiddiq as a friend and caliph.

Pengembangan Sistem Informasi Bank Sampah untuk Optimalisasi Pengelolaan Data

Bank Sampah Sumber Rejeki in Cilacap City provides an opportunity for customers to deposit waste and receive monetary rewards. Unfortunately, current data management is still manual through unstructured notebooks, potentially resulting in data loss due to notebook damage, difficulty in finding customer information, and delays in making performance reports. This research aims to develop a website-based management information system that is tailored to the needs of the sampah bank. This system includes customer data management, recording waste deposit transactions, recording customer balance withdrawals, and improving waste bank data security. Data was collected through direct interviews with the manager of Sumber Rejeki Waste Bank. The development method used is Feature Driven Development (FDD) using the PHP programming language and MySQL database. In addition, testing this system also involves the black box testing method to ensure the functionality is as expected. The result of this research is a web-based system that is significant in improving the efficiency of managing customer data, transactions, and waste bank performance reports. The implementation of this system reduces the risk of errors and data loss due to manual recording and provides easier access for customers to view transaction history in the waste bank.

A Comprehensive Review of Software Development Life Cycle methodologies: Pros, Cons, and Future Directions

The software development process needs specific and studied steps within a reliable plan to achieve the requirements for the success of any project. Software development life cycle (SDLC) methodologies have provided several models that meet the needs of the various proposed projects. These methodologies present various scenarios that can be applied in the process of developing systems to make them more efficient and predictive. The paper aims to illuminate the paramount Software Development Life Cycle (SDLC) methodologies by conducting a comprehensive review of the pros and cons of the various models widely used for software design. Furthermore, the paper discusses fundamental trajectories that are shaping the future landscape of SDLC methodologies. This review included two main types of software development life cycle approaches such as traditional SDLC (heavy-weight) and agile SDLC (light-weight) approaches. The traditional approach included several models such as the Waterfall model, Iterative model, Spiral model, V-Model, and Big Bang Model. Whereas, the agile approach included various models such as the eXtreme Programming (XP) Model, scrum Model, Feature Driven Development (FDD) Model, and Kanban Model. A comprehensive analytical study of all software development life cycle models was achieved and highlighted their most prominent strengths and weaknesses of them. SDLC methodologies wield substantial ramifications across a multitude of sectors, contingent upon several models tailored to individual developmental and research contexts. In culmination, the paper furnishes an all-encompassing perspective on paramount SDLC models, encompassing two principal paradigms: the traditional and the agile approaches. These encompass fundamental sub-models that encapsulate pioneering models poised for application in system development, thus facilitating their refinement more efficiently and predictably.

TATA KELOLA REKAM MEDIS ELEKTRONIK BERBASIS TEKNOLOGI INFORMASI DALAM PELAPORAN PASIEN IGD DENGAN METODE AGILE

This system functions to record daily, monthly, and yearly censuses without changing the performance of the computer used because the data is stored using cloud storage. The purpose of this study was to determine the governance of information technology-based electronic medical records in reporting emergency department patients using the Agile method. The recording of daily, monthly, and yearly censuses in the emergency room at Hermina Arcamanik Hospital in Bandung is not optimal due to frequent problems with the local area network (LAN); computers often hang or freeze, and the system has not been updated. Currently, the recording of daily, monthly, and yearly sensors still uses the Visual Basic program, which has the concern that it requires a very large amount of memory during the installation process. Management of information technology-based electronic medical records in reporting emergency department patients using agile methods The agile method used in the development of this program is feature-driven development (FDD). The system that has been made is tested using the black-box testing method. This program only focuses on completing a certain program and produces medical record management for reporting emergency department patients based on information technology in order to speed up the work process and minimize the occurrence of device errors.

Selection of Feature Driven Development (FDD) Model in Agile Method for Developing Information System of Mosque Management

This paper discusses about software development for building a project using the Feature Driven Development (FDD) model contained in the agile method. As in other agile methods, the Feature Driven Development model has additional properties to implement functions and needs in a short iteration. In terms of the characteristics contained in several other agile models almost all of them have similarities so that makes the stakeholder confusion in determining which model will be chosen as a method of software development. This study focuses on the search for a number of suitable project specifications in the selection of Feature Driven Development models for software development. From the research that has been done on several papers there are several aspects of design and construction in software development by emphasizing the quality and high level of features in developing a software using the Feature Driven Development model. In facilitating the results of the Feature Driven Development model, we will provide a case study of Mosque Management Information System which has several features, such as content management, information of prayer time, online reading Qur’an, and Petty Cash Mosque management. This case is implemented by Feature Driven Development model with short iteration, because this project had done in several months

Development Approach Model for Automotive Headlights with Mixed Delivery Methodologies over APQP Backbone

Headlights’ development for the automotive industry is gaining a lot of volatility due to frequent changes in features, styling and design, hardware interfaces, and software upgrades required by the OEM, supplier, or new trends in regulations. Standard development models based on V-cycle compliant with CMMI are not responding with reactivity on constant changes. The article proposes an approach based on mixed development strategies over the different core domains with Lean, Scrum, Feature-Driven Development, and VDI to satisfy the APQP milestones, with a proposal of a canvas-type model, the rapid delivery of headlights is portrayed. The efficiency and effectiveness of the model are assessed based on the assumed number of changes for new high-end headlights, based on experience and real cases. A delivery baseline LED-based Headlight development—planned versus actual—chart is presented and explained.

Design of emergency response assessment system using Feature-Driven Development approach

This research aims to analyze and design an emergency response assessment system for disaster that will aim for a voluntary team being able to conduct quick assessments in the affected area more effectively and quickly. Feature-Driven Development (FDD) approach is deemed appropriate for analysis and design and later will be developed an emergency response quick assessment system that will be used to collect data such as the impact of facilities and infrastructure, security situation, transportation access, food supply and so on. The aim of the assessment is to used the data will to find out whether an intervention is needed or not. After that, the data is processed and results in the provision of useful assistance on target and on benefits site following the conditions and regulations in Indonesia.

Assessing the Risk of Software Development in Agile Methodologies Using Simulation

Agile methodologies aim to reduce software development risk using short iterations, feature-driven development, continuous integration, testing automation, and other practices. However, the risk of project failure or time and budget overruns is still a relevant problem. The aim of this paper is to present and discuss a new approach to model some key risk factors in agile development, using software process simulation modeling (SPSM), which can complement other approaches, and whose usage is particularly suited for agile development. We introduce a new approach to modeling some key risk factors – namely project duration, number of implemented issues, and key statistics of issue completion time – using a simulator of agile development, which we developed to this purpose. The approach includes modeling the agile process, gathering data from the tool used for project management, and performing Monte Carlo simulations of the process, to get insights about the expected time and effort to complete the project, and to their distributions. The model’s parameters that can cause risk are errors in effort estimation of the features to develop, variations in developers’ assignment to these features, impediments related to developers’ availability and work completion. To validate the simulator, and to demonstrate how the method can be used, we analyzed three open source projects, gathering their data from JIRA repositories. We ran Monte Carlo simulations of these projects, showing that the simulator can well approximate the progress of the real project, then varying the identified risk factors and statistically evaluating their effects on the risk parameters. The proposed approach is relevant for project managers, being able to quantitatively evaluate the risks, provided that the process and the project’s data are properly modeled and gathered. As for the future, we are working to improve our risk assessment method, evaluating it on more case studies, scaling the model from a single team to multiple teams involved in one or more projects.

On the fulfillment of coordination requirements in open-source software projects: An exploratory study

In large-scale open-source software projects, where developers are often distributed across the entire planet, coordination among developers is crucial. To estimate whether a state of socio-technical congruence is achieved, which is associated with software quality and project success, we assess the alignment of collaboration and communication in such software projects in terms of coordination requirements. By means of an empirical study on a substantial set of large-scale open-source software projects—the development histories of all projects sum up to over 180 years—we aim at shedding light on this issue. To this end, to take a more semantic view on this phenomenon in comparison to previous work, we do not only identify coordination requirements arising from files and functions only, but also those arising from features. We found that open-source developers fulfill coordination requirements intentionally, but mostly those coordination requirements that arise from coupled source-code artifacts, while they resolve simpler ones independently. Furthermore, neither of the considered abstraction levels of source-code artifacts (files, functions, features) is more suitable to construct coordination requirements with respect to their fulfillment. This finding strongly indicates that features do not play an as important role in the development process as expected and commonly believed by the research community in the area of feature-oriented and feature-driven development. Finally, we identified notable evolutionary trends in the fulfillment of coordination requirements and showed that far-reaching social events (such as organizational issues) have a huge impact on their fulfillment, both negatively and positively. The key findings of our empirical study are that socio-technical relations are important to understand open-source development communities and that the incorporation of different abstraction levels for developer collaboration does yield important insights to further improve the evolution in open-source software projects.

Identification and integration of security activities for secure agile development

Agile software development is receiving the attention of software developers and researchers thanks to its fast software delivery and flexible development plan capabilities. The fast release and simplified documentation thus leads to the preference of the agile development model over several other traditional models. This, however, also raises critical concerns about the security issues. In this research work, we propose a framework for secure agile development. The selection of development methodology among agile versus plan driven approaches and the particular agile development method among Extreme Programming (XP), Crystal Clear, Scrum, Lean Development, Dynamic Software Development Method and Feature-Driven Development is made on the basis of the specific requirements of the project using empirical methods like AHP and PROMETHEE. Systematic Literature Review (SLR) and survey study are used to obtain the authentic industrial feedback, followed by the application of non-parametric statistical tests to identify and select the most suitable and beneficial security activities from well known security engineering processes like CLASP, Common Criteria, Cigital Touchpoints and Microsoft’s SDL. A lightweight method is also introduced for integrating these security activities identified from SLR and survey study, using a dynamic integration algorithm without compromising the agility of the process. The proposed framework for integration of these security activities is implemented in java to automate the entire process and provides maximum benefit at a low integration cost.

Una revisión comparativa de la literatura acerca de metodologías tradicionales y modernas de desarrollo de software

Existen una gran variedad de metodologías de desarrollo de software, con diferencias significativas en cuanto al tipo de proceso empleado y productos obtenidos, cantidad de recursos involucrados, tiempos de desarrollo y estructura organizacional requerida. Considerando la diversidad de información disponible, este trabajo presenta una revisión enfocada a identificar las tendencias reportadas en la literatura sobre metodologías de desarrollo de software, incluyendo tanto las modernas como las tradicionales. Se aplicaron filtros de búsqueda para seleccionar estudios primarios y secundarios, encontrando que las metodologías de desarrollo tradicionales más reportadas son los de tipo cascada y modelos en espiral, mientras que entre las metodologías modernas las ágiles son las más reportadas, incluyendo programación extrema, scrum, desarrollo orientado a funcionalidades y las basadas en componentes. Se identificaron y compararon las principales ventajas y desventajas de las metodologías, buscando que este trabajo sirva como un punto de partida para los desarrolladores de software a nivel empresarial, educativo e investigativo.

Design and Development of Student Admission System in the State University of Jakarta

.

Using FDD for Small Project: An Empirical Case Study

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.

A Multilayer Secured Messaging Protocol for REST-based Services

The lack of descriptive language and security guidelines poses a big challenge to implementing security in Representational State Transfer (REST) architecture. There is over reliance on Secure Socket Layer/Transport Layer Security (SSL/TLS), which in recent times has proven to be fallible. Some recent attacks against SSL/TLS include: POODLE, BREACH, CRIME, BEAST, FREAK etc. A secure messaging protocol is implemented in this work. The protocol is further compiled into a reusable library which can be called by other REST services. Using Feature Driven Development (FDD) software methodology, a two layer security protocol was developed. The first layer is a well hardened SSL/TLS configuration. The second layer is a well-designed end-to-end protocol that handles authentication, authorization, encryption and message integrity as well as timing and replay attack prevention. The end-to-end protocol uses HMAC-512 and a hybrid encryption system using the AES and RSA algorithms. The protocol was then compiled to a reusable library using C# language. Two different tests were carried out on this protocol: Penetration test and SSL/TLS configuration test. The Penetration Test was carried out using the Open Web Application Security Project Zed Attack Proxy (OWASP ZAP) application and Fiddler Web Debugger. The SSL/TLS test sought to test the SSL/TLS layer of the protocol for known vulnerabilities using a popular SSL/TLS test tool known as SSL Lab. The raw and scaled scores obtained from SSL Lab were 95% and 93% respectively. The results of Implementation test show that the protocol is implementable. The protocol is also resistant to such attacks as: Unauthorized, Timing and Replay attacks as shown by the result of the penetration test. The grade obtained from the SSL/TLS test is “A+”. The result also shows that the implementation is not vulnerable to currently known SSL attacks. The library can be reused by .NET applications and the implementation steps can also be followed by other REST services developers using other platforms.

A simulation environment for polymeric nanoparticles based on multi-agent systems.

Production and characterization of polymeric nanoparticles, as colloidal dispersions, are processes that require time and technical skills to make the results accurate. Computational simulations in nanoscience have been used to help in these processes and provide agility and support to reach results: stability and quality in dispersions. Multi-Agent System for Polymeric Nanoparticles (MASPN) is an innovative and original simulation environment with features to demonstrate interactions of particles from physical-chemical parameters, ensuring Brownian motion of particles and attractive and repulsive behaviour. The MASPN environment has been designed and has been built according to the feature-driven development (FDD), as software methodology, and a multi-agent systems approach. In addition, we have used the event-driven simulation package algs4, the JASON agent building environment, all integrated by Java language. This paper aims to present the relation of the algs4 package and the JASON tool, both integrated into the MASPN environment to generate Brownian motion with elastic and inelastic collisions. The MASPN environment as a simulation tool emerges as a result, including the following features: graphical interface; integrated physical-chemical parameters; Brownian motion; JASON and algs4 integration; and distribution charts (size, zeta potential, and pH).

Empirical Evaluation of Modified Agile Models

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.

Identifying Bottlenecks in Agile Software Development using Theory of Constraints Principles

Theory of Constraints is an analytical tool. A theoretical model for identifying bottlenecks in agile software development methods namely Lean software development, Extreme Programming (XP), Scrum, and Feature Driven Development (FDD) is identified and comparitative analysis is done. Identifying bottlenecks narrows down possible issues in agile software development implementations. These practices are used as surgical tools for various development models to be deployed for software development system. This paper summarizes Targeting with TOC, Eliminating the Constraint and Elevating the Constraint with Agile Principles and Practices. Theory of Constraint is concluded as the best parameter for improvement of development model.Keywords: Agile Software Development, Bottleneck, Extreme Programming (XP), Feature Driven Development (FDD), Lean Software Development, Scrum, Theory of Constraints (TOC)

Secure Feature Driven Development (SFDD) Model for Secure Software Development

This paper introduces an enhanced Feature Driven Development (FDD) model for secure software development. In fact, the enhanced model is based on our previous study and its findings which concluded that existing FDD poses limitations to develop secure software. Thus, an enhanced FDD that supports secure software development is proposed. We have implemented this new FDD model and conducted a case study to compare the level of security in the undergraduate and postgraduate level students. The paper illustrates that agility of FDD is not affected significantly, even after adding new phases.

기능주도개발 Agile 방법을 사용할 때의 안전한 소프트웨어 개발에 관한 문헌연구

Agile 방법론은 시간적 제약하에서도 효율적인 개발 프로세스로 빠르게 제품을 완성할 수 있는 방법으로 알려져 있다. 하지만 scrum, XP, DSDM 등과 같은 여타 Agile 방법들처럼 기능주도개발 (FDD) Agile 방법도 보안요소의 불가용성으로 인해 비판을 받고 있다. 이러한 이슈를 보다 자세히 살펴보기 위해 본 연구는 2001년부터 2012년사이에 나타난 연구들에 대한 체계적인 문헌연구를 수행하였다. 본 연구 결과, 현재 FDD 방법은 안전한 소프트웨어 개발을 부분적으로 지원하고 있는 것으로 나타났다. 하지만 안전한 소프트웨어 사용에 관한 상세한 정보가 문헌에 거의 나타나고 있지 않은 것으로 보아 이 분야에 대한 연구 노력은 거의 없어 보인다. 따라서 현재의 5단계 FDD 방법은 안전한 소프트웨어 개발에 충분하지 않음을 알 수 있고 결국, 본 연구는 FDD 방법에서 보안에 기반을 둔 새로운 수행 단계와 프랙티스가 제안될 필요가 있음을 보여준다. 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.