Method for elicitation, documentation and validation of software user requirements (MEDoV)

Dragicevic, Srdjana; Celar, Stipe

doi:10.1109/iscc.2013.6755073

Cited by 8 publications

(4 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Method for Elicitation, Documentation and Validation of Software User Requirements (MEDoV) [140], [141] 2…”

Section: Elicitation Methods To Understand Business Processesmentioning

confidence: 99%

Elicitation Approaches and Techniques for Automating Business Processes

Menezes¹

2022

Preprint

View full text Add to dashboard Cite

<p>Several organizations have invested in business process automation software to improve their processes. Unstandardized processes with high variance and unstructured data encumber the requirements elicitation for business process automation software. This study conducted a literature review to discover methods for understanding business processes and eliciting requirements for business process automation software. The review revealed many methods used to understand business processes, but only one was employed to elicit requirements for business process automation software. In addition, the review identified some challenges with methods for eliciting requirements in this context.</p>

show abstract

“…Method for Elicitation, Documentation and Validation of Software User Requirements (MEDoV) [140], [141] 2…”

Section: Elicitation Methods To Understand Business Processesmentioning

confidence: 99%

Elicitation Approaches and Techniques for Automating Business Processes

Menezes¹

2022

Preprint

View full text Add to dashboard Cite

show abstract

“…The significance of the human factor at the requirements elicitation stage has been studied by different researchers [12], [13], [14], [15], [16], [17], [18]. For example, Fuentes et al [12] presented a comprehensive Unified Modeling Language (UML) schemata for social issues, providing patterns in order to reconcile stakeholder conflicts.…”

Section: Introductionmentioning

confidence: 99%

“…In addition, it is believed that the elicitation process should involve any factor that might impact the developed system or its use in terms of meeting the customers' needs [12]. Dragicevic and Celar [13] presented a method for requirement elicitation, documentation, and validation called MeDoV. Even-driven process (EPC) and UML activity diagrams were used to model requirements.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Multi-Criteria Decision-Making Approach for Selection of Requirements Elicitation Techniques based on the Best-Worst Method

Aljuhani¹

2021

IJACSA

View full text Add to dashboard Cite

During requirements elicitation stage, requirements engineers gather system requirements and drive stakeholders to convey needs and desired software functionality. The elicitation techniques used to acquire software requirements significantly impact the quality of elicited requirements. Several elicitation techniques have been proposed for the Requirement Engineering (RE) process; however, these techniques are rarely used in reality due to a lack of empirical and relative appraisals to assist software team members in deciding on the most appropriate technique. Requirement engineers encounter difficulty in deciding the suitable elicitation technique to adopt for a certain software project. This difficulty is due to a lack of knowledge regarding the available elicitation techniques, their efficacy, and how appropriate they are for a certain project. According to the literature, requirements engineering processes benefit from the use of Multi-Criteria Decision-Making (MCDM) approaches within particular contexts. An optimal structure is constitutionally presented within the area of the requirements engineering process; hence, the demonstration of a robust decision-making method in the requirements engineering process should motivate a higher level of satisfaction with software projects developed in this way. This study proposes an approach for using the MCDM method in the requirements engineering process. The study contains a model for investigating the selection of an appropriate elicitation technique based on a decision-making method, namely, the Best-Worst Method (BWM). The findings of the proposed model demonstrate the BWM's power in solving complex decision problems involving several criteria and alternatives.

show abstract

A Controlled Experiment on Comparison of Data Perspectives for Software Requirements Documentation

Ibriwesh

Chai

et al. 2017

Arab J Sci Eng

View full text Add to dashboard Cite

Method for elicitation, documentation and validation of software user requirements (MEDoV)

Cited by 8 publications

References 20 publications

Elicitation Approaches and Techniques for Automating Business Processes

Elicitation Approaches and Techniques for Automating Business Processes

Multi-Criteria Decision-Making Approach for Selection of Requirements Elicitation Techniques based on the Best-Worst Method

A Controlled Experiment on Comparison of Data Perspectives for Software Requirements Documentation

Contact Info

Product

Resources

About