In-depth analysis identifies challenges in developing Blockchain-Based Applications, suggesting a new methodology for improvement.
Blockchain is a fast-changing field that is highly useful in such areas as finance, supply chain management, voting systems, and healthcare. As a consequence, software developers are increasingly creating Blockchain-Based Applications (BBAs) and Smart Contracts (SCs). However, the development of BBAs has been associated with various problems, especially in the process of updating and debugging such systems with a high degree of reliability. This is due to the immutability of deployed SCs. In this paper, we conduct an in-depth analysis of 61 published BBA articles between 2017 and 2025 to identify some causes of these challenges. Our results indicate that there is inadequate adaptation of the Software Development Life Cycle (SDLC) for BBAs. In particular, few BBA projects—only 32% of the reviewed projects—address the analysis phase, and only 29% deal with the design phase, frequently ignoring formal modeling methods. Based on these observations, we propose a new, context-adaptive methodology that facilitates BBA developers passing through the requirements, analysis, design, and implementation processes. Formal modeling techniques—such as Use Case Maps (UCMs), Finite State Machines (FSMs), and extended Unified Modeling Language (UML) class and sequence diagrams—are used within the methodology to document BBA structural and behavioral features and maintain complete traceability between requirements and implementation. In order to overcome the blockchain-specific drawbacks of traditional UML, we present formal stereotype extensions of UML class diagrams, where a four-compartment structure is introduced to differentiate state variables, functions, events, and access modifiers on SCs. We also provide analogous extensions to UML sequence diagrams using differentiated arrow notations to distinguish between function calls and event emissions to support accurate modeling of decentralized transaction flows. These extensions are described with a rationale and are formally defined and justified by mapping rules. Our methodology is justified by two case studies that prove its applicability in different fields of blockchain. The initial case study thus designs and executes a system of a halal chicken meat supply chain on Ethereum, showing the complete traceability of requirements that are based on UCM-based requirements and FSM-generated algorithms to implement SCs. The second case study applies the methodology to a decentralized Electronic Health Record (EHR) management system, and it shows coverage and completeness modeling. The methodology was evaluated through two case studies using a structured questionnaire and quantitative metrics, including traceability accuracy, reduction-in-error indicators, SC defect and gas-analysis results, modeling overhead measurements, and static security analysis with Slither. It is also evaluated based on a group of seven literature-based qualitative evaluation criteria that include workflow expressiveness, reusability, technical concept coverage, intelligibility, completeness, tool support, and blockchain limitation modeling.
No takes yet. Share an insight, caveat, or question.
Gaddafi et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: