Hacaloğlu, Tuna
Loading...
Name Variants
Hacaloğlu,T.
H.,Tuna
T., Hacaloğlu
T.,Hacaloğlu
Hacaloglu, Tuna
Tuna, Hacaloğlu
Hacaloglu,T.
T., Hacaloglu
H., Tuna
Tuna, Hacaloglu
T.,Hacaloglu
Hacaloğlu, Tuna
Hacaloglu T.
H.,Tuna
T., Hacaloğlu
T.,Hacaloğlu
Hacaloglu, Tuna
Tuna, Hacaloğlu
Hacaloglu,T.
T., Hacaloglu
H., Tuna
Tuna, Hacaloglu
T.,Hacaloglu
Hacaloğlu, Tuna
Hacaloglu T.
Job Title
Doktor Öğretim Üyesi
Email Address
tuna.hacaloglu@atilim.edu.tr
ORCID ID
Scopus Author ID
Turkish CoHE Profile ID
Google Scholar ID
WoS Researcher ID
Scholarly Output
27
Articles
14
Citation Count
144
Supervised Theses
0
27 results
Scholarly Output Search Results
Now showing 1 - 10 of 27
Article Citation Count: 2Online collaborative tool usage for review meetings in software engineering courses(Routledge Journals, Taylor & Francis Ltd, 2022) Turhan, Cigdem; Akman, Ibrahim; Hacaloglu, Tuna; Information Systems Engineering; Software Engineering; Computer EngineeringThe instructors generally utilize conventional methods in teaching software engineering courses, where the students are provided theoretical knowledge based on text books or lecture notes. Usage of collaborative tools may be a solution to the problems of not practicing the depth of the components of the subject. This study proposes the usage of a collaborative tool, namely, Google Docs in a software engineering course based on predefined scenarios. The review meeting subject was selected for this purpose and students' reactions were assessed with a survey after the completion of the experiments. The survey data were analysed using least square regression method. The results have shown that efficiency, certainty, satisfaction, advantage, complexity, learnability, and intention are indicators of the adoption of the online collaborative tool.Conference Object Citation Count: 2An Exploratory Case Study on Effort Estimation in Microservices(Institute of Electrical and Electronics Engineers Inc., 2023) Unlu,H.; Hacaloglu,T.; Omural,N.K.; Caliskanel,N.; Leblebici,O.; Demirors,O.; Information Systems EngineeringSoftware project management plays an important role in producing high-quality software, and effort estimation can be considered as a backbone for successful project management. Size is a very significant attribute of software by being the only input to perform early effort estimation. Even though functional size measurement methods showed successful results in effort estimation of traditional data-centric architectures such as monoliths, they were not designed for today's architectures which are more service-based and decentralized such as microservices. In these new systems, the event concept is highly used specifically for communication among different services. By being motivated by this fact, in this study, we looked for more microservice-compatible ways of sizing microservices using events and developed a method accordingly. Then, we conducted an exploratory case study in an organization using agile methods and measured the size of 17 Product Backlog Items (PBIs) to assess how this proposed method can be useful in effort estimation in microservices. The implication from the case study is that despite performing a more accurate effort estimation using the proposed size measurement than COSMIC, we were unable to significantly outperform using the total number of events. However, our suggested approach demonstrated to us a different way to use software size in terms of events, namely, to determine the coupling complexity of the project. This finding can be beneficial specifically when evaluating the change requests. © 2023 IEEE.Article Citation Count: 6Teaching Software Verification and Validation Course: A Case Study(Tempus Publications, 2014) Mishra, Deepti; Hacaloglu, Tuna; Mishra, Alok; Computer Engineering; Software Engineering; Information Systems EngineeringSoftware verification and validation (V & V) is one of the significant areas of software engineering for developing high quality software. It is also becoming part of the curriculum of a universities' software and computer engineering departments. This paper reports the experience of teaching undergraduate software engineering students and discusses the main problems encountered during the course, along with suggestions to overcome these problems. This study covers all the different topics generally covered in the software verification and validation course, including static verification and validation. It is found that prior knowledge about software quality concepts and good programming skills can help students to achieve success in this course. Further, team work can be chosen as a strategy, since it facilitates students' understanding and motivates them to study. It is observed that students were more successful in white box testing than in black box testing.Conference Object Citation Count: 1Effort Prediction for Microservices: A Case Study(Ieee, 2021) Unlu, Huseyin; Hacaloglu, Tuna; Leblebici, Onur; Demirors, Onur; Information Systems EngineeringSoftware size measurement is critical as an input to perform important project management processes such as effort, cost and schedule estimation. Functional size measurement (FSM) methods are beneficial in terms of being applicable in the early phases of the software life cycle over functional requirements and providing a systematic and repeatable method. However, in agile organizations, it can be challenging to seperate measurement components of FSM methods from requirements in the early phases as the documentation is kept to a minimum compared to traditional methods such as the Waterfall Model and is detailed as the project steps. In addition, the existing FSM methods are not fully compatible with today's architectural structures, which are from being data-driven and to evolve into a behaviour-oriented structure. In this study, we performed a case study which includes a project developed with agile methods and using microservice-based architecture to compare the effectiveness of COSMIC FSM and event-based software size measurement. For this purpose, we measured the size of the project and created effort estimation models based on two methods. The measurers had difficulty in applying both methods due to the limited detail level of the requirements in the project. However, the event-based method was found to estimate effort with less error than the COSMIC FSM method.Article Citation Count: 7Teaching software verification and validation course: A case study(Tempus Publications, 2014) Mishra,D.; Hacaloglu,T.; Mishra,A.; Computer Engineering; Information Systems Engineering; Software EngineeringSoftware verification and validation (V & V) is one of the significant areas of software engineering for developing high quality software. It is also becoming part of the curriculum of a universities' software and computer engineering departments. This paper reports the experience of teaching undergraduate software engineering students and discusses the main problems encountered during the course, along with suggestions to overcome these problems. This study covers all the different topics generally covered in the software verification and validation course, including static verification and validation. It is found that prior knowledge about software quality concepts and good programming skills can help students to achieve success in this course. Further, team work can be chosen as a strategy, since it facilitates students' understanding and motivates them to study. It is observed that students were more successful in white box testing than in black box testing. © 2014 TEMPUS Publications.Conference Object Citation Count: 24Effort estimation for agile software development: Comparative case studies using COSMIC functional size measurement and story points(Association for Computing Machinery, 2017) Salmanoglu,M.; Hacaloglu,T.; Demirors,O.; Information Systems EngineeringAgile methodologies have gained significant popularity among software development organizations during the last decade. Although agile methodologies are regarded as minimizing formal processes, they still utilize an estimation methodology for proper management. Story point is the most common input for agile effort estimation. Story point is an arbitrary measure; it reflects experiences of project participants. On the other hand, functional size is an alternative measure used in practice as an input for effort estimation. In this research, we collect and present the outcomes of three case studies which compared the effectiveness of COSMIC-based and story point based effort estimation in agile context. On selected projects of these organizations, software functional size was measured with COSMIC functional size measurement methodology. Effort prediction models were formed by using COSMIC size and actual effort spent; and the models were tested in terms of their effectiveness. The results show controversial outcomes. For all the cases, COSMIC based estimation was more precise. Therefore, COSMIC is an appropriate measure to estimate the effort in organizations that adopt agile software development. It is also observed that COSMIC allowed for computing productivity which has less disperse distribution than the productivity computed with SP. The data is also provided to help other researchers conduct their own studies. © 2017 Association for Computing Machinery.Article Citation Count: 11Assessing Team Work in Engineering Projects(Tempus Publications, 2015) Mishra, Deepti; Ostrovska, Sofiya; Hacaloglu, Tuna; Mathematics; Computer Engineering; Information Systems EngineeringTeam work is considered a valuable teaching technique in higher education. However, the assessment of an individual's work in teams has proved to be a challenging task. Consequently, self-and peer-evaluations are becoming increasingly popular for the assessment of individuals in a team work, though it is essential to determine whether students can judge their own as well as their peer's performance effectively. Self-and peer-evaluations have been applied in different disciplines and their authenticity with regard to teacher's assessment has been evaluated in the literature but this issue has not been investigated in the field of engineering education so far. In this study, a peer-and self-assessment procedure is applied to the evaluation of a project work conducted in teams of 3 or 4 students. The participants were engineering students taking two similar courses related with database design and development. It is found that a majority of the students were unable to assess themselves as objectively as their instructor. Further, it is observed that successful students tend to under-estimate, whereas unsuccessful students tend to over-estimate, their own performance. The paper also establishes that the results of self-assessments are independent from the gender factor.Conference Object Citation Count: 5Challenges of using software size in agile software development: A systematic literature review(CEUR-WS, 2018) Hacaloglu,T.; Demirors,O.; Information Systems EngineeringSoftware size is a fundamental measure for software management. Size is used for a variety of purposes, such as benchmarking, normalization, and portfolio measurement, and it is frequently considered as the sole input of estimation. Estimations can be produced for various reasons; e.g., to predict effort, cost and duration of software development projects. There are different types of software size measures. Particularly in projects where agile methodologies are adopted, measurement becomes a significant challenge as it is perceived as a non-value-added task and records of tasks such as requirements identification are not always consistent. The difficulties of applying traditional size measurement techniques in agile contexts, however, do not diminish the need, and new methods and techniques are introduced to improve the manageability of the agile projects. In this paper, we discuss estimation and measurement approaches in relation with ―software size in agile contexts. Based on this review, we present the perceptions of software size and related challenges, such as misinterpretation of size, difficulties in implementation, and acceptability of the measurement processes. We anticipate that providing a baseline for the state of software size measures in agile contexts and presenting related challenges, particularly in terms of its acceptability by practitioners can shed light on the development of new techniques. © 2018 CEUR-WS. All rights reserved.Conference Object Citation Count: 1A Survey on COSMIC Students Estimation Challenge(CEUR-WS, 2022) Hacaloglu,T.; Say,B.; Unlu,H.; Omural,N.K.; Demirors,O.; Information Systems Engineering; Software EngineeringSoftware project management is a significant software engineering practice that is highly related to achieving software-specific project goals. This study aims to share students’ perceptions of incorporating an international software estimation challenge called “COSMIC Students’ Estimation Challenge” into a software project management course. For this aim, students were taught the COSMIC Functional Size Measurement method and entered the competition. After the competition, a questionnaire asking for the students’ opinions was collected. The objective of the research is to get an insight into to what extent incorporating this type of competition activity -a challenge- can contribute to students’ learning perceptions. In the long run, the findings can contribute to creating a foresight about making the necessary curriculum arrangements to form a more up-to-date and dynamic education plan by including the methods applied in the software industry in Software Engineering education. The results suggest that this kind of competition experience and preparation is helpful for students to learn the COSMIC method. © 2020 Copyright for this paper by its authors.Conference Object Citation Count: 2Users' Behavioral Strategies Toward Mobile App Problems: Fight or Flight(Springer international Publishing Ag, 2019) Inal, Yavuz; Hacaloglu, Tuna; Information Systems EngineeringIn this paper, we identify two distinct behavioral strategies for dealing with problems encountered in the use of mobile apps - fight or flight. In the fight strategy, individuals do not give up using an app when faced with a problem; rather, they experiment with different ways to cope with that problem, whereas the flight strategy refers to the user's decision to uninstall an app when they encounter a problem and/or their intention to use an alternative app. These strategies were identified from an analysis of documents, which forty-two users reported, and can be used to understand how users deal with encountered problems. The participants were asked to use a mobile app of their choice for one week and report the behavioral strategies they utilized to counter problems they experienced. According to the findings obtained from content analysis, the most reported complaints concerned the categories of interface design, functional error, feature request, and feature removal. The participants who complained about functional errors, frustrating features, and slow application speed stopped using the app (flight behavior) whereas those that were dissatisfied with the interface, a missing feature or the content of the app continued to use the app and tried to overcome the problems (fight behavior).
- «
- 1 (current)
- 2
- 3
- »