SMSCQA: System for Measuring Source Code Quality Assurance

Today software systems play a critical role in various aspects of human life, and become part of everyday life. Many of these systems are essential for the completion of day-to-day activities. The increased reliance on computer applications, and organization that produced software puts more and more strain on software developers and software systems itself. For these reasons many international standards, requirements, and constrains were established to assure quality of software. In this work the most important fundamentals of software quality assurance used during life cycle development process (LCDP) will be covered. Specially that used in coding phase. This phase is a very important period for all software, because the cure of software system will be established here. Therefore it was sliced in detailes, and all of its aspects were recovered like: Software metrics, Software quality factors, and software quality models like McCall's model, Boehm's model, ISO 9126 model, and SATC NASA model. By comparing and studying these models the System for Measuring Source Code Quality Assurance was retrieved. Using this system over 30 source code metrics, 9 quality factors can be measured and overall quality might be calculated

International Conference on Aerospace Sciences and Aviation Technology, 2003

Today software systems play a critical role in various aspects of human life, from rockets to health care, and become part of everyday life. Many of these systems are relied upon as being essential for the completion of day-today activities. The increased reliance on computer applications, and organizations that produce software puts more and more strain on software developers to produce high quality systems. For these reasons many international standards, requirements, and constrains were established to assure quality of software. This paper introduces a new software Source Code Quality Assurance Measurement System named "SCQAM". In addition, it presents some of the most important software quality assurance fundamentals used during the different phases of software development life cycle. Particularly, the focus of this paper is bounded to the coding phase, where in this phase the cure of software system will be established. Therefore, the scope of this paper covers most of the related aspects of software quality assurance of the coding phase including: software metrics, software quality factors, and software quality models like McCall's model, Boehm's model, ISO 9126 model, and SATC NASA model. As a result of analyzing these models, the proposed "SCQAM" system was designed, developed, and tested. The proposed SCQAM can measure over 30-source code metrics, then group these metrics to compute nine distinct quality factors and indicators, then an overall quality indicator of the input source code is calculated. The experimental results show the superiority of the SCQAM system over Project Analyzer, another quality assurance measurement system, specifically in the area of source code quality measurement.

International Journal of Productivity and Quality Management, 2020

The industries are giving more attention on software quality improvement and assessment, however the majority of researches has been done in the field of internal quality improvement. But, less attention has been given to the user's prospective to improve the quality of a software. The users want the best quality in the usability. The achievement of software companies totally relies upon the user's satisfaction. We focus on customer perspectives of software quality. In this article, first we present some of the existing software quality metrics and their uses. Then, we have accumulated most of the software quality metrics from the literature and prepared a bunch of 27 metrics. Then, we have conducted a survey, with our university students, on the user's perspective to rank the important software quality factors. Based on their responses, we have proposed a new quality model which is user's perspective quality model.

2007

2005-08-03 Welf Löwe changes the initial classification of metrics. The structure of the compendium is adapted accordingly. The compendium moves to Latex and HTML and is published online. 2005-08-01 Rüdiger Lincke produces the first version of the compendium as Word document containing definitions of the Software Quality ISO Standards, cf. Section 2, McCabe Cyclomatic Complexity 3.1.3 and Weighted Method Count 3.1.3 as initial metrics. 2005-06-16 Rüdiger Lincke and Welf Löwe sketch goals and structure of the compendium.

Vojnotehnicki glasnik, 2017

In order to achieve the desired software quality, it is necessary to have information about the existing standards in this field and follow them in all phases of the software life cycle. This study emphasizes the importance of applying the standards in the field of software quality. In the last 20 years, the International Organization for Standards has played an important role in the development of quality standards of a number of software products. At the beginning of this work, the evolution of standards in the field of software quality is summarized and then the current series ISO/IEC standard called SQuaRE are described in detail. This area is very important because the knowledge of software quality standards and their application contributes to the development of quality software that will be widely used and durable. The application of the described standards and the evaluation approaches for the quantification of software qualitiy depends on the resources available for carrying out the method (time, money, the number of evaluators and their expertise, the number of users for testing, facilities and test equipment), the required level of objectivity and its application to various stages of the development of applications.

Software Quality Assurance, 2022

Software products are not built overnight. It takes a lot of effort, team coordination,development and testing to come up with a final version of the product. Regardless of the software product, its complexity or size, the purpose of QA remain same; to reduce the defects to minimum to ensure minimum disruption.This paper is written to propose modern practises for carrying out quality assurance .This research paper solely focuses on how the older methods have been evolved into the new frameworks and models to adapt to the new trends of SDLC .It discusses how these methods are carried out for evaluation of quality and other prominent factors within and throughout the development life of a software and the resulting product thus leading to better customer and managerial satisfaction at both product and process levels. However, with each of the proposed modern methods ,there are some limitations that may vary with the nature of projects. In this paper we describe the limitations of each of the method followed by the comparison with other tools and elaborate when considering the use of a specific tool might be the best choice for us .It also describes the scope of the work that is yet to be discovered and carried out to cater to limitations and disadvantages of the described modern frameworks and models at both general and personal level.

2018

Background and Objectives: One of the major challenges in software engineering is how to respond to the desolate state of high-quality software development in a timely and cost-effective manner. Many studies have been conducted in an attempt to formalize the quality of software. However, according to the recent researches, the lack of comprehensive quality model is rooted in neglecting all quality aspects. Methods: In this study, we review nineteen quality models and classify them from three different perspectives, including structural, behavioral, and basic and derived aspects. The main aim is to specify and extract the more comprehensive set of quality factors to evaluate software quality. Results: This paper compares the different quality models and analyzes the factors to draw the necessary aspects in comprehensive quality models. Since the software quality involves several engineering tasks and several players who deal with quality concepts during software life cycle according ...

International Journal of Software Engineering & Applications, 2010

This work proposes a methodology for source code quality and static behaviour evaluation of a software system, based on the standard ISO/IEC-9126. It uses elements automatically derived from source code enhanced with expert knowledge in the form of quality characteristic rankings, allowing software engineers to assign weights to source code attributes. It is flexible in terms of the set of metrics and source code attributes employed, even in terms of the ISO/IEC-9126 characteristics to be assessed. We applied the methodology to two case studies, involving five open source and one proprietary system. Results demonstrated that the methodology can capture software quality trends and express expert perceptions concerning system quality in a quantitative and systematic manner.

International Journal on Computational Science & Applications, 2018

Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis's software metrics used to measure the software product and process. In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.

All trademarks used herein are the property of their respective owners. The use of any trademark in this text does not vest in the author or publisher any trademark ownership rights in such trademarks, nor does the use of such To my parents, Blima and Elchanan, who inspired me with their love of learning, scholarship, and teaching Contents Preface xvii Unique features of this text xviii The book's audience xix Publisher's acknowledgements xxi About the author xxii Guides for special groups of readers xxiii Guide to readers interested in ISO 9000-3 requirements xxiii Guide to readers interested in ASQ'S CSQE body of knowledge xxiv Part I Introduction 1 Chapter 1 The software quality challenge 3 1.1 The uniqueness of software quality assurance 4 1.2 The environments for which SQA methods are developed 7 Summary 11 Review questions 12 Topics for discussion 12 Chapter 2 What is software quality? 14 2.1 What is software? 15 2.2 Software errors, faults and failures 16 2.3 Classification of the causes of software errors 19 2.4 Software quality-definition 24 2.5 Software quality assurance-definition and objectives 25 2.6 Software quality assurance and software engineering 30 Summary 30 Selected bibliography 32 Review questions 32 Topics for discussion 33 Chapter 3 Software quality factors 3.1 The need for comprehensive software quality requirements 3.2 Classifications of software requirements into software quality factors 3.3 Product operation software quality factors 3.4 Product revision software quality factors 3.5 Product transition software quality factors 3.6 Alternative models of software quality factors 3.7 Who is interested in the definition of quality requirements? 3.8 Software compliance with quality factors Summary Selected bibliography Review questions Topics for discussion Chapter 4 The components of the software quality assurance system-overview 4.1 The SQA system-an SQA architecture 4.2 Pre-project components 4.3 Software project life cycle components 4.4 Infrastructure components for error prevention and improvement 4.5 Management SQA components 4.6 SQA standards, system certification, and assessment components 4.7 Organizing for SQA-the human components 4.8 Considerations guiding construction of an organization's SQA system Part II Pre-project software quality components Chapter 5 Contract review 5.1 Introduction: the CFV Project completion celebration 5.2 The contract review process and its stages 5.3 Contract review objectives 5.4 Implementation of a contract review 5.5 Contract review subjects 5.6 Contract reviews for internal projects viii Contents Summary Selected bibliography Review questions Topics for discussion Appendix 5A: Proposal draft reviewssubjects checklist Appendix 5B: Contract draft reviewsubjects checklist Chapter 6 Development and quality plans 6.1 Development plan and quality plan objectives 6.2 Elements of the development plan 6.3 Elements of the quality plan 6.4 Development and quality plans for small projects and for internal projects Summary Selected bibliography Review questions Topics for discussion Appendix 6A: Software development risks and software risk management Part III SQA components in the project life cycle Chapter 7 Integrating quality activities in the project life cycle 7.1 Classic and other software development methodologies 7.2 Factors affecting intensity of quality assurance activities in the development process 7.3 Verification, validation and qualification 7.4 A model for SQA defect removal effectiveness and cost Summary Selected bibliography Review questions Topics for discussion Chapter 8 Reviews 8.1 Review objectives 8.2 Formal design reviews (DRs) ix Contents 8.3 Peer reviews 8.4 A comparison of the team review methods 8.5 Expert opinions Summary Selected bibliography Review questions Topics for discussion Appendix 8A: DR report form Appendix 8B: Inspection session findings report form Appendix 8C: Inspection session summary report Chapter 9 Software testing-strategies 9.1 Definition and objectives 9.2 Software testing strategies 9.3 Software test classifications 9.4 White box testing 9.5 Black box testing Summary Selected bibliography Review questions Topics for discussion Chapter 10 Software testing-implementation 10.1 The testing process 10.2 Test case design 10.3 Automated testing 10.4 Alpha and beta site testing programs Summary Selected bibliography Review questions Topics for discussion Chapter 11 Assuring the quality of software maintenance components 11.1 Introduction 11.2 The foundations of high quality 11.3 Pre-maintenance software quality components 11.4 Maintenance software quality assurance tools Summary Selected bibliography Review questions Topics for discussion x Contents Chapter Assuring the quality of external participants' contributions 12.1 Introduction: the HealthSoft case 12.2 Types of external participants 12.3 Risks and benefits of introducing external participants 12.4 Assuring quality of external participants' contributions: objectives 12.5 SQA tools for assuring the quality of external participants' contributions Summary Selected bibliography Review questions Topics for discussion Chapter 13 CASE tools and their effect on software quality 13.1 What is a CASE tool? 13.2 The contribution of CASE tools to software product quality 13.3 The contribution of CASE tools to software maintenance quality 13.4 The contribution of CASE tools to improved project management Summary Selected bibliography Review questions Topics for discussion Part IV Software quality infrastructure components Chapter 14 Procedures and work instructions 14.1 The need for procedures and work instructions 14.2 Procedures and procedures manuals 14.3 Work instructions and work instruction manuals 14.4 Procedures and work instructions: preparation, implementation and updating Summary Selected bibliography Review questions Topics for discussion Appendix 14A: Design review procedure xi Contents Chapter Supporting quality devices 15.1 Templates 15.2 Checklists Summary Selected bibliography Review questions Topics for discussion Chapter 16 Staff training and certification 16.1 Introduction: Surprises for the "3S" development team 16.2 The objectives of training and certification 16.3 The training and certification process 16.4 Determining professional knowledge requirements 16.5 Determining training and updating needs 16.6 Planning training and updating programs 16.7 Defining positions requiring certification 16.8 Planning the certification processes 16.9 Delivery of training and certification programs 16.10 Follow-up subsequent to training and certification Summary Selected bibliography Review questions Topics for discussion Chapter 17 Corrective and preventive actions 17.1 Introduction: the "3S" development team revisited 17.2 Corrective and preventive actions-definitions 17.3 The corrective and preventive actions process 17.4 Information collection 17.5 Analysis of collected information 17.6 Development of solutions and their implementation 17.7 Follow-up of activities 17.8 Organizing for preventive and corrective actions Summary Selected bibliography Review questions Topics for discussion xii Contents Chapter Configuration management 18.1 Software configuration, its items and its management 18.2 Software configuration management-tasks and organization 18.3 Software change control 18.4 Release of software configuration versions 18.5 Provision of SCM information services 18.6 Software configuration management audits 18.7 Computerized tools for managing software configuration Summary Selected bibliography Review questions Topics for discussion Chapter 19 Documentation control 19.1 Introduction: where is the documentation? 19.2 Controlled documents and quality records 19.3 The controlled documents list 392 19.4 Controlled document preparation 19.5 Issues of controlled document approval 19.6 Issues of controlled document storage and retrieval Summary Selected bibliography Review questions Topics for discussion Part V Management components of software quality Chapter 20 Project progress control 20.1 The components of project progress control 20.2 Progress control of internal projects and external participants. 20.3 Implementation of project progress control regimes 405 20.4 Computerized tools for software progress control Summary Selected bibliography Review questions Topic for discussion xiii Contents Chapter Software quality metrics 21.1 Objectives of quality measurement 21.2 Classification of software quality metrics 21.3 Process metrics 21.4 Product metrics 21.5 Implementation of software quality metrics 21.6 Limitations of software metrics Summary Selected bibliography Review questions Topics for discussion Appendix 21A: The function point method Chapter Costs of software quality 22.1 Objectives of cost of software quality metrics 22.2 The classic model of cost of software quality 22.3 An extended model for cost of software quality 22.4 Application of a cost of software quality system 22.5 Problems in the application of cost of software quality metrics Summary Selected bibliography Review questions Topics for discussion Part VI Standards, certification and assessment Chapter 23 Quality management standards 23.1 The scope of quality management standards 23.2 ISO 9001 and ISO 9000-3 23.3 Certification according to ISO 9000-3 23.4 Capability Maturity Models-CMM and CMMI assessment methodology 23.5 The Bootstrap methodology 23.6 The SPICE project and the ISO/IEC 15504 software process assessment standard Summary Selected bibliography Review questions Topics for discussion Appendix 23A: CMMI process areas Appendix 23B: ISO/IEC 15504 model processes xiv Contents Chapter SQA project process standards-IEEE software engineering standards 24.1 Structure and content of IEEE software engineering standards 24.2 IEEE/EIA Std 12207-software life cycle processes 24.3 IEEE Std 1012-verification and validation 24.4 IEEE Std-reviews Summary Selected bibliography Review questions...