Software Quality in Academic Curriculum: A Case Study in Turkey

2012 ◽  
Author(s):  
O. Tolga Pusatli ◽  
Sanjay Misra
Keyword(s):  
Software Quality ◽  
Academic Curriculum

scholarly journals The Relation of Test-Related Factors to Software Quality: A Case Study on Apache Systems

2021 ◽  
Vol 26 (2) ◽  
Author(s):  
Fabiano Pecorelli ◽  
Fabio Palomba ◽  
Andrea De Lucia
Keyword(s):  
Software Quality ◽  
Compelling Evidence ◽  
Related Factors ◽  
Code Coverage ◽  
Production Code ◽  
Software Code ◽  
Class Test ◽  
Code Quality ◽  
Lack Of Knowledge

AbstractTesting represents a crucial activity to ensure software quality. Recent studies have shown that test-related factors (e.g., code coverage) can be reliable predictors of software code quality, as measured by post-release defects. While these studies provided initial compelling evidence on the relation between tests and post-release defects, they considered different test-related factors separately: as a consequence, there is still a lack of knowledge of whether these factors are still good predictors when considering all together. In this paper, we propose a comprehensive case study on how test-related factors relate to production code quality in Apache systems. We first investigated how the presence of tests relates to post-release defects; then, we analyzed the role played by the test-related factors previously shown as significantly related to post-release defects. The key findings of the study show that, when controlling for other metrics (e.g., size of the production class), test-related factors have a limited connection to post-release defects.

AN EMPIRICAL STUDY OF SOFTWARE METRICS FOR ASSESSING THE PHASES OF AN AGILE PROJECT

2012 ◽  
Vol 22 (04) ◽  
pp. 525-548 ◽  
Author(s):  
GIULIO CONCAS ◽  
MICHELE MARCHESI ◽  
GIUSEPPE DESTEFANIS ◽  
ROBERTO TONELLI
Keyword(s):  
Software Quality ◽  
Web Application ◽  
Software Metrics ◽  
Pair Programming ◽  
Application Development ◽  
Agile Practices ◽  
Code Metrics ◽  
Agile Process ◽  
Adoption Level

We present an analysis of the evolution of a Web application project developed with object-oriented technology and an agile process. During the development we systematically performed measurements on the source code, using software metrics that have been proved to be correlated with software quality, such as the Chidamber and Kemerer suite and Lines of Code metrics. We also computed metrics derived from the class dependency graph, including metrics derived from Social Network Analysis. The application development evolved through phases, characterized by a different level of adoption of some key agile practices — namely pair programming, test-based development and refactoring. The evolution of the metrics of the system, and their behavior related to the agile practices adoption level, is presented and discussed. We show that, in the reported case study, a few metrics are enough to characterize with high significance the various phases of the project. Consequently, software quality, as measured using these metrics, seems directly related to agile practices adoption.

Trusting Computers Through Trusting Humans

2008 ◽  
pp. 3460-3474
Author(s):  
Alison Adam ◽  
Paul Spedding
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Computer System ◽  
Software Quality ◽  
Software Verification ◽  
Mathematical Proof ◽  
Quality Standards ◽  
Software Quality Assurance ◽  
The Social

This article considers the question of how we may trust automatically generated program code. The code walkthroughs and inspections of software engineering mimic the ways that mathematicians go about assuring themselves that a mathematical proof is true. Mathematicians have difficulty accepting a computer generated proof because they cannot go through the social processes of trusting its construction. Similarly, those involved in accepting a proof of a computer system or computer generated code cannot go through their traditional processes of trust. The process of software verification is bound up in software quality assurance procedures, which are themselves subject to commercial pressures. Quality standards, including military standards, have procedures for human trust designed into them. An action research case study of an avionics system within a military aircraft company illustrates these points, where the software quality assurance (SQA) procedures were incommensurable with the use of automatically generated code.

Enhancing the Testability of Web Services

2010 ◽  
pp. 223-244
Author(s):  
Daniel Brenner ◽  
Barbara Paech ◽  
Matthias Merdes ◽  
Rainer Malaka
Keyword(s):  
Web Services ◽  
Software Quality ◽  
Release Time ◽  
Acceptance Testing ◽  
Testing System ◽  
Software Applications ◽  
Service Oriented ◽  
Phases Of Development ◽  
Early Phases

For the foreseeable future, testing will remain the mainstay of software quality assurance and measurement in all areas of software development, including Web services and service-oriented systems. In general, however, testing Web services is much more challenging than testing normal software applications, not because they are inherently more complex, but because of the limited control and access that users of Web services have over their development and deployment. Whereas the developers of normal applications, by definition, have full control over their application until release time, and thus, can subject them to all kinds of tests in various combinations (e.g., integration testing, system testing, regression testing, acceptance testing, etc.), users of Web services can often only test them at run-time after they have already been deployed and put into service. Moreover, users of Web services often have to share access to them with other concurrent users. In order to effectively test Web services under these conditions special measures and approaches need to be taken to enhance their testability. Right from the early phases of development, the testability of services needs to be taken into account and “designed into” services. In this chapter we consider these issues and with the aid of a case study we present a methodology that can be used to enhance the testability of Web services.

Trusting Computers Through Trusting Humans

2011 ◽  
pp. 384-398
Author(s):  
Alison Adam ◽  
Paul Spedding
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Computer System ◽  
Software Quality ◽  
Software Verification ◽  
Mathematical Proof ◽  
Quality Standards ◽  
Software Quality Assurance ◽  
The Social

This chapter considers the question of how we may trust automatically generated program code. The code walkthroughs and inspections of software engineering mimic the ways that mathematicians go about assuring themselves that a mathematical proof is true. Mathematicians have difficulty accepting a computer generated proof because they cannot go through the social processes of trusting its construction. Similarly, those involved in accepting a proof of a computer system or computer generated code cannot go through their traditional processes of trust. The process of software verification is bound up in software quality assurance procedures, which are themselves subject to commercial pressures. Quality standards, including military standards, have procedures for human trust designed into them. An action research case study of an avionics system within a military aircraft company illustrates these points, where the software quality assurance (SQA) procedures were incommensurable with the use of automatically generated code.

scholarly journals Offshore Insourcing: A Case Study on Software Quality Alignment

2011 ◽  
Author(s):  
Sebastian Barney ◽  
Claes Wohlin ◽  
Panagiota Chatzipetrou ◽  
Lefteris Angelis
Keyword(s):  
Software Quality

scholarly journals Design Patterns as Laws of Quality

2011 ◽  
pp. 104-142 ◽  
Author(s):  
Yann-Gaël Gueheneuc ◽  
Jean-Yves Guyomarc’h ◽  
Khashayar Khosravi ◽  
Hourari Sahraoui
Keyword(s):  
Software Quality ◽  
Design Patterns ◽  
Object Oriented ◽  
Quality Characteristics ◽  
Quality Model ◽  
Quality Models ◽  
First Case ◽  
Software Quality Models

Software quality models link internal attributes of programs with external quality characteristics. They help in understanding relationships among internal attributes and between internal attributes and quality characteristics. Object-oriented software quality models usually use metrics on classes (such as number of methods) or on relationships between classes (for example coupling) to measure internal attributes of programs. However, the quality of object-oriented programs does not depend on classes solely: it depends on the organisation of classes also. We propose an approach to build quality models using patterns to consider program architectures. We justify the use of patterns to build quality models, describe the advantages and limitations of such an approach, and introduce a first case study in building and in applying a quality model using design patterns on the JHotDraw, JUnit, and Lexi programs. We conclude on the advantages of using patterns to build software quality models and on the difficulty of doing so.

Sign in / Sign up

Export Citation Format

Share Document