Troubleshooting Computing Problems
Download as PPTX, PDF1 like328 views
Six steps of troubleshooting include identifying the problem, establishing a theory of probable cause, testing the theory, establishing and implementing a solution plan, verifying full system functionality, and documenting findings, actions, and outcomes. Effective troubleshooting uses a combination of open and closed questions, and thorough documentation of all investigation steps, tests, solutions, and outcomes is critical. Experienced technicians may use a half-split self-evaluation approach that combines top-down and bottom-up methods with educated guesses to efficiently diagnose and resolve issues.
1 of 5
Download to read offline
Recommended
AiTi Education Software Testing Session 01 b
AiTi Education Software Testing Session 01 bAiTi Education
油
This document discusses key fundamentals of software testing. It explains why testing is necessary to build confidence and find faults. It covers the testing process, including re-testing fixes and regression testing to check for unintended effects of changes. The document stresses predicting expected results in advance and prioritizing tests to focus on the most important and riskiest areas given time constraints. Independence in testing and managing relationships with developers is also addressed.Managing agile testing 
Managing agile testing PractiTest
油
-Agile development and Agile testing.
-The aim of test management in Agile projects
- Tips and ideas for successfully managing your Agile testing process.
full webinar recording:
https://www.practitest.com/qa-learningcenter/webinars/agile-test-management/POLITEKNIK MALAYSIA
POLITEKNIK MALAYSIAAiman Hud
油
This chapter outlines the objectives of preventative maintenance and troubleshooting. It discusses the importance of preventative maintenance through regular inspection and cleaning to prevent failures. The troubleshooting process is described as a 5-step approach: 1) identify the problem, 2) generate potential causes, 3) test theories, 4) implement a solution, and 5) verify the solution and document findings. Backing up data and obtaining liability waivers are also emphasized before any repair work.In-depth problem solving tool
In-depth problem solving toolLineView Academy (was OFX Academy)
油
By formalising problem solving reduces the risk of damaging people, product and assets and ensures that issues get resolved right first time.Problem solving overview
Problem solving overviewLineView Academy (was OFX Academy)
油
This document provides an overview of problem solving techniques to help identify the best approach. It discusses choosing techniques that are appropriate for the problem and plant. Formal problem solving ensures issues are resolved correctly the first time, saving time and money. It prevents "heroics" and reduces risk of damage. The right technique is selected to get the best result as a one-size approach does not work. Techniques include root cause analysis tools like 5 Whys and fishbone diagrams. For complex issues, techniques like Kepner-Tregoe analysis are recommended. Defining the problem clearly is critical to solving it efficiently.Estimates in Software Development and Testing
Estimates in Software Development and TestingQualityAssuranceGroup
油
This document discusses different approaches and techniques for estimating software development and testing projects. It describes measuring projects at different levels, from overall project level down to individual task levels. It outlines common software estimation approaches like macro estimation using equations, comparisons, or analogies, and micro estimation using work breakdown. It provides examples of estimating the effort for individual project activities and a five step process for bottom-up estimating. Finally, it notes the tradeoff between project quality, scope, cost and time.Ken Johnston - Big Bugs That Got Away - EuroSTAR 2010
Ken Johnston - Big Bugs That Got Away - EuroSTAR 2010TEST Huddle
油
EuroSTAR Software Testing Conference 2010 presentation on Big Bugs That Got Away by Ken Johnston . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/Quick & easy problem solving tools
Quick & easy problem solving toolsLineView Academy (was OFX Academy)
油
By formalising problem solving reduces the risk of damaging people, product and assets and ensures that issues get resolved right first time.What a DevOps specialist has to know about static code analysis
What a DevOps specialist has to know about static code analysisAndrey Karpov
油
Reasons of failed introductions.
Place of static analysis in the DevOps process.
Static analysis friend or foe.
Notifications about analysis results.
What to do with 10 000 analyzer warnings after the first run?
How much time is needed for fixing all bugs?
Q&A or whats next?
Design Process
Design ProcessRida Murad
油
The document outlines the steps of the engineering design process which includes identifying needs or problems, researching potential solutions, developing possible solutions, selecting the best solution, constructing prototypes, testing and evolving the design, communicating the solution, and redesigning if needed. Some key steps involve examining current solutions to the problem, brainstorming ideas, creating tests for prototypes, and documenting results for manufacturing. The overall process is meant to develop consistent, high quality and safe engineered products and systems.Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew EakinQA or the Highway
油
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing aAn analytical approach to effective risk based test planning 
An analytical approach to effective risk based test planning Joe Kevens
油
Regression is not easily understood, as it seemingly manifests from nowhere. But if you can identify methods to help spot quality failure trends, you stand a better chance of understanding the root causes. This presentation serves to highlight a number of risk identification and planning techniques that you could add to your arsenal! Presented at TestExpo in London, UK, on 31 Oct 2017. Michael Bolton - Heuristics: Solving Problems Rapidly
Michael Bolton - Heuristics: Solving Problems RapidlyTEST Huddle
油
EuroSTAR Software Testing Conference 2008 presentation on Heuristics: Solving Problems Rapidly by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/From Gatekeeper to Partner by Kelsey Shannahan
From Gatekeeper to Partner by Kelsey ShannahanQA or the Highway
油
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.Solving Flaky Automated Tests Using Machine Learning
Solving Flaky Automated Tests Using Machine LearningJames Farrier
油
James Farrier founded Appsurify to address test automation challenges, particularly unreliable or "flaky" tests that fail unexpectedly. The document discusses various causes of flaky tests and strategies for handling them, including manually or automatically removing flaky tests from runs, fixing the tests, rerunning tests, using bots to quarantine flaky results, prioritizing relevant tests for changes, and employing classification algorithms to detect flaky tests. The key challenges are scaling the efforts while still allowing tests to run and find defects.Exploratory Session Based TestingWith A Twist Star East 2009
Exploratory Session Based TestingWith A Twist Star East 2009aandelkovic
油
The document discusses Maquet Critical Care AB's introduction and use of session-based testing (SBTM) to better manage exploratory testing in their FDA-regulated medical device development environment. They created an in-house SBT tool to facilitate SBTM and provide metrics on testing activities. Using SBTM and the tool increased visibility into exploratory testing and engaged more employees in the process. Future goals include enhancing the tool and training more employees on SBTM.Test process
Test processSoori Joy
油
Testing is a process rather than a single activity. This process starts from test planning then designing test cases, preparing for execution and evaluating status till the test closure.Exploratory testing
Exploratory testingBilla Kota Sriram
油
This document discusses exploratory testing. It defines exploratory testing as testing where the tester actively designs tests during the testing process and uses information gained from testing to design new tests. Key aspects of exploratory testing include investigation, discovery, learning, and using imagination to think of new tests. The document outlines what makes an excellent exploratory tester, the differences between exploratory and traditional scripted testing, pros and cons of exploratory testing, how to perform exploratory testing using techniques like the "tour bus principle", and myths about exploratory testing.[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing![[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing](https://cdn.slidesharecdn.com/ss_thumbnails/provingourworth-150208213511-conversion-gate01-thumbnail.jpg?width=560&fit=bounds)
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club
油
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
Over the years writers have defined testing as a process of finding, a process of evaluating, a process of measuring, a process of improving. For a quarter of a century we as testers have been focused on the internal process of testing, while generally disregarding its real purpose. The real purpose of testing is to create information. James Bach nailed it when he wrote, The ultimate reason testers exist is to provide information that others on the project use to create things of value. That is why testing exists to provide information of value. So, when managers complain that testing costs too much perhaps they are really trying to say, Im not getting enough valuable information to justify the cost of testing. When testers say my management doesnt see the value in our work perhaps they are really trying to say, My management doesnt value the information Im providing to them. To prove our worth, to increase the value of testing, we must first focus on testings purpose providing valuable information not its process. Join Lee as he discusses why quantifying the value of testing is difficult work perhaps thats why we concentrate so much on testing processthats much easier. But until we do this difficult work, until we prove our worth through quantifying our contribution, we should expect the bombardments to continue.Fail Smart, Not Just Fast: FMEA Workshop
Fail Smart, Not Just Fast: FMEA WorkshopRob Keefer
油
The document discusses using Failure Mode and Effects Analysis (FMEA) to understand potential failures and risks in a project. FMEA was originally developed for manufacturing but can be applied to review components, assemblies, and subsystems to identify failure modes, causes, and effects. It also presents a risk canvas template to map out goals, constraints, potential positive and negative outcomes, success requirements, risks, contingencies, and next steps. An example risk analysis is provided for a hypothetical project to replace a software system.Exploratory Testing
Exploratory Testingsriks7
油
Presentation on Exploratory Testing delivered by Anutthara Baradwaj at the June 09 Knowledge sharing session hosted at Oracle IndiaExumaTech Dev Process
ExumaTech Dev ProcessExuma Technologies (DockMaster/RVMaster)
油
Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.
We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:
http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products
Find us at http://exumatech.com or @ExumaTechiSQI Certification Days Advanced Level Test Analyst Graham Bath
iSQI Certification Days Advanced Level Test Analyst Graham BathIevgenii Katsan
油
The document provides an overview of the tasks and responsibilities of a test analyst. It discusses principal tasks like test analysis, design, implementation, execution and closure activities. It also covers test techniques like specification-based techniques using tools like equivalence partitioning and boundary value analysis. Defect-based and experience-based techniques are also addressed. Quality characteristics and using checklists in technical reviews are additional topics covered. The role of the test analyst in supporting risk management is also summarized.Ruud Teunissen - The Awful Truth About Estimation, Have I Been Wrong All Alon...
Ruud Teunissen - The Awful Truth About Estimation, Have I Been Wrong All Alon...TEST Huddle
油
EuroSTAR Software Testing Conference 2013 presentation on The Awful Truth About Estimation, Have I Been Wrong All Along by Ruud Teunissen.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/Bad metric, bad!
Bad metric, bad!Centric Consulting
油
About Joseph Ours' Presentation Bad Metric Bad!
Metrics have always been used in corporate sectors, primarily as a way to gain insight into what is an otherwise invisible world. Organizations blindly adopt a set of metrics as a way of satisfying some process transparency requirement, rarely applying any statistical or scientific thought behind the measures and metrics they establish and interpret. Many metrics do not represent what people believe they do and as a result can lead to erroneous decisions. Joseph looks at some of the common and some of the humorous testing metrics and determines why they are failures. He further discusses the real purpose of metrics, metrics programs and finishes with pitfalls into which you fall.Software testing
Software testingAnne-Marie Charrett
油
This document discusses software testing and provides guidance on best practices. It defines software testing as empirically investigating a product to provide stakeholders with quality information. The key aspects of testing discussed are modeling the system, making observations, asking useful questions, using logical reasoning, and taking a process of discovery approach. Testing is distinguished from checking and the importance of test design, exploratory testing, and testability over large automated test suites is emphasized. Credits are given to influential thinkers in the field.What You are Doing Wrong with Automated Testing
What You are Doing Wrong with Automated Testingshawnfaunce
油
This document discusses several anti-patterns that are commonly seen in automated testing practices. It identifies anti-patterns such as relying primarily on UI tests, using screen recorders to build tests, ignoring intermittent low priority bugs, having all tests run as a monolith test suite, having testers write automated tests instead of developers, and thinking that achieving 100% test coverage equals high quality tests. For each anti-pattern, it provides examples of why they look like good solutions on the surface but introduce problems related to maintenance, fragility, dependencies, ownership, and not actually guaranteeing test quality.Innovation management
Innovation managementHandaru Sakti
油
This document discusses innovation management and the importance of developing the right business model rather than prematurely focusing on solutions. It recommends taking a lean startup approach of quickly building prototypes, validating assumptions with customers, and iteratively improving the business model based on experimental feedback. The key steps are to fall in love with problems not solutions, identify the riskiest assumptions to test, and use traction not just build velocity to measure business model success.Professionalism and Ethics
Professionalism and EthicsShaun Wilson
油
This document discusses several topics related to professionalism and ethics in computing including professional bodies, codes of conduct, and key UK legislation around data protection, computer misuse, equality, health and safety, waste disposal, and intellectual property. Professional bodies provide certifications and resources for members, set technical standards, and bring professionals together. Codes of conduct require professionals to act with integrity, reject bribery, uphold their profession's reputation, and protect confidential information. Legislation discussed governs data protection, computer security, equality in the workplace, health and safety, proper waste disposal, and copyright.Software Development (Mobile Technology)
Software Development (Mobile Technology)Shaun Wilson
油
This document discusses key concepts in software development including data types like boolean, integer, real, and string. It also covers programming constructs such as sequence, selection, and iteration. Finally, it outlines the typical documentation for a software project like requirements specification, test plans, code listings, and completed test logs.More Related Content
What's hot (20)
What a DevOps specialist has to know about static code analysis
What a DevOps specialist has to know about static code analysisAndrey Karpov
油
Reasons of failed introductions.
Place of static analysis in the DevOps process.
Static analysis friend or foe.
Notifications about analysis results.
What to do with 10 000 analyzer warnings after the first run?
How much time is needed for fixing all bugs?
Q&A or whats next?
Design Process
Design ProcessRida Murad
油
The document outlines the steps of the engineering design process which includes identifying needs or problems, researching potential solutions, developing possible solutions, selecting the best solution, constructing prototypes, testing and evolving the design, communicating the solution, and redesigning if needed. Some key steps involve examining current solutions to the problem, brainstorming ideas, creating tests for prototypes, and documenting results for manufacturing. The overall process is meant to develop consistent, high quality and safe engineered products and systems.Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew EakinQA or the Highway
油
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing aAn analytical approach to effective risk based test planning
An analytical approach to effective risk based test planning Joe Kevens
油
Regression is not easily understood, as it seemingly manifests from nowhere. But if you can identify methods to help spot quality failure trends, you stand a better chance of understanding the root causes. This presentation serves to highlight a number of risk identification and planning techniques that you could add to your arsenal! Presented at TestExpo in London, UK, on 31 Oct 2017. Michael Bolton - Heuristics: Solving Problems Rapidly
Michael Bolton - Heuristics: Solving Problems RapidlyTEST Huddle
油
EuroSTAR Software Testing Conference 2008 presentation on Heuristics: Solving Problems Rapidly by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/From Gatekeeper to Partner by Kelsey Shannahan
From Gatekeeper to Partner by Kelsey ShannahanQA or the Highway
油
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.Solving Flaky Automated Tests Using Machine Learning
Solving Flaky Automated Tests Using Machine LearningJames Farrier
油
James Farrier founded Appsurify to address test automation challenges, particularly unreliable or "flaky" tests that fail unexpectedly. The document discusses various causes of flaky tests and strategies for handling them, including manually or automatically removing flaky tests from runs, fixing the tests, rerunning tests, using bots to quarantine flaky results, prioritizing relevant tests for changes, and employing classification algorithms to detect flaky tests. The key challenges are scaling the efforts while still allowing tests to run and find defects.Exploratory Session Based TestingWith A Twist Star East 2009
Exploratory Session Based TestingWith A Twist Star East 2009aandelkovic
油
The document discusses Maquet Critical Care AB's introduction and use of session-based testing (SBTM) to better manage exploratory testing in their FDA-regulated medical device development environment. They created an in-house SBT tool to facilitate SBTM and provide metrics on testing activities. Using SBTM and the tool increased visibility into exploratory testing and engaged more employees in the process. Future goals include enhancing the tool and training more employees on SBTM.Test process
Test processSoori Joy
油
Testing is a process rather than a single activity. This process starts from test planning then designing test cases, preparing for execution and evaluating status till the test closure.Exploratory testing
Exploratory testingBilla Kota Sriram
油
This document discusses exploratory testing. It defines exploratory testing as testing where the tester actively designs tests during the testing process and uses information gained from testing to design new tests. Key aspects of exploratory testing include investigation, discovery, learning, and using imagination to think of new tests. The document outlines what makes an excellent exploratory tester, the differences between exploratory and traditional scripted testing, pros and cons of exploratory testing, how to perform exploratory testing using techniques like the "tour bus principle", and myths about exploratory testing.[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club
油
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
Over the years writers have defined testing as a process of finding, a process of evaluating, a process of measuring, a process of improving. For a quarter of a century we as testers have been focused on the internal process of testing, while generally disregarding its real purpose. The real purpose of testing is to create information. James Bach nailed it when he wrote, The ultimate reason testers exist is to provide information that others on the project use to create things of value. That is why testing exists to provide information of value. So, when managers complain that testing costs too much perhaps they are really trying to say, Im not getting enough valuable information to justify the cost of testing. When testers say my management doesnt see the value in our work perhaps they are really trying to say, My management doesnt value the information Im providing to them. To prove our worth, to increase the value of testing, we must first focus on testings purpose providing valuable information not its process. Join Lee as he discusses why quantifying the value of testing is difficult work perhaps thats why we concentrate so much on testing processthats much easier. But until we do this difficult work, until we prove our worth through quantifying our contribution, we should expect the bombardments to continue.Fail Smart, Not Just Fast: FMEA Workshop
Fail Smart, Not Just Fast: FMEA WorkshopRob Keefer
油
The document discusses using Failure Mode and Effects Analysis (FMEA) to understand potential failures and risks in a project. FMEA was originally developed for manufacturing but can be applied to review components, assemblies, and subsystems to identify failure modes, causes, and effects. It also presents a risk canvas template to map out goals, constraints, potential positive and negative outcomes, success requirements, risks, contingencies, and next steps. An example risk analysis is provided for a hypothetical project to replace a software system.Exploratory Testing
Exploratory Testingsriks7
油
Presentation on Exploratory Testing delivered by Anutthara Baradwaj at the June 09 Knowledge sharing session hosted at Oracle IndiaExumaTech Dev Process
ExumaTech Dev ProcessExuma Technologies (DockMaster/RVMaster)
油
Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.
We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:
http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products
Find us at http://exumatech.com or @ExumaTechiSQI Certification Days Advanced Level Test Analyst Graham Bath
iSQI Certification Days Advanced Level Test Analyst Graham BathIevgenii Katsan
油
The document provides an overview of the tasks and responsibilities of a test analyst. It discusses principal tasks like test analysis, design, implementation, execution and closure activities. It also covers test techniques like specification-based techniques using tools like equivalence partitioning and boundary value analysis. Defect-based and experience-based techniques are also addressed. Quality characteristics and using checklists in technical reviews are additional topics covered. The role of the test analyst in supporting risk management is also summarized.Ruud Teunissen - The Awful Truth About Estimation, Have I Been Wrong All Alon...
Ruud Teunissen - The Awful Truth About Estimation, Have I Been Wrong All Alon...TEST Huddle
油
EuroSTAR Software Testing Conference 2013 presentation on The Awful Truth About Estimation, Have I Been Wrong All Along by Ruud Teunissen.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/Bad metric, bad!
Bad metric, bad!Centric Consulting
油
About Joseph Ours' Presentation Bad Metric Bad!
Metrics have always been used in corporate sectors, primarily as a way to gain insight into what is an otherwise invisible world. Organizations blindly adopt a set of metrics as a way of satisfying some process transparency requirement, rarely applying any statistical or scientific thought behind the measures and metrics they establish and interpret. Many metrics do not represent what people believe they do and as a result can lead to erroneous decisions. Joseph looks at some of the common and some of the humorous testing metrics and determines why they are failures. He further discusses the real purpose of metrics, metrics programs and finishes with pitfalls into which you fall.Software testing
Software testingAnne-Marie Charrett
油
This document discusses software testing and provides guidance on best practices. It defines software testing as empirically investigating a product to provide stakeholders with quality information. The key aspects of testing discussed are modeling the system, making observations, asking useful questions, using logical reasoning, and taking a process of discovery approach. Testing is distinguished from checking and the importance of test design, exploratory testing, and testability over large automated test suites is emphasized. Credits are given to influential thinkers in the field.What You are Doing Wrong with Automated Testing
What You are Doing Wrong with Automated Testingshawnfaunce
油
This document discusses several anti-patterns that are commonly seen in automated testing practices. It identifies anti-patterns such as relying primarily on UI tests, using screen recorders to build tests, ignoring intermittent low priority bugs, having all tests run as a monolith test suite, having testers write automated tests instead of developers, and thinking that achieving 100% test coverage equals high quality tests. For each anti-pattern, it provides examples of why they look like good solutions on the surface but introduce problems related to maintenance, fragility, dependencies, ownership, and not actually guaranteeing test quality.Innovation management
Innovation managementHandaru Sakti
油
This document discusses innovation management and the importance of developing the right business model rather than prematurely focusing on solutions. It recommends taking a lean startup approach of quickly building prototypes, validating assumptions with customers, and iteratively improving the business model based on experimental feedback. The key steps are to fall in love with problems not solutions, identify the riskiest assumptions to test, and use traction not just build velocity to measure business model success.[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club
油
More from Shaun Wilson (20)
Professionalism and Ethics
Professionalism and EthicsShaun Wilson
油
This document discusses several topics related to professionalism and ethics in computing including professional bodies, codes of conduct, and key UK legislation around data protection, computer misuse, equality, health and safety, waste disposal, and intellectual property. Professional bodies provide certifications and resources for members, set technical standards, and bring professionals together. Codes of conduct require professionals to act with integrity, reject bribery, uphold their profession's reputation, and protect confidential information. Legislation discussed governs data protection, computer security, equality in the workplace, health and safety, proper waste disposal, and copyright.Software Development (Mobile Technology)
Software Development (Mobile Technology)Shaun Wilson
油
This document discusses key concepts in software development including data types like boolean, integer, real, and string. It also covers programming constructs such as sequence, selection, and iteration. Finally, it outlines the typical documentation for a software project like requirements specification, test plans, code listings, and completed test logs.Computer Systems Fundamentals
Computer Systems FundamentalsShaun Wilson
油
This document provides an overview of computer systems fundamentals including logic gates, number conversions, layers of the operating system, and components of a basic computer system. Specifically, it discusses:
1. Logic gates like AND, OR, and NOT and their truth tables.
2. Conversions between number bases like binary, decimal, and hexadecimal with examples.
3. The main layers of an operating system including the user interface, file management, input/output, memory management, and kernel.
4. Key components of a computer system including the ALU, control unit, registers, buses, and ASCII character encoding.Introduction to Project Management Assessment Notes
Introduction to Project Management Assessment NotesShaun Wilson
油
This document provides an introduction and overview of key project management concepts. It defines what a project is, including that projects have unique goals, defined timelines and budgets. It discusses project tasks, stakeholders, and tools like work breakdown structures, Gantt charts, PERT charts and scope management. PERT charts in particular help schedule projects and identify the critical path of tasks. Careful scope and change management is important to avoid feature creep from altering the original project plan.SQL Assessment Command Statements
SQL Assessment Command StatementsShaun Wilson
油
The document provides examples and explanations of common SQL commands used to query, manipulate, and manage data in a relational database. Key points include:
- The SELECT statement is used to query data from database tables. The WHERE clause filters results.
- INSERT, UPDATE and DELETE statements are used to add, modify and remove rows in database tables.
- CREATE, ALTER, DROP statements manage the database schema by creating, modifying and deleting tables, columns, keys and constraints.
- PRIMARY KEY and FOREIGN KEY constraints enforce data integrity and relationships between tables.The Rise and Fall of the Roman Empire
The Rise and Fall of the Roman EmpireShaun Wilson
油
The document provides an overview of the rise and fall of the Roman Empire from 509 BCE to 476 CE. It discusses the transition from Roman Republic to Roman Empire under Augustus, key emperors like Tiberius, Caligula, Nero, Vespasian, and Hadrian, as well as the division of the empire into eastern and western halves under Diocletian. It also examines factors that contributed to the decline of the western empire, including invasions by barbarian tribes and the removal of the capital to Constantinople, while the eastern empire continued on as the Byzantine Empire until 1453.National 5 Graphic Communication
National 5 Graphic CommunicationShaun Wilson
油
The document discusses color theory and desktop publishing principles. It describes primary, secondary and tertiary colors. It also discusses tints, shades, warm and cold colors. It outlines design principles like alignment, bleed, captions and drop caps. It provides information on fonts, headers, footers, guides and page layout features.Vector journeys!
Vector journeys!Shaun Wilson
油
The document discusses vectors and their components. It provides examples of finding the components of vectors using other known vectors, such as finding the components of vector AC given the components of vectors AB and BC. It also discusses using the triangle rule to find unknown vectors. Diagrams are included to illustrate different vector problems and solutions.Vector multiplication dot product
Vector multiplication dot productShaun Wilson
油
The document discusses vector multiplication using the dot product. It provides two formulas for calculating the dot product:
1) a.b = |a| |b| cos慮, where |a| and |b| are the magnitudes of the vectors, 慮 is the angle between them, and cos慮 gives the effectiveness of their interaction. The dot product is largest when the vectors are parallel (慮 = 0).
2) For vectors in 3D space, a.b = x1x2 + y1y2 + z1z2, where the x, y, z components of each vector are multiplied and summed.
It provides examples of calculating the dot product using both formulas in different vectorDot product calc angle to finish!
Dot product calc angle to finish!Shaun Wilson
油
This document discusses using the dot product to calculate the angle between two vectors. It provides the formula for calculating the dot product and shows examples of using the formula to find the angle between vectors. It also discusses how if two vectors are perpendicular, their dot product will equal 0.Unit vectors 14
Unit vectors 14Shaun Wilson
油
This document introduces unit vectors and how they can be used to write the components of a vector. It defines a unit vector as having a magnitude of 1 and lists the standard unit vectors i, j, k. It then shows how any vector can be written as the sum of its components in the direction of each unit vector, using examples like 3i + 4j + 7k. Finally, it provides additional examples of writing vectors in component form using unit vectors and calculating the sum of two vectors.Vector bits and pieces
Vector bits and piecesShaun Wilson
油
This document provides information about vectors, including:
- The relationship between the magnitude of a vector and the cosine of the angle between two vectors in determining their dot product.
- Unit vectors have a magnitude of 1 and are perpendicular to each other.
- Examples are given of calculating the dot product of vectors in different geometric configurations by decomposing into the dot products of the vectors with the unit vectors.
- Key steps are to start from the same point when calculating dot products of vectors in a figure.Vectors intro
Vectors introShaun Wilson
油
Vectors can represent journeys with distance and direction. They have components that work like coordinates and magnitude that is calculated using Pythagoras. Vectors can be added by placing them nose to tail and adding corresponding components, subtracted by adding the negative vector, and multiplied by a scalar by multiplying each component.Ratios
RatiosShaun Wilson
油
The document discusses applying ratios to vectors. It provides examples of using ratios to find unknown points along vectors. The key steps are: 1) Form an equation using the position vector rule relating the unknown point P to the known endpoints A and B; 2) Make P the subject of the equation; 3) Solve the equation to find the coordinates of P. Examples show setting up equations for points dividing vectors in given ratios and solving to find the coordinates of the unknown points.Parallel + collinear vectors
Parallel + collinear vectorsShaun Wilson
油
Vectors AB and CD are parallel if their direction vectors are proportional.
Vectors A, B, and C are collinear if their direction vectors are proportional and they share a common point.
Three examples are given to demonstrate proving vectors are parallel or collinear by showing their direction vectors are proportional.Position and 3 d vectors amended
Position and 3 d vectors amendedShaun Wilson
油
This document discusses position vectors in 2D and 3D coordinate systems.
- A position vector starts at the origin and represents the displacement from the origin to a point P defined by its coordinates.
- The position vector rule states that the position vector from point P to point R is equal to the vector from R's position vector subtracted by P's position vector.
- Position vectors and their properties like magnitude, addition, subtraction, and scalar multiplication follow the same rules in 3D as in 2D. Several examples are provided to demonstrate calculating the position vector and magnitude between two points in 3D space.Solving trig equations higher
Solving trig equations higherShaun Wilson
油
The document provides information on solving more difficult trigonometric equations. It discusses finding the acute angle and related angles, using trig function properties to isolate the angle, and considering additional solutions that occur every period of the trig function. Example problems are worked through step-by-step to demonstrate these concepts.Solving trig equations + double angle formulae
Solving trig equations + double angle formulaeShaun Wilson
油
1) The document discusses solving trigonometric equations using compound angle formulas and double angle formulas.
2) It provides examples of using these formulas to solve equations such as sin2x + cosx = 0, 2sinxcosx + cosx = 0, and cos2x - sinx = 0.
3) The key steps are to use a double angle formula to get one side equal to zero, factorize the equation, and then solve the resulting trigonometric mini equations.Solving exponential equations
Solving exponential equationsShaun Wilson
油
This document discusses solving exponential equations by taking the log of both sides. It shows how to solve equations with unknown powers and equations containing e as the base. The key steps are:
1) Isolate the term with the unknown power
2) Take the log of both sides
3) Use properties of logs to isolate the unknown variable
4) Calculate the value of the variable
Examples are provided to illustrate solving equations with unknown powers, equations containing e, and applying the method to context problems. The overall approach is to take logs to transform exponential equations into linear equations that can be easily solved.Logarithms intro
Logarithms introShaun Wilson
油
1) Logarithms translate a log statement into an exponential statement with the same base.
2) To translate a log statement, identify the base, power, and starting number.
3) Examples show translating log statements to exponential statements using a calculator to evaluate.Recently uploaded (20)
Principle and Practices of Animal Breeding || Boby Basnet
Principle and Practices of Animal Breeding || Boby BasnetBoby Basnet
油
Principle and Practices of Animal Breeding Full Note
|| Assistant Professor Boby Basnet ||IAAS || AFU || PU || FUAPM People Interest Network Conference - Oliver Randall & David Bovis - Own Y...
APM People Interest Network Conference - Oliver Randall & David Bovis - Own Y...Association for Project Management
油
APM People Interest Network Conference 2025
- Autonomy, Teams and Tension
- Oliver Randall & David Bovis
- Own Your Autonomy
Oliver Randall
Consultant, Tribe365
Oliver is a career project professional since 2011 and started volunteering with APM in 2016 and has since chaired the People Interest Network and the North East Regional Network. Oliver has been consulting in culture, leadership and behaviours since 2019 and co-developed HPTM速an off the shelf high performance framework for teams and organisations and is currently working with SAS (Stellenbosch Academy for Sport) developing the culture, leadership and behaviours framework for future elite sportspeople whilst also holding down work as a project manager in the NHS at North Tees and Hartlepool Foundation Trust.
David Bovis
Consultant, Duxinaroe
A Leadership and Culture Change expert, David is the originator of BTFA and The Dux Model.
With a Masters in Applied Neuroscience from the Institute of Organisational Neuroscience, he is widely regarded as the Go-To expert in the field, recognised as an inspiring keynote speaker and change strategist.
He has an industrial engineering background, majoring in TPS / Lean. David worked his way up from his apprenticeship to earn his seat at the C-suite table. His career spans several industries, including Automotive, Aerospace, Defence, Space, Heavy Industries and Elec-Mech / polymer contract manufacture.
Published in Londons Evening Standard quarterly business supplement, James Caans Your business Magazine, Quality World, the Lean Management Journal and Cambridge Universities PMA, he works as comfortably with leaders from FTSE and Fortune 100 companies as he does owner-managers in SMEs. He is passionate about helping leaders understand the neurological root cause of a high-performance culture and sustainable change, in business.
Session | Own Your Autonomy The Importance of Autonomy in Project Management
#OwnYourAutonomy is aiming to be a global APM initiative to position everyone to take a more conscious role in their decision making process leading to increased outcomes for everyone and contribute to a world in which all projects succeed.
We want everyone to join the journey.
#OwnYourAutonomy is the culmination of 3 years of collaborative exploration within the Leadership Focus Group which is part of the APM People Interest Network. The work has been pulled together using the 5 HPTM速 Systems and the BTFA neuroscience leadership programme.
https://www.linkedin.com/showcase/apm-people-network/about/Essentials of a Good PMO, presented by Aalok Sonawala
Essentials of a Good PMO, presented by Aalok SonawalaAssociation for Project Management
油
APM event hosted by the South Wales and West of England Network (SWWE Network)
Speaker: Aalok Sonawala
The SWWE Regional Network were very pleased to welcome Aalok Sonawala, Head of PMO, National Programmes, Rider Levett Bucknall on 26 February, to BAWA for our first face to face event of 2025. Aalok is a member of APMs Thames Valley Regional Network and also speaks to members of APMs PMO Interest Network, which aims to facilitate collaboration and learning, offer unbiased advice and guidance.
Tonight, Aalok planned to discuss the importance of a PMO within project-based organisations, the different types of PMO and their key elements, PMO governance and centres of excellence.
PMOs within an organisation can be centralised, hub and spoke with a central PMO with satellite PMOs globally, or embedded within projects. The appropriate structure will be determined by the specific business needs of the organisation. The PMO sits above PM delivery and the supply chain delivery teams.
For further information about the event please click here.How to attach file using upload button Odoo 18
How to attach file using upload button Odoo 18Celine George
油
In this slide, well discuss on how to attach file using upload button Odoo 18. Odoo features a dedicated model, 'ir.attachments,' designed for storing attachments submitted by end users. We can see the process of utilizing the 'ir.attachments' model to enable file uploads through web forms in this slide.
Kaun TALHA quiz Finals -- El Dorado 2025
Kaun TALHA quiz Finals -- El Dorado 2025Conquiztadors- the Quiz Society of Sri Venkateswara College
油
Finals of Kaun TALHA : a Travel, Architecture, Lifestyle, Heritage and Activism quiz, organized by Conquiztadors, the Quiz society of Sri Venkateswara College under their annual quizzing fest El Dorado 2025. How to Configure Restaurants in Odoo 17 Point of Sale
How to Configure Restaurants in Odoo 17 Point of SaleCeline George
油
Odoo, a versatile and integrated business management software, excels with its robust Point of Sale (POS) module. This guide delves into the intricacies of configuring restaurants in Odoo 17 POS, unlocking numerous possibilities for streamlined operations and enhanced customer experiences.Blind spots in AI and Formulation Science, IFPAC 2025.pdf
Blind spots in AI and Formulation Science, IFPAC 2025.pdfAjaz Hussain
油
The intersection of AI and pharmaceutical formulation science highlights significant blind spotssystemic gaps in pharmaceutical development, regulatory oversight, quality assurance, and the ethical use of AIthat could jeopardize patient safety and undermine public trust. To move forward effectively, we must address these normalized blind spots, which may arise from outdated assumptions, errors, gaps in previous knowledge, and biases in language or regulatory inertia. This is essential to ensure that AI and formulation science are developed as tools for patient-centered and ethical healthcare.FESTIVAL: SINULOG & THINGYAN-LESSON 4.pptx
FESTIVAL: SINULOG & THINGYAN-LESSON 4.pptxDanmarieMuli1
油
Sinulog Festival of Cebu City, and Thingyan Festival of Myanmar.
Mate, a short story by Kate Grenvile.pptx
Mate, a short story by Kate Grenvile.pptxLiny Jenifer
油
A powerpoint presentation on the short story Mate by Kate Greenville. This presentation provides information on Kate Greenville, a character list, plot summary and critical analysis of the short story.How to Setup WhatsApp in Odoo 17 - Odoo 際際滷s
How to Setup WhatsApp in Odoo 17 - Odoo 際際滷sCeline George
油
Integrate WhatsApp into Odoo using the WhatsApp Business API or third-party modules to enhance communication. This integration enables automated messaging and customer interaction management within Odoo 17.QuickBooks Desktop to QuickBooks Online How to Make the Move
QuickBooks Desktop to QuickBooks Online How to Make the MoveTechSoup
油
If you use QuickBooks Desktop and are stressing about moving to QuickBooks Online, in this webinar, get your questions answered and learn tips and tricks to make the process easier for you.
Key Questions:
* When is the best time to make the shift to QuickBooks Online?
* Will my current version of QuickBooks Desktop stop working?
* I have a really old version of QuickBooks. What should I do?
* I run my payroll in QuickBooks Desktop now. How is that affected?
*Does it bring over all my historical data? Are there things that don't come over?
* What are the main differences between QuickBooks Desktop and QuickBooks Online?
* And moreDigital Tools with AI for e-Content Development.pptx
Digital Tools with AI for e-Content Development.pptxDr. Sarita Anand
油
This ppt is useful for not only for B.Ed., M.Ed., M.A. (Education) or any other PG level students or Ph.D. scholars but also for the school, college and university teachers who are interested to prepare an e-content with AI for their students and others.Blind Spots in AI and Formulation Science Knowledge Pyramid (Updated Perspect...
Blind Spots in AI and Formulation Science Knowledge Pyramid (Updated Perspect...Ajaz Hussain
油
This presentation delves into the systemic blind spots within pharmaceutical science and regulatory systems, emphasizing the significance of "inactive ingredients" and their influence on therapeutic equivalence. These blind spots, indicative of normalized systemic failures, go beyond mere chance occurrences and are ingrained deeply enough to compromise decision-making processes and erode trust.
Historical instances like the 1938 FD&C Act and the Generic Drug Scandals underscore how crisis-triggered reforms often fail to address the fundamental issues, perpetuating inefficiencies and hazards.
The narrative advocates a shift from reactive crisis management to proactive, adaptable systems prioritizing continuous enhancement. Key hurdles involve challenging outdated assumptions regarding bioavailability, inadequately funded research ventures, and the impact of vague language in regulatory frameworks.
The rise of large language models (LLMs) presents promising solutions, albeit with accompanying risks necessitating thorough validation and seamless integration.
Tackling these blind spots demands a holistic approach, embracing adaptive learning and a steadfast commitment to self-improvement. By nurturing curiosity, refining regulatory terminology, and judiciously harnessing new technologies, the pharmaceutical sector can progress towards better public health service delivery and ensure the safety, efficacy, and real-world impact of drug products.
Adventure Activities Final By H R Gohil Sir
Adventure Activities Final By H R Gohil SirGUJARATCOMMERCECOLLE
油
Adventure Activities Final By H R Gohil SirHow to use Init Hooks in Odoo 18 - Odoo 際際滷s
How to use Init Hooks in Odoo 18 - Odoo 際際滷sCeline George
油
In this slide, well discuss on how to use Init Hooks in Odoo 18. In Odoo, Init Hooks are essential functions specified as strings in the __init__ file of a module.APM People Interest Network Conference - Oliver Randall & David Bovis - Own Y...
APM People Interest Network Conference - Oliver Randall & David Bovis - Own Y...Association for Project Management
油
Kaun TALHA quiz Finals -- El Dorado 2025
Kaun TALHA quiz Finals -- El Dorado 2025Conquiztadors- the Quiz Society of Sri Venkateswara College
油
Troubleshooting Computing Problems
- 2. Six Steps of Troubleshooting Identify the Problem Establish Theory of Probably Cause Test Theory to Determine Cause Establish plan of action to resolve problem and implement solution Verify full system functionality Document finding, actions and outcomes
- 3. Open and Close Questions Closed Questions Yes/No Answers Open Questions Detailed Answers
- 4. Documentation Document everything fault reports, investigation plans, error logs, test logs Record steps taken Record actual solution accurately Tickets
- 5. Self-Evaluation Linear Top Down Bottom Up Top down emphasises complete understanding Bottom up emphasises early testing and coding Half Split (Divide and Conquer) Used by experienced technicians Educated guesses, the progression