Natasha Malveira Costa Valentim

Natasha Malveira Costa Valentim

Auto-generated profile, based on publicly available information

Natasha Malveira Costa Valentim

Federal University of Parana

Research Focus & Metrics

Academic Career Length

13Years (2014-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 May 2017
Verified
Conference Paper
Closed access
NVNatasha M. Costa Valentim
Natasha M. Costa Valentim
WSWilliamson Silva
Williamson Silva
TCTayana Conte
Tayana Conte
Design Thinking (DT) is relevant for companies committed to developing a more creative and innovative application. DT provides a human-centered view of technological artifact design. Therefore, it is important to learn DT in Computer Science and Software Engineering courses as an analytic and creative process, in order to better prepare students for the software development industry. We conducted an empirical study with 17 postgraduate students in the context of mobile applications design. We used coding procedures from the Grounded Theory method for analyzing the obtained qualitative data. Based on the results, we identified some difficulties that participants experienced in using different DT techniques. The results of this study can help teachers understand the difficulties faced by students in learning DT and, consequently, help them to look for new teaching strategies for their classes. Moreover, these results can contribute to the software industry showing the competitive advantages of using DT in the design of the applications under development, especially in mobile applications.

23 May 2018 in Journal of Software Engineering Research and Development
Verified
Journal Article
Open access
PDF file
ALAdriana Lopes
Adriana Lopes
NVNatasha Valentim
Natasha Valentim
BMBruna Moraes
Bruna Moraes
RZRenata Zilse
Renata Zilse
TCTayana Conte
Tayana Conte
Techniques that help in understanding and designing user needs are increasingly being used in Software Engineering to improve the acceptance of applications. Among these techniques we can cite personas, scenarios and interaction models. Personas are fictitious representations of target users. Scenarios provide various types of information at different levels of abstraction. Interaction models help in design of an adequate user interaction with the system. This paper presents a research that reports a set of practical activities applied by a software team using techniques in the analysis and design phases of a mobile application. In the analysis phase, we created personas and scenarios for the extraction of requirements. In the design phase, we created interaction models for describes the behavior between user and system during the interaction. We employed these interaction models to develop other artifacts, such as prototypes. In addition, we presented a technique developed by the analysis and design team for the inspection of interaction models. This technique reduced the spread of defects in the interaction models. From the results of this research, we suggest: (i) employing personas and scenarios to understand the requirements; (ii) employing interaction models to understand the behavior between user and system; and (iii) using interaction models as basis to develop other artifacts. Through the reporting of this set of practical activities, we hope to provide support for software engineers willing to adopt techniques that support the analysis and design of applications aiming at better quality of use for their users.

14 December 2022 in Informatics in Education
Verified
Journal Article
Open access
PDF file
APAna Paula Juliana Perin
Ana Paula Juliana Perin
DSDeivid Eive dos S. Silva
Deivid Eive dos S. Silva
NVNatasha M. C. Valentim
Natasha M. C. Valentim
In Education 4.0, a personalized learning process is expected, and that students are the protagonist. In this new education format, it is necessary to prepare students with the skills and competencies of the 21st-Century, such as teamwork, creativity, and autonomy. One of the ways to develop skills and competencies in students can be through block programming, which can be used with emerging technologies such as robotics and IoT and in an interdisciplinary way. Thus, block programming in High School is important because it is possible to work on aspects such as problem-solving, algorithmic thinking, among other skills (Perin et al., 2021), which are necessary in the contemporary world. Thus, our Systematic Mapping Study (SMS) aims to identify which block programming tools support of Education 4.0 in High School. Overall, 46 papers were selected, and data were extracted. Based on the results, a total of 24 identified block programming tools that can be used in high school collaboratively and playfully and with an interdisciplinary methodology. Moreover, it was possible to see that most studies address block programming with high school students, demonstrating a lack of studies that address block programming with teachers. This SMS contributed to identifying block programming tools, emerging technologies, audience (teacher or student), and learning spaces where block programming is being worked on.

1 November 2018 in International Journal of Software Engineering and Knowledge Engineering
Verified
Journal Article
Closed access
PDF file
EOEdson Oliveira
Edson Oliveira
TCTayana Conte
Tayana Conte
MCMarco Cristo
Marco Cristo
NVNatasha Valentim
Natasha Valentim


20 September 2017
Verified
Conference Paper
Open access
LSLeonardo Sousa
Leonardo Sousa
RORoberto Oliveira
Roberto Oliveira
AGAlessandro Garcia
Alessandro Garcia
JLJaejoon Lee
Jaejoon Lee
TCTayana Conte
Tayana Conte
CLCarlos Lucena
Carlos Lucena
When a software design decision has a negative impact on one or more quality attributes, we call it a design problem. For example, the Fat Interface problem indicates that an interface exposes non-cohesive services Thus, clients and implementations of this interface may have to handle with services that they are not interested. A design problem such as this hampers the extensibility and maintainability of a software system. As illustrated by the example, a single design problem often affects several elements in the program. Despite its harmfulness, it is difficult to identify a design problem in a system. It is even more challenging to identify design problems when the source code is the only available artifact. In particular, no study has observed what strategy(ies) developers use in practice to identify design problems when the design documentation is unavailable. In order to address this gap, we conducted a qualitative analysis on how developers identify design problems in two different scenarios: when they are either familiar (Scenario 1) or unfamiliar (Scenario 2) with the analyzed systems. Developers familiar with the systems applied a diverse set of strategies during the identification of each design problem. Some strategies were frequently used to locate code elements for analysis, and other strategies were frequently used to confirm design problems in these elements. Developers unfamiliar with the systems relied only on the use of code smells along the task. Despite some differences among the subjects from both scenarios, we noticed that developers often search for multiple indicators during the identification of each design problem