The Experts below are selected from a list of 95760 Experts worldwide ranked by ideXlab platform
Chi Ruan - One of the best experts on this subject based on the ideXlab platform.
-
extraction of rare earths from the leach liquor of the weathered crust elution deposited rare earth ore with non precipitation
International Journal of Mineral Processing, 2011Co-Authors: Tian Jun, Yin Jingqun, Chen Kaihong, Rao Guohua, Jiang Mintao, Chi RuanAbstract:Abstract In this paper, the development and research connotations of extraction of rare earths from the leach liquor of the weathered crust elution-deposited rare earth ore with non-precipitation, including solvent extraction, ion exchange and liquid membranes were introduced respectively. The principle of extraction and separation of rare earth is described. The advantage, potential and some problems that existed in non-precipitation extraction process were discussed briefly. The developing trend of non-precipitation technology in Industrial Practice has been expected. The green chemistry development orientation is suggested.
Björn Regnell - One of the best experts on this subject based on the ideXlab platform.
-
an investigation of how quality requirements are specified in Industrial Practice
Information & Software Technology, 2013Co-Authors: Richard Berntsson Svensson, Tommy Olsson, Björn RegnellAbstract:Abstract Context This paper analyses a sub-contractor specification in the mobile handset domain. Objective The objective is to understand how quality requirements are specified and which types of requirements exist in a requirements specification from industry. Method The case study is performed in the mobile handset domain, where a requirements specification was analyzed by categorizing and characterizing the pertaining requirements. Results The requirements specification is written in structured natural language with unique identifiers for the requirements. Of the 2178 requirements, 827 (38%) are quality requirements. Of the quality requirements, 56% are quantified, i.e., having a direct metric in the requirement. The variation across the different sub-domains within the requirements specification is large. Conclusion The findings from this study suggest that methods for quality requirements need to encompass many aspects to comprehensively support working with quality requirements. Solely focusing on, for example, quantification of quality requirements might overlook important requirements since there are many quality requirements in the studied specification where quantification is not appropriate.
-
quality requirements in Industrial Practice an extended interview study at eleven companies
IEEE Transactions on Software Engineering, 2012Co-Authors: Richard Berntsson Svensson, Tony Gorschek, Ali Shahrokni, Björn Regnell, Richard Torkar, Robert FeldtAbstract:In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previously piloted, interview study was performed to identify specific challenges associated with the selection, tradeoff, and management of QR in Industrial Practice. Data were collected through semistructured interviews with 11 product managers and 11 project leaders from 11 software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QR. Second, it compares the perceptions and priorities of QR by product and project management, respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in downstream development activities.
Robert Feldt - One of the best experts on this subject based on the ideXlab platform.
-
On the long-term use of visual gui testing in Industrial Practice: a case study
Empirical Software Engineering, 2017Co-Authors: Emil Alegroth, Robert FeldtAbstract:Visual GUI Testing (VGT) is a tool-driven technique for automated GUI-based testing that uses image recognition to interact with and assert the correctness of the behavior of a system through its GUI as it is shown to the user. The technique’s applicability, e.g. defect-finding ability, and feasibility, e.g. time to positive return on investment, have been shown through empirical studies in Industrial Practice. However, there is a lack of studies that evaluate the usefulness and challenges associated with VGT when used long-term (years) in Industrial Practice. This paper evaluates how VGT was adopted, applied and why it was abandoned at the music streaming application development company, Spotify, after several years of use. A qualitative study with two workshops and five well chosen employees is performed at the company, supported by a survey, which is analyzed with a grounded theory approach to answer the study’s three research questions. The interviews provide insights into the challenges, problems and limitations, but also benefits, that Spotify experienced during the adoption and use of VGT. However, due to the technique’s drawbacks, VGT has been abandoned for a new technique/framework, simply called the Test interface. The Test interface is considered more robust and flexible for Spotify’s needs but has several drawbacks, including that it does not test the actual GUI as shown to the user like VGT does. From the study’s results it is concluded that VGT can be used long-term in Industrial Practice but it requires organizational change as well as engineering best Practices to be beneficial. Through synthesis of the study’s results, and results from previous work, a set of guidelines are presented that aim to aid practitioners to adopt and use VGT in Industrial Practice. However, due to the abandonment of the technique, future research is required to analyze in what types of projects the technique is, and is not, long-term viable. To this end, we also present Spotify’s Test interface solution for automated GUI-based testing and conclude that it has its own benefits and drawbacks.
-
quality requirements in Industrial Practice an extended interview study at eleven companies
IEEE Transactions on Software Engineering, 2012Co-Authors: Richard Berntsson Svensson, Tony Gorschek, Ali Shahrokni, Björn Regnell, Richard Torkar, Robert FeldtAbstract:In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previously piloted, interview study was performed to identify specific challenges associated with the selection, tradeoff, and management of QR in Industrial Practice. Data were collected through semistructured interviews with 11 product managers and 11 project leaders from 11 software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QR. Second, it compares the perceptions and priorities of QR by product and project management, respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in downstream development activities.
Philipp Leitner - One of the best experts on this subject based on the ideXlab platform.
-
a mixed method empirical study of function as a service software development in Industrial Practice
Journal of Systems and Software, 2019Co-Authors: Philipp Leitner, Erik Wittern, Josef Spillner, Waldemar HummerAbstract:Function-as-a-Service (FaaS) describes cloud computing services that make infrastructure components transparent to application developers, thus falling in the larger group of “serverless” computing mod- els. When using FaaS offerings, such as AWS Lambda, developers provide atomic and short-running code for their functions, and FaaS providers execute and horizontally scale them on-demand. Currently, there is nosystematic research on how developers use serverless, what types of applications lend themselves to this model, or what architectural styles and Practices FaaS-based applications are based on. We present results from a mixed-method study, combining interviews with practitioners who develop applications and systems that use FaaS, a systematic analysis of grey literature, and a Web-based survey. We find that successfully adopting FaaS requires a different mental model, where systems are primarily constructed by composing pre-existing services, with FaaS often acting as the “glue” that brings these services to- gether. Tooling availability and maturity, especially related to testing and deployment, remains a major difficulty. Further, we find that current FaaS systems lack systematic support for function reuse, and ab- stractions and programming models for building non-trivial FaaS applications are limited. We conclude with a discussion of implications for FaaS providers, software developers, and researchers.
-
all the services large and micro revisiting Industrial Practice in services computing
International Conference on Service Oriented Computing, 2015Co-Authors: Gerald Schermann, Jurgen Cito, Philipp LeitnerAbstract:Services computing is both an academic field of study looking back at close to 15 years of fundamental research and a vibrant area of Industrial software engineering. Industrial Practice in this area is notorious for its ever-changing nature, with the state of the art changing almost on a yearly basis based on the ebb and flow of various hypes and trends (e.g., microservices). In this paper, we provide a look “across the wall” into Industrial services computing. We conducted an empirical study based on the service ecosystem of 42 companies, and report, among other aspects, how service-to-service communication is implemented, how service discovery works in Practice, what Quality-of-Service metrics practitioners are most interested in, and how services are deployed and hosted. We argue that not all assumptions that are typical in academic papers in the field are justified based on Industrial Practice, and conclude the paper with recommendations for future research that is more aligned with the services industry.
Richard Berntsson Svensson - One of the best experts on this subject based on the ideXlab platform.
-
an investigation of how quality requirements are specified in Industrial Practice
Information & Software Technology, 2013Co-Authors: Richard Berntsson Svensson, Tommy Olsson, Björn RegnellAbstract:Abstract Context This paper analyses a sub-contractor specification in the mobile handset domain. Objective The objective is to understand how quality requirements are specified and which types of requirements exist in a requirements specification from industry. Method The case study is performed in the mobile handset domain, where a requirements specification was analyzed by categorizing and characterizing the pertaining requirements. Results The requirements specification is written in structured natural language with unique identifiers for the requirements. Of the 2178 requirements, 827 (38%) are quality requirements. Of the quality requirements, 56% are quantified, i.e., having a direct metric in the requirement. The variation across the different sub-domains within the requirements specification is large. Conclusion The findings from this study suggest that methods for quality requirements need to encompass many aspects to comprehensively support working with quality requirements. Solely focusing on, for example, quantification of quality requirements might overlook important requirements since there are many quality requirements in the studied specification where quantification is not appropriate.
-
quality requirements in Industrial Practice an extended interview study at eleven companies
IEEE Transactions on Software Engineering, 2012Co-Authors: Richard Berntsson Svensson, Tony Gorschek, Ali Shahrokni, Björn Regnell, Richard Torkar, Robert FeldtAbstract:In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previously piloted, interview study was performed to identify specific challenges associated with the selection, tradeoff, and management of QR in Industrial Practice. Data were collected through semistructured interviews with 11 product managers and 11 project leaders from 11 software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QR. Second, it compares the perceptions and priorities of QR by product and project management, respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in downstream development activities.
