16 results
Search Results
Now showing 1 - 10 of 16
Article Citation - WoS: 11Citation - Scopus: 13Assessing 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 - WoS: 3Citation - Scopus: 4Users' Behavioral Strategies Toward Mobile App Problems: Fight or Flight(Springer international Publishing Ag, 2019) Inal, Yavuz; Hacaloglu, TunaIn 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).Article Citation - WoS: 11Citation - Scopus: 13Exploring and Expanding Students' Success in Software Testing(Emerald Group Publishing Ltd, 2017) Mishra, Deepti; Ostrovska, Sofiya; Hacaloglu, TunaPurpose - Testing is one of the indispensable activities in software development and is being adopted as an independent course by software engineering (SE) departments at universities worldwide. The purpose of this paper is to carry out an investigation of the performance of learners about testing, given the tendencies in the industry and motivation caused by the unavailability of similar studies in software testing field. Design/methodology/approach - This study is based on the data collected over three years (between 2012 and 2014) from students taking the software testing course. The course is included in the second year of undergraduate curriculum for the bachelor of engineering (SE). Findings - It has been observed that, from the performance perspective, automated testing outperforms structural and functional testing techniques, and that a strong correlation exists among these three approaches. Moreover, a strong programming background does help toward further success in structural and automated testing, but has no effect on functional testing. The results of different teaching styles within the course are also presented together with an analysis exploring the relationship between students' gender and success in the software testing course, revealing that there is no difference in terms of performance between male and female students in the course. Moreover, it is advisable to introduce teaching concepts one at a time because students find it difficult to grasp the ideas otherwise. Research limitations/implications - These findings are based on the analysis conducted using three years of data collected while teaching a course in testing. Obviously, there are some limitations to this study. For example, student's strength in programming is calculated using the score of C programming courses taken in previous year/semester. Such scores may not reflect their current level of programming knowledge. Furthermore, attempt was made to ensure that the exercises given for different testing techniques have similar difficulty level to guarantee that the difference in success between these testing techniques is due to the inherent complexity of the technique itself and not because of different exercises. Still, there is small probability that a certain degree of change in success may be due to the difference in the difficulty levels of the exercises. As such, it is obviously premature to consider the present results as final since there is a lack of similar type of studies, with which the authors can compare the results. Therefore, more work needs to be done in different settings to draw sound conclusions in this respect. Originality/value - Although there are few studies (see e.g. Chan et al., 2005; Garousi and Zhi, 2013; Ng et al., 2004) exploring the preference of testers over distinct software testing techniques in the industry, there appears to be no paper comparing the preferences and performances of learners in terms of different testing techniques.Article STUDY ON CLOUD COMPUTING PERCEPTION OF TURKISH IT SECTOR(Univ Osijek, Tech Fac, 2016) Okan, Aylin Akca; Hacaloglu, Tuna; Yazici, AliIn this paper an empirical study was carried out to study the Cloud Computing (CC) perception in Turkey. To this extent this study intends to determine the perception of Information Technology decision makers such as Chief Executive Officers and Chief Information Officers by means of a survey by questionnaire approach to explore 98 both public and private IT executives' understandings and concerns about CC. The survey aims to determine how CC is perceived by public or private organizations that are already involved in the e-transformation process. Major results of the study are as follows: both public and private sector executives have positive perception over adoption of CC, participants think that especially web, e-mail, data storage and process management applications are adequate for CC. Lack of well-educated and experienced staff is found to be the common barrier on adopting CC by both public and private sector participants.Article Citation - WoS: 3Citation - Scopus: 6An Exploratory Case Study Using Events as a Software Size Measure(Springer, 2023) Hacaloglu, Tuna; Demirors, OnurSoftware Size Measurement is a critical task in Software Development Life Cycle (SDLC). It is the primary input for effort estimation models and an important measure for project control and process improvement. There exist various size measurement methods whose successes have already been proven for traditional software architectures and application domains. Being one of them, functional size measurement (FSM) attracts specific attention due to its applicability at the early phases of SDLC. Although FSM methods were successful on the data-base centric, transaction oriented stand-alone applications, in contemporary software development projects, Agile methods are highly used, and a centralized database and a relational approach are not used as before while the requirements suffer from a lack of detail. Today's software is frequently service based, highly distributed, message-driven, scalable and has unprecedented levels of availability. In the new era, event-driven architectures are appearing as one of the emerging approaches where the 'event' concept largely replaces the 'data' concept. Considering the important place of events in contemporary architectures, we focused on approaching the software size measurement problem from the event-driven perspective. This situation guided us to explore how useful event as a size measure in comparison to data-movement based methods. The findings of our study indicates that events can be promising for measurement and should be investigated further in detail to be formalized for creating a measurement model thereby providing a replicable approach.Article Citation - WoS: 16What We Know About Software Test Maturity and Test Process Improvement(Ieee Computer Soc, 2018) Garousi, Vahid; Felderer, Michael; Hacaloglu, Tuna[No Abstract Available]Conference Object Citation - WoS: 1Citation - Scopus: 3A Software Development Process Model for Cloud by Combining Traditional Approaches(Springer international Publishing Ag, 2015) Hacaloglu, Tuna; Eren, P. Erhan; Mishra, Deepti; Mishra, AlokEven though cloud computing is a technological paradigm that has been adopted more and more in various domains, there are few studies investigating the software development lifecycle in cloud computing applications and there is still not a comprehensive software development process model developed for cloud computing yet. Due to the nature of cloud computing that is completely different from the traditional software development, there is a need of suggesting process models to perform the software development systematically to create high quality software. In this study, we propose a new conceptual Software Development Life Cycle Model for Cloud Software Development that incorporates characteristics of different process models for traditional software development. The proposed model takes traditional model's specific characteristics into account and also considers cloud's specific nature i.e. advantages and challenges as well.Conference Object Citation - WoS: 7Citation - Scopus: 12Utilization of Three Software Size Measures for Effort Estimation in Agile World: A Case Study(IEEE, 2022) Unlu, Huseyin; Hacaloglu, Tuna; Buber, Fatma; Berrak, Kivilcim; Leblebici, Onur; Demirors, OnurFunctional size measurement (FSM) methods, by being systematic and repeatable, are beneficial in the early phases of the software life cycle for core project management activities such as effort, cost, and schedule estimation. However, in agile projects, requirements are kept minimal in the early phases and are detailed over time as the project progresses. This situation makes it challenging to identify measurement components of FSM methods from requirements in the early phases, hence complicates applying FSM in agile projects. In addition, the existing FSM methods are not fully compatible with today's architectural styles, which are evolving into event-driven decentralized structures. In this study, we present the results of a case study to compare the effectiveness of different size measures: functional -COSMIC Function Points (CFP)-, event-based - Event Points-, and code length-based - Line of Code (LOC)- on projects that were developed with agile methods and utilized a microservice- based architecture. For this purpose, we measured the size of the project and created effort estimation models based on three methods. It is found that the event-based method estimated effort with better accuracy than the CFP and LOC-based methods.Article Citation - WoS: 6Citation - Scopus: 8Software Size Measurement: Bridging Research and Practice(Ieee Computer Soc, 2024) Hacaloglu, Tuna; Unlu, Huseyin; Yildiz, Ali; Demirors, OnurThis study investigates the limited adoption of functional size measurement methods in the software development industry. Using insights from firms experienced in size measurement, it aims to uncover industry expectations and facilitate the translation of theoretical methodologies into practical applications.Review Citation - WoS: 65Citation - Scopus: 80Software Test Maturity Assessment and Test Process Improvement: a Multivocal Literature Review(Elsevier, 2017) Garousi, Vahid; Felderer, Michael; Hacaloglu, TunaContext: Software testing practices and processes in many companies are far from being mature and are usually conducted in ad-hoc fashions. Such immature practices lead to various negative outcomes, e.g., ineffectiveness of testing practices in detecting all the defects, and cost and schedule overruns of testing activities. To conduct test maturity assessment (TMA) and test process improvement (TPI) in a systematic manner, various TMA/TPI models and approaches have been proposed. Objective: It is important to identify the state-of-the-art and the-practice in this area to consolidate the list of all various test maturity models proposed by practitioners and researchers, the drivers of TMA/TPI, the associated challenges and the benefits and results of TMA/TPI. Our article aims to benefit the readers (both practitioners and researchers) by providing the most comprehensive survey of the area, to this date, in assessing and improving the maturity of test processes. Method: To achieve the above objective, we have performed a Multivocal Literature Review (MLR) study to find out what we know about TMA/TPI. A MLR is a form of a Systematic Literature Review (SLR) which includes the grey literature (e.g., blog posts and white papers) in addition to the published (formal) literature (e.g., journal and conference papers). We searched the academic literature using the Google Scholar and the grey literature using the regular Google search engine. Results: Our MLR and its results are based on 181 sources, 51 (29%) of which were grey literature and 130 (71%) were formally published sources. By summarizing what we know about TMA/TPI, our review identified 58 different test maturity models and a large number of sources with varying degrees of empirical evidence on this topic. We also conducted qualitative analysis (coding) to synthesize the drivers, challenges and benefits of TMA/TPI from the primary sources. Conclusion: We show that current maturity models and techniques in TMA/TPI provides reasonable advice for industry and the research community. We suggest directions for follow-up work, e.g., using the findings of this MLR in industry-academia collaborative projects and empirical evaluation of models and techniques in the area of TMA/TPI as reported in this article. (C) 2017 Elsevier B.V. All rights reserved.
