| 1. |
- Pádua, Diana, et al.
(author)
-
High-Throughput Drug Screening Revealed That Ciclopirox Olamine Can Engender Gastric Cancer Stem-like Cells
- 2023
-
In: Cancers. - 2072-6694. ; 15:17
-
Journal article (peer-reviewed)abstract
- Cancer stem cells (CSCs) are relevant therapeutic targets for cancer treatment. Still, the molecular circuits behind CSC characteristics are not fully understood. The low number of CSCs can sometimes be an obstacle to carrying out assays that explore their properties. Thus, increasing CSC numbers via small molecule-mediated cellular reprogramming appears to be a valid alternative tool. Using the SORE6-GFP reporter system embedded in gastric non-CSCs (SORE6−), we performed a high-throughput image-based drug screen with 1200 small molecules to identify compounds capable of converting SORE6− to SORE6+ (CSCs). Here, we report that the antifungal agent ciclopirox olamine (CPX), a potential candidate for drug repurposing in cancer treatment, is able to reprogram gastric non-CSCs into cancer stem-like cells via activation of SOX2 expression and increased expression of C-MYC, HIF-1α, KLF4, and HMGA1. This reprogramming depends on the CPX concentration and treatment duration. CPX can also induce cellular senescence and the metabolic shift from oxidative phosphorylation (OXPHOS) to glycolysis. We also disclose that the mechanism underlying the cellular reprogramming is similar to that of cobalt chloride (CoCl2), a hypoxia-mimetic agent.
|
|
| 2. |
- Peixoto, Mariana, et al.
(author)
-
Evaluating a privacy requirements specification method by using a mixed-method approach : results and lessons learned
- 2023
-
In: Requirements Engineering. - : Springer Science+Business Media B.V.. - 0947-3602 .- 1432-010X. ; 28:2, s. 229-255
-
Journal article (peer-reviewed)abstract
- Although agile software development (ASD) has been adopted in the industry, requirements approaches for ASD still neglect non-functional requirements. Privacy has become a concern due to new user demands and data protection laws. Hence, privacy needs to be properly specified, but agile requirements engineering techniques do not explicitly represent privacy requirements and, therefore, are not able to proper analyze such requirements. In this context, Privacy Criteria Method (PCM), an approach to specify privacy in requirements activities, was proposed to produce more complete and detailed privacy requirements. By considering PCM a promising approach to be used in ASD and the importance of empirical evaluation of new methods, we have as objectives: 1 evaluate the ability of PCM to support systems analysts in specifying privacy requirements when used in conjunction with some agile specification methods; and 2 show our lessons learned in conducting empirical research based on an mix-method approach defined to empirically evaluate the suitability of a requirements specification in specifying privacy requirements. Mixed-method approach is a controlled experiment as a quantitative evaluation and a feasibility study (questionnaire and task analysis based) study as a qualitative and quantitative evaluation. The requirements specifications following PCM allow to represent privacy aspects, such as user’s personal data and the privacy mechanism that can be used to mitigate a privacy risk scenario. We also observed that some extra time is necessary to specify privacy requirements with PCM, but it does not imply a greater perceived effort. Specifications produced with PCM are of good quality and more privacy detailed. Additionally, we attest to the importance of conducting empirical research to evaluate new methods. PCM assists in specifying more complete and detailed in relation to traditional techniques used in ASD, which facilitates communication between the requirements analysts and developers. © 2022, The Author(s), under exclusive licence to Springer-Verlag London Ltd., part of Springer Nature.
|
|
| 3. |
- Peixoto, Mariana, et al.
(author)
-
On Understanding How Developers Perceive and Interpret Privacy Requirements Research Preview
- 2020
-
In: Lecture Notes in Computer Science. - Cham : Springer. - 9783030444280 ; , s. 116-123
-
Conference paper (peer-reviewed)abstract
- [Context and motivation] Ensuring privacy of users’ data has become a top concern in software development, either to satisfy users’ needs or to comply with privacy laws. The problem may increase by the time a new law is in the vacancy period, and companies are working to understand how to comply with it. In addition, research has shown that many developers do not have sufficient knowledge about how to develop privacy-sensitive software. [Question/problem] Motivated by this scenario, this research investigates the personal factors affecting the developers’ understanding of privacy requirements during the vacancy period of a data protection law. [Principal ideas/results] We conducted thirteen interviews in six different private companies. As a result, we found nine personal factors affecting how software developers perceive and interpret privacy requirements. [Contribution] The identification of the personal factors contributes to the elaboration of effective methods for promoting proper privacy-sensitive software development. © 2020, Springer Nature Switzerland AG.
|
|
| 4. |
- Peixoto, Mariana, et al.
(author)
-
Privacy Requirements Specification in Agile Software Development
- 2021
-
In: Proceedings of the IEEE International Conference on Requirements Engineering. - : IEEE Computer Society. - 9781665428569 ; , s. 512-513
-
Conference paper (peer-reviewed)abstract
- Privacy has become a concern in Agile Software Development (ASD), either to satisfy users' needs or to comply with privacy laws. However, recent studies have shown that ASD approaches still neglect non-functional requirements (NFRs), as is the privacy case. This concern and new data protection laws that came into force recently led companies to face the challenges to understand the laws and to comply with them. In addition, research has shown that many developers do not have sufficient knowledge about how to develop privacy-sensitive software. Motivated by this scenario, this tutorial aims to draw attention to the need to understand privacy from the beginning of the software development lifecycle. Initially, we will present an overview of privacy, as well as several privacy principles. Later, we will show the main data protection laws (In-depth detailing of the General Data Protection Regulation - GDPR). Then, we will discuss how to read and evaluate privacy policies. Finally, we will present an approach for specifying privacy requirements in ASD called Privacy Criteria Method (PCM). At the end of the tutorial, participants will be able to have a critical and technical view of privacy when performing the requirements specification activity. © 2021 IEEE.
|
|
| 5. |
- Peixoto, Mariana, et al.
(author)
-
The perspective of Brazilian software developers on data privacy
- 2023
-
In: Journal of Systems and Software. - : Elsevier. - 0164-1212 .- 1873-1228. ; 195
-
Journal article (peer-reviewed)abstract
- Context: Maintaining the privacy of user data is a concern in software development to satisfy customer needs or to comply with privacy laws. Recent studies have shown that software development approaches still neglect non-functional requirements, including privacy. Concern about privacy may increase in the period between when a privacy law is initially announced and when it is passed into law. During this period, companies will be challenged to comply with the new law. Research has shown that many developers do not have sufficient knowledge to develop privacy-preserving software systems.Objective: We investigate the level of knowledge and understanding that developers possess regarding privacy. We explore the personal, behavioural, and external environmental factors affecting a developer's decision-making regarding privacy requirements.Methods: We replicated a study by means of in-depth, semi-structured interviews with thirteen practitioners at six companies. Our data analysis is based on the principles of ‘grounded theory codification’.Results: We identified nine personal factors, five behavioural factors, and seven external environment factors that are relevant to how software developers make decisions regarding.Conclusion: Our identification of factors that influence the development of privacy-preserving software systems can be seen as a contribution to the specification of effective methods for securing privacy. © 2022 Elsevier Inc.
|
|
