8 results
Search Results
Now showing 1 - 8 of 8
Conference Object Citation - WoS: 2A Proposal on Requirements for Cosmic Fsm Automation From Source Code(Ieee, 2016) Tarhan, Ayca; Ozkan, Baris; Icoz, Gonca CananAutomation of functional size measurement (FSM) process has increasingly gained importance since manual measurement is time-consuming, costly, and sometimes error-prone. There exist studies that automate measurement from different software artifacts such as requirements specifications, design models, and software code. In this study we review and compare four studies that we have carried out in recent years to automate COSMIC FSM from software code. Based on the comparison and the lessons learned, we derive an operational scenario for automated FSM from software code and propose a set of requirements that need to be considered in automation. We think the proposal will be helpful not only for our future studies and also for future work of interested researchers.Conference Object Cosmic Light Vs Cosmic Classic Manual: Case Studies in Functional Size Measurement(CEUR-WS, 2020) Hacaloglu,T.; Unlu,H.; Demirors,O.; Abran,A.Functional size has been used in software engineering for more than 40 years. When measured early in the software development life cycle, it can serve as direct input for effort estimation. The COSMIC Functional Size Measurement (FSM) method developed by the Common Software Measurement Consortium (COSMIC) is the latest ISO-compliant functional sizing method. A streamlined manual titled ''Software Development Velocity with COSMIC Function Points'' summarizes the measurement process and shortens the learning time. The aim of this study is to compare the classic COSMIC FSM manual and this new “light” manual in terms of accuracy of the resulting FSM applied to case studies. The findings show that use of the light manual results in accurate measurement. In addition, there were no significant time differences between the two. With respect to the variations in COSMIC Function Points (CFP) values in the two case studies, they three causes were identified: the Object of Interest (OOI) concept and corresponding data groups, details regarding Functional Process Independence, and Error/Confirmation messages related to the scope of the information included in the manuals. Copyright © 2020 for this paper by its authors.Conference Object Citation - Scopus: 1A Survey on Cosmic Students Estimation Challenge(CEUR-WS, 2022) Hacaloglu,T.; Say,B.; Unlu,H.; Omural,N.K.; Demirors,O.Software 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 - Scopus: 8An 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.Software 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.Conference Object Citation - WoS: 3Citation - Scopus: 4Effort Prediction for Microservices: a Case Study(Ieee, 2021) Unlu, Huseyin; Hacaloglu, Tuna; Leblebici, Onur; Demirors, OnurSoftware 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.Conference Object Citation - Scopus: 42Effort 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.Agile 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.Conference Object Citation - Scopus: 9A Proposal on Requirements for Cosmic Fsm Automation From Source Code(Institute of Electrical and Electronics Engineers Inc., 2017) Tarhan,A.; Ozkan,B.; Icoz,G.C.Automation of functional size measurement (FSM) process has increasingly gained importance since manual measurement is time-consuming, costly, and sometimes errorprone. There exist studies that automate measurement from different software artifacts such as requirements specifications, design models, and software code. In this study we review and compare four studies that we have carried out in recent years to automate COSMIC FSM from software code. Based on the comparison and the lessons learned, we derive an operational scenario for automated FSM from software code and propose a set of requirements that need to be considered in automation. We think the proposal will be helpful not only for our future studies and also for future work of interested researchers. © 2016 IEEE.Conference Object Citation - WoS: 16Citation - Scopus: 21Measureability of Functional Size in Agile Software Projects: Multiple Case Studies With Cosmic Fsm(Ieee, 2019) 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 practices
