5 results
Search Results
Now showing 1 - 5 of 5
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 - 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.
