This document discusses software quality assurance and testing. It provides definitions of key terms like software quality, errors, faults and failures. It also lists common causes of software errors and characteristics that differentiate software from other products. Software quality assurance is defined as a planned set of activities to provide confidence that software conforms to requirements, while quality control evaluates quality after development. The objectives of software quality assurance are also prevention of defects rather than finding them after development.
Software Quality Analyst and Software Quality Managementنور شزننا
This presentation slide is purposely for our Software Quality course. You will notice less words, as we had been given only 10 minutes to present. All information is taken through our research on internet. Thanks to all worldwide SE Experts for your valuable knowledge.
Software Quality Analyst and Software Quality Managementنور شزننا
This presentation slide is purposely for our Software Quality course. You will notice less words, as we had been given only 10 minutes to present. All information is taken through our research on internet. Thanks to all worldwide SE Experts for your valuable knowledge.
Why Software Testing is Crucial in Software Development_.pdfXDuce Corporation
Software testing is the process of verifying and then confirming that a software application or product
performs as expected or not. Testing has its own set of advantages like bug prevention, lower costs of
development, and comparatively better performance.
The software cannot be said to be bug-free from the start. Therefore, software developers might strive
to write code that will reduce the number and severity of flaws that are already there. However, the
majority of bugs are latent and only emerge when the conditions are right.
This presentation gives you a walkthorugh on CTFL module 01.
Covers in detail about-
1. Fundamentals of testing
2. Terminologies in testing
3. Seven testing principles
4. Fundamental test process
The presentation describes how to conduct reliability planning and testing for software controlled electron-mechanical systems. It is based on working experience in US FDA, FCC and European CE regulated companies. The presentation provides practical and rational steps to improve product reliability and comply with applicable regulations.
研讨会简报介绍了如何进行软件控制的电子机械系统的可靠性规划和测试。它是基于在美国FDA,FCC和欧洲CE规管公司的工作经验。研讨会演示文稿提供仅结合实际,合理的措施来提高产品的可靠性,并遵守适用的法规.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
Lect1 fault+quality
1. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
TEXT & REFERENCE BOOKSTEXT & REFERENCE BOOKS
1.1. Galin, D. (2004).Galin, D. (2004). Software quality assuranceSoftware quality assurance. Great. Great
Britain: Pearson.Britain: Pearson.
2.2. Sommerville (2004),Sommerville (2004), Software EngineeringSoftware Engineering, 7/e,, 7/e,
Addison-Wesley.Addison-Wesley.
3.3. Pressman,Pressman, R. S. (2005).R. S. (2005). Software Engineering: ASoftware Engineering: A
Practitioner’s ApproachPractitioner’s Approach.. 66th editionth edition.. McGraw-Hill.McGraw-Hill.
4.4. Jarvis, AlkaJarvis, Alka,, && CrandalCrandal, V. (1997)., V. (1997). Inroads to SoftwareInroads to Software
QualityQuality.. Prentice HallPrentice Hall..
5.5. O’Regan (2002).O’Regan (2002). A Practical approach to SoftwareA Practical approach to Software
QualityQuality, Springer., Springer.
6. CMMI Standards6. CMMI Standards
7. ISO9000-3 Standards7. ISO9000-3 Standards
2. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
The objectives of this chapter are to:The objectives of this chapter are to:
1.1. Identify theIdentify the unique characteristics of softwareunique characteristics of software
2.2. Recognize theRecognize the characteristics of thecharacteristics of the
environmentenvironment
3.3. DefineDefine software quality assurance and itssoftware quality assurance and its
objectivesobjectives
4.4. The differences between OC & QAThe differences between OC & QA
3. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
• What is software?
• Software errors, faults and failures
• Classification of the causes of software errors
• Software quality – definition
• Software quality assurance – definition and
objectives
• Software quality assurance and software
engineering
4. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
Software is:
Computer programs, procedures,
and possibly associated
documentation and data related
to the operation of a computer
system.
5. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
The UniquenessThe Uniqueness between Software & Industrial Productbetween Software & Industrial Product
CharacteristicsCharacteristics SoftwareSoftware Industrial productIndustrial product
ComplexityComplexity High: Can be measured by the numberHigh: Can be measured by the number
of operational modesof operational modes
Low: Not allow for moreLow: Not allow for more
than a few thousandsthan a few thousands
modes of operationmodes of operation
VisibilityVisibility InvisibleInvisible VisibleVisible
ProductProduct
developmentdevelopment
Detecting inherent product defectsDetecting inherent product defects Check & test theCheck & test the
product prototype toproduct prototype to
detect its defectsdetect its defects
Product productionProduct production
planningplanning
This phase is not required for theThis phase is not required for the
software productsoftware product
Provides additionalProvides additional
opportunities to inspectopportunities to inspect
the productthe product
ManufacturingManufacturing Limited to copying the product & printingLimited to copying the product & printing
copies of the software manual;copies of the software manual;
expectations for detecting defects areexpectations for detecting defects are
quite limited during this phasequite limited during this phase
QA procedures areQA procedures are
applied to detectapplied to detect
failuresfailures
6. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Software errors, faults & failure
• Software failure lies in a software errors
• Software errors are sections of the code that are partially or
totally incorrect
• Error can be grammatical error, logical error or caused by
other mistake
• Software error can cause improper functioning, i.e. software
fault
• Not all software faults lead to software failure.
• Failures occur when a user tries to apply the specific
software section that is faulty
7. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
The nine causes of software errors are:
1. Faulty requirements definition
2. Client-developer communication failures
3. Deliberate deviations from software requirements
4. Logical design errors
5. Coding errors
6. Non-compliance with documentation and coding
instructions
7. Shortcomings of the testing process
8. User interface and procedure errors
9. Documentation errors
8. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Faulty definition of requirements:
Erroneous definition of requirements
Absence of vital requirements
Incomplete definition of requirements
Inclusion of unnecessary requirements
Client-developer communication failures:
Misunderstanding of the client’s instruction as stated in the requirement
document
Misunderstanding of the client’s requirements changes presented to the
developer in written form
Misunderstanding of the client’s requirements changes presented orally to the
developer
Misunderstanding of the client’s response to the design problems presented by
the developer
Lack of attention to client messages (requirement changes, client response on
the questions that raised by the developer)
9. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Deliberate deviations from software requirements
Reuses software modules without sufficient analysis
Omit part of the required functions to cope with time and budget
constraint
Developer-initiated, unapproved improvements to the software
Logical design errors, for example:
Erroneous algorithm
Process definitions that contain sequencing errors
Erroneous definition of boundary conditions
Omission of required software systems states
Omission of definitions concerning reactions to illegal operation of the
software system
Coding error, for example:
Misunderstanding the design documentation
Linguistic(grammatically) errors in the programming languages
errors in the application of CASE and other development tools
errors in data selection etc.
10. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Non-compliance with documentation and coding instructions
Cause difficulties to coordinate the code in the same team
Difficult to understand the coding when the team member resign, retire or
been promoted
Cause difficulties to design review team, test team and maintenance team
Shortcomings of the test process
Incomplete test plans
Failures to document and report detected errors and faults
Failure to promptly correct detected software faults
Incomplete correction of detected errors
Procedure errors
Documentation errors
Errors in the design documents and in the documentation integrated into
the body of the software.
Error in the user manuals and the help function
11. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Software quality is:
(1) The degree to which a system, component, or
process meets specified requirements.
(2) The degree to which a system, component, or
process meets customer or user needs or
expectations.
12. Quality defines by various software quality specialists:Quality defines by various software quality specialists:
• Achieving high levels of user satisfaction, portability, maintainability,Achieving high levels of user satisfaction, portability, maintainability,
robustness, and fitness for use (Dr. Barry Boehm)robustness, and fitness for use (Dr. Barry Boehm)
• Conformance to user requirements (Phil Crosby)Conformance to user requirements (Phil Crosby)
• Striving for excellence in reliability & functions by continuousStriving for excellence in reliability & functions by continuous
improvement in the process of development, supported by statisticalimprovement in the process of development, supported by statistical
analysis of the causes of failure (Edwards Deming)analysis of the causes of failure (Edwards Deming)
• Achieving excellent levels of fitness for use, conformance toAchieving excellent levels of fitness for use, conformance to
requirements, reliability & maintainability (Watts Humphrey)requirements, reliability & maintainability (Watts Humphrey)
• Software quality means being on time, within budget and meeting userSoftware quality means being on time, within budget and meeting user
needs (James Martin)needs (James Martin)
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
13. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
• High levels of user satisfaction & low defect levels, often associatedHigh levels of user satisfaction & low defect levels, often associated
with low complexity (Tom McCabe)with low complexity (Tom McCabe)
• Quality means low defect levels, adherence of software functions toQuality means low defect levels, adherence of software functions to
users needs, & high reliability (John Musa)users needs, & high reliability (John Musa)
• High levels of user satisfaction & adherence requirements (Bill Perry)High levels of user satisfaction & adherence requirements (Bill Perry)
• Quality consists of freedom from deficiencies (Juran)Quality consists of freedom from deficiencies (Juran)
• Conformance to explicitly stated functional and performanceConformance to explicitly stated functional and performance
requirements, explicitly documented development standards, andrequirements, explicitly documented development standards, and
implicit characteristics that are expected of all professionallyimplicit characteristics that are expected of all professionally
developed software (Pressman)developed software (Pressman)
Quality defines by various software quality specialists:Quality defines by various software quality specialists:
14. Why is quality important?Why is quality important?
•A competitive issueA competitive issue
Differentiate your product from your competitorsDifferentiate your product from your competitors
Customer want to be assured of qualityCustomer want to be assured of quality
Businesses would give prime consideration toBusinesses would give prime consideration to
qualified developerqualified developer
•An issue for survivalAn issue for survival
•Quality is cost-effectiveQuality is cost-effective
Lead to increased productivityLead to increased productivity
Permanently reduced costsPermanently reduced costs
•Retaining customer & increasing profitsRetaining customer & increasing profits
•The sign of global businessThe sign of global business
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
15. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Cost of
software
quality
Prevention
costs
(Evaluate)Appraisal
costs
Internal
failure costs
External
failure costs
Costs of
Control costs
Costs of
Failure of
control costs
16. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
a. Investments in development of SQA infrastructure components
* Procedures and work instructions
* Support devices: templates, checklists etc
* Software configuration management system
* Software quality metrics
b. Regular implementation of SQA preventive activities:
* Instruction of new employees in SQA subjects
* Certification of employees
* Consultations on SQA issues to team leaders and others
c. Control of the SQA system through performance of:
* Internal quality reviews
* External quality audits
* Management quality reviews
17. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
(a) Costs of reviews:
* Formal design reviews (DRs)
* Peer reviews (inspections and walkthroughs)
* Expert reviews
(b) Costs of software testing:
* Unit, integration and software system tests
* Acceptance tests (carried out by customers)
(c) Costs of assuring quality of external participants
18. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
* Costs of redesign or design corrections subsequent to
design review and test findings
* Costs of re-programming or correcting programs in
response to test findings
* Costs of repeated design review and re- testing
(regression tests)
19. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
Typical external failure costs cover:
* Resolution of customer complaints during the warranty period.
* Correction of software bugs detected during regular operation.
* Correction of software failures after the warranty period is over even if the
correction is not covered by the warranty.
* Damages paid to customers in case of a severe software failure.
* Reimbursement of customer's purchase costs.
* Insurance against customer's claims.
Typical examples of hidden external failure costs:
* Reduction of sales to customers that suffered from software failures.
* Severe reduction of sales motivated by the firm's damaged reputation.
* Increased investment in sales promotion to counter the effects of past software
failures.
* Reduced prospects to win a tender or, alternatively, the need to under-price to
prevent competitors from winning tenders.
20. TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
Cost of
software
quality
Prevention costs
Appraisal costs
Internal failure
costs
External failure
costs
Costs of
Control costs
Costs of
Failure of
control costs
Managerial
preparations
and control costs
Managerial
failure costs
21. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
* Costs of carrying out contract reviews
* Costs of preparing project plans, including quality plans
* Costs of periodic updating of project and quality plans
* Costs of performing regular progress control
* Costs of performing regular progress control of external
participants’ contributions to projects
22. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
* Unplanned costs for professional and other resources,
resulting from underestimation of the resources in the
proposals stage.
* Damages paid to customers as compensation for late
project completion, a result of the unrealistic schedule in
the Company’s proposal.
* Damages paid to customers as compensation for late
completion of the project, a result of management’s
failure to recruit team members.
* Domino effect: Damages to other projects planned to be
performed by the same teams involved in the delayed
projects. The domino effect may induce considerable
hidden external failure costs.
23. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Software quality assurance is:
1. A planned and systematic pattern of all actions
necessary to provide adequate confidence that an
item or product conforms to established technical
requirements.
2. A set of activities designed to evaluate the process
by which the products are developed or
manufactured. Contrast with: quality control.
24. Software Quality Control Vs. Software Quality AssuranceSoftware Quality Control Vs. Software Quality Assurance
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Quality ControlQuality Control Quality AssuranceQuality Assurance
A set of activities to evaluate the quality of
a developed or manufactured product,
withholding(avoiding) of any product that
does not qualify
Minimize the cost of guaranteeing quality
by a variety of activities performed
throughout the development &
manufacturing processes
Corrective (Reactive) Prevention (Proactive)
Operational Strategic
Take place as the development or
manufacturing of the product is completed
Take place throughout the development &
manufacturing process
Confidence to producer Confidence to customer
Find defects (corrective) Prevent defects (preventive)
e.g.: walkthrough; inspection; checkpoint
review
e.g.: defining processes; quality audit;
selection of tools; training
25. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
(1) Assuring an acceptable level of confidence that the
software will conform to functional technical
requirements.
(2) Assuring an acceptable level of confidence that the
software will conform to managerial scheduling and
budgetary requirements.
(3) Initiation and management of activities for the
improvement and greater efficiency of software
development and SQA activities.
26. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
(1) Assuring an acceptable level of confidence that the
software maintenance activities will conform to the
functional technical requirements.
(2) Assuring an acceptable level of confidence that the
software maintenance activities will conform to
managerial scheduling and budgetary requirements.
(3) Initiate and manage activities to improve and increase
the efficiency of software maintenance and SQA
activities.
27. SQA & Software EngineeringSQA & Software Engineering
CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
• Software engineering (by IEEE)
– The application of a systematic, disciplined,
quantifiable approach to the development, operation
& maintenance of software; that is, the application of
engineering to software
• SE, a good infrastructure for achieving SQA
activities
• Cooperation between SE & SQA allow the
achievement of efficient, economic development,
maintenance activities, & assure the quality of the
product
28. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
• Being contracted
• Subjection to customer-supplier relationship
• Requirement for teamwork
• Need for cooperation and coordination with other
development teams
• Need for interfaces with other software systems
• Need to continue carrying out a project while the team
changes
• Need to continue maintaining the software system for
years
29. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
1. Contractual Conditions: an agreement between software
developer and the customer, need to cope with customer’s
functional requirements; project budget & timetable
2. Subjection to Customer-supplier relationship: activities are
under the oversight of the customer, continuous cooperation
needed between software developer and customer
3. Required teamwork: Time table requirements, need for
variety of specializations, wish to benefit from professional
mutual support & review
4. Cooperation & coordination with other software teams:
cooperation with other teams especially for large-scale projects
30. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
5. Interfaces with other software systems: to allow data in
electronic form to flow between different software system
6. Need to continue carrying out a project despite team
member changes: the leader has to replace the leaving
members by another employee or new recruit even though
training needed for the new personnel
7. Need to continue carrying out software maintenance for an
extended period: maintenance needed for customer;
maintenance needed for software that has been developed in-
house as well
31. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Reviews
1. Which SQA environment characteristic affect mainly the
professional (developers) side? Justify your answer(s).
2. Which SQA environment characteristic affect mainly the
managerial side? Justify your answer(s).
32. CHAPTER 1 The Software QualityCHAPTER 1 The Software Quality
TQA 7011 SOFTWARE QUALITY ASSURANCE & TESTINGTQA 7011 SOFTWARE QUALITY ASSURANCE & TESTING
Case Studies
The interfaces of a salary processing system are shown in the next slide.
1. Suggest what are the main benefits of applying computerized interfaces
of transferring printouts.
2. Give another example (system) where input interface is applied.
3. Give another example (system) where output interface is applied.
4. Would you advise all information transfers from one organization to
another be performed by computerized interface? Justify your answers.