WoS
Permanent URI for this collectionhttps://hdl.handle.net/20.500.14411/18
Browse
15 results
Search Results
Conference Object Citation - WoS: 4Citation - Scopus: 6Predicting Software Functional Size Using Natural Language Processing: an Exploratory Case Study(IEEE, 2024-08-28) Unlu, Huseyin; Tenekeci, Samet; Ciftci, Can; Oral, Ibrahim Baran; Atalay, Tunahan; Hacaloglu, Tuna; Demirors, OnurSoftware Size Measurement (SSM) plays an essential role in software project management as it enables the acquisition of software size, which is the primary input for development effort and schedule estimation. However, many small and medium-sized companies cannot perform objective SSM and Software Effort Estimation (SEE) due to the lack of resources and an expert workforce. This results in inadequate estimates and projects exceeding the planned time and budget. Therefore, organizations need to perform objective SSM and SEE using minimal resources without an expert workforce. In this research, we conducted an exploratory case study to predict the functional size of software project requirements using state-of-the-art large language models (LLMs). For this aim, we fine-tuned BERT and BERT_SE with a set of user stories and their respective functional size in COSMIC Function Points (CFP). We gathered the user stories included in different project requirement documents. In total size prediction, we achieved 72.8% accuracy with BERT and 74.4% accuracy with BERT_SE. In data movement-based size prediction, we achieved 87.5% average accuracy with BERT and 88.1% average accuracy with BERT_SE. Although we use relatively small datasets in model training, these results are promising and hold significant value as they demonstrate the practical utility of language models in SSM.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: 12Citation - 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: 8Citation - Scopus: 14Utilization of Three Software Size Measures for Effort Estimation in Agile World: A Case Study(IEEE, 2022-08) 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: 2Citation - Scopus: 4Online Collaborative Tool Usage for Review Meetings in Software Engineering Courses(Routledge Journals, Taylor & Francis Ltd, 2019-08-08) Turhan, Cigdem; Akman, Ibrahim; Hacaloglu, TunaThe 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.Article Citation - WoS: 15What We Know About Software Test Maturity and Test Process Improvement(Ieee Computer Soc, 2018-01) Garousi, Vahid; Felderer, Michael; Hacaloglu, Tuna[No Abstract Available]Review Citation - WoS: 67Citation - Scopus: 82Software Test Maturity Assessment and Test Process Improvement: a Multivocal Literature Review(Elsevier, 2017-05) 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.Conference Object Citation - WoS: 3Citation - Scopus: 5Users' 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).Conference Object Citation - WoS: 17Citation - Scopus: 22Measureability of Functional Size in Agile Software Projects: Multiple Case Studies With Cosmic Fsm(Ieee, 2019-08) Hacaloglu, Tuna; Demirors, OnurFunctional size measurement (FSM) has been used in software engineering for decades as a main driver for estimation and significant input for other various project management activities throughout the project life span. To apply FSM accurately at the early stages of software development process, especially for estimation purposes, functional user requirements need to be available in detail as required by the adopted FSM method. However, in agile software development, requirement specifications, in general, are kept minimal. For this reason, the adjustment of the requirements to the necessary granularity level has been articulated as one of the barriers preventing the diffusion of FSM practices among agile teams. In this paper, we take a closer look at this problem in order to investigate the usability of FSM and to reveal FSM related challenges empirically through case studies on real agile projects from different software organizations. This study also provides a snapshot of agile organizations in terms of requirement specification and estimation related practicesArticle Citation - WoS: 3Citation - Scopus: 6An Exploratory Case Study Using Events as a Software Size Measure(Springer, 2023-04-13) 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.