Requirements Engineering Activities Research Articles

Integrating sustainability in the design process of urban service robots.

The concept of sustainability and sustainable development has been well discussed and was subject to many conferences of the EU and UN resulting in agendas, goals, and resolutions. Yet, literature shows that the three dimensions of sustainability (ecological, social, and economic) are unevenly accounted for in the design of mechatronic products. The stated reasons range from a lack or inapplicability of tools for integration into the design process, models for simulation, and impact analyses to necessary changes in policy and social behavior. The influence designers have on the sustainability of a product lies mostly in the early design phases of the development process, such as requirements engineering and concept evaluation. Currently, these concepts emerge mostly from performance-based requirements rather than sustainability impact-based requirements, which are also true for service robots in urban environments. So far, the main focus of research in this innovative and growing product branch lies in performance in perception, navigation, and interaction. This paper sets its focus on integrating all three dimensions of sustainability into the design process. Therefore, we describe the development of an urban service robot supporting municipal waste management in the city of Berlin. It is the set goal for the robot to increase the service and support the employees while reducing emissions. For that, we make use of a product development process (PDP) and its adaptable nature to build a specific development process suited to include the three dimensions of sustainability during the requirements engineering and evaluation activities. Herein, we show how established design methods like the life cycle assessment or life cycle costing can be applied to the development of urban service robots and which aspects are underrepresented. Especially, the social dimension required us to look beyond standardized methods in the field of mechanical engineering. Based on our findings, we introduce a new activity to the development process that we call preliminary social assessment in order to incorporate social aspects in the early design phase.

Activities and Practices of Requirements Engineering in Agile Software Environments

Requirements are one of the important factors for software success. However, Requirements Engineering (RE) activities, in the Waterfall process model, are done sequentially in the analysis phase, which makes it difficult when RE practitioners think and reason about them in Agile Software Development (ASD) process model. RE practitioners need to find the established RE activities conventions in the ASD process model, especially with an increase of software companies, which transform to the ASD process model, in order to foster their transition to the new model. The objective of this study is to provide RE activities in ASD to allow RE practitioners to utilize the appropriate activity for specific ASD methodology. RE activities in ASD are handled repetitively and on a small scale, which makes them embedded in the development life cycle. This paper focuses on highlighting them in different ASD methodologies and discusses the practices that resolve the traditional Waterfall model issues. Although the ASD model has resolved some traditional RE issues, it introduced other issues, such as a consequence of trying to achieve an adequate balance between agility and stability. In addition, there is a lack of practices that target non-functional requirements.

Towards understanding the influence of personality and team behaviors on requirements engineering activities

<span lang="EN-US">Requirements engineers play an important role in the development of software products and services. The nature of requirements engineering (RE) is multifaceted and influences the quality, success, or failure of software products. In gathering software requirements, engineers commonly work in a team, particularly when dealing with the customers or modeling the requirements, hence the team behavior may influence the RE activities. The investigation of requirements engineers’ personality and their team behavior associated with RE activities is still an open area in which research is still developing. This study aims to investigate the personality and team behavior of requirements engineers involved in RE activities using a systematic literature review approach. We included 64 primary studies that addressed the association between personality and team behavior of requirements engineers on the effectiveness of RE activities. The result shows that among personality dimensions, extraversion and conscientiousness were found to be the predominant personality traits that positively affect RE activities. Furthermore, team behavior of requirements engineers such as flexibility, collaboration, creativity, innovation, and norms were discovered as factors that influence the RE process, performance, and success. The findings of this study contribute to the body of knowledge and practice of RE by providing empirical evidence on the influence of requirements engineers’ personality and team behavior on the effectiveness of RE activities.</span>

Requirements engineering for artificial intelligence systems: A systematic mapping study

In traditional software systems, Requirements Engineering (RE) activities are well-established and researched. However, building Artificial Intelligence (AI) based software with limited or no insight into the system’s inner workings poses significant new challenges to RE. Existing literature has focused on using AI to manage RE activities, with limited research on RE for AI (RE4AI). This paper investigates current approaches for specifying requirements for AI systems, identifies available frameworks, methodologies, tools, and techniques used to model requirements, and finds existing challenges and limitations. We performed a systematic mapping study to find papers on current RE4AI approaches. We identified 43 primary studies and analyzed the existing methodologies, models, tools, and techniques used to specify and model requirements in real-world scenarios. We found several challenges and limitations of existing RE4AI practices. The findings highlighted that current RE applications were not adequately adaptable for building AI systems and emphasized the need to provide new techniques and tools to support RE4AI. Our results showed that most of the empirical studies on RE4AI focused on autonomous, self-driving vehicles and managing data requirements, and areas such as ethics, trust, and explainability need further research.

A Freelancer-Supported Requirement Engineering Framework for Software Start-Ups

Resource-constrained start-up communities, faced with higher market failures, can take advantage of freelancers as useful resources in requirement engineering activities. This article proposes a framework that provides multiple criteria, which could help start-ups strategically select freelancers.

Mining and searching app reviews for requirements engineering: Evaluation and replication studies

App reviews provide a rich source of feature-related information that can support requirement engineering activities. Analyzing them manually to find this information, however, is challenging due to their large quantity and noisy nature. To overcome the problem, automated approaches have been proposed for ‘feature-specific analysis’. Unfortunately, the effectiveness of these approaches has been evaluated using different methods and datasets. Replicating these studies to confirm their results and to provide benchmarks of different approaches is a challenging problem. We address the problem by extending previous evaluations and performing a comparison of these approaches. In this paper, we present two empirical studies. In the first study, we evaluate opinion mining approaches; the approaches extract features discussed in app reviews and identify their associated sentiments. In the second study, we evaluate approaches searching for feature-related reviews. The approaches search for users’ feedback pertinent to a particular feature. The results of both studies show these approaches achieve lower effectiveness than reported originally, and raise an important question about their practical use.

Reducing Requirements Ambiguity via Gamification: Comparison with Traditional Techniques.

Requirements elicitation is one of the most significant activities of requirements engineering (RE) process. Poorly specified requirements can lead to a failed project. Various elicitation techniques are used to elicit requirements from the users and other stakeholders, each having its own pros and cons. Lack of user engagement, less user involvement, textual nature of the requirements, time taking process are some of the major problems that make it difficult to perform elicitation via traditional techniques. Moreover, these problems further create other challenges such as ambiguity, inconsistency, and incompleteness in requirements. Currently, researchers have focused on reducing ambiguity in requirements with the help of different techniques such as natural language processing techniques, requirement templates, and formal methods; however, these techniques work on reducing ambiguity during specification or from specified requirements. One of the “young' and exciting way of engaging users in requirements elicitation of a system is “Gamification', which helps in user engagement into the system. We intend to discover how gamification helps in reducing ambiguity by engaging stakeholders in an interactive manner. In this review study, we have reviewed traditional techniques used to detect and reduce requirements ambiguity. On the contrary, we have also presented the significance of gamification in requirements elicitation and the popular but effective game elements used in similar systems. Furthermore, this study highlights the significance of using gamification in requirements elicitation, which is beneficial to software development team as well as the users involved in the system.

Systematic Literature Mapping of User Story Research

User stories are a widely used artifact in Agile software development. Currently, only a limited number of secondary studies have reviewed the research on the user story technique. These research reviews focused on specific research topics related to ambiguity of requirements, effort estimation, and the application of Natural Language Processing. To our knowledge, a systematic mapping of <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">all</i> user story research has not been performed. To this end, we study the academic literature to investigate what user stories research has been performed, what types of problems have been identified, what sort of solutions or other types of research outcomes have been achieved, how mature the research is, and what research gaps exist. We followed Systematic Mapping Study guidelines to synthesize the currently available academic research on user stories. In total, we found 186 unique peer-reviewed studies, published in the period 2001-2021. We observed that research on the user story technique and its use had grown exponentially over the last seven years. Further, using a five-dimensional classification framework– requirements engineering activity, problem class, outcome class, type of research, type of publication– we observed several patterns in the classification of these studies across the different framework dimensions, which provided insights into the state-of-the-art and maturity of the research. We also identified four research gaps: the paucity of focused literature reviews; a lack of research on the role that user stories play in human cognition and interaction; a lack of comprehensive and mature solutions for resolving ambiguity issues with user stories early in the project; and a lack of validation and evaluation of proposed solutions. Several research opportunities are suggested, making our paper a useful reference for future research on user stories allowing researchers to clearly position their contributions.

A systematic mapping of semi-formal and formal methods in requirements engineering of industrial Cyber-Physical systems

The requirements engineering of Industrial Cyber-Physical Systems is extremely challenging due to large system sizes, component heterogeneity, involvement of multi-discipline stakeholders and machines, and continuous evolution. Formal and semi-formal languages, techniques, tools and frameworks can assist by providing repeatable and rigorous structures for eliciting, specifying, analysing, verifying and maintaining requirements. Various approaches have been proposed, but a contemporary and comprehensive study providing a landscape of the state-of-the-art is currently missing. This article reports a systematic mapping study covering 93 primary studies published between 2009 and October 2020. We categorise surveyed studies by current research directions in the use of semi-formal and formal methods for Requirements Engineering phases for Industrial Cyber-Physical Systems. We also identify gaps in current research and develop a novel conceptual model capturing the relationship between available formalisms and Requirements Engineering activities. We find that extensive work has been carried out on the formal analysis and verification of safety and timings requirements. However, the use of semi-formal notations, works on key phases like requirements elicitation and management, and the adoption of industrial standards are largely missing. Moreover, we find no literature providing methods to handle privacy and trust requirements, which have become critical concerns in this area.

An Approach to Elicit Trustworthiness Requirements in Blockchain technology

The leading Blockchain technology facilitates in many sectors including finance and healthcare. However, some technical challenges such as fraud and hacking arise may impact trust of users towards this technology. Requirement elicitation is one of requirement engineering activities to determine system requirements through discussion with stakeholders from documentation and underlying domain before executes it to development stage. The available methods for eliciting requirements, such as interviews and brainstorming are found to be time-consuming, and they fail to identify trustworthiness requirements. Further, eliciting requirements for Blockchain application is found to be challenging, as the properties of Blockchain application are different from the common technology. Moreover, the common elicitation practices are lacking on considering trust elements when eliciting requirements. Therefore, this research aims to propose a new automated elicitation approach which is a library for trust requirements of Blockchain application. A new trust taxonomy will be identified to classify and analyse the association between trust factors and its attributes. A proof concept prototype tool will be developed to realize the approach. Finally, this new approach is expected to enhance the acceptance of people towards application developed using Blockchain technology. Furthermore, this study will provide positive results in producing sustainable Blockchain application or software.

Requirement Engineering Processes, Activities, Flaws, Importance And Review

IT and Software industries are the fastest and most improving industries all over the world. Even in countries like India, Pakistan and other development counties the trend of IT and different TECH technologies is rapidly increasing time to time. There is no doubt on the fact that that all the IT and Software industries follows the Software Development Life Cycle (SDLC) for their software or product development process. Following the IT trends it is essential for the industries to follow the SDLC for their software development. The most important and the first step of any software development is Requirement engineering. In short words requirement engineering is the backbone of any software development process, other than that it also provides an estimation from the start that is the project doable in the time given or not. After reading the paper one will be well aware of what software requirement engineering really is and what activities are involved what flaws are made in those activities and the importance of a requirement engineer in any industry. The information is conducted from different software industries. The data is gathered from all source means and is analyzed and refined with different software like Turnitin. The information conducted will be useful for all local and global software industries including other TECH industries.

Social network sites and requirements engineering: A systematic literature review

AbstractA large volume of highly diverse and real‐time data provided by social network sites has revolutionized several data analytical sciences such as stock exchange fluctuation prediction, sentiment analysis, and political affiliations prediction. From a software engineering viewpoint, social network sites have produced an unprecedented opportunity for software development organizations to monitor the opinion of the large population of users of their systems. The extracted data from social network sites can be used to extract information about newly launched systems, and it enable software development organizations to obtain rapid technical and social feedback about their systems. This paper presents on a systematic literature review of the published research articles on how requirements engineering (RE) activities are conducted using social network sites, elaborated in studies published between 2011 and 2019. From the resulting studies, we extracted data to answer our four questions related to social network site (SNS)‐based RE approaches focusing on requirements elicitation, prioritization, and negotiation activities. Thirty‐one relevant studies were identified and analyzed to answer our research questions. Among 31 studies, 62% of the studies reportedly support requirements elicitation activity, and 14% of the studies reportedly support requirements elicitation, prioritization, and negotiation activities. Ten percent studies were about requirements elicitation and prioritization activities, 7% of the studies support both requirements elicitation and negotiation activities, and prioritization activity was supported by 7% of the studies. It was also observed that 58% of the selected studies adopted semi‐automatic approaches to conduct RE activities while 21% of the selected studies proposed automatic tools, and 21% of the selected studies adopted manual approaches to conduct RE activities. The outcomes of this systematic literature review indicate that social network sites can be a major source that can be used successfully to extract and identify user requirements. Moreover, this systematic literature review also presents implications of this study for practitioners and researchers including challenges, unresolved issues, and future research directions.

The Impact of Controlled Vocabularies on Requirements Engineering Activities: A Systematic Mapping Study

Context: The use of controlled vocabularies (CVs) aims to increase the quality of the specifications of the software requirements, by producing well-written documentation to reduce both ambiguities and complexity. Many studies suggest that defects introduced at the requirements engineering (RE) phase have a negative impact, significantly higher than defects in the later stages of the software development lifecycle. However, the knowledge we have about the impact of using CVs, in specific RE activities, is very scarce. Objective: To identify and classify the type of CVs, and the impact they have on the requirements engineering phase of software development. Method: A systematic mapping study, collecting empirical evidence that is published up to July 2019. Results: This work identified 2348 papers published pertinent to CVs and RE, but only 90 primary published papers were chosen as relevant. The process of data extraction revealed that 79 studies reported the use of ontologies, whereas the remaining 11 were focused on taxonomies. The activities of RE with greater empirical support were those of specification (29 studies) and elicitation (28 studies). Seventeen different impacts of the CVs on the RE activities were classified and ranked, being the two most cited: guidance and understanding (38%), and automation and tool support (22%). Conclusions: The evolution of the last 10 years in the number of published papers shows that interest in the use of CVs remains high. The research community has a broad representation, distributed across the five continents. Most of the research focuses on the application of ontologies and taxonomies, whereas the use of thesauri and folksonomies is less reported. The evidence demonstrates the usefulness of the CVs in all RE activities, especially during elicitation and specification, helping developers understand, facilitating the automation process and identifying defects, conflicts and ambiguities in the requirements. Collaboration in research between academic and industrial contexts is low and should be promoted.

Fostering Continuous Value Proposition Innovation through Freelancer Involvement in Software Startups: Insights from Multiple Case Studies

[Context] The software startups could continuously innovate business model value proposition by involving freelancers as a source of innovative ideas (that enhance customer perceived value) and as experts for implementing the innovative ideas (by undertaking software engineering tasks). Startups employ one of three strategies for associating with freelancers i.e., task based (association ends with completion of the outsourced task), panel based (outsourcing task to a panel of freelancers associated with startup), or hybrid. Uncertainties, terminology issues, high technical debt, lack of documentation, lack of systematic decision making processes, lack of resources, lack of brand values, need for the continuous involvement of the freelancer to incorporate continuous validated learnings, merging freelancer perspectives, and deciding the level of their involvement in individual requirement engineering (or value proposition innovation) activities, are the main inhibitors for associations with freelancers. The availability of good freelancers and their long term and continuous commitments are necessary requirements for value proposition innovation. The theory about freelancer association with the software startups is extended by studying the real practices of startups, which successfully involved freelancers for value proposition innovation by capturing innovative ideas and acquiring the freelancer’s skills to implement those ideas. [Objectives] The objective of this paper is to explain the strategies adopted by the software startups to foster value proposition innovation by continuously involving the freelancers and the way they overcome the challenges arising because of the associations. The findings are driven by the study of real practices of startups that proved to be successful in the market by involving freelancers and continuous innovations leading to increased market shares. [Method] This paper performs empirical studies through case studies of three software startups located in Italy, France, and India, which are at the verge of being transforming into big companies, with large market share. The current practices highlighting the successful way of executing freelancing association strategies for value proposition innovation and the way to overcome the arising challenges are reported. The findings are also compared with those of two young startups based in Switzerland and India, to bring useful lessons for the young startups. The case study results are validated by employees from the studied startups (both those who participated in data collection and those who did not). [Results] The results indicate that freelancer involvement during value proposition activities, which is the core business operation, is beneficial to the both freelancers and the startups. Startup teams could reduce the development costs, shorten time to market, and increase customer satisfaction (by providing features addressing real market needs) by correctly involving the freelancers uniformly across value proposition activities. The startups could manage innovation with small teams (compared to human resources in companies) if done jointly with the freelancers, that helps the team members to learn new skills, upgrade their skills, and learn new perspectives about their markets. Business impacts due to freelancer involvement are stronger if the level of freelancer involvement across various value proposition activities is higher compared to their involvement across few activities only. The studied startups are not completely dependent on the freelancers but the freelancer’s perspectives and skills are valued as a rich source of market success. Freelancer involvement is taken as an opportunity to gain access to global market perspectives, which otherwise would be effortful for in-house teams to collect. In addition, they resolve technical debt, are a source of upgrading skills for undertaking future innovation, and help reaching customers for marketing (promoting product and gaining access to the feedbacks). Overall, the value proposition innovation in the studied startups have different levels of involvement of the freelancers but these startups have reported positive impacts on the business in terms of development cost reductions, shorten time to market, and high customer satisfaction (measured on early attainment of product/market fit and fast growth thereafter). The case study results are validated by the startup employees (member checking). The responses collected are analysed using box plots, which shows a higher level of result agreements among the employees.

Fostering product innovations in software startups through freelancer supported requirement engineering

This research paper explores the involvement of freelancers in requirement engineering activities to continuously innovating the value propositions and utilizing their expertise in various requirement engineering tasks. This paper reports the case study conducted with the startups that involve freelancers for the requirement engineering activities. The findings are then compared with the literature to explore the freelancer supported requirement engineering domain. Results indicate that the freelancers could help innovate value proposition by providing different perspectives of the global segments and also expertise in executing requirement engineering activities. The freelancers have varying levels of involvement in requirement engineering activities depending on on startup contexts and is highly challenged by various inhibitors. The inhibitors include difficulty to select freelancers optimally, ensuring their long term association for continuous rework arising because of continuous learnings in the market, building trust, mechanism to integrate their perspective, establishing communication, negotiations and strategic pricings. However, there is a need to optimally establish the freelancer involvement from beginning of the startup life cycle with a promise for long term benefits in exchange for their trustworthy and accurate perspectives, which is harder to get by involving crowds of customers due to resource limitations. Further research is required to investigate how freelancers could represent the samples of globally distributed customer segments as input source of information on one side and on another side become startup team representatives to establish direct interactions with global customer segments.

What lies behind requirements? A quality assessment of statement grounds in requirements elicitation

In requirements engineering (RE), an early yet critical activity consists in eliciting the requirements from various stakeholders, who usually have different assumptions, knowledge, and intentions. The goal during elicitation is to understand what stakeholders expect from a given software, expectations which then feed the analysis, prioritization, validation, and ultimately specification activities of the RE process. Elicitation is an interactive activity. It relies on verbal communication of statements of stakeholders about their requirements, their ideas, their assumptions, the constraints they know apply in the environment of the future software, and so forth. Statements, we claim, build either on a past experience of the stakeholder or are the result of reasoning from indirect experience, i.e., they have different grounds. In this paper, we introduce the concept of “Statement Ground” during RE, contrast it with the classical perspective on requirements elicitation, and position the concept in existing RE literature. We conduct an empirical assessment of the relative qualities of statements that have different grounds. Our work results in a better understanding of the statements produced by stakeholders during requirements elicitation, of their qualities, and of the interplay between those qualities and the concept of statement ground. It also results in the definition of a series of research questions which focus on the implications of our findings on the overall requirements engineering activity.

Requirements Engineering in Software Startups: A Systematic Mapping Study

Startups have high failure rates due to their inability to attain a sufficient product/market fit, i.e., delivering a solution that best matches the user needs in the market. Requirement engineering is the activity that could help startup teams identify the value proposition that provides high value to the users and continuously innovate it. The objective of the study is to analyse the state of art of the requirement engineering research in the context of startups, as available in the literature. The analysis of the research area highlights the research trends to achieve two things i.e., (a) predict how much support the startups can get from the literature for enhancing their success rates and (b) identify the research gaps to motivate researchers to conduct future research that could be adoptable in startup contexts. Systematic mapping is conducted on studies extracted from the four bibliographic databases (IEEExplore, ACM, Springerlink and ScienceDirect) and studies extracted by using a forward snowballing approach. Individual studies are coded to yield the classification scheme. Formulated schemes and those already available in literature, were populated with information extracted from the abstracts of the studies. The research is mostly focused on generic requirement engineering and product validation activities. The research is conducted mostly as evaluations (empirical studies) with the outcome of providing theory to the research community. Major underlying motivation of the research is to attain the product/market fit. However, research studies focusing on requirement documentation, prioritization and elicitation are losing focus from 2017, 2018 and 2019, respectively. The literature lacks the studies that reports research solutions which are validated in laboratory settings or in real contexts, experience reports, opinion papers and philosophical papers. The positive side of the finding is that the number of requirement engineering research studies in a startup context have increased in the past five years. At this instant, unfortunately the literature has limited ability to support startups by providing solutions (for instance, research solutions, evidence to support decision makings, best practices, experiences etc.) that are adoptable in their real context. Uniform focus of the researchers across all sub-activities of requirement engineering is required with effort distributed across different research types that supports startups, not only by providing validated solutions but experience reports, opinions, new conceptual frameworks and empirical evidence that can aid their decision making.

A Comparison of Traditional Machine Learning Approaches for Supervised Feedback Classification in Bahasa Indonesia

The advancement of machine learning and natural language processing techniques hold essential opportunities to improve the existing software engineering activities, including the requirements engineering activity. Instead of manually reading all submitted user feedback to understand the evolving requirements of their product, developers could use the help of an automatic text classification program to reduce the required effort. Many supervised machine learning approaches have already been used in many fields of text classification and show promising results in terms of performance. This paper aims to implement NLP techniques for the basic text preprocessing, which then are followed by traditional (non-deep learning) machine learning classification algorithms, which are the Logistics Regression, Decision Tree, Multinomial Naïve Bayes, K-Nearest Neighbors, Linear SVC, and Random Forest classifier. Finally, the performance of each algorithm to classify the feedback in our dataset into several categories is evaluated using three F1 Score metrics, the macro-, micro-, and weighted-average F1 Score. Results show that generally, Logistics Regression is the most suitable classifier in most cases, followed by Linear SVC. However, the performance gap is not large, and with different configurations and requirements, other classifiers could perform equally or even better.

A Mini Comparative Study of Requirements Modelling Diagrams towards Swimlane: Evidence of Enterprise Resource Planning System

Model-based requirements engineering (MBRE) is an approach that empowers requirements engineers with adequate models to perform requirements engineering (RE) activities. This approach is increasingly becoming an essential part of system engineering projects as it reduces development time, enhances analysis capability and increases the potential for reuse. Use case diagram, activity diagram, business process management and notation diagram (BPMN) and swimlane diagram are among the diagram used in representing the requirements. However, the swimlane diagram has received little attention in the literature and lack of empirical support, particularly in the requirements engineering field. In this study, a multi-criteria comparative work is performed where three other diagrams are identified and examined against the swimlane diagram. Walkthrough sessions are conducted using enterprise application documents with real users to validate the model-based requirements exemplified using the swimlane diagram. These activities are carried out to highlight the efficacy of the swimlane diagram in representing requirements in the RE field. The results confirmed that the swimlane diagram outperforms NL in overall completion time for the requirement validation process. Furthermore, it gives users a better understanding as they did not need to read textual requirements which are typically ambiguous, confusing, and lengthy.

Exploratory analysis of cultural influences on requirements engineering activities based on stakeholders’ profile

Abstract Requirements Engineering (RE) is a critical process in the development of any software. It requires intensive communication among many stakeholders in order to identify software requirements accurately. As RE activities require intensive communication, cultural influences might need to be considered to improve these activities and to avoid issues that might affect the software project outcomes. In our work, we explored the influence of national culture on RE activities. We conducted an empirical study in two countries that have different cultural profiles: Saudi Arabia and Australia. To explore this issue, we conducted 41 face-to-face interviews. To consolidate the collected data, we conducted also 30 follow-up interviews with the same practitioners. The aim of our study was to empirically identify the set of cultural influences affecting RE activities, and analyse their implication on RE activities. This paper reports the results of the analysis of participants’ responses with respect to their industrial profiles, in terms of three factors: the type of software methodology applied by the participants (Traditional vs. Agile), the size of their company/organisation (small, medium, and large), and its type (private vs. government). The results showed a number of significant differences in the cultural influences that determine the type of software development methodology, i.e., Traditional or Agile, being applied within the corresponding company. In this paper, we discuss the identified differences and the factors that determine them. This in-depth analysis provides a broader examination of the influence of culture on RE activities, which might assist RE practitioners to select the most suitable RE practices/methodology to overcome any negative effects of these influences.