This document provides an overview of software quality management. It describes software quality management as a process that ensures software meets required quality levels to satisfy users. The process involves quality assurance, quality planning, and quality control. The document is divided into sections for easy understanding and is intended for software development professionals to understand the importance of software quality management. It requires a basic understanding of the software development life cycle.
The Internship was an excellent opportunity for me to relate my academic knowledge with the industry trend. I am really grateful to Institute of Information Technology, University of Dhaka for providing me this opportunity. Here is the report based on my experiences and learnings during my internship at Orion Informatics Ltd., starting from January 01 to June 30, 2014.
The Internship was an excellent opportunity for me to relate my academic knowledge with the industry trend. I am really grateful to Institute of Information Technology, University of Dhaka for providing me this opportunity. Here is the report based on my experiences and learnings during my internship at Orion Informatics Ltd., starting from January 01 to June 30, 2014.
Certainly! Here's a description for a class diagram in the context of JavaScript development:
Class "User": This class represents users of the system. It can have attributes such as username, email, password, and other relevant user information.
Class "Product": This class represents products or items available in the system. It may have attributes like name, description, price, and other product-specific details.
Class "Cart": This class represents a shopping cart, which contains a collection of products that a user has added for purchase. It can have attributes like the user associated with the cart and the list of products in the cart.
Class "Order": This class represents an order placed by a user. It can have attributes such as the user who placed the order, the list of products in the order, order status, and other order-related information.
Class "Payment": This class represents the payment details associated with an order. It may have attributes like payment method, transaction ID, payment status, and other payment-related information.
Class "APIHandler": This class represents a handler or utility class responsible for making API calls to a backend server. It can have methods for handling different types of API requests, such as fetching user information, retrieving products, placing orders, and processing payments.
These classesCertainly! Here's a description for a class diagram in the context of JavaScript development:
Class "User": This class represents users of the system. It can have attributes such as username, email, password, and other relevant user information.
Class "Product": This class represents products or items available in the system. It may have attributes like name, description, price, and other product-specific details.
Class "Cart": This class represents a shopping cart, which contains a collection of products that a user has added for purchase. It can have attributes like the user associated with the cart and the list of products in the cart.
Class "Order": This class represents an order placed by a user. It can have attributes such as the user who placed the order, the list of products in the order, order status, and other order-related information.
Class "Payment": This class represents the payment details associated with an order. It may have attributes like payment method, transaction ID, payment status, and other payment-related information.
Class "APIHandler": This class represents a handler or utility class responsible for making API calls to a backend server. It can have methods for handling different types of API requests, such as fetching user information, retrieving products, placing orders, and processing payments.
These classesCertainly! Here's a description for a class diagram in the context of JavaScript development:
Class "User": This class represents users of the system. It can have attributes such as username, email, password, an
In commerce, supply chain management, the management of the flow of goods and services, between businesses and locations, and includes the movement and storage of raw materials, of work-in-process inventory, and of finished goods as well as end to end order fulfillment from point of origin to point of consumption.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
Palestine last event orientationfvgnh .pptxRaedMohamed3
An EFL lesson about the current events in Palestine. It is intended to be for intermediate students who wish to increase their listening skills through a short lesson in power point.
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
The Roman Empire A Historical Colossus.pdfkaushalkr1407
The Roman Empire, a vast and enduring power, stands as one of history's most remarkable civilizations, leaving an indelible imprint on the world. It emerged from the Roman Republic, transitioning into an imperial powerhouse under the leadership of Augustus Caesar in 27 BCE. This transformation marked the beginning of an era defined by unprecedented territorial expansion, architectural marvels, and profound cultural influence.
The empire's roots lie in the city of Rome, founded, according to legend, by Romulus in 753 BCE. Over centuries, Rome evolved from a small settlement to a formidable republic, characterized by a complex political system with elected officials and checks on power. However, internal strife, class conflicts, and military ambitions paved the way for the end of the Republic. Julius Caesar’s dictatorship and subsequent assassination in 44 BCE created a power vacuum, leading to a civil war. Octavian, later Augustus, emerged victorious, heralding the Roman Empire’s birth.
Under Augustus, the empire experienced the Pax Romana, a 200-year period of relative peace and stability. Augustus reformed the military, established efficient administrative systems, and initiated grand construction projects. The empire's borders expanded, encompassing territories from Britain to Egypt and from Spain to the Euphrates. Roman legions, renowned for their discipline and engineering prowess, secured and maintained these vast territories, building roads, fortifications, and cities that facilitated control and integration.
The Roman Empire’s society was hierarchical, with a rigid class system. At the top were the patricians, wealthy elites who held significant political power. Below them were the plebeians, free citizens with limited political influence, and the vast numbers of slaves who formed the backbone of the economy. The family unit was central, governed by the paterfamilias, the male head who held absolute authority.
Culturally, the Romans were eclectic, absorbing and adapting elements from the civilizations they encountered, particularly the Greeks. Roman art, literature, and philosophy reflected this synthesis, creating a rich cultural tapestry. Latin, the Roman language, became the lingua franca of the Western world, influencing numerous modern languages.
Roman architecture and engineering achievements were monumental. They perfected the arch, vault, and dome, constructing enduring structures like the Colosseum, Pantheon, and aqueducts. These engineering marvels not only showcased Roman ingenuity but also served practical purposes, from public entertainment to water supply.
This is a presentation by Dada Robert in a Your Skill Boost masterclass organised by the Excellence Foundation for South Sudan (EFSS) on Saturday, the 25th and Sunday, the 26th of May 2024.
He discussed the concept of quality improvement, emphasizing its applicability to various aspects of life, including personal, project, and program improvements. He defined quality as doing the right thing at the right time in the right way to achieve the best possible results and discussed the concept of the "gap" between what we know and what we do, and how this gap represents the areas we need to improve. He explained the scientific approach to quality improvement, which involves systematic performance analysis, testing and learning, and implementing change ideas. He also highlighted the importance of client focus and a team approach to quality improvement.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
The Indian economy is classified into different sectors to simplify the analysis and understanding of economic activities. For Class 10, it's essential to grasp the sectors of the Indian economy, understand their characteristics, and recognize their importance. This guide will provide detailed notes on the Sectors of the Indian Economy Class 10, using specific long-tail keywords to enhance comprehension.
For more information, visit-www.vavaclasses.com
Students, digital devices and success - Andreas Schleicher - 27 May 2024..pptxEduSkills OECD
Andreas Schleicher presents at the OECD webinar ‘Digital devices in schools: detrimental distraction or secret to success?’ on 27 May 2024. The presentation was based on findings from PISA 2022 results and the webinar helped launch the PISA in Focus ‘Managing screen time: How to protect and equip students against distraction’ https://www.oecd-ilibrary.org/education/managing-screen-time_7c225af4-en and the OECD Education Policy Perspective ‘Students, digital devices and success’ can be found here - https://oe.cd/il/5yV
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
Thesis Statement for students diagnonsed withADHD.ppt
Software quality management_tutorial
1.
2. i
AbouttheTutorial
Software Quality Management is a process that ensures the required level of software
quality is achieved when it reaches the users, so that they are satisfied by its performance.
The process involves quality assurance, quality planning, and quality control.
This tutorial provides a complete overview of Software Quality Management and describes
the various steps involved in the process. The entire content is divided into sections for
easy understanding.
Audience
This tutorial is designed for software development professionals so that they can
understand the importance of software quality management. It is especially beneficial for
software quality managers, software testing professionals, and software developers.
Prerequisites
To get the most out of this tutorial, it is good to have a basic understanding of the Software
Development Life Cycle (SDLC).
Copyright&Disclaimer
Copyright 2018 by Tutorials Point (I) Pvt. Ltd.
All the content and graphics published in this e-book are the property of Tutorials Point (I)
Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish
any contents or a part of contents of this e-book in any manner without written consent
of the publisher.
We strive to update the contents of our website and tutorials as timely and as precisely as
possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt.
Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our
website or its contents including this tutorial. If you discover any errors on our website or
in this tutorial, please notify us at contact@tutorialspoint.com
3. ii
TableofContents
About the Tutorial....................................................................................................................................i
Audience..................................................................................................................................................i
Prerequisites............................................................................................................................................i
Copyright & Disclaimer.............................................................................................................................i
Table of Contents....................................................................................................................................ii
1. SQM ─ INTRODUCTION........................................................................................................1
The Software Quality Challenge ..............................................................................................................1
2. SQM ─ SOFTWARE QUALITY FACTORS.................................................................................3
McCall’s Factor Model.............................................................................................................................3
Product Operation Software Quality Factors...........................................................................................3
Product Revision Quality Factors.............................................................................................................4
Product Transition Software Quality Factor ............................................................................................5
3. SQM ─ SQA COMPONENTS..................................................................................................6
Components of SQA System....................................................................................................................7
Pre-project Software Quality Components..............................................................................................8
4. SQM ─ SOFTWARE QUALITY METRICS .................................................................................9
Product Quality Metrics ..........................................................................................................................9
In-process Quality Metrics ....................................................................................................................10
Maintenance Quality Metrics................................................................................................................12
5. SQM ─ BASICS OF MEASUREMENT....................................................................................14
Measurement in Everyday Life..............................................................................................................14
Measurement in Software Engineering .................................................................................................14
The Representational Theory of Measurement.....................................................................................15
6. SQM ─ MEASUREMENT & MODELS ...................................................................................18
4. iii
7. SQM ─ MEASUREMENT SCALES.........................................................................................20
Nominal Scale .......................................................................................................................................20
Ordinal Scale .........................................................................................................................................20
Interval Scale.........................................................................................................................................20
Ratio Scale ............................................................................................................................................21
Absolute Scale.......................................................................................................................................21
8. SQM ─ EMPIRICAL INVESTIGATIONS..................................................................................22
Choosing an Investigation Technique ....................................................................................................22
Stating the Hypothesis ..........................................................................................................................23
Maintaining Control over Variables.......................................................................................................23
Making the Investigation Meaningful....................................................................................................23
9. SQM ─ SOFTWARE MEASUREMENT...................................................................................25
Classifying the Entities to be Examined .................................................................................................25
Determining Relevant Measurement Goals...........................................................................................26
Identifying the Level of Maturity...........................................................................................................28
10. SQM ─ SOFTWARE MEASUREMENT VALIDATION..............................................................30
Validating the Measurement Systems...................................................................................................30
Validating the Prediction Systems.........................................................................................................30
11. SQM ─ SOFTWARE METRICS..............................................................................................32
Scope of Software Metrics ....................................................................................................................32
12. SQM ─ DATA MANIPULATION............................................................................................35
What is Good Data? ..............................................................................................................................35
How to Define the Data?.......................................................................................................................35
How to Collect Data?.............................................................................................................................36
How to Store and Extract Data..............................................................................................................36
5. iv
13. SQM ─ ANALYZING SOFTWARE MEASUREMENT DATA......................................................38
The Nature of Data................................................................................................................................38
The Purpose of the Experiment.............................................................................................................38
Design Considerations...........................................................................................................................40
14. SQM ─ INTERNAL PRODUCT ATTRIBUTES ..........................................................................41
Measuring Internal Product Attributes..................................................................................................41
15. SQM ─ ALBRECHT’S FUNCTION POINT METHOD ...............................................................44
What is a Function Point?......................................................................................................................44
Applying Albrecht’s Function Point Method..........................................................................................44
16. SQM ─ MEASURING THE STRUCTURE................................................................................48
Types of Structural Measures................................................................................................................48
Measuring Control-Flow Structure ........................................................................................................48
Measuring Data-Flow Structure ............................................................................................................48
Measuring Data Structure .....................................................................................................................49
17. SQM ─ STANDARDS AND CERTIFICATES.............................................................................50
SQA Standards ......................................................................................................................................50
ISO 9001 Certification............................................................................................................................51
18. SQM ─ SOFTWARE PROCESS ASSESSMENT........................................................................54
Software Process Maturity Assessment ................................................................................................54
Software Process Assessment Cycle ......................................................................................................55
SCAMPI .................................................................................................................................................55
19. SQM ─ QUALITY ASSURANCE.............................................................................................57
Objectives of SQA Activities ..................................................................................................................57
Organizing for Quality Assurance ..........................................................................................................57
6. v
20. SQM ─ ROLE OF MANAGEMENT IN QA..............................................................................59
Top Management Responsibilities in Software Quality .........................................................................59
Software Quality Policy.........................................................................................................................59
21. SQM ─ THE SQA UNIT........................................................................................................64
Tasks Performed by the Head of the SQA Unit ......................................................................................64
Project Life Cycle SQA ...........................................................................................................................65
SQA Infrastructure Operations Tasks ....................................................................................................66
SQA Internal Audit and Certification Tasks............................................................................................66
SQA Support Tasks ................................................................................................................................68
SQA Standards and Procedures Tasks....................................................................................................68
SQA Engineering Tasks ..........................................................................................................................68
SQA Information Systems Tasks ............................................................................................................69
SQA Trustees and Their Tasks................................................................................................................69
SQA Committees and Their Tasks..........................................................................................................70
7. 1
Quality software refers to a software which is reasonably bug or defect free, is delivered
in time and within the specified budget, meets the requirements and/or expectations, and
is maintainable. In the software engineering context, software quality reflects both
functional quality as well as structural quality.
Software Functional Quality ─ It reflects how well it satisfies a given design,
based on the functional requirements or specifications.
Software Structural Quality ─ It deals with the handling of non-functional
requirements that support the delivery of the functional requirements, such as
robustness or maintainability, and the degree to which the software was produced
correctly.
Software Quality Assurance ─ Software Quality Assurance (SQA) is a set of
activities to ensure the quality in software engineering processes that ultimately
result in quality software products. The activities establish and evaluate the
processes that produce products. It involves process-focused action.
Software Quality Control ─ Software Quality Control (SQC) is a set of activities
to ensure the quality in software products. These activities focus on determining
the defects in the actual products produced. It involves product-focused acction.
TheSoftwareQualityChallenge
In the software industry, the developers will never declare that the software is free of
defects, unlike other industrial product manufacturers usually do. This difference is due to
the following reasons.
Product Complexity
It is the number of operational modes the product permits. Normally, an industrial product
allows only less than a few thousand modes of operation with different combinations of its
machine settings. However, software packages allow millions of operational possibilities.
Hence, assuring of all these operational possibilities correctly is a major challenge to the
software industry.
Product Visibility
Since the industrial products are visible, most of its defects can be detected during the
manufacturing process. Also the absence of a part in an industrial product can be easily
detected in the product. However, the defects in software products which are stored on
diskettes or CDs are invisible.
Product Development and Production Process
In an industrial product, defects can be detected during the following phases:
Product development: In this phase, the designers and Quality Assurance (QA)
staff checks and tests the product prototype to detect its defects.
1. SQM ─ Introduction
8. 2
Product production planning: During this phase, the production process and
tools are designed and prepared. This phase also provides opportunities to inspect
the product to detect the defects that went unnoticed during the development
phase.
Manufacturing: In this phase, QA procedures are applied to detect failures of
products themselves. Defects in the product detected in the first period of
manufacturing can usually be corrected by a change in the product’s design or
materials or in the production tools, in a way that eliminates such defects in
products manufactured in future.
However, in the case of software, the only phase where defects can be detected is the
development phase. In case of software, product production planning and manufacturing
phases are not required as the manufacturing of software copies and the printing of software
manuals are conducted automatically.
The factors affecting the detection of defects in software products versus other industrial
products are shown in the following table.
These characteristics of software such as complexity and invisibility make the development
of software quality assurance methodology and its successful implementation a highly
professional challenge.
9. 3
The various factors, which influence the software, are termed as software factors. They
can be broadly divided into two categories. The first category of the factors is of those that
can be measured directly such as the number of logical errors, and the second category
clubs those factors which can be measured only indirectly. For example, maintainability
but each of the factors is to be measured to check for the content and the quality control.
Several models of software quality factors and their categorization have been suggested
over the years. The classic model of software quality factors, suggested by McCall, consists
of 11 factors (McCall et al., 1977). Similarly, models consisting of 12 to 15 factors, were
suggested by Deutsch and Willis (1988) and by Evans and Marciniak (1987).
All these models do not differ substantially from McCall’s model. The McCall factor model
provides a practical, up-to-date method for classifying software requirements (Pressman,
2000).
McCall’sFactorModel
This model classifies all software requirements into 11 software quality factors. The 11
factors are grouped into three categories – product operation, product revision, and
product transition factors.
Product operation factors: Correctness, Reliability, Efficiency, Integrity, Usability.
Product revision factors: Maintainability, Flexibility, Testability.
Product transition factors: Portability, Reusability, Interoperability.
ProductOperationSoftwareQualityFactors
According to McCall’s model, product operation category includes five software quality
factors, which deal with the requirements that directly affect the daily operation of the
software. They are as follows:
Correctness
These requirements deal with the correctness of the output of the software system. They include:
Output mission
The required accuracy of output that can be negatively affected by inaccurate data
or inaccurate calculations.
The completeness of the output information, which can be affected by incomplete data.
The up-to-dateness of the information defined as the time between the event and
the response by the software system.
The availability of the information.
2. SQM ─ Software Quality Factors
10. 4
The standards for coding and documenting the software system.
Reliability
Reliability requirements deal with service failure. They determine the maximum allowed
failure rate of the software system, and can refer to the entire system or to one or more
of its separate functions.
Efficiency
It deals with the hardware resources needed to perform the different functions of the
software system. It includes processing capabilities (given in MHz), its storage capacity
(given in MB or GB) and the data communication capability (given in MBPS or GBPS).
It also deals with the time between recharging of the system’s portable units, such as,
information system units located in portable computers, or meteorological units placed
outdoors.
Integrity
This factor deals with the software system security, that is, to prevent access to
unauthorized persons, also to distinguish between the group of people to be given read as
well as write permit.
Usability
Usability requirements deal with the staff resources needed to train a new employee and
to operate the software system.
ProductRevisionQualityFactors
According to McCall’s model, three software quality factors are included in the product
revision category. These factors are as follows:
Maintainability
This factor considers the efforts that will be needed by users and maintenance personnel
to identify the reasons for software failures, to correct the failures, and to verify the
success of the corrections.
Flexibility
This factor deals with the capabilities and efforts required to support adaptive maintenance
activities of the software. These include adapting the current software to additional
circumstances and customers without changing the software. This factor’s requirements
also support perfective maintenance activities, such as changes and additions to the
software in order to improve its service and to adapt it to changes in the firm’s technical
or commercial environment.
Testability
Testability requirements deal with the testing of the software system as well as with its
operation. It includes predefined intermediate results, log files, and also the automatic
diagnostics performed by the software system prior to starting the system, to find out
whether all components of the system are in working order and to obtain a report about
11. 5
the detected faults. Another type of these requirements deals with automatic diagnostic
checks applied by the maintenance technicians to detect the causes of software failures.
ProductTransitionSoftwareQualityFactor
According to McCall’s model, three software quality factors are included in the product
transition category that deals with the adaptation of software to other environments and
its interaction with other software systems. These factors are as follows:
Portability
Portability requirements tend to the adaptation of a software system to other
environments consisting of different hardware, different operating systems, and so forth.
The software should be possible to continue using the same basic software in diverse
situations.
Reusability
This factor deals with the use of software modules originally designed for one project in a
new software project currently being developed. They may also enable future projects to
make use of a given module or a group of modules of the currently developed software.
The reuse of software is expected to save development resources, shorten the
development period, and provide higher quality modules.
Interoperability
Interoperability requirements focus on creating interfaces with other software systems or
with other equipment firmware. For example, the firmware of the production machinery
and testing equipment interfaces with the production control software.
12. 6
Software Quality Assurance (SQA) is a set of activities for ensuring quality in software
engineering processes. It ensures that developed software meets and complies with the
defined or standardized quality specifications. SQA is an ongoing process within the
Software Development Life Cycle (SDLC) that routinely checks the developed software to
ensure it meets the desired quality measures.
SQA practices are implemented in most types of software development, regardless of the
underlying software development model being used. SQA incorporates and implements
software testing methodologies to test the software. Rather than checking for quality after
completion, SQA processes test for quality in each phase of development, until the
software is complete. With SQA, the software development process moves into the next
phase only once the current/previous phase complies with the required quality standards.
SQA generally works on one or more industry standards that help in building software
quality guidelines and implementation strategies.
It includes the following activities:
Process definition and implementation
Auditing
Training
Processes could be:
Software Development Methodology
Project Management
Configuration Management
Requirements Development/Management
Estimation
Software Design
Testing, etc.
Once the processes have been defined and implemented, Quality Assurance has the
following responsibilities:
Identify the weaknesses in the processes
Correct those weaknesses to continually improve the process
3. SQM ─ SQA Components
13. 7
ComponentsofSQASystem
An SQA system always combines a wide range of SQA components. These components
can be classified into the following six classes:
Pre-project components
This assures that the project commitments have been clearly defined considering the
resources required, the schedule and budget; and the development and quality plans have
been correctly determined.
Components of project life cycle activities assessment
The project life cycle is composed of two stages: the development life cycle stage and the
operation–maintenance stage.
The development life cycle stage components detect design and programming errors. Its
components are divided into the following sub-classes: Reviews, Expert opinions, and
Software testing.
The SQA components used during the operation–maintenance phase include specialized
maintenance components as well as development life cycle components, which are applied
mainly for functionality to improve the maintenance tasks.
Components of infrastructure error prevention and improvement
The main objective of these components, which is applied throughout the entire
organization, is to eliminate or at least reduce the rate of errors, based on the
organization’s accumulated SQA experience.
Components of software quality management
This class of components deal with several goals, such as the control of development and
maintenance activities, and the introduction of early managerial support actions that
mainly prevent or minimize schedule and budget failures and their outcomes.
Components of standardization, certification, & SQA system assessment
These components implement international professional and managerial standards within
the organization. The main objectives of this class are utilization of international
professional knowledge, improvement of coordination of the organizational quality
systems with other organizations, and assessment of the achievements of quality systems
according to a common scale. The various standards may be classified into two main
groups: quality management standards and project process standards.
Organizing for SQA – the human components
The SQA organizational base includes managers, testing personnel, the SQA unit and the
persons interested in software quality such as SQA trustees, SQA committee members,
and SQA forum members. Their main objectives are to initiate and support the
implementation of SQA components, detect deviations from SQA procedures and
methodology, and suggest improvements.
14. 8
End of ebook preview
If you liked what you saw…
Buy it from our store @ https://store.tutorialspoint.com