© 2026 The authors. This article is published by IIETA and is licensed under the CC BY 4.0 license (http://creativecommons.org/licenses/by/4.0/).
OPEN ACCESS
Socialization, Externalization, Combination, and Internalization (SECI) Failures in requirements elicitation often arise from trust dysfunction, yet current methodologies lack systematic mechanisms to quantify, monitor, and manage trust. This study introduces a trust-enhanced SECI model that integrates multidimensional trust with knowledge creation processes across pre-elicitation, elicitation, and post-elicitation phases. The framework provides mathematical trust indices, early warning indicators, and predictive quality pathways, enabling objective trust assessment and actionable interventions at each phase. Competence, benevolence, and integrity dimensions capture stakeholder trust toward analysts, while requirements quality is evaluated through completeness, consistency, and clarity metrics. Longitudinal validation was conducted across 45 pedagogical information systems projects in Algerian higher education, involving 500 stakeholders and 1,500 temporal observations. Results demonstrate that trust stability is a strong predictor of requirements quality. Statistical analyses, including variance assessment and structural equation modeling, indicate that integrity and benevolence exert greater influence than technical competence. Empirically-derived thresholds guide phase-specific interventions to ensure robust management. This approach systematically links trust dynamics, collaborative knowledge transformation, and requirements quality, providing theoretical insights into trust-based elicitation processes while offering practical tools to improve stakeholder collaboration and project outcomes. By embedding trust evaluation into each phase, the model enhances the reliability and effectiveness of requirements elicitation in complex organizational settings.
requirements elicitation, trust quantification, Socialization, Externalization, Combination, and Internalization model, collaborative knowledge, requirements quality, longitudinal validation, phase-specific intervention SECI
Trust dysfunction in requirements elicitation systematically undermines software project success. However, current Requirements Engineering (RE) methodologies lack quantifiable frameworks to measure or manage trust relationships. The Requirements Elicitation Process (REP) often produces incorrect, incomplete, and inconsistent requirements due to socio-emotional complexity [1, 2]. However, existing approaches treat trust as unmeasurable. This is problematic because projects with dysfunctional trust experience 40-60% higher defect rates and two to three times longer development cycles [3]. This void manifests across three deficiencies. Gap 1: Absence of Quantifiable Trust Measurement. No mathematically rigorous methods exist to assess trust levels. Burnay and Snoeck [3] provided conceptual definitions but lacked operational instruments. This absence creates a "measurement vacuum" that remains invisible to project management systems. Gap 2: Missing Integration Between Trust Theory and Knowledge Transformation. The SECI model [4] and trust theory [5] remain disconnected within REP contexts [6, 7]. This disconnection prevents practitioners from understanding several critical aspects [8]: dimension-phase matching, configuration effects, temporal dynamics, and bidirectional causality. Gap 3: Insufficient Empirical Evidence: Current research offers anecdotal observations [3] but lacks large-scale validation, with studies suffering from small samples (n < 10) [9, 10], cross-sectional designs, subjective metrics, and no validated predictive thresholds. This research addresses these gaps through three primary contributions. Contribution 1: Mathematical Trust Quantification Framework. We integrated the three-dimensional trust model of Mayer et al. [5] with requirements quality assessment across Socialization, Externalization, Combination, and Internalization (SECI) phases. This integration enables objective measurement on validated 100-point scales (α = 0.93), variance-based early warning indicators, and predictive modeling with empirically validated intervention thresholds. Contribution 2: Phase-Specific Trust-Knowledge Integration Theory: We establish systematic relationships between trust dimensions and SECI transformation stages, revealing how trust configurations facilitate or impede knowledge conversion, which dimensions dominate each REP phase, and how trust accumulation creates compound quality effects. Contribution 3: Large-Scale Empirical Validation: We provide comprehensive statistical evidence through longitudinal analysis of pedagogical information systems in Algerian higher education, featuring high collaborative complexity, knowledge-intensive tacit-to-explicit conversion, and trust-sensitive academic hierarchies, enabling robust validation with empirically-derived predictive thresholds for quality forecasting and intervention protocols.
The paper is organized as follows. Sections 2 and 3 lay the theoretical groundwork by establishing the REP domain context through trust theory, collaborative work, and knowledge transformation. Section 4 surveys the related literature on trust-enhanced requirements elicitation. Sections 5 and 6 present the trust-enhanced SECI model and its associated trust calculation methodology. Section 7 empirically validates the proposed approach through a MOOC case study, while Sections 8 and 9 address the key findings and directions for future research.
In this section, we present the application domain of our research work, which is RE in general and REP in particular.
RE is a crucial subject in the development of solutions that fulfill user requirements [1]. It is a fundamental discipline in the development of solutions that meet user needs. It is a process of discovering, acquiring, and developing requirements [11]. It is therefore the earliest and crucial stage in the system development life cycle. According to Nuseibeh and Easterbrook [12], a RE process includes the phases of elicitation, modeling, analysis, specification, validation, and requirements management.
Our work focuses on the elicitation phase, the first phase of the process, which is one of the most critical activities in system development and has a strong impact on project success and quality. System development is a communicative process that requires to follow many lifecycle phases. Human involvement in any phase is obvious in order to ensure the correctness and reliability of the development process and thus increase and ensure trust [11]. Therefore and in the context of this analysis, trust and trustability can be two meta-properties that cannot be added to a product after its creation. They are rather built into meta-properties, integrated with the quality properties from the very first steps of the system development. In reality, though, it is rather common that people do not trust systems that they are not familiar with, but after experiencing their functions, trust may evolve. In this case, trust evolves in the person (trustor) even though the system has not been changed [13].
RE is often more complex than it seems at first glance. In the parallel model (see Figure 1), this stage kicks off right at the beginning of the RE process, taking up a significant amount of activity initially. It’s all about collecting information from stakeholders to really grasp their needs and expectations [14]. As time goes on, its importance gradually lessens as other tasks like analysis and specification come into play, but it still plays a crucial role for a good chunk of the process. This highlights its importance as the bedrock for all the subsequent work on requirements [14]. Essentially, REP is a series of activities aimed at identifying, gathering, understanding, clarifying, and documenting what’s needed for a system or product. These activities need to be tailored to fit the project’s context, the system’s complexity, and the stakeholders involved [15]. It’s the essential first step in RE, making sure that the final product aligns with both business goals and user needs.
Figure 1. Parallel model of requirements process [16]
REP has been identified by past research to be a contextually situated process that evolves dynamically as a function of the collaborative interaction of the participants with diverse viewpoints (e.g., [17]).
REP has received considerable attention in engineering research communities, as elicitation is considered to be one of the most important and difficult activities in REP.
Several Re models have been proposed in the literature, such as Robertson’s Volere requirements methodology, which includes a detailed model of its RE activities with inputs, outputs, and recommended techniques for each activity [17].
Several researchers [18, 19] have developed specific models that define how to use scenarios to generate requirements. Sutcliffe and Ryan [20] present an elicitation model that combines scenarios, prototypes, and a design rationale. Sommerville and Sawyer [21] describe their approach for using viewpoints to elicit requirements.
In the present research work, we adopt the unified model of requirements REP, developed by Hickey and Davis [16], that emphasizes the iterative nature of elicitation as it transforms the current state of the requirements and the situation to an improved understanding of the requirements and, potentially, a modified situation.
In this section, we present three domains of interest for our research work.
3.1 Trust
The trust could be of great significance for the RE process because it might affect the trust among stakeholders and analysts. Requirements engineers or analysts must be aware of the nature of various types of trust relationships and trust assumptions that exist during the specific activities of this process.
3.1.1 Trust in theory
Trust can be interpersonal, organizational, or institutional. Indeed, it can be horizontal (between colleagues), vertical (between managers and employees or between employees and managers), or institutional (between employees and organizations) [22].
Trust has been studied in many disciplines, including sociology [23], psychology [24], economics [25], and computer science [26] from different angles.
In general, trust is a measure of assurance that one or more entities will behave in the expected way [27]. According to [28], it is possible to classify trust perspectives into three categories: (i) that of personality theorists, who conceptualize trust as a belief, expectation or feeling deeply rooted in the personality; (ii) that of sociologists, focused on the understanding of the social bond; (iii) that of psychosociologists, who define trust in terms of the hope and consent of a third party who engages in a transaction.
The work of Marsh and Dibben [29] is considered to be the first to have introduced the notion of trust in computer systems. Today, many well-known computer systems and applications are based on this notion.
Firstly, there is agreement on the fact that trust is a dyadic relationship; it involves two people, referred to as Trustor (the one who trusts) and Trustee (the one who is trusted) [22].
Secondly, it is common to consider trust as a subjective evaluation made by the trustor over the trustee [30]. In the study [31], for example, trust is defined as "the perceived credibility and benevolence of a target of trust». The definition emphasizes the perception aspect of trust: trust is not the result of an objective process, but is the result of some sensations from the trustor about the trustee.
Thirdly, trust systematically follows from an intention. In the study [32], trust is defined as "the willingness to rely on an exchange party in whom one has confidence", thereby emphasizing the necessity of a voluntary trustor.
Fourthly, trust implies vulnerability [3, 33]. In the study [3], Burnay and Snoeck define trust as "the willingness of a party to be vulnerable to the actions of another party". The definition clearly states that a trustor is vulnerable to some risk when trusting the trustee.
Figure 2. Integrative model of trust [5]
To measure, understand, and explain trust, it is important to identify its dimensions. Research has identified several key elements of trust. It arises from certain factors of reliability that the trustor perceives in the trustee. These factors vary according to context, and are assessed by the trustor so that he or she can decide whether the trustee is trustworthy and whether the outcome of an interaction is fruitful [34]. These factors represent the dimensions of trust. Mayer et al. [5] studies have shown that trust has three main dimensions (Figure 2):
3.1.2 Trust in engineering
The concept of trust has received considerable attention in engineering research communities, as trust is perceived as the basis for decision-making in many contexts and the motivation for maintaining long-term relationships based on cooperation and collaboration [8, 35]. In some environments, trust relationships are understood only as interpersonal relationships between human beings. However, in some computer environments, these trust relationships can be extended to concern different kinds of entities. Indeed, the trustee can be: any entity, such as a person, a group of persons, or an organization; a system agent representing a person or organization; a piece of system; a device; a network; a data resource like a document or a database; the development process; the business process where the system is used; or the whole system.
The trustor has to be an entity capable to assess the trustworthiness of another entity, and also capable of making decisions based on that. It is rather common that people do not trust systems that they are not familiar with, but, after experiencing their functions, trust may evolve. In this case, trust evolves in the person (trustor) even though the system has not been changed.
3.2 Collaboration work
Collaboration is a complex phenomenon whose definitions remain very vague and variable. The literature provides several definitions of collaboration, which generally translate into a joint effort toward a common goal [36]. Given the many definitions that exist, it was important to choose one that we felt was the most generic. We therefore chose the definition, which states that interprofessional collaboration is: ’made up of a set of relationships and interactions that may or may not enable professionals to pool and share their knowledge, expertise, experience and skills in order to use them concomitantly in the service of clients and for the greater good of the clients’ [37].
It is also seen by the study [38] as a process in which stakeholders with different perspectives on a problem, can constructively explore the differences and can search for solutions that go beyond their own limited visions. In a collaborative context, all participants co-construct together, even if the task can be divided into several other subtasks. In collaboration, all participants intervene in each step so that it is not possible to distinguish individual work in the final result [39]. Collaboration is often done synchronously, even if it is possible in an asynchronous way [40] to create synergy and benefit most from interaction. In fact, the quantitative prospective analysis conducted by Quinteros provides stakeholders with a strategic tool that enables them to take proactive measures to reduce employee turnover and maintain the organization’s vitality [8].
Through the above definitions, we can notice that collaboration is a complex task because it is more difficult to co-construct than to emit or receive information (communication) and more difficult than to assemble information by gathering and coordinating the work of individuals (cooperation and coordination) [41].
3.2.1 Collaboration engineering
Collaboration engineering is a structured approach to facilitating collaborative working. It involves three key roles: facilitator, practitioner, and collaboration engineer [42]:
Processes are organized into six basic patterns: "Generate," "Clarify," "Reduce," "Organize," "Evaluate," and "Build Consensus." These patterns help create predictable group behavior and achieve common goals.
3.2.2 Collaboration in engineering
Collaboration in engineering involves bringing together experts from various fields to create, develop, and execute complex solutions, ensuring innovation, quality, and efficiency [45]. By implementing structured processes, adopting good tools, and promoting effective communication, teams can maximize efficiency. However, collaboration processes depend on engineering processes [41].
The Electronic Industries Alliance standard 632 (EIA-632) defines the processes required to design, develop, implement, and support complex systems throughout their lifecycle [46]. Konaté et al. [41], have used the collaborative engineering approach to define the collaborative processes within the EIA-632 standard. This led them to focus on collaborative engineering tasks.
3.3 Knowledge transformation
Knowledge is dynamic and context-specific; it is created in social interactions among individuals and organizations and depends on a particular time and space [47]. A portion of knowledge is usually recorded, but the rest may still remain in the individuals’ mind.
Knowledge transformation is the transformation of raw data into usable, understandable, and exploitable knowledge, crucial for learning, innovation, and decision-making in fields like engineering, education, and management. Given its link to organizational performance, it is essential to continue to identify the factors and contexts that facilitate employees’ knowledge creation and sharing behaviour [48].
RE is a knowledge-intensive activity [49], and a variety of tools and techniques are needed to capture and process this knowledge.
3.3.1 Knowledge management
Knowledge management (KM) refers to the management of individual, structural, and organizational knowledge [50]. Knowledge is intrinsically embedded in human cognition, and knowledge management occurs in frames of social context [51]. Thus, the consideration of the human and social factors is a necessary and crucial element of the knowledge management process. Indeed, within organizational contexts, stakeholder behavioral data constitutes a significant knowledge resource, one that increasingly shapes and informs the foundations of strategic decision-making [19]. One of the greatest challenges of knowledge organizations is to extract tacit knowledge possessed by their knowledge employees, so as to apply the right knowledge at the right place when needed and to encourage innovation. One of the main obstacles to these efforts is the lack of trust between managers and employees, and between employees themselves [52]. To effectively achieve the objectives of REP, tacit knowledge must be converted into formal knowledge that is easily accessible and can be widely used to develop quality requirements. Knowledge management processes can be used as a complement to support analyst engineers.
3.3.2 Knowledge elicitation
System engineering [53, 54] has a lot in common with knowledge management in the knowledge elicitation phase. Knowledge elicitation involves acquiring and transferring the knowledge of individuals to an abstract and effective representation to organize it, model it, and finally express it. REP involves the acquisition and transfer of knowledge from individuals, teams, or systems in order to organize, model, and formalize it in an understandable format and finally use it in various contexts.
3.3.3 Socialization, Externalization, Combination, and Internalization model
This model, developed by Ikujiro Nonaka and Hirotaka Takeuchi [4], is a framework for understanding the process of knowledge creation and transfer within organizations. The model is one of the most influential theories of knowledge creation [48] and has therefore been the one most adopted by researchers studying the relationship between knowledge creation and innovation [55]. Nonaka et al. [4] distinguishes between implicit (tacit) and explicit knowledge. Explicit knowledge is characterized by being formal and systematic knowledge that can be expressed without ambiguity through writing, schematics, databases, etc. It is stored in textbooks, system products, and documents; implicit knowledge is highly informal, personal, unverbalized, intuitive, and derived from experience. It is stored in the minds of people in the form of memory, skills, experience, education, imagination, and creativity. The model consists of four modes of knowledge conversion: SECI. It does involve a process of knowledge transformation. Stages of the SECI model (1) Socialization (Tacit to Tacit): individuals share tacit knowledge (personal and experiential) with others through direct interaction and shared experiences. This could occur through apprenticeships, mentoring, or other forms of personal interactions. (2) Externalization (Tacit to Explicit): the articulation of tacit knowledge into explicit forms. This process involves expressing personal insights and experiences in a form that can be communicated and shared with others. This often takes the form of creating documents, diagrams, or other tangible representations.
Combination (Explicit to Explicit): explicit knowledge (codified and documented) is combined and organized in a systematic way. This can include the integration of different explicit knowledge sources, such as databases, manuals, or other structured information repositories.
Internalization (Explicit to Tacit): the process of converting explicit knowledge back into tacit knowledge. Individuals acquire explicit knowledge from external sources and internalize it by applying it in their own context, thereby making it part of their personal experience and tacit knowledge.
The SECI model is often represented as a continuous cycle, emphasizing the dynamic and iterative nature of knowledge creation and transfer within a team [4]. While it is not a direct elicitation process for gathering requirements, it highlights the importance of understanding and managing the flow of knowledge within a REP.
Existing literature on REP has focused on the process and product. A review of this literature suggests that there are very few studies examining the socio-emotional process associated with REP. For example, Fatima et al. [56] discuss how to use cognitive psychology and learning style models (LSM) to understand the psychology of clients. Aranda et al. [9] propose a model based on psychological theories to identify suitable elicitation techniques according to cognitive aspects of most stakeholders in the group. Previous studies have shown that trust has a positive effect on relations between employees and managers [57]. In REP, trust is acknowledged as a critical success factor of systems [3].
Firstly, it is common to consider trust as a key element for effective communication and teamwork between analysts and stakeholders. Moreover, trust in REP has recently become an important topic of debate. Burnay and Snoeck [3] provide a first empirical study on the impact of trust during Re and propose a first definition of trust in the engineers and trust in the stakeholders during RE. In fact, it is a key element in effective communication and teamwork between engineers and stakeholders. Interpersonal trust can also facilitate collaboration and reduce conflict between team members. Trust has been shown to influence the ability of a team to achieve greater cohesion and cooperation in reaching a common understanding of requirements. Reduced levels of trust have been associated with a lack of collaboration.
Secondly, there is agreement on the fact that the evolution of requirements based on the transformation of knowledge deals with tacit and explicit requirements. Knowledge is purely human in the knowledge management and requirement engineering fields [10]. Many authors have argued that one of the major bottlenecks in building a knowledge-based system is the knowledge elicitation process [10]. Tacit knowledge has also proved to be an important challenge in elicitation. Indeed, knowledge creation has been identified by previous research as an important factor in organizational success [47]. It is a process of making available and amplifying knowledge created by individuals, as well as crystallizing and linking it to the organization’s knowledge system [4, 55]. Given its link to organizational performance, it is essential to continue identifying the factors and contexts that facilitate employees’ knowledge creation and sharing behavior [48]. The knowledge of both the stakeholders and analysts can be divided into explicit knowledge and tacit knowledge, and REP is an iterative process of knowledge SECI. The knowledge creation theory of Nonaka is appropriate for analyzing and creating knowledge [6]. Li et al. [7] analyzed REP from the view of knowledge management. The studies [58, 59] have shown that the level of vertical trust affects employees’ actions in decision-making. Similarly, horizontal trust is also necessary for the processes of knowledge creation, transfer, and dissemination between colleagues and within an organization. Previous research indicates that trust in colleagues is more important for knowledge sharing than trust in superiors [60]. It is therefore important to understand the behaviors of managers and employees to create this trust.
Thirdly, collaboration engineering is an approach to designing and deploy processes for recurring collaborative tasks [59]. REP activities must allow for communication and collaboration with all the relevant stakeholders and requirements engineers [61]. Konaté et al. [41] present a methodology aimed at enhancing collaborative RE in the context of product development. Their approach distinguishes between engineering components and collaborative elements. Initially, they focus on the engineering process, which is grounded in the system engineering standard EIA-632 [46]. Subsequently, they establish a collaboration process specifically tailored for requirements engineering, employing the principles of Collaboration Engineering, especially the collaboration patterns [41]. In this model, engineering collaboration is defined as a function that describes the various interactions between the participants and the data flow.
As mentioned above, our research focuses on REP, which is a collaborative activity between stakeholders and analysts, whose success relies on the ability of both groups to work together, combining their different sets of knowledge and taking into account the mutual trust. In fact, we are focusing on three important dimensions: Collaborative Knowledge and Trust.
Firstly, REP is a collaborative activity that can be designed and defined using collaborative engineering. REP without effective knowledge conversion is determined to fail. Indeed, in the processes of knowledge internalization, because of a crisis of trust in knowledge communication, developers did not effectively communicate with users.
Secondly, one of the most cited factors affecting knowledge sharing is trust [62]. Trust is an important factor in ensuring the organizational climate and, hence, the success of REP.
To our knowledge, there is no previous work that investigates the influence of trust on the behavior of analysts and stakeholders in REP activities in individual and collaborative contexts using the SECI model. There is no coherent conceptual framework that integrates trust in REP activities. The purpose of this paper is to examine the impact of trust as a constraint for the collaboration process on knowledge creation in REP using the SECI model introduced by Nonaka and Takeuchi [63].
5.1 Socialization, Externalization, Combination, and Internalization model in Requirements Elicitation Process
REP can be viewed through the SECI model a knowledge management framework that explains how tacit and explicit knowledge are created, converted, and utilized within an organization [64]. The SECI model comprises four stages: SECI, each playing a distinct role in the elicitation process. Integrating the SECI model into REP provides a structured approach to understanding and managing the knowledge involved in the process [16]. The application of the SECI model in REP is further enhanced by considering distinct phases: Pre-elicitation, Elicitation, and Post-elicitation. Each phase corresponds to one or more specific stages of the SECI model, creating a cohesive framework for managing the flow of knowledge during RE.
5.1.1 Pre-elicitation
This phase, which is grounded in internalization, focuses on equipping the elicitation team with the necessary knowledge and context. This involves a deep dive into existing documentation, such as project charters, market research reports, and competitor analyses, to gain a comprehensive understanding of the project’s goals, target audience, and competitive landscape [65]. The team members internalize this information, transforming it into their own tacit knowledge, which forms the basis for subsequent elicitation activities. Figure 3 illustrates the systematic conversion of explicit knowledge sources into tacit understanding through structured transformation activities.
Figure 3. Pre-elicitation phase
5.1.2 Elicitation
As illustrated in Figure 4, this phase, which is grounded in socialization. emphasizes the importance of direct interaction and shared experiences among stakeholders. It involves fostering an environment where stakeholders can freely exchange ideas, perspectives, and tacit knowledge related to the system’s needs and functionalities [66]. It often involves techniques such as brainstorming sessions, interviews, and ethnographic studies to capture the implicit and unarticulated requirements that reside within the stakeholders’ minds [67]. These interactive sessions facilitate a deeper understanding of the problem domain and user needs, enabling the elicitation of requirements that might otherwise be overlooked [15].
Figure 4. Elicitation phase
5.1.3 Post-elicitation
This phase, which is grounded on externalization and combination, embodies the crucial process of articulating tacit knowledge into explicit forms that can be readily comprehended, shared, and leveraged across the organization [16]. This transformation is pivotal for ensuring that the valuable insights, experiences, and understandings held by individual stakeholders are not confined to their personal cognitive domains but are instead converted into tangible assets that can be readily disseminated and utilized by the wider development team and relevant stakeholders. As indicated in Figure 5, the combination represents the culmination of the knowledge creation process within the SECI model, involving the integration and synthesis of newly externalized knowledge with existing explicit knowledge to form more complex, comprehensive, and systematic bodies of knowledge [68].
Figure 5. Post-elicitation phase
This holistic approach ensures that knowledge is systematically created, shared, and preserved throughout REP, leading to more effective and comprehensive requirements understanding while building organizational knowledge assets for future projects. As the Figure 6 demonstrates, this framework integrates Nonaka's SECI model with the Requirements Elicitation Process, illustrating knowledge transformation across three phases: Pre-Elicitation (Internalization) converts explicit domain knowledge into analyst tacit competence; Elicitation (Socialization) enables tacit-to-tacit exchange through collaborative activities in Ba spaces; Post-Elicitation (Externalization and Combination) transforms shared understanding into formal requirements documentation, with cyclical flows illustrating continuous individual-to-collective knowledge conversion.
Figure 6. Knowledge conversion dynamics in requirements elicitation
5.2 Integrated Framework Logic: Phase-wise trust- Socialization, Externalization, Combination, and Internalization-quality pathways
This research demonstrates that knowledge conversion, team performance, and requirements quality are significantly positively correlated, with trust as a crucial facilitator operating at multiple levels to influence knowledge processes and team outcomes. We position interpersonal trust as both a precondition and outcome of effective collaboration, recognizing that horizontal and vertical trust moderate collaborative processes since trust between team members is necessary for creating and disseminating tacit knowledge [47].
Our theoretical integration operates through three interconnected phase-specific mechanisms. During pre-elicitation (Internalization), analysts convert explicit domain knowledge into tacit understanding while competence trust forms through demonstrated mastery, determining stakeholders' willingness to share complete information. During elicitation (Socialization), tacit-to-tacit knowledge sharing occurs through direct interaction as benevolence trust (perceived care) and integrity trust (consistent behavior) create psychological safety, enabling honest, unambiguous communication. During post-elicitation (Externalization-Combination), cumulative trust from previous phases enables collaborative validation as stakeholders actively participate in converting shared tacit knowledge into explicit, refined requirement artifacts. Three critical interaction points govern this process: trust accumulates across phases with compounding effects, requirements quality outcomes recursively reinforce or diminish trust for subsequent iterations, and trust instability at any phase disrupts downstream knowledge conversion regardless of mean trust levels.
5.2.1 Trust as a catalyst for knowledge creation
Given that trust among team members serves as a prerequisite for generating and sharing tacit knowledge [47], we suppose that both horizontal and vertical trust dimensions moderate collaborative processes through several mechanisms:
5.2.2 Trust as a foundation of knowledge transformation
REP ensures that the collected requirements achieve optimal levels of consistency, clarity, and completeness through systematic refinement and validation [69]. Figure 7 demonstrates that trust serves as the fundamental enabler that core enabling mechanism through which three quality dimensions are sustained across all SECI model phases during REP. Without trust, knowledge transformation becomes superficial, incomplete, or entirely blocked. Trust manifests differently across each phase while maintaining its critical role throughout the entire process.
Figure 7. Trust Foundation (with Competence, Integrity, and Benevolence) as the core element around which the entire requirements elicitation cycle revolves
Trust functions as both a prerequisite and outcome of effective knowledge transfer in RE, creating a virtuous cycle where trust enables better knowledge sharing, which in turn builds stronger trust relationships among stakeholders.
This approach effectively communicates that successful RE depends not just on following the SECI process, but on cultivating trust at every phase to ensure authentic, complete, reliable knowledge transfer.
Trust serves as the fundamental cornerstone of knowledge transformation processes within RE activities. The dynamic nature of elicitation demands that varying forms of trust be cultivated and deployed strategically across the three phases of REP (see Figure 6). Each phase presents unique challenges and opportunities that require specific trust configurations to optimize knowledge flow and stakeholder engagement. REP exhibits a cyclical nature, where trust operates as both an enabler and an outcome of continuous improvement initiatives. As trust levels increase through successful collaborative experiences, teams become more willing to engage in iterative refinement, constructive feedback, and adaptive learning. This creates a positive feedback loop where enhanced trust leads to better knowledge transformation, which in turn strengthens trust relationships and enables more sophisticated elicitation practices. We adopt the dimensions of trust mentioned in the work of Mayer et al. [5]. Indeed, the entire system is supported by three foundational trust dimensions that work synergistically to create an environment conducive to effective knowledge transformation.
Together, these dimensions create a robust foundation that sustains trust throughout the complexity and uncertainty inherent in REP (see Figure 6).
5.3 Conceptual framework trust-enhanced Socialization, Externalization, Combination, and Internalization model in Requirements Elicitation Process
We propose a coherent conceptual framework that integrates trust in REP activities. This model (Figure 8) explains how trust relationships become crucial during requirements gathering, where stakeholders must be willing to share knowledge, admit uncertainties, and engage honestly with analysts.
Figure 8. Conceptual framework trust-enhanced Socialization, Externalization, Combination, and Internalization (SECI) model in Requirements Elicitation Proces (REP)
This model integrates three complementary theoretical perspectives into a unified framework. The SECI model provides temporal structure through the PHASE-ACTIVITY-TASK hierarchy (Internalization, Socialization, Externalization, Combination). Collaboration Engineering operationalizes stakeholder interactions via COLLABORATION_PROCESS entities with structured facilitation PATTERNS and TRUST_ACTOR participation. Trust theory functions as a moderating mechanism through TRUST constructs.
The model depicts causal pathways where trust influences: (i) stakeholders' willingness to externalize tacit knowledge during socialization, (ii) articulation quality during externalization, and (iii) knowledge integration reliability during combination—operationalized through "participate to define" relationships linking TRUST_ACTOR to NEED specifications that produce REQUIREMENT artifacts. This represents not a static construct list, but dynamic pathways where trust enhances collaborative knowledge conversion to impact requirements quality, providing the ontological foundation for measuring trust-knowledge-quality relationships across the project's empirical validation.
Current REP methodologies struggle with quantifying trust relationships, leading to subjective assessments that fail to predict quality requirements effectively. The absence of statistical rigor in trust measurement creates gaps in REP and stakeholder relationship management. This research fills these gaps by providing a mathematically sound framework for trust quantification and quality prediction.
Trust formalization encompasses diverse mathematical frameworks across computational, game-theoretic, probabilistic, and social network domains, each tailored to specific application contexts. While computational models employ algorithms like Marsh's T(a,b) = Σ(wi × Ei) and cryptographic approaches utilize certificate chains, our research adopts the cognitive formalization based on the Mayer-Davis-Schoorman tripartite model [5]. This cognitive framework formalizes trust through three fundamental dimensions: competence trust (stakeholder confidence in technical expertise), benevolence trust (perception of genuine concern for stakeholder interests), and integrity trust (belief in ethical adherence and honesty). This choice is particularly suited to RE contexts where human-centered trust dynamics are paramount, as it captures the psychological foundations of trust formation between stakeholders and requirements engineers. Unlike purely computational or mathematical approaches, the cognitive formalization provides a theoretically grounded yet practically applicable framework that aligns with natural human trust assessment processes, making it optimal for understanding and facilitating effective knowledge transformation in collaborative requirements elicitation environments.
The framework integrates trust measurement with requirements quality assessment across the three SECI knowledge conversion phases. It measures trust through three dimensions (Competence, Benevolence, Integrity) and requirement quality through three dimensions (Completeness, Consistency, Clarity), all on 0-100 scales. REP phases include Pre-elicitation (20% weight), Elicitation (30% weight), and Post-elicitation (50% weight). The weighted phase distribution (20%-30%-50%) reflects empirical findings indicating the cumulative nature of trust development and its maximal impact during post-elicitation activities.
The framework provides a comprehensive tool for analyzing trust-quality relationships in SECI-based REP. It introduces standard analysis and SEM, which is a statistical approach that combines factor analysis and regression to test relationships between observed variables (trust and quality scores) and latent variables (overall Trust, Quality, and SECI). It helps visualize direct and indirect effects, model fit, and how different dimensions interact in complex systems) (Structural Equation Model) analysis modes.
Standard analysis mode introduces mathematical formulas categorized across five analytical domains: base performance indices, diagnostic variance detection, predictive correlation modeling, statistical validation, and impact measurement. This is a quantitative approach to measuring trust across different phases of REP. An interactive trust calculation dashboard that implements the framework, allowing users to input scores and see real-time trust calculations across all three phases. The comprehensive REP Dashboard that fully implements the Trust-Enhanced SECI. The model framework provides a valuable analytical tool for requirements engineers, enabling them to monitor and enhance the quality of REP activities. It automatically calculates the global requirements quality index and provides immediate visual feedback on how trust levels impact overall REP quality.
Structural Equation Modeling mode features real-time visualization of trust metrics across competence, benevolence, and integrity dimensions through interactive slider controls, stakeholder performance matrices, and multi-phase correlation analysis spanning pre-elicitation, elicitation, and post-elicitation stages. The integrated SEM analysis serves as the dashboard's analytical core, providing continuous monitoring of latent variable relationships (ηTrust, ηQuality, ηSECI) with real-time path coefficient calculations (β₁ = 0.72 for Trust→Quality, β₂ = 0.45 for SECI→Quality, γ₂ = 0.68 for SECI→Trust), model fit indices (CFI = 0.952, TLI = 0.941, RMSEA = 0.058, SRMR = 0.045), and structural equation displays that demonstrate how knowledge creation processes influence both trust formation and requirements quality through the primary equation:
$\eta_{ {Quality}}=0.72 \eta_{ {Trust}}+0.45 \eta_{S E C I}+\zeta$ (1)
with explained variance calculations and live prediction capabilities that update dynamically as trust dimensions are modified. Factor loadings for trust dimensions were adopted from Mayer et al. [5] validated trust scale (λcompetence = 0.89, λbenevolence = 0.84, λintegrity = 0.87).
This research contributes to a broader initiative aimed at adapting cross-curricular and discovery modules for diverse learners to establish a comprehensive national e-learning framework. The initiative, spearheaded by Algeria’s Ministry of Higher Education and Scientific Research (MESRS), focuses on converting traditional cross-curricular modules into Massive Open Online Courses (MOOCs).
The systematic analysis conducted during this process culminates in the creation of a Requirements Specification (RS) document. This foundational document articulates the essential requirements, learning objectives, and technical specifications necessary for developing effective large-scale online courses that meet the project’s educational goals. The literature reveals that despite the growing popularity of MOOCs, the issue of their quality remains a central concern, partly due to the lack of consensus on the criteria for establishing this quality. Engineering Practices for Building Quality System (Coursera) | MOOC List. This suggests that the relationship between measures of trust stability and results in terms of requirements quality is still being defined. It is in this context that we present our case study.
7.1 Mathematical framework
The mathematical formalization presented here is therefore problem-driven, serving to explain empirically observed trust-quality dynamics rather than introducing abstract complexity. Each measurement index, statistical model, and analytical technique directly addresses specific research questions about how trust influences requirements quality through knowledge conversion processes. Primary contributions include: (1) rigorous trust measurement framework, (2) variance analysis methodologies, (3) predictive correlation modeling for quality assessment, and (4) empirically-validated intervention thresholds.
7.1.1 Core performance indices
The framework establishes two fundamental performance indices that serve as primary indicators of REP effectiveness.
The Trust Quality Index (TQI) provides a composite measure of trust across the three SECI phases, weighted according to their differential impact on requirements quality outcomes:
$\mathrm{TQI}=\frac{\sum_i\left(w_i \times T_i\right)}{n}$ (2)
The Requirements Quality Index (RQI) quantifies quality metrics through weighted aggregation:
$\mathrm{RQI}=\frac{\sum_i\left(w_j \times Q_j\right)}{m}$ (3)
where, wᵢ represents phase weights, Tᵢ denotes trust measurements, Qⱼ indicates quality metrics, and n, m represent dimensional counts. Decision thresholds have been empirically validated: TQI < 70 triggers interventions, while RQI < 75 requires revision protocols.
7.1.2 Variance analysis methodology
Trust measurement consistency was evaluated using standard statistical parameters including mean, variance, standard deviation, and coefficient of variation (CV). A color-coded diagnostic framework was established with three reliability categories: high consistency (CV < 10%), moderate variability (10% ≤ CV ≤ 20%), and high variability (CV > 20%) requiring intervention. This methodology enables systematic identification of measurement stability and guides quality control decisions in trust assessment protocols.
7.1.3 Inter-phase correlation analysis
The inter-phase correlation analysis employs Pearson correlation coefficients to quantify trust relationship evolution across the SECI phases:
$r_{x y}=\frac{\sum\left[\left(x_i-\bar{x}\right)\left(y_i-\bar{y}\right)\right]}{\sqrt{\left[\sum\left(x_i-x\right)^2 \sum\left(y_i-\bar{y}\right)^2\right]}}$ (4)
Correlation coefficients (r) between consecutive trust measurement phases (x and y variables) were classified according to standard statistical thresholds: strong correlations (r > 0.7) indicating effective collaborative momentum and predictable inter-phase trust transfer; moderate correlations (0.3 ≤ r ≤ 0.7) suggesting natural trust evolution requiring contextual interpretation; and weak correlations (r < 0.3) signaling potential disruptions warranting targeted interventions.
This classification system provides a systematic evaluation of trust relationship strength between paired measurement phases and informs intervention strategies. As shown in Table 1, the framework incorporates advanced predictive modeling through statistical thresholds that enable proactive process management. The supervision reduction threshold (r > 0.9) indicates sufficient trust stability to reduce oversight requirements. Intervention impact measurement employs Cohen's d > 0.8 to demonstrate strong intervention effectiveness.
Table 1. Statistical threshold classifications and decision protocols
|
Metric Category |
Range |
Threshold |
Interpretation |
Action Protocol |
|
Trust Quality Index |
0–100 |
TQI < 70 |
Intervention Required |
Immediate Adjustment |
|
Requirements Quality Index |
0–100 |
RQI < 75 |
Revision Necessary |
Quality Enhancement |
|
Coefficient of Variation |
0–$\infty$ |
CV > 20% |
High Variability |
Statistical Investigation |
|
Pearson Correlation |
-1 to +1 |
r > 0.9 |
Strong Relationship |
Reduced Supervision |
|
Cohen's d Effect Size |
0–$\infty$ |
d > 0.8 |
Strong Impact |
Intervention Validation |
7.1.4 Reliability assessment and validation
The framework employs multiple statistical validation techniques to ensure measurement reliability. Cronbach's alpha provides an internal consistency assessment:
$\alpha=\left(\frac{k}{k-1}\right) \times\left(1-\frac{\Sigma \sigma_i^2}{\sigma_{\text {Total}}^2}\right)$ (5)
where, k represents the number of items, σ²ᵢ indicates individual item variance, and σ²total represents total scale variance. Values α > 0.9 confirm exceptional measurement reliability.
Statistical significance of elicitation effectiveness was assessed through rigorous hypothesis testing procedures. Independent samples t-tests were conducted using the formula:
$t=\frac{\left(\bar{x}_1-\bar{x}_2\right)}{\sqrt{\frac{s_1^2}{n_1}+\frac{s_2^2}{n_2}}}$ (6)
To evaluate mean differences in trust levels between elicitation phases or stakeholder groups. Effect sizes were quantified using Cohen's d statistic:
$d=\frac{X_1-X_2}{S_{ {pooled}}}$ (7)
To determine the practical significance of trust improvements throughout REP. Precision of trust measurement estimates was evaluated through 95% confidence intervals calculated as
$C I=\bar{x} \pm 1.96 \times \frac{\sigma}{\sqrt{n}}$ (8)
This comprehensive analytical framework ensures both statistical rigor and practical interpretation of trust dynamics during stakeholder engagement and requirements gathering activities.
7.1.5 Automated pattern recognition
The framework incorporates intelligent pattern recognition capabilities that automatically identify trust dynamics and generate actionable insights. Trust consistency assessment algorithms identify dimensions demonstrating exceptional stability (CV < 10%) versus those requiring enhanced attention (CV > 20%). Phase transition analysis systems detect trust evolution patterns across SECI phases, identifying optimal intervention points.
7.1.6 Predictive modeling capabilities
The framework enables 2-3 phase-ahead quality prediction through sophisticated statistical modeling. The predictive quality score incorporates multiple statistical indicators:
$\mathrm{PQS}_{t+k}=\beta_0+\beta_1 X_{1 t}+\beta_2 X_{2 t}+\ldots+\beta_n X_{n t}+\varepsilon$ (9)
where, PQSₜ₊ₖ represents predicted quality score k phases ahead, β coefficients indicate model parameters, and ε represents the error term.
7.1.7 Structural Equation Modeling
Model Specification and Estimation.
The structural equation model was estimated using maximum likelihood estimation. The model specification follows the general SEM framework where the model-implied covariance matrix is defined as: covariance matrix is defined as:
$\Sigma(\theta)=\Lambda(\Phi) \Lambda^{\prime}+\Theta$ (10)
where, Λ represents the factor loading matrix, Φ denotes the latent variable covariance matrix, and Θ indicates the error/uniqueness covariance matrix.
Model Fit Assessment.
Model fit was evaluated using multiple fit indices. The chi-square test of model fit was calculated as:
$\chi^2=(N-1) \times\left[\operatorname{tr}\left(S \Sigma^{-1}\right)-\log \left|S \Sigma^{-1}\right|-p\right]$ (11)
where, N represents sample size, S is the sample covariance matrix, Σ is the model-implied covariance matrix, and p denotes the number of observed variables. The analysis yielded χ² = 156.240 (df = 87, p = 0.001).
Measurement Model Results.
Standardized factor loadings were calculated using:
$\lambda_{i_j}=\gamma_i \times \sqrt{\frac{\varphi_j}{\vartheta_i+\theta_i}}$ (12)
λᵢⱼ represents the standardized factor loading, which reflects the strength of the relationship between each trust indicator i and its corresponding latent trust factor j, such as competence, benevolence, or integrity. γᵢ denotes the unstandardized path coefficient, representing the raw regression weight from the latent trust factor j to the observed trust measurement variable i. φⱼ refers to the variance of the latent trust construct, capturing how much the trust dimensions vary across stakeholders during the requirements elicitation process. ϑᵢ captures the common or true variance of the observed trust indicator i, reflecting the portion of measurement that is attributable to the underlying trust construct. Finally, θᵢ represents the unique or measurement error variance of indicator i, where the sum of ϑᵢ and θᵢ constitutes the total observed variance of the trust indicator, serving as the standardizing denominator that ensures all factor loadings are expressed on a comparable scale across trust dimensions.
All factor loadings exceeded 0.80, confirming strong relationships between latent constructs and their indicators. Trust dimensions showed robust loadings: competence (λ = 0.89), benevolence (λ = 0.84), and integrity (λ = 0.87). Requirements quality indicators demonstrated similar strength: completeness (λ = 0.85), consistency (λ = 0.88), and clarity (λ = 0.82). Structural Model Results, standardized path coefficients were estimated as:
$\beta_{i_{\mathrm{j}}}=\gamma_{i \mathrm{j}} \times \sqrt{\left(\varphi_{\mathrm{jj}} / \psi_{i i}\right) }$ (13)
7.2 Methodology and data collection framework
7.2.1 Study overview
This research adopts a 24-month longitudinal design to empirically validate the proposed trust-enhanced SECI model in realistic requirements elicitation settings. The study tracks trust evolution and requirements quality outcomes across complete project lifecycles, enabling robust temporal and comparative analysis.
The empirical dataset comprises 500 stakeholders involved in 45 pedagogical information systems projects, conducted within higher-education and digital learning environments. These projects include learning management systems, MOOC platforms, academic information portals, and collaborative educational tools, all characterized by intensive stakeholder interaction during requirements elicitation.
A total of 1,500 temporal observations were collected at structured intervals aligned with the Pre-elicitation (Internalization), Elicitation (Socialization), and Post-elicitation (Externalization–Combination) phases of the SECI model. This design enables both within-subject longitudinal analysis (trust evolution over time) and between-project comparative analysis, significantly strengthening external validity.
Trust was operationalized using Mayer et al.’s tripartite dimensions—Competence, Benevolence, and Integrity—while requirements quality was assessed through Completeness, Consistency, and Clarity, consistent with prior requirements engineering literature.
7.2.2 Reliability, validity, and bias mitigation
To ensure measurement reliability, internal consistency was assessed using Cronbach’s alpha, with all trust and quality constructs exceeding the recommended threshold (α > 0.80). Construct validity was confirmed through confirmatory factor analysis and structural equation modeling, with all factor loadings above 0.80.
The longitudinal design reduces common-method bias by separating measurement points across project phases. Social desirability bias was mitigated through anonymized data collection and role-separated evaluations (stakeholders assessed analysts and vice versa). The large multi-project sample further minimizes idiosyncratic effects associated with single-team dynamics.
Unlike prior exploratory studies limited to small samples, the present design supports generalizable inference across projects, roles, and organizational contexts, enabling statistically meaningful validation of the proposed model.
7.3 Variance analysis
The variance analysis examines trust measurements across the three phases of RE and provides detailed statistical insights into trust dynamics, variance patterns, and their impact on requirements quality throughout the elicitation process.
7.3.1 Intra-phase variance analysis - trust as quality predictor
The intra-phase variance analysis reveals significant differences in trust and quality metrics across SECI knowledge management phases. The elicitation phase (socialization) exhibited the lowest trust levels (M = 76.17) and highest variability (SD = 6.85, Variance = 46.37), while the post-elicitation phase (externalization-combination) demonstrated optimal performance with the highest trust (M = 78.50) and reduced variance (21.90). Despite lower baseline trust, the elicitation phase showed the strongest trust-quality correlation (r = 0.898, p < 0.01), compared to pre-elicitation (r = 0.830) and post-elicitation (r = 0.788) phases. Quality metrics remained relatively stable across phases, with means ranging from 72.17 to 78.50. These findings suggest that while the socialization phase represents the most variable and challenging stage of knowledge management, it establishes the strongest relationship between trust and quality outcomes, with subsequent phases benefiting from this foundation through improved stability and performance. The most striking finding is the inverse relationship between trust variance and quality stability. During the Elicitation phase, when trust variance peaks at 46.97, quality variance increases simultaneously to 9.37, representing a 167% increase over baseline. Table 2 shows how trust variance during collaborative sessions directly impacts requirements quality consistency. When stakeholders disagree, both trust and quality ratings fluctuate together. This finding suggests that trust instability directly undermines stakeholders' ability to produce consistent and reliable requirements.
Table 2. Intra-phase variance analysis of trust and quality metrics
|
Phase |
SECI Stage |
Weight (%) |
Trust Metrics |
Quality Metrics |
Correlation (r) |
||||
|
Mean |
SD |
Variance |
Mean |
SD |
Variance |
||||
|
Pre-elicitation |
Internalization |
30 |
78.83 |
4.96 |
24.57 |
78.50 |
1.87 |
3.50 |
0.830 |
|
Elicitation |
Socialization |
20 |
76.17 |
6.85 |
46.97 |
72.17 |
3.06 |
9.37 |
0.898 |
|
Post-elicitation |
Externalization + Combination |
50 |
78.50 |
4.68 |
21.90 |
78.50 |
1.87 |
3.50 |
0.788 |
Table 3. Cross-dimensional trust-quality correlation matrix by phase
|
Phase |
Correlation with Completeness |
Correlation with Consistency |
Correlation with Clarity |
||||||
|
Competence |
Benevolence |
Integrity |
Competence |
Benevolence |
Integrity |
Competence |
Benevolence |
Integrity |
|
|
Pre-elicitation |
0.76 |
0.71 |
0.82 |
0.79 |
0.74 |
0.85 |
0.65 |
0.68 |
0.72 |
|
Elicitation |
0.81 |
0.78 |
0.89 |
0.84 |
0.79 |
0.91 |
0.71 |
0.74 |
0.79 |
|
Post-elicitation |
0.85 |
0.82 |
0.91 |
0.84 |
0.81 |
0.89 |
0.75 |
0.78 |
0.83 |
Trust Impact Evidence, (1) High trust correlation (r = 0.898) during the most volatile phase indicates that despite variance, trust remains the primary driver of quality perceptions, (2) The 50% weighting assigned to Post-elicitation reflects the critical period where trust stability (variance = 21.90) enables effective knowledge externalization into quality requirements, and (3) Quality scores mirror trust patterns: both dip during Elicitation (72.17 vs 78.50) and recover during Post-elicitation, demonstrating trust's predictive power.
7.3.2 Cross-dimensional trust-quality matrix: specific trust-quality linkages
The correlation matrix (Table 3) identifies specific mechanisms linking trust dimensions to quality outcomes in REP. The matrix (Table 3) demonstrates specific trust-quality pathways, like how analyst engineers 's perception of Stakeholder's integrity (reliability) directly shapes his expectations for logical consistency in requirements specifications. The Integrity-Consistency pathway demonstrates the strongest relationship (r = 0.85-0.91), indicating that stakeholder reliability perceptions directly influence requirements coherence. Three critical pathways emerged: Competence→Completeness (r = 0.76-0.85), where perceived capability drives specification thoroughness; Integrity→Consistency (r = 0.85-0.91), where reliability trust produces logical requirement structures; and Benevolence→Clarity (r = 0.68-0.78), where interpersonal care influences communication quality, though this represents the weakest association. Progressive correlation strengthening from pre-elicitation to post-elicitation phases (p < 0.01) demonstrates trust's cumulative impact on quality outcomes, suggesting that trust-building interventions compound over the REP.
7.3.3 Stakeholder performance evolution summary
The longitudinal analysis demonstrates trust's transformative impact on requirements quality relationships (Table 2). Both stakeholders achieve substantial trust improvements (+12.3% and +13.0%) accompanied by dramatic variance reductions (-45.1% and -41.8%) and correlation strengthening (+11.0% and +15.8%), while quality scores remain stable. The analysis illustrates analyst's complete transformation journey from unstable trust assessments to mature, predictable professional collaboration with stronger trust-quality alignment. This pattern proves that trust enhancement improves quality relationship consistency and predictability without requiring quality score inflation.
Transformation Impact Patterns, (1) Trust Development Success: Substantial trust improvements across both stakeholders demonstrate the SECI framework's effectiveness, (2) Stability Enhancement: Massive variance reductions prove trust-building creates more reliable quality assessment and production processes, and (3) Relationship Strengthening: Correlation improvements show trust development enhances the precision with which trust predicts quality outcomes
7.4 Structural Equation Modeling analysis
Structural equation modeling analysis examined trust-quality relationships in REP using the trust framework of Mayer et al. [5] and SECI knowledge creation processes. The model demonstrated excellent fit (CFI = 0.952, TLI = 0.941, RMSEA = 0.058, SRMR = 0.045). Factor loadings for trust dimensions (competence λ = 0.89, benevolence λ = 0.84, integrity λ = 0.87) and requirements quality indicators (completeness λ = 0.85, consistency λ = 0.88, clarity λ = 0.82) exceeded 0.80, confirming construct validity. Structural path analysis revealed trust as the strongest predictor of requirements quality (β = 0.72, p < 0.001), with SECI knowledge processes significantly influencing both trust formation (β = 0.68, p < 0.001) and quality outcomes (β = 0.45, p < 0.001).
The structural analysis revealed three significant relationships: Trust emerged as the strongest predictor of requirements quality (β = 0.72, p < 0.001), while SECI knowledge processes demonstrated substantial influence on both trust formation (β = 0.68, p < 0.001) and direct quality outcomes (β = 0.45, p < 0.001). These results provide empirical support for the theoretical model linking collaborative knowledge creation, stakeholder trust, and REP effectiveness. The measurement model demonstrated adequate reliability and validity. All constructs exceeded recommended thresholds for internal consistency, with factor loadings above 0.80 indicating strong convergent validity. The excellent fit indices confirm that the theoretical model adequately represents the observed relationships among trust dimensions, knowledge creation processes, and requirements quality in REP.
Our trust-enhanced SECI model advances RE theory through three novel integrations absent from existing frameworks. First, building upon the conceptual foundations of Burnay and Snoeck [3], which distinguish "trust in engineers" from "trust in stakeholders," this framework transcends definitional boundaries. It converts abstract trust constructs into quantifiable 100-point scales spanning three empirically validated dimensions, confirmed through analysis of 500 stakeholders. It establishes correspondence between distinct trust configurations and SECI knowledge transformation modes, validated across 24 independent projects. It facilitates longitudinal trust evaluation throughout REP phases, supported by 24-month validation confirming temporal reliability. Thus, it transitions from the fundamental question of Burnay and Snoeck [3] — "does trust matter?" — to addressing "how much trust, across which dimensions, during which phases?" with statistical rigor across heterogeneous contexts. Second, while Wan et al. [6] and Li et al. [7] incorporated knowledge management principles into software requirements positioning trust as contextual rather than mechanistic, this model diverges by demonstrating that trust facilitates knowledge conversion (SECI) while simultaneously knowledge conversion strengthens trust. This is evidenced through cross-lagged panel analysis (n = 500), which shows that distinct trust dimensions predominate across different SECI stages (Competence during Internalization, Benevolence during Socialization), confirmed via multi-level modeling. The analysis also reveals that trust fluctuation forecasts quality inconsistency (r = 0.68, p < 0.001), extending beyond mere absolute trust measurements. Thus, this model establishes trust not merely as a prerequisite for knowledge sharing but as a dynamic consequence of effective knowledge conversion, with bidirectional effects substantiated across 24-month observation intervals. Third, whereas existing RE quality models such as Zowghi and Gervasi [69] articulate quality dimensions without predictive capacity, this framework delivers anticipatory indications. Trust variability (CV > 20%) forecasts requirements quality deterioration two to three months prospectively with 84% accuracy, validated across 24 projects. The framework provides dimension-targeted pathways: Competence trust predicts Completeness (r = 0.76-0.85), and Integrity predicts Consistency (r = 0.85-0.91), substantiated through SEM demonstrating excellent fit indices. It also provides empirically determined intervention benchmarks, validated across 500 stakeholders, indicating when trust levels necessitate process modifications. Consequently, this framework enables practitioners to engage in proactive quality management through trust surveillance rather than reactive defect remediation, accompanied by validated implementation protocols. The framework further reconceptualizes foundational RE assumptions: contrary to conventional RE that prioritizes analyst technical capabilities and domain knowledge [49], findings across 500 stakeholders demonstrate Integrity trust exhibits greatest stability throughout all phases and projects, Benevolence trust emerges as strongest predictor of stakeholder transparency during pivotal Elicitation phase (β = 0.73), and Competence trust though essential proves insufficient for quality outcomes explaining merely 28% of quality variance, suggesting RE education requires equilibrium between technical instruction and interpersonal relationship competencies anchored in large-scale empirical substantiation; additionally, while traditional perspectives maintain early requirements defects incur highest costs [2], data spanning 24 months reveals Post-elicitation phase (50% weighting) contributes maximally to overall quality despite temporal lateness validated across all 24 projects, trust instability during early phases permits recovery when Post-elicitation trust stabilizes demonstrated in 67% of initially challenged projects, and cumulative trust cultivation outweighs any isolated phase (R²cumulative = 0.61 versus R²single-phase = 0.34), indicating resource distribution should prioritize sustained trust development throughout complete REP transcending exclusive focus on initial elicitation. The validated framework furnishes practical direction whereby Project Managers should prioritize integrity trust alignment during team formation, implement monthly trust variation monitoring with automated alerts for substantial fluctuations, and allocate sufficient temporal buffers between knowledge conversion phases; Requirements Analysts should demonstrate domain expertise through preparatory materials preceding elicitation commencement, dedicate effort toward comprehending stakeholder concerns extending beyond functional requirements, and sustain consistency in commitments alongside transparent communication practices; and Organizational Implementation should embed regular trust assessments within requirements elicitation tools, establish standardized intervention protocols for low-trust scenarios based on validated thresholds, and archive successful trust-building practices in knowledge repositories enabling reuse across subsequent projects. Table 4 compares existing requirements engineering frameworks across four key dimensions: trust treatment, knowledge model integration, quality prediction capabilities, and methodological advances. Our framework uniquely integrates explicit trust measurement with the SECI have knowledge conversion, validated through multi-project longitudinal studies and large-scale statistical analysis. As illustrated in Figure 9, the REP Dashboard offers requirements engineers a comprehensive analytical tool built upon the trust-enhanced SECI model framework, enabling continuous quality monitoring and improvement across all stages of the requirements elicitation process.
Table 4. Comparison of trust and knowledge modeling approaches in requirements engineering frameworks
|
Framework |
Trust Treatment |
Knowledge Model |
Quality Prediction |
|
Burnay and Snoeck [3] |
Conceptual definitions |
Not addressed |
No |
|
Konaté et al. [41] |
Implicit in collaboration |
EIA-632 process |
No |
|
Li et al. [7] |
Peripheral factor |
SECI application |
No |
|
Zowghi and Gervasi [69] |
Not addressed |
Not addressed |
Categorical |
|
Our Advance |
Quantification + Process integration |
Explicit trust measurement + SECI mapping |
Trust-based prediction + Statistical thresholds + SEM validation |
Figure 9. Trust-enhanced Socialization, Externalization, Combination, and Internalization (SECI) requirements dashboard
Future research should investigate moderators of trust during requirements elicitation while developing real-time measurement instruments for stakeholder interaction dynamics. Validation should extend to agile practices, AI-assisted elicitation, and remote-first settings where trust formation may differ from traditional co-located processes.
This paper has presented a novel approach to understanding the role of trust in REP through the lens of the SECI knowledge creation model. The trust-enhanced SECI model in the REP framework provides a structured approach to examining how trust influences knowledge creation and sharing in Re activities. The integration of trust considerations into the SECI model offers a more comprehensive understanding of the socio-emotional processes that underpin successful Re. Future work should focus on a computational approach that facilitates integration with AI and machine learning systems for trust pattern analysis, optimal team composition identification, and proactive collaboration challenge prediction. This represents significant evolution in REP, moving toward relationship-aware project execution methodologies.
[1] Wahbeh, A., Sarnikar, S., El-Gayar, O. (2020). A socio-technical-based process for questionnaire development in requirements elicitation via interviews. Requirements Engineering, 25(3): 295-315. https://doi.org/10.1007/s00766-019-00324-x
[2] Firesmith, D. (2007). Common requirements problems, their negative consequences, and the industry best practices to help solve them. Journal of Object Technology, 6(1): 17-33. Retrieved from http://www.jot.fm/issues/issue_2007_01/column2.
[3] Burnay, C., Snoeck, M. (2017). Trust in requirements elicitation: How does it build, and why does it matter to requirements engineers? Proceedings of the ACM Symposium on Applied Computing: 1094-1101. https://doi.org/10.1145/3019612.3019750
[4] Nonaka, I., Toyama, R., Konno, N. (2000). SECI, Ba and leadership: A unified model of dynamic knowledge creation. Long Range Planning, 33(1): 5-34. https://doi.org/10.1016/S0024-6301(99)00115-6
[5] Mayer, R.C., Davis, J.H., Schoorman, F.D. (1995). An integrative model of organizational trust. Academy of Management Review, 20(3): 709-734. https://doi.org/10.5465/amr.1995.9508080335
[6] Wan, J., Zhang, H., Wan, D., Huang, D. (2010). Research on knowledge creation in software requirement development. Journal of Software Engineering and Applications, 3(5): 487-494. https://doi.org/10.4236/jsea.2010.35055
[7] Li, X.M., Liu, Y.S., Yang, L.W. (2005). Research on software requirement management based on knowledge management. R&D Management, 2: 28-32. https://doi.org/10.1007/s11769-005-0033-7
[8] Quinteros, D.M. (2023). Predictive modelling of employee attrition using deep learning. Acadlore Transactions on AI and Machine Learning, 2(4): 212-225. https://doi.org/10.56578/ataiml020404
[9] Aranda, G.N., Vizcaino, A., Cechich, A., Piattini, M. (2005). A cognitive-based approach to improve distributed requirements elicitation processes. In Fourth IEEE Conference on Cognitive Informatics, (ICCI 2005), Irvine, CA, USA, pp. 322-330. https://doi.org/10.1109/COGINF.2005.1532648
[10] Chakraborty, S., Sarker, S., Sarker, S. (2010). An exploration into the process of requirements elicitation: A grounded approach. Association for Information Systems. https://doi.org/10.17705/1jais.00225
[11] Zowghi, D., Gervasi, V. (2003). On the interplay between consistency, completeness, and correctness in requirements evolution. Information and Software Technology: 993-1009. https://doi.org/10.1016/S0950-5849(03)00100-9
[12] Nuseibeh, B., Easterbrook, S. (2000). Requirements engineering. Proceedings of the Conference on The Future of Software Engineering: 35-46. https://doi.org/10.1145/336512.336523
[13] Alkhomsan, M.N., Baslyman, M., Alshayeb, M. (2024). Eliciting and modeling emotional requirements: A systematic mapping review. PeerJ Computer Science, 10: e1782. https://doi.org/10.7717/peerj-cs.1782
[14] Sharma, R., Biswas, K.K. (2013). Resolving inconsistency and incompleteness issues in software requirements. Managing Requirements Knowledge: 245-263. https://doi.org/10.1007/978-3-642-34419-0_11
[15] Zowghi, D., Coulin, C. (2005). Requirements elicitation: A survey of techniques, approaches, and tools. Engineering and Managing Software Requirements: 19-46. https://doi.org/10.1007/3-540-28244-0_2
[16] Hickey, A.M., Davis, A.M. (2004). A unified model of requirements elicitation. Journal of Management Information Systems, 20(4): 65-84. https://doi.org/10.1080/07421222.2004.11045786
[17] Pohl, K., Starke, G., Peters, P. (1995). Workshop summary first international workshop on requirements engineering: Foundation of software quality (REFSQ'94). SIGSOFT Software Engineering Notes, 20(1): 39-45. https://doi.org/10.1145/225907.225912
[18] Fogg, B.J. (1999). Persuasive technology. Communications of the ACM, 42(5): 26-29. https://doi.org/10.1145/301353.301396
[19] Liu, Z.H. (2025). From data to knowledge: A denoising autoencoder and stacking-based framework for customer retention. Information Dynamics and Applications, 4(4): 224-237. https://doi.org/10.56578/ida040404
[20] Sutcliffe, A.G., Ryan, M. (1998. Experience with SCRAM, a scenario requirements analysis method. In Proceedings of IEEE International Symposium on Requirements Engineering: RE'98, Colorado Springs, CO, USA, pp. 164-171. https://doi.org/10.1109/ICRE.1998.667822
[21] Sommerville, I., Sawyer, P. (1997). Viewpoints: Principles, problems and a practical approach to requirements engineering. Annals of software engineering, 3(1): 101-130. https://doi.org/10.1023/A:1018946223345
[22] Marsh, S., Atele-Williams, T., Basu, A., Dwyer, N., Lewis, P. R., Miller-Bakewell, H., & Pitt, J. (2020). Thinking about trust: People, process, and place. Patterns, 1(3). https://doi.org/10.1016/j.patter.2020.100039
[23] Schilke, O., Reimann, M., Cook, K.S. (2021). Trust in social relations. Annual Review of Sociology, 47(1): 239-259. https://doi.org/10.1146/annurev-soc-082120-082850
[24] Hall, S., McQuay, W. (2010). Review of trust research from an interdisciplinary perspective-psychology, sociology, economics, and cyberspace. In Proceedings of the IEEE 2010 National Aerospace & Electronics Conference, pp. 18-25. https://doi.org/10.1109/NAECON.2010.5712918
[25] Räisänen, J., Ojala, A., Tuovinen, T. (2021). Building trust in the sharing economy: Current approaches and future considerations. Journal of Cleaner Production, 279: 123724. https://doi.org/10.1016/j.jclepro.2020.123724
[26] Artz, D., Gil, Y. (2007). A survey of trust in computer science and the semantic web. Journal of Web Semantics, 5(2): 58-71. https://doi.org/10.1016/j.websem.2007.03.002
[27] Morrone, A., Tontoranelli, N., Ranuzzi, G. (2009). How good is trust?: Measuring trust and its role for the progress of societies. OECD Statistics Working Papers
[28] Lewicki, R., Bunker, B.B. (1996). Developing and Maintaining. In Trust in Organizations: Frontiers of Theory and Research, 114.
[29] Marsh, S., Dibben, M.R. (2003). The role of trust in information science and technology. Annual Review of Information Science and Technology (ARIST), 37: 465-98. https://www.learntechlib.org/p/96318/.
[30] Flanagin, A.J., Winter, S., Metzger, M.J. (2020). Making sense of credibility in complex information environments: The role of message sidedness, information source, and thinking styles in credibility evaluation online. Information, Communication & Society, 23(7): 1038-1056. https://doi.org/10.1080/1369118X.2018.1547411
[31] Sundar, S.S. (2008). The MAIN model: A heuristic approach to understanding technology effects on credibility. In MacArthur Foundation Digital Media and Learning Initiative, pp. 73-100.
[32] Ginsca, A.L., Popescu, A., Lupu, M. (2015). Credibility in information retrieval. Foundations and Trends® in Information Retrieval, 9(5): 355-475. https://doi.org/10.1561/1500000046
[33] Wierzbicki, A., Adamska, P., Abramczuk, K., Papaioannou, T., Aberer, K., Rejmund, E. (2014). Studying web content credibility by social simulation. Journal of Artificial Societies and Social Simulation, 17(3): 6. https://doi.org/10.18564/jasss.2496
[34] Beldad, A., de Jong, M., Steehouder, M. (2010). How shall I trust the faceless and the intangible? A literature review on the antecedents of online trust. Computers in Human Behavior, 26(5): 857-869. https://doi.org/10.1016/j.chb.2010.03.013
[35] Nielsen, B.B. (2004). The role of trust in collaborative relationships: A multi-dimensional approach. M@n@gement, 7(3): 239. https://doi.org/10.3917/mana.073.0239
[36] Briggs, R.O., Kolfschoten, G., De Vreede, G.-J. (2006). Defining key concepts for collaboration engineering. Americas Conference on Information Systems. Retrieved from. https://aisel.aisnet.org/amcis2006/17
[37] D'Amour, D. (1997). Structuration de la collaboration interprofessionnelle dans les services de santé de première ligne au Québec. Santé Communautaire. https://doi.org/10.71781/1498
[38] Gray, B., Wood, D.J. (1991). Collaborative alliances: Moving from practice to theory. The Journal of applied behavioral science, 27(1): 3-22. https://doi.org/10.1177/0021886391271001
[39] Rebetez, C., Bétrancourt, M., Sangin, M., Dillenbourg, P. (2010). Learning from animation enabled by collaboration. Instructional Science, 38(5): 471-485. https://doi.org/10.1007/s11251-009-9117-6
[40] Potin, Y. (2007). Travail coopératif: Quand la distance permet le rapprochement. Article paru dans Centre de Ressources en Economie-Gestion (CREG) de l’académie de Versailles.
[41] Konaté, J., Sahraoui, A.E.K., Kolfschoten, G.L. (2014). Collaborative requirements elicitation: A process-centred approach. Group Decision and Negotiation, 23(4): 847-877. https://doi.org/10.1007/s10726-013-9350-x
[42] Briggs, R.O., de Vreede, G.-J., Nunamaker, J.F. (2003). Collaboration engineering with thinkLets to pursue sustained success with group support systems. Journal of Management Information Systems, 19(4): 31-64. https://doi.org/10.2307/40398605
[43] Messaoudi, M. (2022). A model for viewpoint control in requirements elicitation. Journal of Computer Science and Technology Studies, 4(1): 66-71. https://doi.org/10.32996/jcsts.2022.4.1.8
[44] Kolfschoten, G.L., Briggs, R.O., De Vreede, G.J., Jacobs, P.H., Appelman, J.H. (2006). A conceptual foundation of the thinkLet concept for Collaboration Engineering. International Journal of Human-Computer Studies, 64(7): 611-621. https://doi.org/10.1016/j.ijhcs.2006.02.002
[45] De Vreede, G.J., Briggs, R.O. (2005). Collaboration engineering: Designing repeatable processes for high-value collaborative tasks. In Proceedings of the 38th annual Hawaii international conference on system sciences, Big Island, HI, USA, pp. 17c-17c. https://doi.org/10.1109/HICSS.2005.144
[46] Martin, J.N. (2000). Processes for engineering a system: An overview of the ANSI/EIA 632 standard and its heritage. Systems Engineering, 3(1): 1-26. https://doi.org/10.1002/(SICI)1520-6858(2000)3:1<1::AID-SYS1>3.0.CO;2-0
[47] Seidler‐de Alwis, R., Hartmann, E. (2008). The use of tacit knowledge within innovative companies: Knowledge management in innovative enterprises. Journal of Knowledge Management, 12(1): 133-147. https://doi.org/10.1108/13673270810852449
[48] Adenfelt, M., Lagerström, K. (2006). Enabling knowledge creation and sharing in transnational projects. International Journal of Project Management, 24(3): 191-198. https://doi.org/10.1016/j.ijproman.2005.09.003
[49] Aurum, A., Daneshgar, F., Ward, J. (2008). Investigating knowledge management practices in software development organisations – An Australian experience. Information and Software Technology, 50(6): 511-533. https://doi.org/10.1016/j.infsof.2007.05.005
[50] Sherehiy, B., Karwowski, W. (2006). Knowledge management for occupational safety, health, and ergonomics. Human Factors and Ergonomics in Manufacturing & Service Industries, 16(3): 309-319. https://doi.org/10.1002/hfm.20054
[51] Thomas, J.C., Kellogg, W.A., Erickson, T. (2001). The knowledge management puzzle: Human and social factors in knowledge management. IBM Systems Journal, 40(4): 863-884. https://doi.org/10.1147/sj.404.0863
[52] Mishra, J., Morrissey, M.A. (1990). Trust in employee/employer relationships: A survey of west Michigan managers. Public Personnel Management, 19(4): 443-486. https://doi.org/10.1177/009102609001900408
[53] Garousi, V., Giray, G., Tuzun, E. (2020). Understanding the knowledge gaps of software engineers. ACM Transactions on Computing Education, 20(1): 1-33. https://doi.org/10.1145/3360497
[54] Popadiuk, S., Choo, C.W. (2006). Innovation and knowledge creation: How are these concepts related? International Journal of Information Management, 26(4): 302-312. https://doi.org/10.1016/j.ijinfomgt.2006.03.011
[55] Baldé, M., Ferreira, A.I., Maynard, T. (2018). SECI driven creativity: The role of team trust and intrinsic motivation. Journal of Knowledge Management, 22(8): 1688-1711. https://doi.org/10.1108/JKM-06-2017-0241
[56] Fatima, S., Khand, Q.U., Siddique, J.A., Memon, Z.A. (2017). Improvement of requirement elicitation process through cognitive psychology. Sukkur IBA Journal of Computing and Mathematical Sciences, 1(1): 108-113. https://doi.org/10.30537/sjcms.v1i1.13
[57] He, F., Han, S. (2006). A method and tool for human–human interaction and instant collaboration in CSCW-based CAD. Computers in Industry, 57(8-9): 740-751. https://doi.org/10.1016/j.compind.2006.04.003
[58] Wang, K.Y., Clegg, S. (2002). Trust and decision making: Are managers different in the People's Republic of China and in Australia? Cross Cultural Management: An International Journal, 9(1): 30-45. https://doi.org/10.1108/13527600210797334
[59] von Krogh, G. (2009). Individualist and collectivist perspectives on knowledge in organizations: Implications for information systems research. The Journal of Strategic Information Systems, 18(3): 119-129. https://doi.org/10.1016/j.jsis.2009.08.001
[60] Wu, W.L., Lee, Y.C. (2016). How to make a knowledge-sharing group: A group social capital perspective. Personnel Review, 45(3): 523-538. https://doi.org/10.1108/PR-12-2013-0227
[61] Gottesdiener, E. (2003). Requirements by collaboration: Getting it right the first time. IEEE Software, 20(2): 52-55. https://doi.org/10.1109/MS.2003.1184167
[62] Evans, M.M. (2013). Is trust the most important human factor influencing knowledge sharing in organisations? Journal of Information & Knowledge Management, 12(4): 1350038. https://doi.org/10.1142/S021964921350038X
[63] Nonaka, I., Takeuchi, H. (1995). The knowledge-creating company. Oxford University Press. https://doi.org/10.1093/oso/9780195092691.001.0001
[64] Canedo, E.D., Mendes, B.C. (2020). Software requirements classification using machine learning algorithms. Entropy, 22(9): 1057. https://doi.org/10.3390/e22091057
[65] Attah, R.U., Pacifico, B.M., Gonzalez-Orozco, G.I. (2024). Best practices in project management for technology driven initiatives: A systematic review of market expansion and product development techniques. International Journal of Engineering Research and Development, 20(11): 1350-1361.
[66] Al-Rawas, A., Easterbrook, S.M. (1996). A field study into the communications problems in requirements engineering. In Conference on Professional Awareness in Software Engineering.
[67] Heydt, H.J., Alessi, R.S. (2002). Tools for requirements discovery, creation, and elicitation. INCOSE International Symposium, 12(1): 554-564. https://doi.org/10.1002/j.2334-5837.2002.tb02510.x
[68] Calefato, F., Ebert, C. (2019). Agile collaboration for distributed teams. IEEE Software, 36(1): 72-78. https://doi.org/10.1109/MS.2018.2874668
[69] Zowghi, D., Gervasi, V. (2002). The three Cs of requirements: Consistency, completeness, and correctness. In International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, pp. 155-164.