A socio-technical-based process for questionnaire development in requirements elicitation via interviews
2019
- 580Usage
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage580
- Downloads562
- Abstract Views18
Article Description
Software development is the process of building systems that solve users’ need and satisfy stakeholders’ objectives. Such needs are determined through requirements elicitation, which is considered an intensive, complex, and multi-disciplinary process. Traditional methods of elicitation often fail to uncover requirements that are critical for successful and wide-scale user adoption because these methods primarily focus on the technical aspects and constraints of the systems rather than considering a socio-technical perspective. The success of information system development involves the identification of the social, organizational and technical features of the systems, which in turn can result in a more acceptable system by users. In this paper, we propose a requirements elicitation process based on socio-technical (ST) systems theory. The process leverages ST system components to help identify a set of ST imbalances, which in turn help in requirements elicitation. The applicability of the process is demonstrated using empirical investigation with a randomized two-group experimental design, where the objective is to see the potential of the proposed process to enhance analysts’ understanding of socio-technical aspects of a domain, interview readiness, and questionnaire quality.
Bibliographic Details
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know