Requirement Elicitation Techniques for Software Projects in Ukrainian IT: An Exploratory Study

Gobov, Denys; Huchenko, Inna

doi:10.15439/2020f16

Cited by 12 publications

(15 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Recently, several surveys were conducted among Polish and Ukrainian IT specialists on various aspects of Requirements Engineering, such as requirements elicitation [8,9] or specification [10,19,20].…”

Section: Surveys and Experiments With Industrymentioning

confidence: 99%

What Should a Good Software Requirements Specification Include? Results of a Survey

Rączkowska-Gzowska

Walkowiak-Gall

2023

Foundations of Computing and Decision Sciences

View full text Add to dashboard Cite

Software requirements specification is an important foundation of the software development process. It documents the requirements, expectations, and restrictions for a system to be developed. It should describe what the produced system will offer in detail and unambiguously. It should also provide a realistic basis for estimating product costs, risks, and schedules. Still, it is difficult to prepare a useful specification effectively. We want to propose an approach to creating a good specification. We started the work from scratch by determining what the scope of the specification should be. We asked people who work on IT projects what information is and should be included in the specifications with which they work. This paper presents results from a survey conducted with 163 participants who have experience working on commercial software development projects. The main observation is that the content of requirements specification differs with respect to project characteristics, such as industry or financing method. We also noticed that the information about integration with external systems and functionalities most often appears in the SRS.

show abstract

Section: Surveys and Experiments With Industrymentioning

confidence: 99%

What Should a Good Software Requirements Specification Include? Results of a Survey

Rączkowska-Gzowska

Walkowiak-Gall

2023

Foundations of Computing and Decision Sciences

View full text Add to dashboard Cite

show abstract

“…The specification and modelling techniques long list was created based on the techniques from different sources (see Table 1), namely PMI [1], IIBA [6], Pohl [7], and Paul [8]. [20], with a focus on the Elicitation and Collaboration topic. This article briefly describes the questionnaire design and concentrates on its Analysis and Design section.…”

Section: Related Workmentioning

confidence: 99%

“…Q2: Requirements Elicitation and Collaboration. This section was described in [20]. We are interested in elicitation sources, techniques, and project roles within the given questions category, which has primary responsibility for the solution requirements (functional, non-functional requirements) elicitation on the respondent's ongoing project.…”

Section: Related Workmentioning

confidence: 99%

Practical Study on Software Requirements Specification and Modelling Techniques

Gobov¹

2023

IJC

View full text Add to dashboard Cite

The quality of specified and modeled requirements is critical for IT project success. A significant number of specialized techniques are used for documenting the requirements. The selection of the appropriate technique considerably influences a project plan and the success of a change as a whole. This paper aims to examine practitioners’ industrial standards and experience in the requirements specification activities and identify factors influencing the choice of specific techniques. To get the data from business analysis practitioners, we carried out a survey involving 328 specialists from Ukrainian IT companies and a series of interviews with experts. A list of specification and modelling techniques is selected based on international standards and bodies of knowledge. Project context and participants’ background inﬂuence on the probability of particular technique selection are analyzed. A set of dependencies are identiﬁed using the Chi-Square test for association and Cramer’s V. Results can be used as guidelines for building a framework for business analysis techniques selection in IT projects.

show abstract

“…Feature that provides information related to the Shelter Units, such as the Secretary of Social Development, the Specialized Reference Center for Homeless People (POP) 4 , the Social Assistance Reference Centers (CRAS) and the Specialized Social Assistance Reference Centers (CREAS).…”

Section: Feature Description Temporary Housingmentioning

confidence: 99%

“…Despite the techniques and tools provided in the Requirements Engineering's literature 2,3,4,5,6,7 , there is a constant urge for innovation and creativity, in order to understand the users' needs and the particularities of each system, according to what the users need or request 1,8 .…”

Section: Introductionmentioning

confidence: 99%

Using Design Thinking to Break Social Barriers: an Experience Report with Former Inmates

Amaral

Canedo

Cançado

et al. 2022

Preprint

View full text Add to dashboard Cite

Context and motivation: Design Thinking techniques have been widely used in the elicitation of software requirements, since such methods obtain satisfying results when applied to understand the necessities of both stakeholders and end-users. However, there is a lack of evidence on their effectiveness when applied to populations considered vulnerable. Question/problem: What are the implications of using Design Thinking techniques to elicit requirements in a community of former inmates - and what would be the benefits of and challenges in this deployment? Principal ideas/results: In this paper, we report our experience on using Design Thinking for Requirements Elicitation of a mobile application, customized for a vulnerable population: the former inmates of the Brazilian Prison System and their families. Research approach and methodology: We utilized the d.school Design Thinking method during our research. Techniques such as Brainstorming, Stakeholder Mapping, Personas Creation, Rapid Ethnography, and Interviews were used to obtain relevant data. Furthermore, during the development process, several prototypes were created. Contribution: The use of these techniques generated important contributions for the development of an uncommon application that aims to help the reintegration process of former inmates into society. The results obtained validate the initial hypothesis that such techniques, even when applied to a sensitive context such as this one, assist in the development of a product that meets the needs of the end-users by creating a higher quality product. Limitations of results: The main limitation of the research was the lack of access to low literacy end-users and/or former inmates without previous experience using mobile devices.

show abstract

Requirement Elicitation Techniques for Software Projects in Ukrainian IT: An Exploratory Study

Cited by 12 publications

References 12 publications

What Should a Good Software Requirements Specification Include? Results of a Survey

What Should a Good Software Requirements Specification Include? Results of a Survey

Practical Study on Software Requirements Specification and Modelling Techniques

Using Design Thinking to Break Social Barriers: an Experience Report with Former Inmates

Contact Info

Product

Resources

About