A review of practice and problems in requirements engineering in small and medium software enterprises in Thailand

Khankaew, Supha; Riddle, Steve

doi:10.1109/empire.2014.6890109

Cited by 16 publications

(10 citation statements)

References 23 publications

(25 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Additionally, a number of in-vivo studies have been made on diverse aspects of the software process in small organizations such as requirements engineering problems and practice (Khankaew and Riddle 2014), the benefits of using Scrum (Caballero et al 2011), software inspection (Misra et al 2014), the practices of self-organizing Agile teams (Hoda et al 2012), knowledge management in small teams (O'Connor and Basri 2012), factors that motivate software engineering teams (Verner et al 2014), factors that may influence the adoption of best practice (Cater-Steel 2000), program of process improvement software (Schoeffel and Benitti 2012) and the influence of SPI on business success in software SMEs (Clarke and O'Connor 2012b). These studies use live observation or surveys as their research methodology, so that the findings are based on actual process but they do not address the entire software process.…”

Section: Software Process In Small Organizationsmentioning

confidence: 99%

Understanding the gap between software process practices and actual practice in very small companies

Sánchez‐Gordón

O’Connor

2015

Software Qual J

View full text Add to dashboard Cite

This paper reports on a grounded theory to study into software developers' use of software development process in actual practice in the specific context of very small companies. This study was conducted in three very small software product companies located in Ecuador. The data collection was based on semi-structured qualitative interviews with software project managers, focus group with software developers and was supplemented by literature and documents studies. We interviewed two types of participants (managers and developers), so as to ensure that we elicited a holistic perspective of how they approached the software development process in actual practice. The goal was to study what practices are actually used and their opinion and attitude towards the potential adopting of an international standard (ISO/IEC 29110) specifically designed for very small companies. With the collected data we performed an analysis utilizing Grounded Theory coding techniques, as this methodology promotes the focus on uncovering the real concerns of the participants. This study highlighted three areas of concern: customer, software product and development tasks coordination and tracking. The findings in this study give an insight towards the work products as they relate to software development process practices in very small companies and the important factors that must be considered to assist project success.

show abstract

Section: Software Process In Small Organizationsmentioning

confidence: 99%

Understanding the gap between software process practices and actual practice in very small companies

Sánchez‐Gordón

O’Connor

2015

Software Qual J

View full text Add to dashboard Cite

show abstract

“…Some country-specific RE problem investigations include the surveys conducted by Solemon et al [10] and Liu et al [11], with Malaysian and Chinese organizations, respectively. Khankaew and Riddle [12], report on a survey with focus on more recently conducted semi-structured interviews with organizations from Thailand. These investigations provide valuable insights into industrial environments.…”

Section: Re Surveysmentioning

confidence: 99%

“…Many researchers have addressed identifying and analyzing RE problems faced by industry [3] [4]. More recently, a project called NaPiRE (Naming the Pain in Requirements Engineering) comprises the design of a family of surveys on RE practice and problems, and it is conducted in joint collaboration with various researchers from dierent countries [5].…”

Section: Introductionmentioning

confidence: 99%

Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil

Kalinowski

Felderer

Conte

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract.[Context] Many software projects fail due to problems in requirements engineering (RE).[Goal] The goal of this paper is analyzing a specific and relevant RE problem in detail: incomplete/hidden requirements.[Method] We replicated a global family of RE surveys with representatives of software organizations in Austria and Brazil. We used the data to (a) characterize the criticality of the selected RE problem, and to (b) analyze the reported main causes and mitigation actions. Based on the analysis, we discuss how to prevent the problem.[Results] The survey includes 14 different organizations in Austria and 74 in Brazil, including small, medium and large sized companies, conducting both, plan-driven and agile development processes. Respondents from both countries cited the incomplete/hidden requirements problem as one of the most critical RE problems. We identified and graphically represented the main causes and documented solution options to address these causes. Further, we compiled a list of reported mitigation actions.[Conclusions] From a practical point of view, this paper provides further insights into common causes of incomplete/hidden requirements and on how to prevent this problem.

show abstract

“…Khankaew and Riddle [5], more recently conducted semi-These investigations provide valuable insights into industrial environments. However, as each of them focuses on specific aspects in RE or on specific countries, their results are isolated and not generalizable.…”

Section: A Survey Research On Re Problemsmentioning

confidence: 99%

“…However, industry is still struggling to apply high-quality RE practices [3] and getting a further understanding on common RE problems and their causes is of great interest to both industry and academy. Therefore, many researchers have addressed identifying and analyzing RE problems faced by industry [4] [5].…”

Section: Introductionmentioning

confidence: 99%

Towards Building Knowledge on Causes of Critical Requirements Engineering Problems

Kalinowski¹,

Spínola²,

Conte³

et al. 2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-[Context] Many software projects fail due to problems in requirements engineering (RE).[Objective] The goal of this paper is to gather information on relevant RE problems and to represent knowledge on their most common causes.[Method] We replicated a global family of RE surveys in Brazil and used the data to identify critical RE problems and to build probabilistic causeeffect diagrams to represent knowledge on their common causes.[Results] The survey was answered by 74 different organizations, including small, medium and very large sized companies, conducting both, plan-driven and agile development. The most critical RE problems, according to those organizations, are related to communication and to incomplete or underspecified requirements. We provide the full probabilistic cause-effect diagrams with knowledge on common causes of the most critical identified RE problems online.[Conclusion] We believe that the knowledge presented in the diagrams can be helpful to support organizations in conducting causal analysis sessions by providing an initial understanding on what usually causes critical RE problems.

show abstract

A review of practice and problems in requirements engineering in small and medium software enterprises in Thailand

Cited by 16 publications

References 23 publications

Understanding the gap between software process practices and actual practice in very small companies

Understanding the gap between software process practices and actual practice in very small companies

Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil

Towards Building Knowledge on Causes of Critical Requirements Engineering Problems

Contact Info

Product

Resources

About