Ask Experts: Explicitation/Implicitation and Elicitation; two commonly used but barely unraveled concepts
Last updated: January 15, 2024 Read in fullscreen view
- 02 Nov 2023 Differences between software walkthrough, review, and inspection
- 20 Mar 2022 What is a Multi-Model Database? Pros and Cons?
- 03 Jul 2022 What is the difference between Project Proposal and Software Requirements Specification (SRS) in software engineering?
- 05 Jul 2020 What is Sustaining Software Engineering?
- 01 Oct 2020 Fail fast, learn faster with Agile methodology
What is the Explicitation strategy?
Explicitation is a technique of making explicit in the target text information what is implicit in the source text. Explicitation (implicitation) strategies are generally discussed together with addition (omission) strategies.
What is the difference between Explicitation and Implicitation?
The discussion of explicitation usually involves implicitation. This might be attributable to the fact that explicitation in, its simplest forms, involves addition, whereas, implicitation involves deletion or omission.
What is the Elicitation technique?
Elicitation is a critical part of the “Collect Requirements” process of the Scope Management that helps to derive and extract information from stakeholders or other sources.
What is an Elicitation strategy?
Elicitation techniques include interviews, observation of either naturally occurring behavior (including as part of participant observation) or behavior in a laboratory setting, or the analysis of assigned tasks.
What is Elicitation of business requirements?
What is requirements elicitation? Business analysts conduct requirements elicitation to identify the business need, scope, assumptions, and risks of a project based on data from key stakeholders.
What is Elicitation in business analysis?
In business analysis, elicitation, however, does not involve magic or trickery. It refers to a structured approach aimed to "draw out" information and forge a consensus among Subject Matter Experts (SMEs) regarding the requirements of application/software development.
What is the difference between Elicitation and Acquisition?
Knowledge elicitation consists of a set of techniques and methods that attempt to elicit the knowledge of a domain expert1 , typically through some form of direct interaction with the expert. Knowledge elicitation is a sub-process of knowledge acquisition (which deals with the acquisition or capture of knowledge from any source), and knowledge acquisition is, in turn, a sub-process of knowledge engineering (which is a discipline that has evolved to support the whole process of specifying, developing and deploying knowledge-based systems).