Applied Sciences

Permanent URI for this communityhttps://hdl.handle.net/11693/115470

Browse

Browsing Applied Sciences by Author "Albayrak, Özlem"

Filter results by typing the first few letters
Now showing 1 - 6 of 6
  • Thumbnail Image
    ItemOpen Access
    Are software engineers' responses to incomplete requirements related to project characteristics?
    (IEEE, 2009) Albayrak, Özlem; Albayrak, Duygu; Kiliç, T.
    Software requirements quality affects software product quality. For high-quality software products, software requirements must be complete. When faced with incomplete requirements, software engineers attempt to fill the requirements' gaps differently, either by getting feedback from the user or by making assumptions. Assumptions may be explicit or implicit. Explicit assumptions are preferable to implicit assumptions as explicit assumptions can be validated. We conduct an empirical study to determine whether the number of explicit assumptions made by software engineers is related to a project's characteristics. Using data from two CMMI Level 3 companies and 16 projects, we investigated the responses of 92 software engineers to the same incomplete software requirement. Our findings show possible relationships between projects' characteristics and the number of explicit assumptions. ©2009 IEEE.
  • Thumbnail Image
    ItemOpen Access
    An experiment to observe the impact of UML diagrams on the effectiveness of software requirements inspections
    (IEEE, 2009) Albayrak, Özlem
    Software inspections aim to find defects early in the development process and studies have found them to be effective. However, there is almost no data available regarding the impact of UML diagram utilization in software requirements specification documents on inspection effectiveness. This paper addresses this issue by investigating whether inclusion of UML diagrams impacts the effectiveness of requirements inspection. We conducted an experiment in an academic environment with 35 subjects to empirically investigate the impact of UML diagram inclusion on requirements inspections' effectiveness and the number of reported defects. The results show that including UML diagrams in requirements specification document significantly impacts the number of reported defects, and there is no significant impact on the effectiveness of individual i nspections. © 2009 IEEE.
  • Thumbnail Image
    ItemOpen Access
    Impact of maintainability defects on code inspections
    (ACM, 2010) Albayrak, Özlem; Davenport, David
    Software inspections are effective ways to detect defects early in the development process. In this paper, we analyze the impact of certain defect types on the effectiveness of code inspection. We conducted an experiment in an academic environment with 88 subjects to empirically investigate the effect of two maintainability defects, i.e., indentation and naming conventions, on the number of functional defects found, the effectiveness of functional defect detections, and the number of false positives reported during individual code inspections. Results show that in cases where both naming conventions and indentation defects exist, the participants found minimum number of defects and reported the highest number of false positives, as compared to the cases where either indentation or naming defects exist. Among maintainability defects, indentation seems to significantly impact the number of functional defects found by the inspector, while the presence of naming conventions defects seems to have no significant impact on the number of functional defects detected. The presence of maintainability defects significantly impacts the number of false positives reported. On the effectiveness of individual code inspectors we observed no significant impact originated from the presence of indentation or naming convention defects. © 2010 ACM.
  • Thumbnail Image
    ItemOpen Access
    Incomplete software requirements and assumptions made by software engineers
    (IEEE, 2009) Albayrak, Özlem; Kurtoǧlu, Hülya; Biçakçi, M.
    Many software engineers make implicit assumptions when working with incomplete software requirements. To study assumptions made by software engineers while converting incomplete requirements to software design or to implementation phase deliverables, we conducted an experiment with 251 software engineers from eight companies. The results of this empirical study showed that how software engineers responded (using source code, pseudo code, or prototype) to an incomplete requirement significantly impacted the number of explicit assumptions they made. We studied relationships between the number of explicit assumptions and the engineers' experience and educational backgrounds. On average, non-computer-background engineers made more explicit assumptions than computerbackground graduates. We found a significant relationship between the engineers' experience and the number of explicit assumptions made. We discuss the results and their implications. © 2009 IEEE.
  • No Thumbnail Available
    ItemMetadata only
    Software quality and model-based process improvement
    (CRC Press, 2022-05-30) Bariş, Özkan; Albayrak, Özlem; Demirörs, Onur
    In this chapter, we introduced software quality and model based process improvement. Quality is more and more often seen as a critical software attribute and a determinant of business success. The absence of quality in software products and services results in dissatisfied users, financial loss, and may even endanger to our lives. SPI is a process oriented approach to address quality problems. We presented underlying principles by focusing on quality, process and quality, and the Co Q. We explained quality using different defining approaches, such as transcendental, product, user, manufacturing, and value based approaches. We then defined process and qualitystartingwiththeconceptofprocessaswidelyappreciatedastheproper ground for improving product quality and productivity. We highlighted the importance of SPC, plan do check act, and TQM. We also explained Co Q. Co Q analysis and technique shave been in use for more than 50 years and there are multiple models for Co Q. These models are the effective tools in feasibility analysis of SPI programs and the measurement and evaluation of the program performance. Both theory and experience advise investing on prevention and appraisal costs to get the highest returns from the decreased costs of appraisal and failure. In terms of best practices, we focused on software process maturity, models for SPI, and results from implementations. The use of maturity models has been popularized in software engineering through the SEI software CMM, which was published in 1991. In 1993,inEurope, ISO started the SPICE initiative. Both these models define capability levels for software processes and corresponding key process areas. Not every organization that has attempted model based process improvement has succeeded. A group of problems were observed to be general and related to the management of change and to underestimated costs and timeframes. Survey results also included evidence that SPI efforts were overcome by crisis due political struggles within the organizations. Software processes are characterized by a vast number off actors, that is, business goals, organizational culture, accumulated knowledge and experience, company size, the market, domain and environmental and regulatory constraints, etc. SPI is thus challenged by this process diversity, and there is no generic reference model that suits all software development projects and organizations. Furthermore, our analysis showed that the main are as of future research should focus on SPI for small organizations and agile development, measurement, and using SPC and automation/tools.
  • Thumbnail Image
    ItemOpen Access