| 1. |
- Wu, Chen, et al.
(author)
-
WT1 Enhances Proliferation and Impedes Apoptosis in KRAS Mutant NSCLC via Targeting cMyc
- 2015
-
In: Cellular Physiology and Biochemistry. - : S. Karger AG. - 1015-8987 .- 1421-9778. ; 35:2, s. 647-662
-
Journal article (peer-reviewed)abstract
- Background: A novel link between oncogenic KRAS signalling and WT1 was recently identified. We sought to investigate the role of WT1 and KRAS in proliferation and apoptosis. Methods: KRAS mutations and WT1 (cMyc) expression were detected using Sanger sequencing and real-time PCR in 77 patients with non-small cell lung cancer (NSCLC). Overexpression and knockdown of WT1 were generated with plasmid and siRNA via transient transfection technology in H1299 and H1568 cells. MTT assay for detection of cell proliferation, and TUNEL assay amd proteomic profiler assay for apoptosis evaluation were carried out. Dual luciferase reporter assay and ChIP-PCR were performed to validate the effect of WT1 on the cMyc promoter. Results: KRAS mutations showed a negative impact on overall survival ( OS). High expressions of WT1 and cMyc were associated with poor OS in KRAS mutant subgroup. The potential mechanisms that WT1 promotes proliferation and impedes apoptosis through affecting multiple apoptosis-related regulators in KRAS mutant NSCLC cells were identified. WT1 could activate cMyc promoter directly in KRAS mutant cells. Conclusion: The results suggest that WT1 and c-MYC expression is important for survival in KRAS mutant tumors as opposed to KRAS wild-type tumors. For treatment of KRAS mutant NSCLC, targeting WT1 and cMyc may provide alternative therapeutic strategies.
|
|
| 2. |
- Abdeen, Waleed, et al.
(author)
-
An approach for performance requirements verification and test environments generation
- 2023
-
In: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 28:1, s. 117-144
-
Journal article (peer-reviewed)abstract
- Model-based testing (MBT) is a method that supports the design and execution of test cases by models that specify theintended behaviors of a system under test. While systematic literature reviews on MBT in general exist, the state of the arton modeling and testing performance requirements has seen much less attention. Therefore, we conducted a systematic map-ping study on model-based performance testing. Then, we studied natural language software requirements specificationsin order to understand which and how performance requirements are typically specified. Since none of the identified MBTtechniques supported a major benefit of modeling, namely identifying faults in requirements specifications, we developed thePerformance Requirements verificatiOn and Test EnvironmentS generaTion approach (PRO-TEST). Finally, we evaluatedPRO-TEST on 149 requirements specifications. We found and analyzed 57 primary studies from the systematic mappingstudy and extracted 50 performance requirements models. However, those models don’t achieve the goals of MBT, whichare validating requirements, ensuring their testability, and generating the minimum required test cases. We analyzed 77 Soft-ware Requirements Specification (SRS) documents, extracted 149 performance requirements from those SRS, and illustratethat with PRO-TEST we can model performance requirements, find issues in those requirements and detect missing ones.We detected three not-quantifiable requirements, 43 not-quantified requirements, and 180 underspecified parameters in the149 modeled performance requirements. Furthermore, we generated 96 test environments from those models. By modelingperformance requirements with PRO-TEST, we can identify issues in the requirements related to their ambiguity, measur-ability, and completeness. Additionally, it allows to generate parameters for test environments
|
|
| 3. |
- Badampudi, Deepika, 1984-, et al.
(author)
-
Large scale reuse of microservices using DevOps andInnerSource practices - A longitudinal case study
-
Other publication (other academic/artistic)abstract
- Contemporary practices such as InnerSource and DevOps promote software reuse. This study investigates the implications of using contemporary practices on software reuse. In particular, we investigate the costs, benefits, challenges, and potential improvements in contemporary reuse at Ericsson. We performed the study in two phases: a) the initial data collection based on a combination of data collection methods (e.g., interviews, discussions, company portals), and b) a follow-up group discussion after a year to understand the status of the challenges and improvements identified in the first phase. Our results indicate that developing reusable assets resulted in upfront costs, such as additional effort in ensuring compliance. Furthermore, development with reuse also resulted in additional effort, for example, in integrating and understanding reusable assets. Ericsson perceived the additional effort as an investment resulting in long-term benefits such as improved quality, productivity, customer experience, and way of working. Ericsson's main challenge was increased pressure on the producers of reusable assets, which was mitigated by scaling the InnerSource adoption. InnerSource success is evident from the increase in the contributions to reusable assets. In addition, Ericsson implemented measures such as automating the compliance check, which enhanced the maturity of reusable assets and resulted in increased reuse.
|
|
| 4. |
- Chen, Xingru
(author)
-
Improving Internal Software Reuse in the Context of Contemporary Software Engineering Practices
- 2023
-
Licentiate thesis (other academic/artistic)abstract
- Context: Companies adopt many software reuse practices, such as software product line, reuse verbatim, and systematic reuse, to improve their internal software development and maximize the benefits. Contemporary software engineering (SE) practices, such as microservices and InnerSource, influence internal software reuse.Objective: In this thesis, we aim to improve internal software reuse in the context of contemporary SE practices. To do that, we want to 1) understand the state-of-the-art and the state-of-the-practice of software reuse costs and benefits and the challenges that companies are currently facing and 2) identify interventions to improve internal software reuse. Methods: We conducted a systematic literature review to understand the state-of-the-art of software reuse costs and benefits. We performed two exploratory case studies to understand the state-of-the-practice of software reuse costs and benefits, challenges, and improvement areas in the context of contemporary SE practices. We performed another follow-up improving case study to investigate the medium-sized case company's readiness of adopting InnerSource for software reuse.Results: Existing literature reported more software reuse benefits than costs. The most reported software reuse benefits are better product quality and improved productivity. Verbatim reuse and systematic reuse result in more reuse benefits. Most of the included primary studies are of moderate quality, with only four having high quality. Practitioners think that software reuse costs in developing reusable assets will be paid off when developers start to reuse them. Challenges in software reuse in the context of contemporary SE practices differ between medium-sized and large-sized companies. Both of the companies perceive that InnerSource can help improve internal software reuse. Asking practitioners about both current and desired InnerSource reuse status helps identify the needed InnerSource improvements, thus helping companies succeed in adopting InnerSource for reuse. Conclusion: Both existing literature and our two case studies investigating software reuse in the context of contemporary SE practices showed that software reuse improves quality and productivity and has costs in developing and integrating reusable assets. However, the overall benefits outweigh the costs. Both case companies faced challenges in improving their internal reuse, where the most common challenges were about developing and maintaining reusable assets. The results showed that InnerSource helps develop and maintain reusable assets and further improves internal software reuse.
|
|
| 5. |
- Chen, Xingru, et al.
(author)
-
Reuse in Contemporary Software Engineering Practices - An Exploratory Case Study in A Medium-sized Company
- 2022
-
In: e-Informatica Software Engineering Journal. - : Wroclaw University of Technology. - 1897-7979 .- 2084-4840. ; 16:1
-
Journal article (peer-reviewed)abstract
- Background: Software practice is evolving with changing technologies and practices such as InnerSource, DevOps, and microservices. It is important to investigate the impact of contemporary software engineering (SE) practices on software reuse.Aim: This study aims to characterize software reuse in contemporary SE practices and investigate its implications in terms of costs, benefits, challenges, and potential improvements in a medium-sized company.Method: We performed an exploratory case study by conducting interviews, group discussions, and reviewing company documentation to investigate software reuse in the context of contemporary SE practices in the case company.Results: The results indicate that the development for reuse in contemporary SE practices incurs additional coordination, among other costs. Development with reuse led to relatively fewer additional costs and resulted in several benefits such as better product quality and less development and delivery time. Ownership of reusable assets is challenging in contemporary SE practice. InnerSource practices may help mitigate the top perceived challenges: discoverability and ownership of the reusable assets, knowledge sharing and reuse measurement.Conclusion: Reuse in contemporary SE practices is not without additional costs and challenges. However, the practitioners perceive costs as investments that benefit the company in the long run.
|
|
| 6. |
- Chen, Xingru, et al.
(author)
-
Understanding and Evaluating Software Reuse Costs and Benefits from Industrial Cases - A Systematic Literature Review
-
Other publication (other academic/artistic)abstract
- Companies adopt various software reuse practices to achieve more benefits. Existing secondary studies aggregated primary evidence on software reuse benefits more than the costs. It is important to know how the software reuse costs and benefits are measured and the strength of the evidence. This study aims to conduct a systematic literature review to identify the observed software reuse costs and benefits from industrial cases and investigate how the identified software reuse costs and benefits are measured. In addition, we also assess the quality of the included primary studies to understand the strength of evidence behind the identified software reuse costs and benefits. We included 30 primary studies on software reuse costs and benefits in industrial cases using a mixed search strategy - automated search and snowballing. We identified nine software reuse benefits, six software reuse costs, and the metrics used to measure them. Better quality and improved productivity are the most investigated software reuse benefits, and most primary studies that report these two benefits are of good or moderate quality. Few primary studies reported software reuse costs, and most of them are of low quality. Generally, the quality of primary studies reporting software reuse benefits is better than those reporting software reuse costs.
|
|
| 7. |
- Chen, Xingru, et al.
(author)
-
Understanding and evaluating software reuse costs and benefits from industrial cases—A systematic literature review
- 2024
-
In: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 171
-
Research review (peer-reviewed)abstract
- Context: Software reuse costs and benefits have been investigated in several primary studies, which have been aggregated in multiple secondary studies as well. However, existing secondary studies on software reuse have not critically appraised the evidence in primary studies. Moreover, there has been relatively less focus on how software reuse costs and benefits were measured in the primary studies, and the aggregated evidence focuses more on software reuse benefits than reuse costs. Objective: This study aims to cover the gaps mentioned in the context above by synthesizing and critically appraising the evidence reported on software reuse costs and benefits from industrial cases. Method: We used a systematic literature review (SLR) to conduct this study. The results of this SLR are based on a final set of 30 primary studies. Results: We identified nine software reuse benefits and six software reuse costs, in which better quality and improved productivity were investigated the most. The primary studies mostly used defect-based and development time-based metrics to measure reuse benefits and costs. Regarding the reuse practices, the results show that software product lines, verbatim reuse, and systematic reuse were the top investigated ones, contributing to more reuse benefits. The quality assessment of the primary studies showed that most of them are either of low (20%) or moderate (67%) quality. Conclusion: Based on the number and quality of the studies, we conclude that the strength of evidence for better quality and improved productivity as reuse benefits is high. There is a need to conduct more high quality studies to investigate, not only other reuse costs and benefits, but also how relatively new reuse-related practices, such as InnerSource and microservices architecture, impact software reuse. © 2024 The Author(s)
|
|
| 8. |
- Chen, Xingru, et al.
(author)
-
Using InnerSource for Improving Internal Reuse : An Industrial Case Study
- 2023
-
In: ACM International Conference Proceeding Series. - : Association for Computing Machinery (ACM). - 9798400700446 ; , s. 348-357
-
Conference paper (peer-reviewed)abstract
- Background: InnerSource consists of the use of open source development techniques within the corporation. It helps improve software reuse through increased transparency and inter-team collaboration. Companies need to understand their context and specific needs before deciding to adopt any specific InnerSource practices since they cannot apply all InnerSource practices at once. Aim: This study aims to support the case company in assessing its readiness for adopting InnerSource practices to improve its internal reuse, identify and prioritize the improvement areas, and identify suitable solutions. Method: We performed a case study using a questionnaire and a workshop to check the current and desired status of adopting InnerSource practices and collect potential solutions. Results: The study participants identified that the company needs to prioritize the improvements related to the discoverability, communication channels, and ownership of the reusable assets. In addition, they identified certain InnerSource practices as solutions for the prioritized improvement areas, such as better structured repositories for storing and searching the reusable assets and standardized documentation of the reusable assets. Conclusion: The questionnaire instrument aids the case company in identifying the improvement areas related to InnerSource and reuse practices. InnerSource practices could improve the development and maintenance of reusable assets. Keywords: InnerSource, software reuse, readiness © 2023 Owner/Author.
|
|
