The document discusses software quality assurance. It defines quality assurance, quality management, and their key aspects. It also describes the different elements of software quality assurance - software quality planning, software quality control, and software quality metrics. Under software quality control, it discusses various quality control methods like reviews, tests, and audits. It then covers topics like standards, quality models, capability maturity model, and process improvement methods like six sigma. Finally, it provides examples of software metrics that can be used to measure quality.
Software design is the first of three technical activities—design, code generation, and test—that are required to build and verify the software
The design task produces a data design, an architectural design, an interface design, and a component design
The data design transforms the information domain model created during analysis into the data structures that will be required to implement the software
Software design is the first of three technical activities—design, code generation, and test—that are required to build and verify the software
The design task produces a data design, an architectural design, an interface design, and a component design
The data design transforms the information domain model created during analysis into the data structures that will be required to implement the software
Quality, quality concepts
Software Quality Assurance
Software Reviews
Formal Technical Reviews
SQA Group Plan
ISO 9000, 9001
Example
Internal and external attributes
What is Quality ||
Software Quality Metrics ||
Types of Software Quality Metrics ||
Three groups of Software Quality Metrics ||
Customer Satisfaction Metrics ||
Tools used for Quality Metrics/Measurements ||
PERT and CPM ||
Requirements elicitation "brainstorming" techniques is conducted, analysis principles are applied, and a model of the software to be built, called a prototype, is constructed for customer and developer assessment
This presentation throws light on some of the essential elements of web testing which have become crucial to ensure quality in this day and age. To know more on web testing, Graphical User Interface Testing, workflow testing along with Cross Browser or Compatibility testing, go through this presentation as well as the ones coming soon.
Quality, quality concepts
Software Quality Assurance
Software Reviews
Formal Technical Reviews
SQA Group Plan
ISO 9000, 9001
Example
Internal and external attributes
What is Quality ||
Software Quality Metrics ||
Types of Software Quality Metrics ||
Three groups of Software Quality Metrics ||
Customer Satisfaction Metrics ||
Tools used for Quality Metrics/Measurements ||
PERT and CPM ||
Requirements elicitation "brainstorming" techniques is conducted, analysis principles are applied, and a model of the software to be built, called a prototype, is constructed for customer and developer assessment
This presentation throws light on some of the essential elements of web testing which have become crucial to ensure quality in this day and age. To know more on web testing, Graphical User Interface Testing, workflow testing along with Cross Browser or Compatibility testing, go through this presentation as well as the ones coming soon.
Begins during the communication activity and continues into the modeling activity
Builds a bridge from the system requirements into software design and construction
Software is a set of instructions to acquire inputs and to manipulate them to produce the desired output in terms of functions and performance as determined by the user of the software
*A modular design reduces complexity
*The concept of functional independence is a direct outgrowth of modularity and the
concepts of abstraction and information hiding
*functional independence is a key to good design, and design is the key to software quality
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.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
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.
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
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.
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
Ethnobotany and Ethnopharmacology:
Ethnobotany in herbal drug evaluation,
Impact of Ethnobotany in traditional medicine,
New development in herbals,
Bio-prospecting tools for drug discovery,
Role of Ethnopharmacology in drug evaluation,
Reverse Pharmacology.
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.
How to Split Bills in the Odoo 17 POS ModuleCeline George
Bills have a main role in point of sale procedure. It will help to track sales, handling payments and giving receipts to customers. Bill splitting also has an important role in POS. For example, If some friends come together for dinner and if they want to divide the bill then it is possible by POS bill splitting. This slide will show how to split bills in odoo 17 POS.
2. 2
What is Software Quality
Assurance?
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
3. 3
What is Quality?
Quality – developed product meets it’s specification
Problems:
• Development organization has requirements exceeding customer's
specifications (added cost of product development)
• Certain quality characteristics can not be specified in
unambiguous terms (i.e. maintainability)
• Even if the product conforms to it’s specifications, users may
not consider it to be a quality product (because users may not be involved in
the development of the requirements)
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
4. 4
Quality Management – ensuring that required level of
product quality is achieved
• Defining procedures and standards
• Applying procedures and standards to the product and process
• Checking that procedures are followed
• Collecting and analyzing various quality data
Problems:
• Intangible aspects of software quality can’t be standardized
(i.e elegance and readability)
What is Quality Management?
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
5. 5
What are SQA, SQP, SQC, and SQM?
SQA includes all 4 elements…
• Software Quality Assurance – establishment of network of
organizational procedures and standards leading to high-
quality software
2. Software Quality Planning – selection of appropriate
procedures and standards from this framework and adaptation
of these to specific software project
3. Software Quality Control – definition and enactment of
processes that ensure that project quality procedures and
standards are being followed by the software development
team
4. Software Quality Metrics – collecting and analyzing quality
data to predict and control quality of the software product
being developed
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
7. 7
Why are Standards Important?
• Standards provide encapsulation of best, or at least most
appropriate, practice
• Standards provide a framework around which the quality
assurance process may be implemented
• Standards assist in continuity of work when it’s carried out by
different people throughout the software product lifecycle
Standards should not be avoided. If they are too extensive
for the task at hand, then they should be tailored.
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
8. 8
SDS a Simplistic approach
In most mature organizations:
• ISO is not the only source of SDS
• Process and Product standards are derived independently
• Product standards are not created by SQA
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
10. 10
ISO - 9001 Elements
• Quality System Requirements
• Management Responsibility
• Quality system
• Contract review
• Design Control
• Document control
• Purchasing
• Purchaser supplied product
• Product identification and traceability
• Process control
• Inspection and testing
• Inspection, measuring and test equipment
• Inspection and test status
• Control of non-conforming product
• Corrective action
• Handling, storage, preservation, packaging
and shipping
• Quality records
• Internal quality audits
• Training
• Servicing
• Statistical techniques
• Software Quality Responsibilities
• Management Responsibility
• Quality system
• Contract review
• Design Control
• Document control
• Purchasing
• -
• Product identification and traceability
• Process control
• Inspection and testing
• -
• Inspection and test status
• -
• Corrective action
• -
• Quality records
• Internal quality audits
• Training
• -
• Statistical techniques
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
13. 13
Quality Improvement – The Wheel of 6Sigma
Six Sigma
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
14. 14
Quality Improvement – Six Sigma Process
• Visualize – Understand how it works now and imagine how it
will work in the future
• Commit – Obtain commitment to change from the stakeholders
• Prioritize – Define priorities for incremental improvements
• Characterize – Define existing process and define the time
progression for incremental improvements
• Improve – Design and implement identified improvements
• Achieve – Realize the results of the change
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
15. 15
Continuity and Independence of SQA
• Software Quality Assurance team must be independent in order to
take an objective view of the process and report problems to senior
management directly
• If prescribed process is inappropriate for the type of software
product which is being developed, then it should be tailored
• The standards must be upheld no matter how small the task.
Prototyping doesn’t mean no standards. It means tailored standards.
• Quality is FREE, if it’s Everyone’s Responsibility!
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
17. 17
Software Quality Plan
• Tailoring - SQP should select those organizational standards that
are appropriate to a particular product
• Standardization - SQP should use (call out) only approved
organizational process and product standards
• If new standards are required a quality improvement should be
initiated
• Elements - SQP elements are usually based on the ISO-9001
model elements
• SQP is not written for software developers. It’s written for SQE’s
as a guide for SQC and for the customer to monitor development
activities
• Things like software production, software product plans and risk
management should be defined in SDP, IP
• Quality Factor’s shouldn’t be sacrificed to achieve efficiency.
Don’t take the job if quality process can’t be upheld
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
19. 19
Methods of Software Quality Control
SQC involves overseeing the software development process to ensure that the
procedures and STD’s are being followed
The following activities constitute SQC:
• Quality Reviews - in-process reviews of processes and products
Reviews are the most widely used method of validating the quality of processes and
products. Reviews make quality everyone's responsibility. Quality must be built-in.
SQE is responsible for writing Quality Engineering Records (QERs) documenting their
participation in these reviews.
• Tests - end-result verifications of products. These verifications are conducted after the
software has been developed. Test procedures are followed during conduct of these
activities. SQE is responsible for keeping the logs and some times for writing the test
report.
• Quality Audits - in-process verifications of processes. These audits are conducted
periodically (twice a month) to assess compliance to the process STD’s.
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
20. 20
Quality Reviews
• Peer reviews - reviews of processes and products by groups of people. These
reviews require pre-review preparation by all participants. If a participant is not
prepared, then the review is not effective. This type of review requires
participation of the SQE, moderator, recorder, author(s), and one or more critical
reviewers. All issues found during these reviews are documented on AR forms.
• Walkthroughs - reviews of products by groups of people mostly without
preparation. For example a requirements traceability review is a walkthrough. It
involves tracing a requirement from customer requirements to the test procedures.
All issues found during these reviews are documented on CAR forms.
• Desk inspections - reviews of products by individuals. These reviews involve
people reviewing products by themselves (not in a group) and then submitting
their comments to the author(s). The issues found during these reviews are
treated in informal manner.
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
21. 21
Tests
• Engineering Dry-run - test conducted by engineering without SQE. These tests
include Unit Tests and engineering dry-runs of the formal tests. These engineering dry-
runs are used to verify correctness and completeness of the test procedures. Also, these
is the final engineering verification of the end-product before sell-off to SQE. All
issues found during these tests are documented on STR forms.
• SQE Dry-run - test conducted by SQE. These tests include PQT, FAT and SAT dry-
runs. These tests are used to verify the end-product before the formal test with the
customer. An SQE is sometimes responsible for writing the test report. However, if a
separate test group is available, then SQE is relived of this obligation. All issues found
during these tests are documented on STR forms.
• TFR - test conducted as “RFR - run-for-record” with the SQE and the customer.
These tests include FAT and SAT. These tests are conducted to sell the end-product off
to the customer. SQE is present at all such tests. All issues found during these tests are
documented on STR forms.
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
22. 22
Quality Audits
• SQE Audits - audits conducted by SQE to verify that the process STD’s are
being followed. Examples of these audits are IPDS compliance, Configuration
Control, and Software Engineering Management. All findings for these audits are
documented on QER forms. The results of the audits are distributed to the next
level of management (above project level). If the issue(s) are not fixed then the
findings are elevated to upper management.
• Independent Audits - audits conducted by ISO generalists or other independent
entities to verify that the process STD’s are being followed. These audits are
usually conducted on a division/facility level. The results of these audits are
distributed to upper management.
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
24. 24
Metrics Collection
• Software measurement - the process of deriving a numeric value
for some attribute of a software product or a software process. Comparison of these
values to each other and to STD’s allows drawing conclusions about the quality of
software products or the process.
• The focus of the metrics collecting programs is usually on collecting metrics on
program defects and the V&V process.
• Metrics can be either Control Metrics or Predictor Metrics
• Most of the “Ilities” can not be measured directly unless there’s historical data.
Instead tangible software product attributes are measured and the “Ility” factors are
derived using predefined relationships between measurable and synthetic attributes.
• The boundary conditions for all measurements should be established in advance
and then revised once a large databank of historical data has been established
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
25. 25
The Process of Product Measurement
1. Decide what data is to be collected
2. Assess critical (core) components first
3. Measuring component characteristics might require automated tools
4. Look for consistently (unusually only works in a factory) high or low values
5. Analysis of anomalous components should reveal if the quality of product is
compromised
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
26. 26
Predictor and Control Metrics
Examples of Predictor Analysis:
• Code Reuse: SLOC = ELOC = Ported Code
• Nesting Depth: ND > 5 = Low Readability
• Risk Analysis: # STR P1 > 0 at SAT = Low Product Reliability
Examples of Control Analysis:
• STR aging: Old STRs = Low Productivity
• Requirements Volatility: High Volatility = Scope Creep
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
27. 27
Software Product Metrics
There are two categories of software product metrics:
1. Dynamic metrics – this metrics is collected by measuring elements
during program’s execution. This metrics help to asses efficiency and
reliability of a software product. The parameters collected can be
easily measured (i.e. execution time, mean time between failures)
2. Static metrics – this metrics is collected by measuring parameters of
the end products of the software development. This metrics help to
asses the complexity, understandability, and maintainability of a
software product. The SLOC size and ND are the most reliable
predictors of understandability, complexity, and maintainability.
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
28. 28
Examples of Software Metric – Chapter 24
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW
29. 29
Examples of OO Software Metric – Chapter 24
Prepared by, Dr.T.Thendral, Assistant
Professor, SRCW