HIEF: An Interpretable Evidence-Fusion Framework for Phishing Email Detection with Decomposable Decision Uncertainty and a Preliminary English–Spanish Evaluation
(1) Background: Phishing remains a pervasive and economically damaging cyberthreat. The dominant detection paradigm has moved toward deep neural and transformer-based classifiers, a literature that reports high accuracy and that does not, in general, expose a per-decision justification, whereas interpretability and auditability are increasingly required in regulated environments; no comparison against transformer-scale detectors is made in this paper. This work asks how far a fully interpretable detector can close the accuracy gap to an opaque text classifier while preserving per-decision explanations, and what such a detector returns that accuracy alone does not measure. (2) Methods: HIEF, an interpretable evidence-fusion framework, is presented. Each email is represented by eighteen human-readable signals: fourteen structural and linguistic cues and four lexical aggregates derived from a published sparse log-odds lexicon. The signals are fused by three transparent layers, namely an L1-regularized logistic model, a shallow interaction-rule tree, and a calibrated Dempster–Shafer stage that reports belief, disbelief and ignorance masses together with an order-invariant global conflict coefficient derived in closed form. A logistic meta-learner fitted on out-of-fold component scores integrates the three layers. The evidential layer uses a type-aware calibration in which discrete signals are calibrated on their attainable values and continuous signals by isotonic regression. Evaluation uses 38,908 public emails, 38,512 of them after exact-duplicate removal, with near-duplicate control, group-aware partitioning, ten repeated splits, a source-held-out protocol, a two-class cross-source test set, a component ablation and a human audit of 100 messages annotated independently by two evaluators. (3) Results: Under group-aware partitioning, HIEF attains an F1 of 0.855 and the strongest term frequency–inverse document frequency (TF–IDF) baseline 0.954; a compact character n-gram neural reference model, evaluated over the same ten partitions, attains 0.973. The linear layer alone attains 0.872, so the two fusion layers do not improve accuracy over it, and the paired difference of 0.017 excludes zero. Type-aware calibration raises the evidential layer from 0.771 to 0.780 and more than halves its partition-to-partition standard deviation, but does not make it competitive; the weakness, therefore, lies in the fusion formulation rather than in the binning. What the evidential layer does supply is a decomposable account of decision uncertainty: the ignorance mass separates errors from correct decisions, 0.265 against 0.175. The human audit reaches an inter-annotator Cohen’s kappa of 0.950 over the five categories before adjudication, and shows that the permissive corpus label agrees with human phishing judgment at a Cohen’s kappa between 0.18 and 0.21, against 0.70 to 0.77 for the automatic strict rule; the audited block is annotated by two of the authors and its human positives are confined to the advance-fee family, so the audit is a bounded comparison of label assignments and not an independent annotation study. (4) Conclusions: HIEF is positioned as an uncertainty and explanation framework rather than as an accuracy-improving fusion method, since the measured accuracy cost of the fusion layers is not compensated by an accuracy gain. Quantifying how much of the performance reported on these widely used corpora is attributable to template leakage and to label permissiveness is a contribution independent of the detector itself. Cross-source operation has not been demonstrated: specificity falls to 0.041 on an unseen collection, so all evaluation reported here is proof-of-concept and no operational deployment claim is made. The Spanish-language evaluation rests on a small and entirely positive subset and is reported as preliminary.
Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 179 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
To compete in this age of disruption, large companies cannot rely on cost efficiency, lead time reduction and quality improvement. They are now looking for ways to innovate like startups. Meanwhile, the awareness and use of the Lean startup approach have grown rapidly amongst the software startup community in recent years. This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors. A multiple case study approach is followed in the investigation. Two software product innovation projects from two large companies are examined, using a conceptual framework that is based on the method-in-action framework and extended with the previously developed Lean-Internal Corporate Venture model. Seven face-to-face in-depth interviews of the employees with different roles are conducted. Within-case analysis and cross-case comparison are applied to draw the findings from the cases. A generic process flow summarises the common key processes of Lean internal startups. The findings suggest that an internal startup that is initiated management or employees faces different challenges. A list of enablers of applying Lean startup in large companies are identified, including top management support and cross-functional team. Both cases face different inhibitors due to the different process of inception, objective of the team and type of the product. Our contributions are threefold. First, this study is one of the first attempt to investigate the use of Lean startup approach in large companies empirically. Second, the study shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context. The third is a general process of Lean internal startup and the evidence of the enablers and inhibitors of implementing it, which are both theory-informed and empirically grounded.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9