A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...dheimann5
The IEEE is in the process of updating and adding significant content to its IEEE-730-2002 standard on Software Quality Assurance (SQA). The new version will coordinate with the four process areas and sixteen SQA tasks in the IEEE-12207-2008 standard “Systems and Software Engineering: Software Life Cycle Processes”, providing detailed elaborations for these areas and tasks.
The presentation provides a brief overview of these areas and tasks, discuss the difference between SQA and testing, and cover the annexes in IEEE 730 that provide industry-specific information as well as the relationships with software process approaches such as CMMI, Agile, SPICE, CSQE, PMBOK, and VSEs.
This lecture is about the detail definition of software quality and quality assurance. Provide details about software tesing and its types. Clear the basic concepts of software quality and software testing.
More Information:
https://flevy.com/browse/business-document/pdca-problem-solving-technique-and-tools-151
BENEFITS OF DOCUMENT
Learn how to apply the PDCA approach to solve problems and save money.
Learn how to apply the basic quality tools to identify and analyse problems.
Learn how to develop problem solving teams to sustain a continuous improvement culture.
DOCUMENT DESCRIPTION
In this training presentation, you will be able to teach employees on the structured Plan-Do-Check-Act (PDCA) approach to problem solving. Many world class companies such as Toyota uses the PDCA problem solving process for the relentless pursuit of continuous improvement. When combined with the basic quality tools, this approach identifies problems, analyzes root causes and generates solutions. Teach your staff to put effective solutions in place to prevent similar problems from recurring in the future. This methodology can be applied to both manufacturing and service organizations.
LEARNING OBJECTIVES:
1. Understand the principles and key concepts of problem solving
2. Learn how to apply the PDCA technique and basic quality tools to problem solving
3. Learn how to identify root causes and develop countermeasures
4. Learn how to prepare a problem solving storyboard
5. Understand the roles of problem solving team
6. Define the critical success factors for effective problem solving
CONTENTS:
1. Introduction to Problem Solving
2. Concept of Problem Solving Teams
3. Overview of Process Management
4. PDCA Problem Solving - The Step-by-step Approach
5. Basic Problem Solving Tools
6. Project Reporting Using A3 Storyboard
7. 10 Common Mistakes
8. Critical Success Factors
This training presentation can be used together with the 'PDCA Problem Solving Template' (sold separately).
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...dheimann5
The IEEE is in the process of updating and adding significant content to its IEEE-730-2002 standard on Software Quality Assurance (SQA). The new version will coordinate with the four process areas and sixteen SQA tasks in the IEEE-12207-2008 standard “Systems and Software Engineering: Software Life Cycle Processes”, providing detailed elaborations for these areas and tasks.
The presentation provides a brief overview of these areas and tasks, discuss the difference between SQA and testing, and cover the annexes in IEEE 730 that provide industry-specific information as well as the relationships with software process approaches such as CMMI, Agile, SPICE, CSQE, PMBOK, and VSEs.
This lecture is about the detail definition of software quality and quality assurance. Provide details about software tesing and its types. Clear the basic concepts of software quality and software testing.
More Information:
https://flevy.com/browse/business-document/pdca-problem-solving-technique-and-tools-151
BENEFITS OF DOCUMENT
Learn how to apply the PDCA approach to solve problems and save money.
Learn how to apply the basic quality tools to identify and analyse problems.
Learn how to develop problem solving teams to sustain a continuous improvement culture.
DOCUMENT DESCRIPTION
In this training presentation, you will be able to teach employees on the structured Plan-Do-Check-Act (PDCA) approach to problem solving. Many world class companies such as Toyota uses the PDCA problem solving process for the relentless pursuit of continuous improvement. When combined with the basic quality tools, this approach identifies problems, analyzes root causes and generates solutions. Teach your staff to put effective solutions in place to prevent similar problems from recurring in the future. This methodology can be applied to both manufacturing and service organizations.
LEARNING OBJECTIVES:
1. Understand the principles and key concepts of problem solving
2. Learn how to apply the PDCA technique and basic quality tools to problem solving
3. Learn how to identify root causes and develop countermeasures
4. Learn how to prepare a problem solving storyboard
5. Understand the roles of problem solving team
6. Define the critical success factors for effective problem solving
CONTENTS:
1. Introduction to Problem Solving
2. Concept of Problem Solving Teams
3. Overview of Process Management
4. PDCA Problem Solving - The Step-by-step Approach
5. Basic Problem Solving Tools
6. Project Reporting Using A3 Storyboard
7. 10 Common Mistakes
8. Critical Success Factors
This training presentation can be used together with the 'PDCA Problem Solving Template' (sold separately).
How many photo carousels have you built? Date pickers? Dynamic tables and charts? Wouldn't it be great if there was a way to make these custom elements encapsulated and reusable? Welcome to Web Components! The building blocks are well known: HTML templates, custom elements, HTML imports, and shadow DOM. It's fairly easy to build simple examples. But what happens when performance degrades? Join this discussion of the synchronous and asynchronous nature of web components, and how they can impact the rendering of the entire page.
SREcon 2016 Performance Checklists for SREsBrendan Gregg
Talk from SREcon2016 by Brendan Gregg. Video: https://www.usenix.org/conference/srecon16/program/presentation/gregg . "There's limited time for performance analysis in the emergency room. When there is a performance-related site outage, the SRE team must analyze and solve complex performance issues as quickly as possible, and under pressure. Many performance tools and techniques are designed for a different environment: an engineer analyzing their system over the course of hours or days, and given time to try dozens of tools: profilers, tracers, monitoring tools, benchmarks, as well as different tunings and configurations. But when Netflix is down, minutes matter, and there's little time for such traditional systems analysis. As with aviation emergencies, short checklists and quick procedures can be applied by the on-call SRE staff to help solve performance issues as quickly as possible.
In this talk, I'll cover a checklist for Linux performance analysis in 60 seconds, as well as other methodology-derived checklists and procedures for cloud computing, with examples of performance issues for context. Whether you are solving crises in the SRE war room, or just have limited time for performance engineering, these checklists and approaches should help you find some quick performance wins. Safe flying."
Building a Software Chain of Custody: A Guide for CTOs, CIOs, and Enterprise ...XebiaLabs
For most of us, compliance audits are painful processes that interfere with our ability to do our job – building and delivering software – and steal time and resources away from that next great innovation. Until now.
The XebiaLabs Software Chain of Custody provides everything you need to visualize, monitor, and prove the integrity of your software delivery pipelines on demand. Push the button, get the report. You’re done. No more audit hell.
Learn how a Software Chain of Custody helps:
DevOps teams focus on doing what they love, rather than wasting valuable time putting together audit reports
Executives gain full visibility into release pipelines so they can stop losing sleep over governance and security audits
InfoSec teams and auditors instantly get the reports they need so they can quickly approve releases
Learn how to establish a greater sense of confidence in your release cycle, along with the practices and processes to create a high-performing engineering culture within your team.
This webinar was held live on March 4th, 2021. Watch the on demand recording here: https://curiositysoftware.ie/resources/democratisation-testing-webinar/
Learn how Infuse, Kumoco and Curiosity enabled rigorous in-sprint test automation at a large telecommunications company. BAs, Testers and Developers at the telco now collaborate to build visual flows of the system logic in-sprint. The easy-to-maintain diagrams generate complete SIT and E2E tests for the latest business processes, rigorously testing before every rapid release.
To overcome siloes and overly-manual processes, Infuse, Kumoco and Curiosity built a “telecommunications-company-in-a-box”, a digital twin of the system under test. Artifacts created by BA’s were imported to build complete business flows, providing a single source of truth for the systems in scope. The flows were then used to generate rigorous tests in seconds, and were further used by developers and testers to build CI/CD assets. This generated a complete set of artifacts across the SDLC, while allowing every stakeholder to use their favourite tools.
Join Infuse, Kumoco and Curiosity live to see this cutting-edge approach to in-sprint design, development and testing in action. You will discover how:
1. Slow and siloed system design and test creation were replaced by test generation for useMango, with matching test cases generated in Jira.
2. Risk-based test generation identified exactly what to test in short sprints, overcoming the challenge of having more in a system than you could ever test in-sprint.
3. The rigorous automation is now maintained in-sprint, updating tests across tools as the business customize processes in BPMN-style diagrams.
4. The business know that their changes will be validated rigorously before each release, optimizing test generation for time and risk and defining reliably when testing is ‘done’.
This webinar was held live on March 4th, 2021. Watch the on demand recording here: https://curiositysoftware.ie/resources/democratisation-testing-webinar/
From Prototype to Production_ The Embedded Software Development Lifecycle.pdfEmblem Technologies
"Building Robust Communication Protocols for Embedded Systems" delves into the intricate process of designing and implementing reliable communication frameworks tailored to the unique constraints and requirements of embedded systems, ensuring seamless data exchange and system interoperability. This comprehensive guide explores strategies, best practices, and key considerations essential for engineers navigating the complexities of embedded systems development.
From Prototype to Production_ The Embedded Software Development Lifecycle.pdfEmblem Technologies
"Building Robust Communication Protocols for Embedded Systems" delves into the intricate process of designing and implementing reliable communication frameworks tailored to the unique constraints and requirements of embedded systems, ensuring seamless data exchange and system interoperability. This comprehensive guide explores strategies, best practices, and key considerations essential for engineers navigating the complexities of embedded systems development.
Primer on application_performance_testing_v0.2Trevor Warren
This presentation focuses on the basics of Performance Testing. It talks about the processes, challenges and activities involved with Performance Testing.
Simplify Salesforce Testing with AI-Driven Codeless ToolsSauce Labs
Testing Salesforce Apps presents numerous challenges for enterprise organizations. Teams have to navigate complex architecture, integration workflows, and continuous changes in the customized SFDC implementation, as well as a wide range of different applications hosted on Salesforce Cloud. If left unchecked, these challenges can hamper critical enterprise processes like the revenue-generating Quote to Cash process.
During this webinar, you will learn how to automate functional testing and thoroughly test both the UIs and the APIs in your Salesforce applications using AutonomIQ’s AI-driven codeless tool. We’ll discuss how Aryaka Networks, a global leader in WAN transformation solutions, uses AutonomIQ to autonomously test critical business processes like Quote to Cash in their customized Salesforce application, and we’ll show you how to streamline UI testing to improve test creation, execution, and maintenance, and easily add API testing to your strategy for better coverage.
Key Takeaways:
Simplify the creation of your test scripts using plain English statements and a codeless studio
Learn how to autonomously create UI and API tests for Salesforce and integrations with other applications
Ensure the health of your end-to-end SFDC applications for key business processes like quote to cash
Tektronix Technologies: Software Development System
Tektronix Technologies offers a robust software development system (SDS) catering to the diverse needs of modern developers. Their system provides a comprehensive set of tools and features to streamline the software development lifecycle,
2. About: me
last 8 years i have been working as performance test engineer with
different tools and enviroments.
Telefónica Digital 2
Product Development & Innovation
19. The Future
• Continuous Performance Integration
– Performance tests integrated in Jenkins
– Automation of the trend reports
– Real User Monitoring Real time feedback
21. Testing
Proactive Performance testing for each release. Load tests will discover the flaws and bottlenecks, the application or the system
Pruebas de Rendimiento
may have in production environment
22. Availability
Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es
High availability of the application and the system is the goal of a ready for service status. The application and the systems must be stable ,
La hipótesis de partida con más éxito.
efficient and dimensioned according to the usage.
23. Velocity
Not only the response time is important, an intelligent use of the resources is needed to grow in the future. Efficiency, understood as
capacity to dispose of the system resources to achive an objective, in our case response time and uptime
24. Scalability
Being able to grow depending on the necessities of the market, users and new technologies is one of the focus for a performance engineer
25. Scenarios
A performance test is easy. It is easy to design non realistic scenarios. It is easy to collect irrelevant data. Even with a good scenario and
Appropiate data, it is easy to use and incorrect statistic method to analysis the results.
- Alberto Savoia
26. PreProduction
One of the most important parts of a good performance test design is to have an appropiate load test environment, as similar as possible to
Production at all levels, networking, systems and application architecture.
27. Otro título
Monitoring
Escenarios
To know the production environment is key to take good decisions about how to design a performance test plan. Designing a plan according
To real traffic and usage of the platform is key in creating validation criteria
28. Performance Teams
Developers, DBA's, QA's, DevOps, product owners ... All the team is part of performance
29. Otro título
Tools
There are many tools available in the market for load testing and monitoring. An effort in evaluating these tools will benefit at long term the
Execution of the tests. However, the most important part is how the reports are generated and who is going to interpret them.
30. Otro título
Mas puntos
Real User Monitoring
Not only unique users or session times are important. How the users work with the application and the psicology of the them are key to
Understand the results and how it affects to business.
31. Best Practices
Keep it simple, use cache wisely, invest in testing and monitoring, create a culture of performance in all the organization
32. Tuning
Innovation
Techonology develops at high speed. To bring out the best of our product, business and techonology need to evolve by the hand. Investing in
Performance research is crucial to keep up with other internet competitors.
33.
34. Understand the Project Vision and Context
Project Vision
Project Context
Understand the system
Understand the Project Environment
Understand the Performance Build Schedule
Telefónica Digital 34
Product Development & Innovation
35. Identify Reasons for Testing Performance
Success Criteria
• Application performance requirements and goals
• Performance-related targets and thresholds
• Exit criteria (how to know when you are done)
• Key areas of investigation
• Key data to be collected
Telefónica Digital 35
Product Development & Innovation
36. Identify the Value Performance Testing Adds to
the Project
In general, the types of information that may be valuable to discuss with
the team when preparing a performance-testing strategy for a
performance build include:
› The reason for performance testing this delivery
› Prerequisites for strategy execution
› Tools and scripts required
› External resources required
› Risks to accomplishing the strategy
› Data of special interest
› Areas of concern
› Pass/fail criteria
› Completion criteria
› Planned variants on tests
› Load range
› Tasks to accomplish the strategy
Telefónica Digital 36
Product Development & Innovation
37. Configure the Test Environment
Set up isolated networking environment
Procure hardware as similar as possible to production
Coordinate bank of IP’s for IP spoofing
Monitoring tools and operating systems like production
Load generation tools or develop your own
Telefónica Digital 37
Product Development & Innovation
38. Identify and Coordinate Tasks
Work item execution method
Specifically what data will be collected
Specifically how that data will be collected
Who will assist, how, and when
Sequence of work items by priority
Telefónica Digital 38
Product Development & Innovation
39. Execute Task(s)
Keys to Conducting a Performance-Testing Task
• Analyze results immediately and revise the plan accordingly.
• Work closely with the team or sub-team that is most relevant to the task.
• Communicate frequently and openly across the team.
• Record results and significant findings.
• Record other data needed to repeat the test later.
• Revisit performance-testing priorities after no more than two days.
Telefónica Digital 39
Product Development & Innovation
40. Analyze Results and Report
pause periodically to consolidate results
conduct trend analysis
create stakeholder reports,
pair with developers, architects, and administrators to analyze results
Telefónica Digital 40
Product Development & Innovation