Context. Compare with bespoke RE, market-driven requirements engineering (MDRE), has manyclassical requirements engineering activities of bespoke RE. Elicitation is one of these activities. Thisprocess is to capture, extract and obtain needs from stakeholders. And there are many techniques toguide MDRE elicitation, and some techniques for bespoke RE are also used in MDRE contextnowadays. However, not all of these techniques are suitable for MDRE due to the difference betweenMDRE and bespoke RE, for example, in MDRE context, there is no specific customers’ participation.Meanwhile, there is a lack of studies that compare elicitation techniques by evaluating theircompetence of mitigating MDRE challenges. Objectives. In this study, we investigate and collect techniques which can be used for MDREelicitation. We also identify challenges of MDRE elicitation practice from literature as evaluatingcriteria. Then, we evaluate elicitation techniques’ competence of mitigating these challenges. Finally,we discuss with some interviewees to validate our result with real-world MDRE context. Methods. We use literature review and snowball sampling to investigate and collect MDRE elicitationtechniques and challenges. Next, we summarize elicitation techniques’ advantages and limitationsfrom literature and compare these techniques by evaluating whether they can mitigate MDREchallenges we find. Next, we conduct interview with 8 interviewees who are practitioners or havedeveloping experience in order to find out and discuss the difference between academic and realworldMDRE. Results. We identify 6 elicitation techniques which can be used in MDRE to compare. We also collect6 challenges which may happen in MDRE elicitation process. We compare them by literature studyand interview with practitioners and find that although some interviewees’ opinions are similar withliterature, there are still many different cases we need to consider before choosing elicitationtechniques. Conclusions. In this research, we fill the gap that there is a lack of studies about the comparison ofelicitation techniques in MDRE context. We also find 4 factors which should be studied in-depth inthe future MDRE elicitation techniques research, and validate our result with practice and discuss thereason of differences. Our result can help requirements engineers to choose suitable elicitationtechniques in MDRE projects.

Requirements Engineering has two main directions, Bespoke (product developed for one customer) and Market-Driven (several potential customers for the same product). These two are in some ways very much alike but in some aspects very different. Over the last couple of years the software development industry has tended to shift more and more to Market-Driven Requirements Engineering. This has brought attention to the challenges facing a Market-Driven development organization, without focusing on the actual shift from Bespoke development. Based on the differences and similarities between Bespoke and Market-Driven Requirements Engineering, this thesis presents a framework for shifting from the former to the latter. The framework (BESMART) involves three steps. Firstly, the organization assesses their potential to become more Market-Driven. Secondly they assess their current way of working to identify which areas that may need to be improved. Finally, BESMART provides multiple suggestions that address the identified improvement areas. The organization is then able to choose the one that best suits their needs. This also lets the organization choose a solution that they find feasible. The framework was used at a case organization during its development. This way it was ensured that the theoretical framework could actually be used in a real world setting. The practical use of BESMART resulted in some refinements aimed at making it more applicable in industry. Once the framework had been applied, it was evaluated by representatives from the case organization. The industry evaluation resulted in some improvement suggestions but showed that the framework was both useful and usable and provided an improvement plan that seemed promising enough to pilot in the organization.

In market-driven requirements engineering requirements are elicited from various internal and external sources. These sources may include engineers, marketing teams, customers etc. This results in a collection of requirements at multiple levels of abstractions. The Requirements Abstraction Model (RAM) is a Market Driven Requirements Engineering (MDRE) model that helps in managing requirements by organizing them at four levels (product, feature, function and component) of abstraction. The model is adaptable and can be tailored to meet the needs of the various organizations e.g. number of abstraction levels can be changed according to the needs of the organization. Software requirements are an important source of information when developing high-level tests (acceptance and system level tests). In order to place a requirement on a suitable level, workup activities (producing abstraction or breaking down a requirement) can be performed on the requirement. Such activities on the requirements can affect the test cases designed from them. Organizations willing to adopt the RAM need to know the suitability of the RAM requirements for designing high-level tests. This master thesis analyzes the requirements at product, feature, function and component level to evaluate their suitability for supporting the creation of high-level system test. This analysis includes designing test cases from requirements at different levels and evaluating how much of the information needed in the test cases is available in the RAM requirements. Test cases are graded on a 5 to 1 scale according to the level of detail they contain, 5 for better detailed and 1 for very incomplete. Twenty requirements have been selected for this document analysis; twenty requirements contain five requirements from each level (product, feature, function and component). Organizations can utilize the results of this study, while making decision to adopt the RAM model. Decomposition of the tests developed from the requirements is another area that has been explored in this study. Test decomposition involves dividing tests into sub-tests. Some benefits of the test decomposition include better resource utilization, meet time-to-market and better test prioritization. This study explores how tests designed from the RAM requirements support test decomposition, and help in utilizing above listed benefits of the test decomposition.

Research findings in requirements engineering (RE) report that software organizations still struggle in establishing processes that lead to proper requirements handling. This leads to the acknowledgement that the adoption of good requirements engineering practices by industry is still not common. Although some initiatives have been made to spread the use of good practices of bespoke RE, the area of market-driven requirements engineering (MDRE) still lacks a contribution in that direction. MDRE is characterized by strong market and strategic orientation, which contrasts with the customer/development organization relationship of bespoke RE. This poses several challenges to software product organizations, such as the need for aligning development activities with organizational and product strategies. In an attempt to help these organizations to realize the benefits of MDRE, this Master Thesis presents the Market-Driven Requirements Engineering Process Model (MDREPM). MDREPM is both a collection of good practices in MDRE, and an assessment tool for organizations to get a snapshot of the current state of their MDRE practices. The assessment intends to reveal problem areas of organization’s requirements process, which can then be worked upon by introducing good practices described in the model. The thesis describes the motivation for creating MDREPM, both from an academia and industry perspectives. In addition, it describes the process of developing the model, from its creation through to its validation within academia and industry. As the series of three case studies conducted indicate, the MDREPM has been shown to be useful for industry practitioners. A unanimous opinion has been found as to the good coverage it provides of issues related to MDRE, and as to its usefulness for driving improvement efforts in requirements engineering.