Problem
Research questions and friction points this paper is trying to address.
Proof of Concept
architectural decision
software engineering
decision traceability
conceptual clarity
Proof of Concept as a First-Class Architectural Decision Instrument
🤖 AI Summary
This study addresses the prevalent lack of clear definition and systematic methodology for proof-of-concept (PoC) activities in current software engineering practice, where PoCs are often treated as informal experiments, leading to untraceable architectural decisions and poor knowledge retention. Through a systematic literature review, the work identifies core characteristics of PoCs and, for the first time, establishes them as first-class vehicles for architectural decision-making, while introducing the anti-pattern of “undocumented architectural experiments.” Building on this foundation, the authors propose a lightweight, three-phase framework—encompassing planning, execution, and decision-making—that integrates conceptual modeling and decision analysis to define and operationalize PoCs in a structured manner. This approach significantly enhances the quality and traceability of architectural decisions and strengthens organizational learning.
📝 Abstract
Proofs of Concept (PoCs) are widely adopted practices in software engineering. Despite their relevance, PoCs remain conceptually underdefined and methodologically ad hoc in both research and industry, with definitions and implementation approaches that often lack clarity and consistency. This paper investigates the concept of PoCs with two complementary goals: (1) to provide a refined definition and astructured framework for PoC development grounded in a systematic review of academic and grey literature; and (2) to position PoCs as first-class architectural decision instruments rather than informal experiments or disposable artifacts. Through a systematic review of academic and grey literature we identify the key characteristics, processes, associated with PoCs and expose a significant gap the academic literature describes PoC outcomes but rarely its process. By synthesizing insights from diverse sources we propose a refined definition and a lightweight, three-phase framework (planning, execution, decision-making) that encompasses technical validation and explicit decision traceability. We also introduce the Undocumented Architectural Experiment anti-pattern, arising when PoCs influence high-impact architectural decisions without leaving durable architectural knowledge. We argue that elevating PoCs to first-class status improves decision quality, enhances traceability, and supports more systematic learning in architectural practice.
Innovation
Methods, ideas, or system contributions that make the work stand out.
Proof of Concept
Architectural Decision
Decision Traceability
Anti-pattern
Software Architecture
🔎 Similar Papers
No similar papers found.
